srmdocs's Posts

Thanks for posting this. It works for me as well. The example in the documentation also works for me, though it doesn't do exactly the same thing as the sample you posted here. We'll take a closer look at how our example could be improved, sine we really want to documentation to be trustworthy (and correct).

I think you need the <ovf:Info> element, as shown here (from Create a vApp From a Template) <NetworkConfigSection> <ovf:Info>Configuration parameters for logical networks</ovf:Info>   <NetworkConfig networkName="vAppNetwork">   <Configuration>   <ParentNetwork href="https://vcloud.example.com/api/network/54"/>   <FenceMode>bridged</FenceMode>   </Configuration>   </NetworkConfig>   </NetworkConfigSection>

Hi... I looked up vCloud REST API - InstantiationParamsType in the VMware docs and it does include a NetworkConnectionSection. Where were you seeing that this element is not part of InstantiationParams?

The VirtualSystemIdentifier is contained in the ovf:System element, as shown in this request fragment. -------------------------- POST https://vcloud.example.com/api/vApp/vm-4/action/reconfigureVm Content-Type: application/vnd.vmware.vcloud.vm+xml ... <?xml version="1.0" encoding="UTF-8"?> <Vm ...>    ...    <ovf:VirtualHardwareSection ...>       <ovf:Info>Virtual hardware requirements</ovf:Info>       <ovf:System>          <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>          <vssd:InstanceID>0</vssd:InstanceID>          <vssd:VirtualSystemIdentifier>ABCDEFG</vssd:VirtualSystemIdentifier>          <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>       </ovf:System>          ...    </ovf:VirtualHardwareSection>       ... </Vm> ---------------------------

If you're using v5.1 of the REST API, you can take advantage of the reconfigureVm action to change the name, Description, and other config details of a Vm. See Update Multiple Sections of a Virtual Machine

If this is an AllocationPool vDC, then CPU Used and Overhead values are always shown as 0, since all VMs in the vDC get what amounts to an equal distribution of  CPU resources (the 6370 in your example, which is what was allocated when the vDC was created).