Ok great, you have a cluster host prepared and your management machine prepped and ready to go. The next step is to take the cluster host under management of your SSME with the ss-remote command, a bash alias for remote.sh.
Taking a Cluster Host under Management
Taking a remote SSH endpoint under management is as simple as issuing the following command which creates a new incus remote called dev. The SSME will reach out to clusterhost01.domain.tld (defined in your DNS server) using SSH/t and installs and initializes incus on the remote host.
ss-remote dev clusterhost01.domain.tld --disk=/dev/nvme0n1p3The --disk flag should be set to the device corresponding to the large UNFORMATTED partition.
You can also specify --data-plane-interface=<eno1> is the physical network interface that VMs will attach to expose services on the network underlay (i.e., SERVERS_VLAN). Note, if you only have ONE physical interface on the device, it is UNNECESSARY to specify the --data-plane-interface. If you have two or more physical interfaces, then you can separate the data plane from the management plane.
remote.conf
If this is the first time you're running the command, Sovereign Stack will stub ~/ss/remotes/dev/remote.conf . You should review the config file and set it up to match your particular requirements, then run the ss-remote command again so it completes.
# see https://www.sovereign-stack.org/ss-remote for more info!
# REGISTRY_URL=http://registry.domain.tld:5000This file will be used in later sections to customize your infrastructure.
At the end of remote.sh, a new incus remote is created in your SSME. Finally, the incus client is switched to the remote such that any subsequent incus commands target that remote. You can use incus remote list to get information about your current remotes.