Current status: Decommissioned · Deployment: ISO Isolated VMs (one VM per node) · Install: Tarball (myharem)
The repo install path is not built yet, so nodes are still deployed from tarballs via myharem. You get per-node OS, network and failure isolation, but not package-level fidelity.
Pause/decommission is enforced at whole-environment scope. Partial single-node lifecycle outcomes are not supported.
Timezone policy: UTC · Challenge timeout: 30 min
Setup can be edited until provisioning starts. Pause/Resume controls compute cost state; MariaDB service operations stay manual after provisioning.
Node access targets
Access targets from the last successful provision via the isolated_vms_dynamic executor. Real host — SSH access requires whatever key/credentials that host's operator has configured for you.
Node
Host
Port
User
Role
Cluster
node-01
63.183.101.178
10000
rocky
member
cluster-a (galera)
Connection methods
SSH — node-01
Log into the host running node-01.
ssh rocky@63.183.101.178
MariaDB client — node-01
Connect to this node's MariaDB via myharem's CLI, over the SSH session above.
ssh rocky@63.183.101.178
sudo mh cli 10000
Custom topology
1 clusters, 0 MaxScale, 1 nodes, 0 links
cluster-a (Galera cluster)
Node
Role
Edition
MariaDB
Distro
node-01
member
ES
11.8.5-2
rocky 9
Event timeline
cleanup · success · system
Expired environment cleaned up by policy.
expire · success · system
Environment marked as expired.
pause · success · claudio.nanni@mariadb.com
Environment paused. All compute nodes in this environment are stopped to reduce cost while keeping setup metadata for later resume.