Create vApp with Guest Customization and Recipes
To create a vApp, use the following request:
| |
XML Request Example
| |
JSON Request Example
| |
Where:
- name - name of the vApp
- vdc_id - ID of the datacenter on which the vApp will be created
- vapp_template_id - ID of the template on which the vApp will be built
- virtual_machines - array of parameters associated with the VSs
- id - ID of the VS
- name -choose a 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
- hard_disks - array of parameters associated with the VS disks
- disk_space - set the disk’s size
- storage_policy - the disks’s storage police
- nics - array of parameters associated with the NICs
- network_id - the ID of the network to which the NIC will be connected
- 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 creating the vApp with guest customization 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