wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

VMware: improve readability and fix privileges names on scenario_clone_template (#47889)

Browse source
This commit is contained in:
angystardust 2018-11-02 07:12:41 +01:00 committed by Abhijeet Kasurde
parent b92556549e
commit 89f03314ce
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/docsite/rst/vmware/scenario_clone_template.rst
View file

@ -34,14 +34,14 @@ Scenario Requirements
* Administrator user with following privileges
- Virtual machine.Provisioning.Clone virtual machine on the virtual machine you are cloning
- Virtual machine.Inventory.Create from existing on the datacenter or virtual machine folder
- Virtual machine.Configuration.Add new disk on the datacenter or virtual machine folder
- Resource.Assign virtual machine to resource pool on the destination host, cluster, or resource pool
- Datastore.Allocate space on the destination datastore or datastore folder
- Network.Assign network on the network to which the virtual machine will be assigned
- Virtual machine.Provisioning.Customize on the virtual machine or virtual machine folder if you are customizing the guest operating system
- Virtual machine.Provisioning.Read customization specifications on the root vCenter Server if you are customizing the guest operating system
- ``VirtualMachine.Provisioning.Clone`` on the virtual machine you are cloning
- ``VirtualMachine.Inventory.CreateFromExisting`` on the datacenter or virtual machine folder
- ``VirtualMachine.Config.AddNewDisk`` on the datacenter or virtual machine folder
- ``Resource.Assign`` virtual machine to resource pool on the destination host, cluster, or resource pool
- ``Datastore.AllocateSpace`` on the destination datastore or datastore folder
- ``Network.AssignNetwork`` on the network to which the virtual machine will be assigned
- ``VirtualMachine.Provisioning.Customize`` on the virtual machine or virtual machine folder if you are customizing the guest operating system
- ``VirtualMachine.Provisioning.ReadCustSpecs`` on the root vCenter Server if you are customizing the guest operating system
Assumptions
===========