Simulacro (MSRS)SSH — Volgo-01
Log into the host running Volgo-01.
ssh rocky@52.59.12.4
Environment colo_dynamic_13Aug (msrs-env-0047)
Current status: Decommissioned · Deployment: DYN Colocated (dynamic VM) · Install: Tarball (myharem)
- Display ID
- msrs-env-0047
- Internal ID
- f40dac34-2c60-444d-8ea4-e69ce70ab10e
- Status
- Decommissioned
- Profile
- VM
- Provider
- aws
- Setup source
- custom-75084ac7-fcd0-4e5a-a77d-7932ba1f123b
- MariaDB
- custom-multi-node
- Distro
- mixed
- Retention
- 9/12/2026, 12:10:18 PM
- Auto-stop
- -
- Primary timezone
- UTC
- Assigned engineer timezones
- UTC
- Challenge timeout
- 30 minutes
- Presence challenge
- none
Lifecycle actions
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 colocated_dynamic executor. Real host — SSH access requires whatever key/credentials that host's operator has configured for you.
| Node | Host | Port | User | Role | Cluster |
|---|---|---|---|---|---|
| Volgo-01 | 52.59.12.4 | 10000 | rocky | master | cluster-a (async_replica) |
| Volgo-02 | 52.59.12.4 | 10010 | rocky | slave | cluster-a (async_replica) |
Connection methods
MariaDB client — Volgo-01
Connect to this node's MariaDB via myharem's CLI, over the SSH session above.
ssh rocky@52.59.12.4 sudo mh cli 10000
SSH — Volgo-02
Log into the host running Volgo-02.
ssh rocky@52.59.12.4
MariaDB client — Volgo-02
Connect to this node's MariaDB via myharem's CLI, over the SSH session above.
ssh rocky@52.59.12.4 sudo mh cli 10010
Custom topology
1 clusters, 0 MaxScale, 2 nodes, 0 links
cluster-a (Async replica cluster)
| Node | Role | Edition | MariaDB | Distro |
|---|---|---|---|---|
| Volgo-01 | master | CS | 10.6.18 | rocky 9 |
| Volgo-02 | slave | CS | 10.6.22 | rocky 9 |
Event timeline
- decommission · success · claudio.nanni@mariadb.comDecommission completed via colocated_dynamic executor. All nodes removed.
- decommission-started · success · claudio.nanni@mariadb.comDecommission started via colocated_dynamic executor. All nodes in this environment are torn down together.
- pause · success · claudio.nanni@mariadb.comEnvironment paused. All compute nodes in this environment are stopped to reduce cost while keeping setup metadata for later resume.
- pause-started · success · claudio.nanni@mariadb.comPause started via colocated_dynamic executor (attempt 2). All compute nodes in this environment are stopped together.
- resume · success · claudio.nanni@mariadb.comEnvironment resumed. Compute nodes are available again and setup remains locked.
- resume-started · success · claudio.nanni@mariadb.comResume started via colocated_dynamic executor (attempt 1). Compute nodes are being started again.
- pause · success · claudio.nanni@mariadb.comEnvironment paused. All compute nodes in this environment are stopped to reduce cost while keeping setup metadata for later resume.
- pause-started · success · claudio.nanni@mariadb.comPause started via colocated_dynamic executor (attempt 1). All compute nodes in this environment are stopped together.
- provision · success · claudio.nanni@mariadb.comProvision completed via colocated_dynamic executor. Setup is locked; 2 node(s) ready.
- provision-started · success · claudio.nanni@mariadb.comProvisioning started via colocated_dynamic executor (attempt 1).
- create · success · claudio.nanni@mariadb.comSetup saved with preset 'custom-75084ac7-fcd0-4e5a-a77d-7932ba1f123b'. Review and run provision when ready.