Base Test Stand¶

This section contains site specific variations for the Base test stand.

Resources¶

LOVE: https://base-lsp.lsst.codes/love
Argo CD: https://base-lsp.lsst.codes/argo-cd
Chronograf: https://base-lsp.lsst.codes/chronograf
Nublado: https://base-lsp.lsst.codes/
Rancher: https://rancher.ls.lsst.org
Slack: #base-teststand

Update Configuration¶

Configurations for the different applications deployed to BTS can be found in the Phalanx repo (lsst-sqre/phalanx).

LOVE Summary View¶

The overall system summary state view is called SummaryState.

Interacting with Kubernetes¶

Commands can be executed from your own machine with kubectl and the manke.yaml kubeconfig file. You can obtain the kubeconfig file from https://rancher.ls.lsst.org. If you don’t have access, file a Jira ticket with IT. Once you’re able to log into Rancher:

Select the manke cluster.
Click the Kubeconfig File button in top-right.
Near bottom of dialog, click the download link.
Save the config file under your local .kube directory as manke.yaml

Point to the required cluster by doing:

export KUBECONFIG=~/.kube/manke.yaml
kubectl config use-context manke

Ensure you are pointing to the right cluster by doing:
```
kubectl config current-context
```

Bare Metal Machines¶

ATCamera (Tony Johnson): auxtel-mcm.ls.lsst.org
MTCamera (Tony Johnson): lsstcam-mcm.ls.lsst.org

Shutdown Camera Services¶

Shutdown ATCamera OCS Bridge From auxtel-mcm.ls.lsst.org run:
```
sudo systemctl stop ats-ocs-bridge.service
```
Shutdown MTCamera OCS Bridge From lsstcam-mcm.ls.lsst.org run:
```
sudo systemctl stop lsstcam-ocs-bridge.service
```

Startup Camera Services¶

Startup ATCamera OCS Bridge From auxtel-mcm.ls.lsst.org run:
```
sudo systemctl start ats-ocs-bridge.service
```
Startup MTCamera OCS Bridge From lsstcam-mcm.ls.lsst.org run:
```
sudo systemctl start lsstcam-ocs-bridge.service
```

Ensure bridge services are running using:

sudo systemctl status <camera-name>-ocs-bridge.service

Transition to OFFLINE_AVAILABLE:

ccs-shell
ccs> set target <camera-name>-ocs-bridge
ccs> setAvailable --withLock
ccs> exit

Enabled CSCs¶

If proceeding with integration testing, the CSCs will be brought to ENABLED state as part of that process. All of the startup processes may be necessary for recovering the BTS from any maintenance. The following components will automatically transition to ENABLED state when launched:

WeatherForecast
ScriptQueue:1
ScriptQueue:2
ScriptQueue:3
DSM:1
DSM:2

Only leverage the following scripts, if necessary. Required configurations will be given for each script execution.

set_summary_state.py

data:
  - [ESS:*, ENABLED]
  - [Watcher, ENABLED]