Managing VirtualApp
Children
You can add
virtual machines and virtual applications to your virtual application as direct
or linked children.
You use different methods for adding or removing
direct or linked children, as follows:
- Direct children. Use one of the following methods:
- CreateChildVMTaskadds a new virtual machine.
- CreateVAppadds a new virtual application.
- MoveIntoResourcePooladds or removes an existing virtual machine or virtual application
- Linked children.Use UpdateLinkedChildrento add or remove virtual machines or virtual applications.
You can call the
UpdateVappConfig
method to
specify how each virtual machine fits into the virtual application.
Property
| Enumeration
|
|---|---|
destroyWithParent
| True if the entity
should be removed when the
VirtualApp is removed.
|
key
| Key for the virtual
machine or virtual application, a managed object reference to the child.
|
startAction
| One of the strings in
the
VAppAutoStartAction
enumeration.
|
startDelay
| Delay, in seconds,
before continuing with the next entity.
|
startOrder
| Specifies the start
order for this entity. Entities are started from lower numbers to
higher-numbers and reverse on shutdown. Multiple entities with the same start
order are started in parallel and the order is unspecified. This value must be
0 or higher.
|
stopAction
| Defines the stop action
for the entity. Can be set to
none ,
powerOff ,
guestShutdown , or
suspend . If set to
none , then the entity
does not participate in auto-stop.
|
stopDelay
| Delay, in seconds,
before continuing with the next entity.
|
tag
| Tag for the entity.
|
waitingForGuest
| Determines if the
virtual machine should start after receiving a heartbeat, from the guest.
|
For more information about
direct children and linked children, see
Direct and Linked Children.