Operational Environments#
Overview#
This procedure is intended for users of the Rubin Observatory that are interested in interacting with the Observatory Control System. It contains basic information (with links and description) on how to connect to the observing interface tools at the summit and at the different test stands.
Each operational environment is composed of a nublado instance, an EFD instance (with Chronograf and other visualization tools) and LOVE interface.
Coordination on the use of each operational environment is managed through Slack channels.
Most components are deployed as docker containers, orchestrated via ArgoCD and Kubernetes. A small subset of components are deployed with docker-compose and, in some cases, deployment is still done directly on bare metal nodes manually.
Prerequisites#
You must be logged on the LSST-WAP, into the NOAO or summit VPN.
Post-Condition#
Successfully access nublado and other observing interface tools.
Ability to command components.
Procedure Steps#
In a browser open the links below under the heading corresponding to the operational environment you want to interact with.
For instance, open the nublado link in TTS to interact with the observatory control system in that operational environment.
Base Facility Test Stand (BTS)#
BTS is a simulation operational environment running at the base facility in La Serena. The main difference between the TTS and this operational environment is that some systems will run using hardware simulators.
Hardware simulators are, in general, higher fidelity than those of pure software available at TTS. For that, BTS will be used mostly for higher fidelity testing, development and debugging. It will also be particularly useful for testing lower-level hardware interfaces.
Nublado: https://base-lsp.lsst.codes/
Chronograf: https://base-lsp.lsst.codes/chronograf/
LOVE: N/A
Rancher: https://rancher.cp.lsst.org/
Kubernetes Cluster: kueyen
Slack: N/A
Alarm Slack: N/A
Tucson Test Stand (TTS)#
The TTS is currently being used as a staging platform to test new software versions and procedures prior to deployment at the summit. Systems that control hardware at the Summit run here in simulation mode. Once a deployment is tested here, the platform is made available for general users for training, testing and developing of control algorithm and procedures.
Nublado: https://tucson-teststand.lsst.codes/
Chronograf: https://tucson-teststand.lsst.codes/chronograph/
- LOVE
bare metal: http://love1.tu.lsst.org
kubernetes: http://love.tu.lsst.org
Rancher: https://rancher.tu.lsst.org/
Kubernetes Cluster: pillan
Slack: rubinobs-tucson-teststand
Alarm Slack: tucson-teststand-watcher
Summit#
Summit is our main production operational environment. Systems running here will be directly controlling hardware or communicating with components that control actual hardware.
Important
In the case of the Summit it is required to have personnel present at the site prior to any activity that involves moving hardware. These must be planned activities and require an accompanying summit activity project Jira ticket organized by appropriate personnel.
Nublado: https://summit-lsp.lsst.codes/
Chronograf: https://summit-lsp.lsst.codes/chronograf/
Rancher: https://rancher.cp.lsst.org/
Kubernetes Cluster: yagan
Slack: summit-announce
Alarm Slack: summit-watcher
Troubleshooting#
If you can not open the links to the operational environment you intend to work with, make sure you are connected to the LSST-WAP wifi network in one of the designed areas (Tucson, La Serena or Summit facilities) or that you are connected to the NOAO VPN.
If problems persist, you can ask for help in the designated Slack channels or in the com-square-support channel.
Contact Personnel#
This procedure was last modified Apr 24, 2024.
This procedure was written by Tiago Ribeiro. The following are contributors: Michael Reuter, Patrick Ingraham.