VMware VS4-ENT-PL-A Setup Guide - Page 176

Test and Repair Rule Compliance

Page 176 highlights

vSphere Installation and Setup Procedure 1 Run the Connect-VIServer PowerCLI cmdlet to connect to the vCenter Server system that Auto Deploy is registered with. Connect-VIServer 192.XXX.X.XX The cmdlet might return a server certificate warning. In a production environment, make sure no server certificate warnings result. In a development environment, you can ignore the warning. 2 Define a rule in which hosts with certain attributes, for example a range of IP addresses, are assigned to a folder or a cluster. New-DeployRule -Name "testrule3" -Item "my folder" -Pattern "vendor=Acme,Zven", "ipv4=192.XXX.1.10-192.XXX.1.20" This example passes in the folder by name. You can instead pass in a folder, cluster, or datacenter object that you retrieve with the Get-Folder, Get-Cluster, or Get-Datacenter cmdlet. 3 Add the rule to the rule set. Add-DeployRule testrule3 By default, the working rule set becomes the active rule set, and any changes to the rule set become active when you add a rule. If you use the NoActivate parameter, the working rule set does not become the active rule set. What to do next n Upgrade existing hosts to be added to the specified vCenter Server location by performing test and repair compliance operations on those hosts. See "Test and Repair Rule Compliance," on page 176. n Turn on unprovisioned hosts to add them to the specified vCenter Server location. Test and Repair Rule Compliance When you add a rule to the Auto Deploy rule set or make changes to one or more rules, hosts are not updated automatically. Auto Deploy applies the new rules only when you test their rule compliance and perform remediation. This task assumes that your infrastructure includes one or more ESXi hosts provisioned with Auto Deploy, and that the host on which you installed vSphere PowerCLI can access those ESXi hosts. Prerequisites n Install vSphere PowerCLI and all prerequisite software. n If you encounter problems running PowerCLI cmdlets, consider changing the execution policy. See "Using Auto Deploy Cmdlets," on page 170. Procedure 1 Use PowerCLI to check which Auto Deploy rules are currently available. Get-DeployRule The system returns the rules and the associated items and patterns. 2 Make a change to one of the available rules, for example, you might change the image profile and the name of the rule. Copy-DeployRule -DeployRule testrule -ReplaceItem MyNewProfile You cannot edit a rule already added to a rule set. Instead, you copy the rule and replace the item or pattern you want to change. By default, PowerCLI uses the old name for the copy and hides the old rule. 176 VMware, Inc.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276

Procedure
1
Run the
Connect-VIServer
PowerCLI cmdlet to connect to the vCenter Server system that Auto Deploy
is registered with.
Connect-VIServer 192.XXX.X.XX
The cmdlet might return a server certificate warning. In a production environment, make sure no server
certificate warnings result. In a development environment, you can ignore the warning.
2
Define a rule in which hosts with certain attributes, for example a range of IP addresses, are assigned to
a folder or a cluster.
New-DeployRule -Name "testrule3" -Item "my folder" -Pattern "vendor=Acme,Zven",
"ipv4=192.XXX.1.10-192.XXX.1.20"
This example passes in the folder by name. You can instead pass in a folder, cluster, or datacenter object
that you retrieve with the
Get-Folder
,
Get-Cluster
, or
Get-Datacenter
cmdlet.
3
Add the rule to the rule set.
Add-DeployRule testrule3
By default, the working rule set becomes the active rule set, and any changes to the rule set become
active when you add a rule. If you use the
NoActivate
parameter, the working rule set does not become
the active rule set.
What to do next
n
Upgrade existing hosts to be added to the specified vCenter Server location by performing test and
repair compliance operations on those hosts. See
“Test and Repair Rule Compliance,”
on page 176.
n
Turn on unprovisioned hosts to add them to the specified vCenter Server location.
Test and Repair Rule Compliance
When you add a rule to the Auto Deploy rule set or make changes to one or more rules, hosts are not
updated automatically. Auto Deploy applies the new rules only when you test their rule compliance and
perform remediation.
This task assumes that your infrastructure includes one or more ESXi hosts provisioned with Auto Deploy,
and that the host on which you installed vSphere PowerCLI can access those ESXi hosts.
Prerequisites
n
Install vSphere PowerCLI and all prerequisite software.
n
If you encounter problems running PowerCLI cmdlets, consider changing the execution policy. See
“Using Auto Deploy Cmdlets,”
on page 170.
Procedure
1
Use PowerCLI to check which Auto Deploy rules are currently available.
Get-DeployRule
The system returns the rules and the associated items and patterns.
2
Make a change to one of the available rules, for example, you might change the image profile and the
name of the rule.
Copy-DeployRule -DeployRule testrule -ReplaceItem MyNewProfile
You cannot edit a rule already added to a rule set. Instead, you copy the rule and replace the item or
pattern you want to change. By default, PowerCLI uses the old name for the copy and hides the old
rule.
vSphere Installation and Setup
176
VMware, Inc.