Cluster Component: Launcher

The launcher component launches sessions. Sessions connect back to the launcher. The launcher component manages connected sessions and updates the state of the session.

The webserver or client connects directly to the launcher in order to connect to a running session via the FastX protocol.

FastX Sessions

By default, a FastX session will run on the same system as the launcher. Administrators can add a job scheduling script to the FastX settings to allow for alternate methods of starting sessions as well as starting sessions on systems where the launcher is not running.

Container Support

FastX was designed specifically to support containerization. Containers can be located on the launcher host, or distributed across a cluster and communicate remotely to the launcher component. FastX officially supports containers via Docker, and Kubernetes.