Skip to content
SHC Docs

An Alibaba Cloud node

This page has not been walked: no test instance is made on Alibaba Cloud, so no ECS instance has run these commands. The walk is still owed. Its command lines are what the CLI takes. Where a line of output is written, it is the form the walked pages print; the rest is left open.

Alibaba Cloud nodes are not detected: an ECS instance records no cloud and no location until you say so, and until then no disk reaches it. One AccessKey pair gives a cluster DNS, a network load balancer and disks.

Write the AccessKey on home01 as ~/alibaba.json. Both halves are secrets.

{"access_key_id": "<AccessKey ID>", "access_key_secret": "<AccessKey secret>"}
home01
$ chmod 600 ~/alibaba.json

In the Alibaba Cloud console create one ECS instance: Debian 13, in zone cn-hangzhou-h of region cn-hangzhou, a type that attaches disks over virtio, named after the node. Install SHC on it and allow the cluster ports between it and the learn nodes. Call the node ali01 and join it without saying where it is, to see what SHC records on its own.

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

ali01
$ ssh home01 shc node token --fields token -o text | shc node join - --name ali01
✔ joined cluster as node "ali01" at 47.96.1.2
home01
$ shc node ls
NAME STATE CONDITION AVAIL CLOUD LOCATION ROOM LEADER VOTER
...

ali01’s cloud and location read -. Set both on the row in place, then connect the account. region and zone_id are coordinates, typed inline; the keys come from the file.

home01
$ shc node update ali01 --cloud alibaba --location cn-hangzhou-h
...
$ shc node ls
...
$ shc connection connect alibaba --cred region=cn-hangzhou --cred zone_id=cn-hangzhou-h --value-file ~/alibaba.json
...
$ shc connection show alibaba
...

Install notes onto ali01 with its data on an ESSD disk. A disk is at least 20 GiB and is created in the connection’s zone_id, which is why ali01’s location had to say that zone.

home01
$ shc install notes -s alidb --where node=ali01 --storage alibaba
...
$ shc volume ls
...
$ shc volume snapshot pgdata -s alidb
...
$ shc uninstall alidb -y
...
$ shc volume ls
...

Take ali01 out and remove the connection, then release the instance in the console.

The system ingress keeps a traefik replica on every node, so a node that still hosts one refuses to leave with X409025LVDEPS: drain it first, from any node, and the cluster moves what it hosts. Then the node leaves from itself.

home01
$ shc node drain ali01 --yes
...
ali01
$ shc node leave
...
home01
$ shc node ls
...
$ shc connection rm alibaba --yes
...

Delete 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: A Scaleway node.