1. 04 Jan, 2019 1 commit
  2. 21 Dec, 2018 2 commits
    • Swann Perarnau's avatar
      [refactor] use downstream messaging layer · 75df2004
      Swann Perarnau authored
      Replace the downstream API handling by the new messaging layer. Not that
      we don't have a clean way to deal with dynamic concurrency control using
      this API, so we disable the handling of it for now.
      75df2004
    • Swann Perarnau's avatar
      [feature] add downstream rpc to messaging layer · 0bae924d
      Swann Perarnau authored
      Add downstream RPC client/server classes that are the same as the
      upstream ones.
      
      This is part of a series of changes to downstream to allow for more
      reliable communications between the daemon and applications. At this
      time, the daemon never replies, so the RPC_REQ is basically used as a
      way to publish events to the daemon.
      0bae924d
  3. 10 Dec, 2018 1 commit
    • Valentin Reis's avatar
      Small work session with Swann: · 5b550e0b
      Valentin Reis authored
      - added correct SIGINT/process ending handling to cmd
      - fixed  kill/list containers
      - added ZMQ_LINGER 0 to the socket options.
      5b550e0b
  4. 28 Nov, 2018 3 commits
    • Swann Perarnau's avatar
      [refactor] move container start/exit to up_pub · f81b95e0
      Swann Perarnau authored
      Move the container start/exit events to the upstream pub/sub event
      stream. As these are more of a global event now that we support multiple
      commands in the same container, it makes sense to move them to the more
      general event stream.
      
      This patch also remove the code in cmd waiting for container start or
      exit, making (temporarily) the cmd unable to report power metrics. We
      will fix that in a later commit.
      
      This patch fixes complicated issues we had with how a job running
      multiple commands in the container might not all wait for the end of the
      container: now none of them do.
      f81b95e0
    • Swann Perarnau's avatar
      [feature] add messaging class for pub client · c4e50535
      Swann Perarnau authored
      Add a upstream pub client, to be able to listen to messages coming from
      the daemon on the upstream pub/sub channel.
      
      Doesn't support any fancy filter, as that's not used by the daemon so
      far.
      c4e50535
    • Swann Perarnau's avatar
      [refactor/fix] always send process events for run · 6e0c1e7a
      Swann Perarnau authored
      Current code sends start/exit events when a container is created and
      process_start/process_exit when its already there. Instead, have the
      container start/exit only care about container stuff, and always sends
      the process start/exit events around. That makes the cmd run fsm easier
      to work out.
      
      Changes the message format a tiny bit.
      Fixes some missing stdout/stderr issues we had before.
      6e0c1e7a
  5. 21 Oct, 2018 2 commits
    • Swann Perarnau's avatar
      [refactor] replace upstream comms with msg layer · 0b0ab966
      Swann Perarnau authored
      Replace the fragile upstream communications with the new messaging
      layer, improving the stability and performance of this API.
      
      NOTE: this breaks previous clients
      NOTE: this patch is missing client tracking, to handle children signals.
      0b0ab966
    • Swann Perarnau's avatar
      [feature] add messaging layer for upstream API · c29ed7ea
      Swann Perarnau authored
      Abstracts away the exact wire format and client/server details, while
      changing the RPC side to work over ROUTER/DEALER sockets, as to avoid
      the lost messages issues we've been having with PUB/SUB for RPC.
      c29ed7ea