VMware VC-VLM4-C User Guide - Page 61

Deploy a Configuration with Default Settings, Understanding Default Deployment Settings

Page 61 highlights

Chapter 7 Working with Configurations 4 Specify the Host Spanning setting. This option is only available if the configuration's organization includes an enabled host spanning transport network and the configuration uses fencing or a virtual network. For a configuration that is unfenced and does not include any virtual networks, Lab Manager can always deploy its virtual machines across multiple hosts For network intensive operations, enabling Host Spanning may result in a slight decrease in throughput and a slight increase in latency. 5 Select the Use Server Boot Sequence check box to boot the virtual machines in the order specified in the configuration properties. If you do not select this option, Lab Manager boots the virtual machines all at once. 6 Deselect the Power On Machines After Deployment check box to prevent Lab Manager from powering on virtual machines immediately after deployment. Use this option when you need to manually power on virtual machines. For example, you might need to ensure a database, application, and Web server are working individually rather than all at once. 7 Specify a resource pool on which to deploy the configuration or select Any Available. 8 Specify a time to undeploy the configuration. 9 (Optional) Type change summary text that will appear on the configuration's History tab. 10 Click OK. Deploy a Configuration with Default Settings If you do not need to specify any custom deployment settings, you can deploy a configuration using its default settings. For more information about how the default settings are determined, see "Understanding Default Deployment Settings" on page 61. To deploy a configuration with default settings Move the pointer over the configuration name and select Deploy with defaults. If the configuration is already partially deployed, Lab Manager only deploys the configuration's undeployed virtual machines. Understanding Default Deployment Settings Table 7‐1 provides information about how Lab Manager determines default deployment settings. Table 7-1. Default Deployment Settings Setting Name Setting Value Fence Virtual Machines Connect Virtual Networks to Physical Networks If the configuration or any of its physical networks has a Fenced Only fencing policy, then all physical networks in the configuration are fenced and network connectivity is set to Allow In and Out, unless one of the physical networks requires a different connectivity setting. If the configuration and physical network policies conflict (one is set to Fenced Only and the other is set to Unfenced Only), Lab Manager displays an error and prevents deployment. If both the configuration and physical network properties are set to Allow Fenced or Unfenced, the default is determined by the deployment setting specified in the organization properties. Not selected. VMware, Inc. 61

  • 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

VMware, Inc.
61
Chapter 7
Working with Configurations
4
Specify the Host Spanning setting.
This option is only available if the configuration’s organization includes an enabled host spanning
transport network and the configuration uses fencing or a virtual network. For a configuration that is
unfenced and does not include any virtual networks, Lab Manager can always deploy its virtual machines
across multiple hosts
For network intensive operations, enabling Host Spanning may result in a slight decrease in throughput
and a slight increase in latency.
5
Select the
Use Server Boot Sequence
check box to boot the virtual machines in the order specified in the
configuration properties.
If you do not select this option, Lab Manager boots the virtual machines all at once.
6
Deselect the
Power On Machines After Deployment
check box to prevent Lab Manager from powering
on virtual machines immediately after deployment.
Use this option when you need to manually power on virtual machines. For example, you might need to
ensure a database, application, and Web server are working individually rather than all at once.
7
Specify a resource pool on which to deploy the configuration or select
Any Available
.
8
Specify a time to undeploy the configuration.
9
(Optional) Type change summary text that will appear on the configuration’s History tab.
10
Click
OK
.
Deploy a Configuration with Default Settings
If you do not need to specify any custom deployment settings, you can deploy a configuration using its default
settings. For more information about how the default settings are determined, see
“Understanding Default
Deployment Settings”
on page 61.
To deploy a configuration with default settings
Move the pointer over the configuration name and select
Deploy with defaults
.
If the configuration is already partially deployed, Lab Manager only deploys the configuration’s undeployed
virtual machines.
Understanding Default Deployment Settings
Table 7
1
provides information about how Lab Manager determines default deployment settings.
Table 7-1.
Default Deployment Settings
Setting Name
Setting Value
Fence Virtual Machines
If the configuration or any of its physical networks has a Fenced Only fencing policy, then
all physical networks in the configuration are fenced and network connectivity is set to
Allow In and Out, unless one of the physical networks requires a different connectivity
setting.
If the configuration and physical network policies conflict (one is set to Fenced Only and
the other is set to Unfenced Only), Lab Manager displays an error and prevents
deployment.
If both the configuration and physical network properties are set to Allow Fenced or
Unfenced, the default is determined by the deployment setting specified in the
organization properties.
Connect Virtual Networks
to Physical Networks
Not selected.