Cylc UI Server
This project contains the Cylc UI Server which serves the Cylc UI
and communicates with running Cylc Schedulers. It also bundles the GUI.
Cylc Website |
Contributing |
Developing |
Forum
Introduction
The functionality in this repository is required to run the Cylc web user
interface.
This repository provides the following components of the Cylc system.
-
The UI
This is the Cylc web app that provides control and monitoring functionalities
for Cylc workflows.
Note
The UI is developed in a separate repository https://github.com/cylc/cylc-ui
-
The UI Server
This is a web server which serves the Cylc web UI. It connects to running
workflows and workflow databases to provide the information the UI displays.
It is a Jupyter Server.
-
The Hub
In multi-user setups this launches UI Servers, provides a proxy for running
server and handles authentication. It is a
JupyterHub server.
Installation
For more information on the Cylc components and full-stack Cylc installations
see the
Cylc documentation.
For Single-User Setups
Install:
Conda/Mamba (preferred) | Pip |
---|
conda install cylc-uiserver-base | pip install cylc-uiserver |
Then start your server:
cylc gui
For Multi-User Setups
Install:
Conda/Mamba (preferred) | Pip + Npm |
---|
conda install cylc-uiserver | pip install cylc-uiserver[hub] |
| npm install configurable-http-proxy |
Then start your hub:
cylc hub
List Of Packages
There are a few different packages to suit different needs.
Tool | Package | Description | Cylc UI Server | Jupyter Hub | Configurable HTTP Proxy |
---|
pip | cylc-uiserver | Single user | :heavy_check_mark: | :x: | :x: |
conda | cylc-uiserver-base | Single user | :heavy_check_mark: | :x: | :x: |
conda | cylc-uiserver-hub-base | Multi user (without proxy) | :heavy_check_mark: | :heavy_check_mark: | :x: |
pip | cylc-uiserver[hub] | Multi user (without proxy) | :heavy_check_mark: | :heavy_check_mark: | :x: |
conda | cylc-uiserver | Multi user | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
The Configurable HTTP Proxy package (Node JS) provides the reverse proxy
that Jupyter Hub requires to collate user's servers behind a single URL. It can
be installed via conda install configurable-http-proxy
but is not available
via pip (because it requires Node JS)
Other proxies including the
Traefik Proxy (Python) can also
fulfil this purpose, see
list of Jupyter Hub proxies.
Installing Jupyter Hub Separately
The easiest way to get going with Cylc and Jupyter Hub is to install and deploy
them together and launch Jupyter Hub via the cylc hub
command.
conda install cylc-uiserver
cylc hub
However, you can also deploy Jupyter Hub separately from the servers it
deploys (e.g. Jupyter Lab or Cylc UI Server) and launch it via the jupyterhub
command.
If you are deploying Jupyter Hub separately from Cylc UI Server, these
configurations may be relevant:
- The Jupyter Hub
spawner.cmd
determines the command that Jupyter Hub runs in order to start a user's
server. You may wish to use a wrapper script to activate the required environment. - The Jupyter Server
ServerApp.jpserver_extensions
configuration determines what Jupyter Server Extensions (e.g. Jupyter Lab or
Cylc UI Server) are activated when Jupyter Server starts.
The default behaviour is to activate any installed extensions, however, if
overridden, you may need to explicitly list cylc-uiserver here. - The Cylc
jupyter_config.py
file contains the default Cylc configuration. This applies to hubs started by
cylc hub
command but not by the jupyterhub
command. You may want to
include some of the configurations from this file in your Jupyter Hub
configuration.
Running
The Cylc UIServer is a
Jupyter Server
extension (like JupyterLab).
For Single-User Setups
Run as a standalone server using a URL token for authentication:
$ cylc gui
$ jupyter cylc
Note
By default, authentication is provided by the URL token. Alternatively, a
password can be configured (see Jupyter Server docs).
There is no per-user authorisation, so anyone who has the URL token has full
access to the server.
For Multi-User Setups
Run a central JupyterHub server
under a user account with the privileges required to spawn cylc
processes as
other users.
$ cylc hub
Users then authenticate with the hub which launches and manages their UI Server.
Configuring
Hub
The Cylc Hub will load the following files in order:
-
System Config
These are the Cylc defaults which are hardcoded within the repository.
(<python-installation>/cylc/uiserver/jupyter_config.py
)
-
Site Config
This file configures the Hub/UIS for all users. The default path can be
changed by the CYLC_SITE_CONF_PATH
environment variable.
(/etc/cylc/uiserver/jupyter_config.py
)
-
User Config
This file
(~/.cylc/uiserver/jupyter_config.py
)
Alternatively a single config file can be provided on the command line.
cylc hub --config
Warning
If specifying a config file on the command line, the system config containing
the hardcoded Cylc default will not be loaded.
Note
The hub can also be run using the jupyterhub
command, however, you
must source the configuration files manually on the command line.
See the JupyterHub documentation for details on configuration options.
UI Server
See the Cylc documentation
for all Cylc-specific configuration options.
The Cylc UI Server is a
Jupyter Server extension.
Jupyter Server can run multiple extensions. To control the extensions that
are run use the ServerApp.jpserver_extensions
configuration, see the
Jupyter Server configuration documentation.
By default the Cylc part of the UI Server log is written to
~/.cylc/uiserver/uiserver.log
.
UI
The UI can be configured via the "Settings" option in the Dashboard.
Currently these configurations are stored in the web browser so won't travel
around a network and might not persist.
Developing
Contributions welcome:
-
Install from source into your Python environment:
pip install -e .[all]
Note
If you want to run with a development copy of Cylc Flow you must install
it first else pip
will download the latest version from PyPi.
-
For UI development follow the developer instructions for the
cylc-ui project, then
set the following configuration so Cylc uses your UI build
(rather than the default bundled UI build):
import os
c.CylcUIServer.ui_build_dir = os.path.expanduser('~/cylc-ui/dist')
Note about testing: unlike cylc-flow, cylc-uiserver uses the
pytest-tornasync plugin
instead of pytest-asyncio.
This means you should not decorate async test functions with
@pytest.mark.asyncio
.
Copyright and Terms of Use
Copyright (C) 2019-2024 NIWA & British Crown (Met Office) & Contributors.
Cylc is free software: you can redistribute it and/or modify it under the terms
of the GNU General Public License as published by the Free Software Foundation,
either version 3 of the License, or (at your option) any later version.
Cylc is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with
Cylc. If not, see GNU licenses.