paraita/ns-watcher repository overview

⁠ns-watcher

This project allows to add nodesources to a ProActive Resource Manager by adding well-formed yml files into a specified folder. It's purpose is to ease frequent adds and removals of node sources and is NOT ready for a production use.

⁠Requirements

For this, the project assumes the following:

• we have credentials for the RM
• the proactive-client script is reachable
• the scheduler REST API is reachable

There's a requirements.txt file for the dependencies.

⁠Configuration

This project needs a ns-watcher.conf in your home directory. This file can be overriden if specified on the command line. See the ns-watcher.template.conf file. At the moment, only the StaticPolicy is supported.

Supported infrastructures:

• AzureInfrastructure
• LocalInfrastructure
• AWSEC2Infrastructure
• CLIInfrastructure
• AutoUpdateInfrastructure
• OpenstackInfrastructure
• DefaultInfrastructureManager
• SSHInfrastructure
• VMWareInfrastructure
• AzureVMScaleSetInfrastructure
• GenericBatchJobInfrastructure
• NativeSchedulerInfrastructure
• SSHInfrastructureV2
• LSFInfrastructure
• PBSInfrastructure

Supported policies:

• SimpleJMXNodeSourcePolicy
• TimeSlotPolicy
• StaticPolicy
• CronLoadBasedPolicy
• SchedulerLoadingPolicy
• ReleaseResourcesWhenSchedulerIdle
• NativeSchedulerPolicy
• CronSlotLoadBasedPolicy
• RestartDownNodesPolicy
• CronPolicy

⁠Usage

Not ready to be run as a regular bin at the moment.

To test run your dev copy, run the following command instead:

python -m nswatcher.main

An NS declaration file should have the following format:

infrastructure:
  type: "DefaultInfrastructureManager"
policy:
  type: "StaticPolicy"
  userAccessType: "ALL"
  providerAccessType: "ME"

Adding such a file to the watch-folder will create the node source in the RM. Removing that file will also remove the node source from the RM.

Run a python -m nswatcher.main -v to try.

⁠Docker

A dockerfile is provided to build an image:

docker build -t ns-watcher:dev .

The image embed the ns-watcher.template.conf file so you'll have to map those accordingly to your environment. An image is already pushed to the docker hub. Here's an example of how to run an ns-watcher container:

docker run --name ns-watcher --rm -it \
  -v /home/paraita/.ns-watcher.conf:/home/.ns-watcher.conf \
  -v /home/paraita/proactive:/root/proactive \
  -v /home/paraita/ns-available:/root/ns-enabled \
  paraita/ns-watcher:dev