Recompose vApp
To recompose a vApp, use the following request:
| |
XML Request Example
| |
JSON Request Example
| |
Where:
- vapp_template_id - the ID of the template on which the vApp will be built
- virtual_machines - the array of parameters associated with the VSs
- id - the ID of the VS
- name - edit the name for the VS
- cpus - set the number of cores
- cores_per_socket - set the number of cores per socket
- memory - the amount of RAM allocated to this VS in Mb
- storage_policy - the virtual server’s storage policy that is a default data store ID. If Fast Provisioning is not enabled for the previously selected VDC, you can select a different data store for the VS’s disks.
- hard_disks - the array of parameters associated with the VS disks
- instance_id - the ID of the corresponding disk that is available via the Get List of vApp Templates request
- disk_space - set the disk size in Gb
- storage_policy - the disk storage policy that is a data store ID. This option is available only if the selected VDC has Fast Provisioning disabled. If you do not select a data store, the disk is built on the default data store.
- nics - the array of parameters associated with the NICs
- network_id - the ID of the network to which the NIC will be connected
- adapter_type - the network adapter type provided for the VS that can be one of the following values:
- Vlance
- E1000
- E1000E
- VMXNET
- VMXNET2
- VMXNET3
- FLEXIBLE
- vcloud_guest_customization - array of parameters associated with guest customization
- computer_name - VS’s computer name
- enabled - set true if guest customization should be enabled for the VS, otherwise, set false
- admin_password_enabled - set true if the local admin password should be allowed; otherwise, set false
- admin_password - enter the password of the administrator
- admin_password_auto - set true if the admin password should be generated automatically; otherwise, set falseIf you set the admin_password_auto parameter to true, Resync vCloud VS after recomposing the vApp to be able to view the password.
- recipe_ids - the IDs of the recipes that are to be applied to the VS
- custom_recipe_variables - array of parameters associated with custom variables
- name - the name of the custom variable
- value - the value of the custom variable
- enabled - set to true if the custom variable should be enabled; otherwise, set false
- disable_guest_customization_after_run - set true if guest customization for this VS should be disabled after vApp deployment; otherwise, set false
- boot_vm - set true if the VS should be switched on after vApp deployment; otherwise, set false
Page History
v. 5.3
- Added parameters related to guest customization and recipes
v. 5.2
- Added the following parameters:
- virtual_machines
- id
- name
- cpus
- cores_per_socket
- memory
- storage_policy
- nics, network_id