An Oracle Cloud node
This page has not been walked: no SHC test account exists on Oracle Cloud. Its command lines are what the CLI takes; its output lines are left open.
The oci connection signs its requests with an API key, so it carries
six fields: the tenancy, the user, the key’s fingerprint, the private
key, the region and the compartment. One connection lights OCI DNS, a
network load balancer and block volumes. OCI nodes are not detected, and
a block volume is scoped to one availability domain, so a node’s location
is that domain’s label in lower case.
Write the six fields on home01 as ~/oci.json, the private key
as one string with its line breaks written \n.
{"tenancy_ocid": "<tenancy ocid>", "user_ocid": "<user ocid>", "fingerprint": "<key fingerprint>", "private_key": "<private key pem>", "region": "us-phoenix-1", "compartment_ocid": "<compartment ocid>"}$ chmod 600 ~/oci.jsonCreate one compute instance in that compartment: Debian 13, availability
domain PHX-AD-1, named after the node, with a security list that allows
the cluster ports between it and the learn nodes. Install SHC on it. Call
the node oci01 and join it without a location, then set it.
The join asks home01 for its token over ssh, so give root on oci01 the learn nodes’ names and a key home01 accepts, as the learn nodes have.
$ ssh home01 shc node token --fields token -o text | shc node join - --name oci01...$ shc node ls...$ shc node update oci01 --cloud oci --location phx-ad-1...$ shc node ls...$ shc connection connect oci --value-file ~/oci.json...$ shc connection show oci...$ shc install notes -s ocidb --where node=oci01 --storage oci...$ shc volume ls...$ shc uninstall ocidb -y...$ shc volume ls...$ shc node leave...$ shc node ls...$ shc connection rm oci --yes...Terminate the instance in the console.
This page leaves the cluster as the runtimes ladder left it: the learn nodes, with no cloud node and no connection.
Next: An UpCloud node.