...
From the Kubernetes master node in the site, simply run the sdnc.makeActive script:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| # /path/makeActive
| |||||
ubuntu@k8s-s2-master:~/oom/kubernetes/sdnc/resources/geo/bin$ ./sdnc.makeActive dev (release name) |
This script will make use of kubectl to access the PROM pod and execute promoverride.py with the appropriate parameters to force PROM to switch activity to the local site.
Alternatively, the promoverride.py script could be executed directly from the PROM pod if so desired:
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@dev-prom-6485f566fb-hdhzs:/app/config# ../promoverride.py -i sdnc02 |
Here, 'sdnc02' is the identifier specified for the second site during deployment.
Automatic failover
The PROM instance in each SDN-C site is responsible for periodically ascertaining the health of the local site based on the health of each component. This information is published to MUSIC in order for the remote site to also be aware of this information.
...