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-bmm-ssh.md
+35-35Lines changed: 35 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ If the User Principal Name for a user isn't a member of the supplied group, the
21
21
> [!NOTE]
22
22
> There is currently a transitional period where specifying User Principal Names is optional. In a future release, it will become mandatory and Microsoft Entra ID validation will be enforced for all users. Users are encouraged to add User Principal Names to their keysets before the transitional period ends (planned for July 2024) to avoid keysets being invalidated. Note that if any User Principal Names are added to a keyset, even if they are not added for all users, Microsoft Entra ID validation will be enabled, and this will result in the entire keyset being invalidated if the Group ID specified is not valid.
23
23
24
-
When the command runs, it executes on each bare metal machine in the Cluster with an active Kubernetes node. There's a reconciliation process that runs periodically that retries the command on any bare metal machine that wasn't available at the time of the original command. Also, any bare metal machine that returns to the cluster via an `az networkcloud baremetalmachine actionreimage` or `az networkcloud baremetalmachine actionreplace` command (see [BareMetal functions](./howto-baremetal-functions.md)) sends a signal causing any active keysets to be sent to the machine as soon as it returns to the cluster. Multiple commands execute in the order received.
24
+
When the command runs, it executes on each bare metal machine in the Cluster with an active Kubernetes node. There's a reconciliation process that runs periodically that retries the command on any bare metal machine that wasn't available at the time of the original command. Also, any bare metal machine that returns to the cluster via an `az networkcloud baremetalmachine reimage` or `az networkcloud baremetalmachine replace` command (see [BareMetal functions](./howto-baremetal-functions.md)) sends a signal causing any active keysets to be sent to the machine as soon as it returns to the cluster. Multiple commands execute in the order received.
25
25
26
26
There's no limit to the number of users in a group.
27
27
@@ -56,21 +56,21 @@ The command syntax is:
56
56
57
57
```azurecli
58
58
az networkcloud cluster baremetalmachinekeyset create \
59
-
--name <bare metal machine Keyset Name> \
60
-
--extended-location name=<Extended Location ARM ID> \
59
+
--name "<bare metal machine Keyset Name>" \
60
+
--extended-location name="<Extended Location ARM ID>" \
61
61
type="CustomLocation" \
62
-
--location <Azure Region> \
63
-
--azure-group-id <Azure Group ID> \
64
-
--expiration <Expiration Timestamp> \
65
-
--jump-hosts-allowed <List of jump server IP addresses> \
66
-
--os-group-name <Name of the Operating System Group> \
67
-
--privilege-level <"Standard" or "Superuser"> \
62
+
--location "<Azure Region>" \
63
+
--azure-group-id "<Azure Group ID>" \
64
+
--expiration "<Expiration Timestamp>" \
65
+
--jump-hosts-allowed "<List of jump server IP addresses>" \
66
+
--os-group-name "<Name of the Operating System Group>" \
67
+
--privilege-level "<"Standard" or "Superuser">" \
68
68
--user-list '[{"description":"<User List Description>","azureUserName":"<User Name>",\
69
69
"sshPublicKey":{"keyData":"<SSH Public Key>"}, \
70
70
"userPrincipalName":""}]', \
71
-
--tags key1=<Key Value> key2=<Key Value> \
72
-
--cluster-name <Cluster Name> \
73
-
--resource-group <Resource Group>
71
+
--tags key1="<Key Value>" key2="<Key Value>" \
72
+
--cluster-name "<Cluster Name>" \
73
+
--resource-group "<cluster_RG>"
74
74
```
75
75
76
76
### Create Arguments
@@ -100,7 +100,7 @@ az networkcloud cluster baremetalmachinekeyset create \
100
100
--privilege-level [Required] : The access level allowed for the users
101
101
in this key set. Allowed values:
102
102
"Standard" or "Superuser".
103
-
--resource-group -g [Required] : Name of resource group. Optional if
103
+
--resource-group -g [Required] : Name of cluster resource group. Optional if
104
104
configuring the default group using `az
105
105
configure --defaults group=<name>`.
106
106
--user-list [Required] : The unique list of permitted users.
@@ -149,9 +149,9 @@ This example creates a new keyset with two users that have standard access from
149
149
```azurecli
150
150
az networkcloud cluster baremetalmachinekeyset create \
@@ -161,7 +161,7 @@ az networkcloud cluster baremetalmachinekeyset create \
161
161
{"description":"Needs access for troubleshooting as a part of the support team","azureUserName":"userXYZ","sshPublicKey":{"keyData":"ssh-rsa AAtsE3njSONzDYRIZv/WLjVuMfrUSByHp+jfaaOLHTIIB4fJvo6dQUZxE20w2iDHV3tEkmnTo84eba97VMueQD6OzJPEyWZMRpz8UYWOd0IXeRqiFu1lawNblZhwNT/ojNZfpB3af/YDzwQCZgTcTRyNNhL4o/blKUmug0daSsSXTSTRnIDpcf5qytjs1XoyYyJMvzLL59mhAyb3p/cD+Y3/s3WhAx+l0XOKpzXnblrv9d3q4c2tWmm/SyFqthaqd0= admin@vm"}, "userPrincipalName":"[email protected]"}]' \
162
162
--tags key1="myvalue1" key2="myvalue2" \
163
163
--cluster-name "clusterName"
164
-
--resource-group "resourceGroupName"
164
+
--resource-group "cluster_RG"
165
165
```
166
166
167
167
For assistance in creating the `--user-list` structure, see [Azure CLI Shorthand](https://github.com/Azure/azure-cli/blob/dev/doc/shorthand_syntax.md).
@@ -174,9 +174,9 @@ The command syntax is:
174
174
175
175
```azurecli
176
176
az networkcloud cluster baremetalmachinekeyset delete \
177
-
--name <bare metal machine Keyset Name> \
178
-
--cluster-name <Cluster Name> \
179
-
--resource-group <Resource Group Name>
177
+
--name "<bare metal machine Keyset Name>" \
178
+
--cluster-name "<Cluster Name>" \
179
+
--resource-group "<cluster_RG>"
180
180
```
181
181
182
182
### Delete Arguments
@@ -185,7 +185,7 @@ az networkcloud cluster baremetalmachinekeyset delete \
185
185
--bare-metal-machine-key-set-name --name -n [Required] : The name of the bare metal machine key set to be
186
186
deleted.
187
187
--cluster-name [Required] : The name of the cluster.
188
-
--resource-group -g [Required] : Name of resource group. Optional if configuring the
188
+
--resource-group -g [Required] : Name of cluster resource group. Optional if configuring the
189
189
default group using `az configure --defaults
190
190
group=<name>`.
191
191
--no-wait : Do not wait for the long-running operation to
@@ -199,7 +199,7 @@ This example removes the "bareMetalMachineKeysetName" keyset group in the "clust
199
199
az networkcloud cluster baremetalmachinekeyset delete \
200
200
--name "bareMetalMachineKeySetName" \
201
201
--cluster-name "clusterName" \
202
-
--resource-group "resourceGroupName"
202
+
--resource-group "cluster_RG"
203
203
```
204
204
205
205
## Updating a Bare Metal Machine Keyset
@@ -210,15 +210,15 @@ The command syntax is:
210
210
211
211
```azurecli
212
212
az networkcloud cluster baremetalmachinekeyset update \
213
-
--name <bare metal machine Keyset Name> \
214
-
--jump-hosts-allowed <List of jump server IP addresses> \
215
-
--privilege-level <"Standard" or "Superuser"> \
213
+
--name "<bare metal machine Keyset Name>" \
214
+
--jump-hosts-allowed "<List of jump server IP addresses>" \
215
+
--privilege-level "<"Standard" or "Superuser">" \
216
216
--user-list '[{"description":"<User List Description>","azureUserName":"<User Name>",\
217
217
"sshPublicKey":{"keyData":"<SSH Public Key>"}, \
218
218
"userPrincipalName":""}]', \
219
-
--tags key1=<Key Value> key2=<Key Value> \
220
-
--cluster-name <Cluster Name> \
221
-
--resource-group <Resource Group>
219
+
--tags key1="<Key Value>" key2="<Key Value> "\
220
+
--cluster-name "<Cluster Name>" \
221
+
--resource-group "<cluster_RG>"
222
222
```
223
223
224
224
### Update Arguments
@@ -245,7 +245,7 @@ az networkcloud cluster baremetalmachinekeyset update \
245
245
userPrincipalName: Optional. The User Principal Name of the User.
246
246
247
247
Multiple users can be specified by using more than one --user-list argument.
248
-
--resource-group -g [Required] : Name of resource group. Optional if
248
+
--resource-group -g [Required] : Name of cluster resource group. Optional if
249
249
configuring the default group using `az
250
250
configure --defaults group=<name>`.
251
251
--tags : Space-separated tags: key[=value]
@@ -270,7 +270,7 @@ az networkcloud cluster baremetalmachinekeyset update \
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-baremetal-run-data-extract.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,7 @@ The command produces an output file containing the results of the data extract l
20
20
- This article assumes that you've installed the Azure command line interface and the `networkcloud` command line interface extension. For more information, see [How to Install CLI Extensions](./howto-install-cli-extensions.md).
21
21
- The target bare metal machine is on and has readyState set to True.
22
22
- The syntax for these commands is based on the 0.3.0+ version of the `az networkcloud` CLI.
23
+
- Get the Cluster Managed Resource group name (cluster_MRG) that you created for Cluster resource.
23
24
24
25
## Executing a run command
25
26
@@ -50,10 +51,10 @@ The command syntax is:
50
51
51
52
```azurecli-interactive
52
53
az networkcloud baremetalmachine run-data-extract --name "<machine-name>" \
Specify multiple commands using json format in `--commands` option. Each `command` specifies command and arguments. For a command with multiple arguments, provide as a list to the `arguments` parameter. See [Azure CLI Shorthand](https://github.com/Azure/azure-cli/blob/dev/doc/shorthand_syntax.md) for instructions on constructing the `--commands` structure.
@@ -68,7 +69,7 @@ This example executes the `hardware-support-data-collection` command and get `Sy
68
69
69
70
```azurecli
70
71
az networkcloud baremetalmachine run-data-extract --name "bareMetalMachineName" \
@@ -277,4 +277,4 @@ This guide walks you through accessing the output file that is created in the Cl
277
277
278
278
1. Select the output file from the run-read command. The file name can be identified from the `az rest --method get` command. Additionally, the **Last modified** timestamp aligns with when the command was executed.
279
279
280
-
1. You can manage & download the output file from the **Overview** pop-out.
280
+
1. You can manage & download the output file from the **Overview** pop-out.
0 commit comments