jumonc 0.7.1

Jülich Monitoring and Control

Installation | Execution | Authorization | Encryption | Further documentation | Getting help |

JuMonC

JuMonC stands for "Jülich monitoring and control" and allows easier access to monitor running simulations and provides data using a REST-API.

---

Installation

JuMonC can be installed using pip:

pip install JuMonC

This also creates an entry point, allowing to start JuMonC with just the command JuMonC

Runtime dependencies

• python3
• mpi4py
• flask
• flask-login
• Flask-SQLAlchemy

Optional runtime dependencies

• python-papi
• pynvml
• psutil
• pyopenssl

Extras

JuMonC allows installation with extras for the optional dependencies. Some of them need installed software on the system, that is not part of the PyPi installation, so that still has to be provided. It still makes the setup easier. Currently the following options for the extras are avaiable:

• PAPI: For use of PAPI
• NVLM: For use of NVML
• psutil: For use of psutil
• SSL: Only needed when using adhoc certificates
• Full: All of the above dependencies provided at once
• Devel: Includes the ful ldependencies and installs all tools neeeded for CI as well, to allow local tests

These extras can be used like this:

pip install JuMonC[psutil,SSL]

Execution

JuMonC needs to be started parallel to your running simulation and needs one mpi process on each node your simulation is using. The actual REST-API will only be avaiable on node 0 and then communicate internaly using mpi.

It can be started by running srun -n <#nodes> --ntasks-per-node=1 JuMonC &

By default, this will start the REST-API on port 12121 on rank 0 of this allocation. The port can be changed by providing -p=<port>. Depending on the firewall rules of the system you are using, it might be necessary to use a ssh-tunnel to forward this endpoint of the API to somewhere else where you can access it.

Authorization

Security is always a concern, and to block unauthorized access of this API there is a scope based token authorization included. This means each action requires authorization, with different tokens having a different scope of allowed actions. The tokens included by default and printed to stdout on startup are hierarchical, therefore every token includes the authorized functions of all lower tokens:

1. see_links
2. retrieve_data
3. compute_data
4. retrieve_simulation_data
5. compute_simulation_data
6. full

There are two options to prove your authorization, either cookie based by providing the token once in the login function (e.g. /login?token=12345678) or providing it by every API call as an additional parameter (e.g. /v1/network?token=12345678).

Encryption

JuMonC offers two different modes to use encryption. One uses adhoc generated certificates, the other one allows you to supply your own certificates.

1. adhoc certificates:

• depending on the used software to acces JuMonC you will get a warning or by default (e.g. Mozilla firefox) a complete blocking of the connection (e.g. curl) that you need to accept or override. This is due to the certificates not having any chain of trust to already trusted certificates.
• you need to have pyopenssl avaiable to use adhoc certificates
• used with --SSL_ENABLED

2. Providing certificates

• You can generate your own self-singed certificates using for example openssl req -x509 -newkey rsa:4096 -nodes -out cert.pem -keyout key.pem -days 365
  • This leads to the same warings as the adhoc certificates, but allows a manual control of the signed certificate
• using this methods needs three arguments, one for enabeling SSL --SSL_ENABLED and one each for the certificate and the key --SSL_CERT=/path/to/cert.pem --SSL_KEY=/path/to/key.pem. The paths can either be absolute paths or relatic paths from the current working directory.

Further documentation

• REST-API
• Possible cmd arguments or using the -h flag
• JuMonC_overview

Getting help

Open an issue