[Removing old code] removing old downstream API c code.

See merge request !31

[Fix] Handle container with no power profiling

See merge request !29

Handles container with no power profiling enabled in the manifest file.
In such cases the 'exit' response on process termination would generate
TypeError.

Improve Messaging layer

See merge request !28

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.

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.

[Feature] Multi- node and process support

Closes #17

See merge request !27

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

[fix] Lock with Pipenv all packages

See merge request !25

Some packages were being pulled into the virtual environment through
setup.py. It just happens that the new versions of pyzmq and tornado
don't really play nice with the current daemon code. Mostly because of a
"better" ioloop hijacking mecanism, that doesn't work for us.

This patch moves the install requirements of the setup.py to Pipfile,
and lock them to a working version.

Note: the code still currently triggers #14.

Add application level power profiling support

Closes #12

See merge request !24

Added power profile data to the exit event response at the end of
application run. The profile data is generated using functions from
`SensorManager` and is obtained using the sensor update in `Daemon`

See Issue #12

Made changes in `SensorManager` to allow calculation of the difference in measured
(stored) values using `rapl_reader` functions

See Issue #12

Added profiling parameter to manifest file that can be used to specify
if power profile is required for a container/application. Also, changed
namedtuple "Container" key from "powerpolicy" to "power" and made
changes to reflect this

See Issue #12

[CI] ensure py.test is ran on runner with rapl

See merge request !22

Since our tests include checking that coolr can access the rapl
interface, we should ensure that only runners having rapl will test the
code.

Resolve "Integration of power policy in to NRM"

Closes #10

See merge request !20

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

Fixed the C downstream_api messages sent by the application to NRM to be more
generic. These messages can be used to invoke power or any other policies
relying on contextual information from an application phase

See Issue #10

Added initialization of power policy using the manifest file and fixed
appropriate TODOs in `PowerPolicyManager` (PPM) Class using container
information (except adding new power policies). Also, fixed PPM to use None
instead of NONE

See Issue #10

The container creation information (resources and powerpolicy) added to
`ContainerManager` class can be used to intiliaze power policy parameters
in the present and more in the future

See Issue #10

Added damper and slowdown parameters to manifest file that can be used to
initiliaze power policy parameters

See Issue #10

Pass environment explicitly

See merge request !21

Kamil Iskra authored Aug 08, 2018 and Swann Perarnau committed Aug 09, 2018

When invoking 'argo_nodeos_config run', we were passing the job
environment implicitly.  This wasn't very clean and was also causing
problems with variables such as LD_PRELOAD, which were being filtered
out because argo_nodeos_config is suid root.

[CI] Remove CI for work-in-progress refs

See merge request !19

No need to trigger CI for things that are not ready.

Merge Power policy interface

Closes #11

See merge request !18

The Power Policy Manager will allow invocation of all power policies by the NRM
See Issue #11

DDCM based power policy is aimed to mitigate workload imbalance in parallel
applications that use barrier synchronizations (E.g. MPI). It reduces the duty
cycle of CPUs not on the critical path of execution thereby reducing energy
with little or no adverse impact on performance.

See Issue #11

Added Duty Cycle module to set, reset and check Duty Cycle of a CPU. This
module makes use of the MSR module

See Issue #11

Added Model Specific Register (MSR) module to allow access to MSRs. This module
provides the interfaces to read and write msr through msr_safe kernel module.

See Issue #11

On enabling the powepolicy manifest option and setting the policy parameter to
any valid value (except "NONE") the application library providing contextual
information is loaded using LD_PRELOAD

See issue #10

Allow applications to transmit context information to NRM (daemon)

See merge request !17