1. 22 May, 2019 1 commit
  2. 03 May, 2019 3 commits
    • Swann Perarnau's avatar
      [refactor] use singularity instances · b3450523
      Swann Perarnau authored
      Instances in singularity are basically the same as being able to create
      an empty container and then run something in it, so we can have the same
      thing as with nodeos.
      
      One main issue with the code as is: we should probably refactor the
      container_manager code to modify the manifest on the fly according to
      the options listed in it. It would make it easy to pass along stuff like
      PWD, necessary binds and so on.
      b3450523
    • Swann Perarnau's avatar
      [fix] export downstream_event_uri in container · 0ad81e0b
      Swann Perarnau authored
      If monitoring is active, make sure to export the
      ARGO_NRM_DOWNSTREAM_EVENT_URI variable required by libnrm.
      
      Fix #49.
      0ad81e0b
    • Florence Monna's avatar
      [feature] add nrmd-wide support for singularity · e0d0abb4
      Florence Monna authored
      The daemon can be configured to launch singularity containers. In such
      case, the manifest must contain an image section.
      
      Note that this doesn't support any resource management with singularity,
      since that stuff is only available as root. We will add a second
      container runtime option to support it later.
      e0d0abb4
  3. 24 Apr, 2019 1 commit
  4. 26 Feb, 2019 1 commit
  5. 15 Feb, 2019 1 commit
  6. 08 Feb, 2019 1 commit
    • Swann Perarnau's avatar
      [fix] remove unused pipe in subprocess · 8516435a
      Swann Perarnau authored
      For some reason this seems to be triggering a leak of a open file
      descriptor, even though it should be garbage collected.
      
      As for why it's there...well there was a time when I had hoped of
      implementing support for stdin.
      8516435a
  7. 06 Feb, 2019 5 commits
    • Swann Perarnau's avatar
      [feature] add a dummy container runtime · 8c547615
      Swann Perarnau authored
      Add a container runtime that doesn't create containers, but can still
      launch commands.
      
      That should make it possible, once we figure out how to change it in the
      configuration, to actually run the NRM without a setuid binary.
      8c547615
    • Swann Perarnau's avatar
      [refactor] add an abstraction for container runtimes · c8ca4fa5
      Swann Perarnau authored
      Extract the container runtime interface from the container manager, and
      use a hierarchy of classes to enforce a runtime interface that makes
      sense.
      
      This will allow us to create alternative runtime implementations without
      major changes to the container manager code.
      c8ca4fa5
    • Swann Perarnau's avatar
      [log] adding binding output to create log · 1fa07af3
      Swann Perarnau authored
      Just to make it easy to debug binding issues.
      1fa07af3
    • Swann Perarnau's avatar
      [fix] restore the use of resources tuple · dca6debb
      Swann Perarnau authored
      !27 replaced the resource field of the `container` named tuple by a
      dictionary. Restore the old type, a `resources` named tuple and make
      sure to propagate this across all the code.
      dca6debb
    • Swann Perarnau's avatar
      [refactor] extract out basic container management · eb7c6380
      Swann Perarnau authored
      Refactor the container creation code to isolate the building/retrieving
      of a container namedtuple out of the core container creation code.
      
      This simplifies quite a bit the different branches of this code, and
      makes the core create method almost entirely dedicated to just launching
      a command.
      eb7c6380
  8. 05 Feb, 2019 4 commits
  9. 04 Feb, 2019 1 commit
  10. 21 Jan, 2019 3 commits
    • Sridutt Bhalachandra's avatar
      [fix] Aggregative downstream & new msg layer · f3c53106
      Sridutt Bhalachandra authored
      Made necesseary fixes required to make the aggregative downstream api
      integration to work with the new downstream messaging layer.
      
      Also,fixed the case where daemon crashed when an application message
      (from libnrm using pmpi) was received after container was killed
      
      run_policy on all containers removed as the controller no longer has
      application manager info
      
      Any other refactoring and fixes required (check merge request
      discussion)
      
      See Issues #13, #20 and Merge !41
      f3c53106
    • Sridutt Bhalachandra's avatar
      [feature] Support for Process/Task pinning · 402a2524
      Sridutt Bhalachandra authored
      Added support for pinning process/task to a core. This is important for
      allowing the use of power policies that use contextual information from an
      application phase and use it for computing frequency levels for the next phase.
      In absence of process/task pinning, the contextual information obtained does
      not serve any value as it is not representative of application phase behavior
      on a core as the processes and task can migrate during the next phase.
      
      See Issue #20
      402a2524
    • Sridutt Bhalachandra's avatar
      [fix] Multi-node support and msg layer interaction · 33316192
      Sridutt Bhalachandra authored
      Fixed the interaction of the multi-node support feature (#17) with the new
      messaging layer feature. Also, added any other fixes required to make the
      libnrm work with the Aggregative downstream API
      33316192
  11. 18 Dec, 2018 1 commit
  12. 12 Dec, 2018 2 commits
    • Valentin Reis's avatar
      [fix] Fixes the process kill call. · ec503ffa
      Valentin Reis authored
      Fixing a bug introduced by the 'progress-report' branch in a recent
      previous commit. The process object is the result of a tornado spawn, so
      the call has to be slightly different than what was there.
      ec503ffa
    • Valentin Reis's avatar
      [Feature] Adds configuration management and environment variables · 25443c64
      Valentin Reis authored
      This commit adds a command-line interface to `daemon`:
      ```
      usage: daemon [-h] [-c FILE] [-d] [--nrm_log NRM_LOG] [--hwloc HWLOC]
                    [--argo_nodeos_config ARGO_NODEOS_CONFIG] [--perf PERF]
                    [--argo_perf_wrapper ARGO_PERF_WRAPPER]
      
      optional arguments:
        -h, --help            show this help message and exit
        -c FILE, --configuration FILE
                              Specify a config json-formatted config file to
                              override any of the available CLI options. If an
                              option is actually provided on the command-line, it
                              overrides its corresponding value from the
                              configuration file.
        -d, --print_defaults  Print the default configuration file.
        --nrm_log NRM_LOG     Main log file. Override default with the NRM_LOG.
                              environment variable
        --hwloc HWLOC         Path to the hwloc to use. This path can be relative
                              and makes uses of the $PATH if necessary. Override
                              default with the HWLOC environment variable.
        --argo_nodeos_config ARGO_NODEOS_CONFIG
                              Path to the argo_nodeos_config to use. This path can
                              be relative and makes uses of the $PATH if necessary.
                              Override default with the ARGO_NODEOS_CONFIG
                              environment variable.
        --perf PERF           Path to the linux perf tool to use. This path can be
                              relative and makes uses of the $PATH if necessary.
                              Override default with the PERF environment variable.
        --argo_perf_wrapper ARGO_PERF_WRAPPER
                              Path to the linux perf tool to use. This path can be
                              relative and makes uses of the $PATH if necessary.
                              Override default with the PERFWRAPPER environment
                              variable.
      ```
      25443c64
  13. 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
  14. 21 Oct, 2018 1 commit
    • 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
  15. 17 Oct, 2018 1 commit
    • Sridutt Bhalachandra's avatar
      [Feature] Multi- node and process support · 5a41baba
      Sridutt Bhalachandra authored
      Added multi- node and process support that will allow launching of
      multiple processes within a container. This is important for enabling
      use of NRM with MPI applications with multiple processes in a container
      and thus enabling multi-node executions
      
      See Issue #17
      5a41baba
  16. 15 Aug, 2018 1 commit
  17. 14 Aug, 2018 1 commit
  18. 10 Aug, 2018 3 commits
  19. 17 Jul, 2018 1 commit
  20. 21 Dec, 2017 1 commit
  21. 19 Dec, 2017 3 commits
  22. 15 Dec, 2017 1 commit
    • Swann Perarnau's avatar
      [refactor] Only track container inside the CM · f2bc8b80
      Swann Perarnau authored
      The daemon code was maintaining its own container tracker using pids,
      instead of using the one in the container manager. This patch removes
      this additional tracking, and let the daemon side deal with an actual
      namedtuple.
      f2bc8b80
  23. 14 Dec, 2017 2 commits
    • Swann Perarnau's avatar
      [refactor] Fix container namedtuple · 9afe59c7
      Swann Perarnau authored
      This patch propagates the process object into the container namedtuple,
      fix a couple of bad function calls and adapt the run command handler to
      use that process object instead of just the pid of it.
      9afe59c7
    • Swann Perarnau's avatar
      [feature] Use argo_nodeos_config --exec · edeb413b
      Swann Perarnau authored
      Use the new argo_nodeos_config --exec feature in development.
      Allow us to delegate fork+attach+exec to argo_nodeos_config, and
      simplifying the create command as a result.
      
      We use tornado.process to wrap this command, as we want to able to
      stream stdout/stderr in the future.
      
      This patch also misuse, the 'pid' field of the container namedtuple to
      save the tornado.process.Subprocess object itself, so some functions
      need to be adapted.
      edeb413b