You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-baremetal-nexusctl.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ run simple actions on bare metal machines without using the Azure console or com
24
24
25
25
## Prerequisites
26
26
27
-
1.Create a [BareMetalMachineKeySet](./howto-baremetal-bmm-ssh.md) to allow ssh access to the bare metal machines. The user must have superuser privilege level.
27
+
1.A [BareMetalMachineKeySet](./howto-baremetal-bmm-ssh.md) must be available to allow ssh access to the bare metal machines. The user must have superuser privilege level.
28
28
1. The platform Kubernetes must be up and running on site.
29
29
30
30
## Overview
@@ -69,7 +69,7 @@ The status is blank until the operation completes and reaches either a "succeede
69
69
70
70
## Start a bare metal machine
71
71
72
-
A single bare metal machine can be started from a power-off state by connecting to a control-plane or management-plane node via ssh and running the command:
72
+
A single bare metal machine can be started by connecting to a control-plane or management-plane node via ssh and running the command:
@@ -85,19 +85,19 @@ The status is blank until the operation completes and reaches either a "succeede
85
85
86
86
## Unmanage a bare metal machine (set to unmanaged state)
87
87
88
-
A single bare metal machine can be moved from a managed state to an unmanaged state by connecting to a control-plane or management-plane node via ssh and running the command:
88
+
A single bare metal machine can be switched to an unmanaged state by connecting to a control-plane or management-plane node via ssh and running the command:
While in an unmanaged state, no actions are permitted for that machine, except for returning it to a managed state (see next section). This can be used to keep a bare metal machine powered off in the instance it's caught in a rebooting crash loop.
94
+
While in an unmanaged state, no actions are permitted for that machine, except for returning it to a managed state (see next section). This function can be used to keep a bare metal machine powered off if it's in a rebooting crash loop.
95
95
96
96
`unmanage` isn't a long-running command, so there's no associated command to check operation status.
97
97
98
98
## Manage a bare metal machine (set to managed state)
99
99
100
-
A single bare metal machine can be moved from an unmanaged state to a managed state by connecting to a control-plane or management-plane node via ssh and running the command:
100
+
A single bare metal machine can be switched to a managed state by connecting to a control-plane or management-plane node via ssh and running the command:
0 commit comments