1. 06 Feb, 2019 1 commit
  2. 21 Jan, 2019 2 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] Aggregative Downstream API integration · a501c976
      Sridutt Bhalachandra authored
      Adds support for aggregation of phase context information for an
      application. The damper value (in nanoseconds in the manifest file)
      decides the minimum phase length for which the phase context
      information is sent to the NRM (implemented in 'libnrm' repo
      [See Issue 2]). This will limit the number of msgs sent to the NRM.
      
      See Issue #13
      a501c976
  3. 04 Jan, 2019 1 commit
  4. 21 Dec, 2018 1 commit
    • 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
  5. 14 Aug, 2018 1 commit
  6. 10 Aug, 2018 1 commit
    • Sridutt Bhalachandra's avatar
      [Feature] NRM response to phase_context event · b07a4ff6
      Sridutt Bhalachandra authored
      Made changes in NRM to respond to phase_context event from [previously
      called power_policy event (874a6a4d)] from the application. The NRM can now
      store the informaton received on the event and call DDCM power policy through
      interfaces developed (Issue #11) in the control loop
      
      See Issue #10
      b07a4ff6
  7. 20 Dec, 2017 1 commit
    • Swann Perarnau's avatar
      [feature] Add actuator to the controller logic · cbbf2354
      Swann Perarnau authored
      This patch introduce one more level of abstraction to the controller:
      an actuator. Actuators will act as the middleman between specific
      managers and the controller, while providing enough info to implement
      actual models on top.
      
      For now, we only have the application threads actuator.
      cbbf2354
  8. 19 Dec, 2017 1 commit
    • Swann Perarnau's avatar
      [feature] Implement Application Manager · f43a38d3
      Swann Perarnau authored
      This patch moves the tracking of applications clients of the downstream
      API into a ApplicationManager, that is able to track progress and thread
      management.
      
      This change is necessary in the long term to build a comprehensive
      downstream API and centralize the management of application tracking.
      
      Note that this tracking is currently independent of the container and
      pid tracking, and that might be a problem in the long term.
      f43a38d3