Production HTTP Server

This sections explains how to setup production HTTP with Slurm-web. Multiple HTTP servers are supported:

For simplicity reason and focus on Slurm-web specifics, this documentation provides configuration snippets to setup HTTP servers with insecure HTTP protocol without SSL/TLS. Of course, you MUST setup HTTPS with SSL/TLS on your production HTTP server to protect sensible data (passwords, confidential Slurm information, etc).

There are plenty of methods to setup HTTPS with SSL/TLS certificates, it mostly depends on your network environment (ex: Let’s Encrypt, Internet trusted CA, entreprise CA, …), so it is not covered in this documentation. Please refer to official HTTP servers documentation for more help.

All these examples propose to launch Slurm-web gateway and agent with uWSGI because it is stable, versatible with good performances. There are alternatives though like Gunicorn or mod_wsgi. While documentation is not provided, Slurm-web should be compatible with these alternatives.

In this documentation, gateway and agent are installed on the same host, in mono-cluster mode. However, Slurm-web supports multi-clusters mode with one central gateway and multiple agents. It is just a matter of:

  • Deploying a production HTTP server with only the agent component on all clusters,

  • Deploying one production HTTP server with only the gateway component on central server,

  • Settings the agents URL in gateway configuration file.