Skip to content
SHC Docs

An OpenStack node

This page has not been walked: no SHC test account exists on an OpenStack cloud. Its command lines are what the CLI takes; its output lines are left open.

OpenStack is a family of clouds, and each runs some of the services. The openstack connection lights three providers, designate for DNS, octavia for a load balancer and cinder-volume for block volumes, and each one works only where the cloud runs that service. OVH Public Cloud, the reference, runs none of the three, so an estate there points a cloudflare connection at a zone it owns and keeps data on node disks.

Write the credentials on home01 as ~/openstack.json.

{"auth_url": "<keystone url>", "username": "<user>", "password": "<password>"}
home01
$ chmod 600 ~/openstack.json

Create one Nova instance: Debian 13, named after the node, in a security group that allows the cluster ports between it and the learn nodes. Install SHC on it. Call the node os01; its location is the availability zone Nova put it in.

The join asks home01 for its token over ssh, so give root on os01 the learn nodes’ names and a key home01 accepts, as the learn nodes have.

os01
$ ssh home01 shc node token --fields token -o text | shc node join - --name os01 --cloud openstack --location nova
...
home01
$ shc node ls
...
$ shc connection connect openstack --value-file ~/openstack.json
...
$ shc connection show openstack
...
$ shc install ~/learn/nginx -s osweb --where node=os01 --expose 18088=nginx:80
...
os01
$ curl -s http://localhost:18088/
...
home01
$ shc uninstall osweb -y
...
os01
$ shc node leave
...
home01
$ shc node ls
...
$ shc connection rm openstack --yes
...

Delete the instance in the cloud’s dashboard.

This page leaves the cluster as the runtimes ladder left it: the learn nodes, with no cloud node and no connection.

Next: An Oracle Cloud node.