Hi Guys,
I am looking for API which can add newly created resource pool in esxi cluster in provider vdc in vCloud Director. can any one point to exact endpoints?
Thanks
Bharat
Hi Guys,
I am looking for API which can add newly created resource pool in esxi cluster in provider vdc in vCloud Director. can any one point to exact endpoints?
Thanks
Bharat
After deploying a new VM in vCloud Director (with New-CIVM via PowerCLI), what PowerCLI cmdlets are available to then modify the number of CPUs and RAM for a given deployed VM? I can't find any documentation on this at all. Some say to modify the ExtensionData but that appears to just be reporting the current state instead of allowing to update it.
Doesn't seem to work:
for($i=0; $i-le$VM.ExtensionData.Section[0].Item.Length; $i++) {
if($VM.ExtensionData.Section[0].Item[$i].Description.Value -eq"Memory Size") {
$VM.ExtensionData.Section[0].Item[$i].VirtualQuantity.Value =$line.RAM
} elseif ($VM.ExtensionData.Section[0].Item[$i].Description.Value -eq"Number of Virtual CPUs") {
$VM.ExtensionData.Section[0].Item[$i].VirtualQuantity.Value =$line.CPU
}
}
Where can I locate detailed documentation about Cloud Edge NAT and Firewall confnguration?
Regards
marius
Hi,
in the Attached.
ARomeo
Many thanks!
marius
I apologize foe the very basic question.
I am new to vCloud Director and I have a vApp with few VMs.
I need to create a new net inside the vApp to connect some VMs
The net should exist and be accessible only to VMs inside the vApp.
Some VMs wil be connected to the exisging network (provided by the vApp) other VMs sould be connected only to the new net, other VMs should be connected to both and will act as routers.
Does the design make sense?
Which kind of network should I create?
Regards
marius
Hello,
I am trying to deploying a VM using vRealize Orchestrator using VCD Plugin for vRO functions and workflows but I can't do the Guest Customization works.
I'm doing this:
But If I powered off and power On VM from the VCD GUI, it worked!!!
What did I do wrong ? What are I missing? What the VCD GUI does different to VCD Plugin for vRO??
I tried to follow this procedure vCloud Director 5.5 - how to perform "power on and force guest os customization" through rest API ? , but it looks only worked for VCD 5.5, for VDC 9.7 is not working.
Regards
I installed vCD 10 with NSX 6.4.6, vCenter Server 6.7U1, ESXi 6.7U1. This is a supported configuration according to the VMware products compatibility matrix.
When I tried to create an external network, I went through the wizard and when I clicked on the last button to complete the operation I got the following error:
"Unknown API version: null". Attached is the screen shot.
I tried several things to get around it, but nothing worked.
I then went back to vCD 9.7 while maintaining the same version of NSX, vCenter and ESXi, and was able to successfully create the external network and complete the vCD configuration.
Is this a known compatibility issue? If so, how can I get around it using the above configuration? I haven't tested with vCD 10 & 6.7 U3 yet.
Thanks.
Hi guys,
we are currently testing vCD with NSX-T 2.5 in a provider environment and ran into a problem.
In vCD, you are able to create networks with IPv4 OR IPv6, but if you use the API, you could easily deploy networks with a dual stack configuration.
Problem is: As soon as we created such a network, we could not configure a IPv4 DHCP Server any more.
Is this normal behavior, or a bug?
In NSX-T 2.5 we are easily able to create such segments, using a dual stack configuration AND DHCP for the IPv4
Error message in vCD is:
[xxxxSOMEIDyyyyy] Segment path=[/infra/segments/yyyyyySOMEIDyyyyyy] has invalid input: DHCP is not supported for IPv6 subnet., error code 503046
Hi,
In the current GET vApp API there is no information of vAppTemplate (ID/HREF).
I am creating the vApp using instantiateVAppTemplate, hence I need the vAppTemplate ID to verify.
vApp GET API do not provide any sort of information related to the vApp Template.
GET API return vApp object which has no info related to vAppTemplate.
I am using following API
GET- vCloud REST API - GET-VApp
Admin LIST- /api/query?type=adminVApp&format=records
Non-Admin LIST- /api/query?type=vApp&format=records
Is there any way by which I can find the vAppTemplate ID by which the vApp is created ?
Hello,
is there any way how to manage "VM policy placement" the new feature in vCloud Director 10 for SP via CLI / API.
I google it and also look into vCloud Director API [ vCloud Director API - VMware API Explorer - VMware {code} ]. But didnt find a command.
or it can be manage via vCenter as this are VM Group in DRS
Thanks
Stan
I think we have not tested with such storage policies with I/O control. Therefore this requires more investigation, it may be a feature request.
As long as there are ESXi host at 6.0 the HWV level allowed will still remain at 13 at most.
One fix here is to upgrade those hosts to have ESXi 6.5, then change the HWV level of all PVDCs to be vmx-13.
You need to create a vApp network that will be contained inside the vApp and that any VM in the vApp can connect to.
vApp that were created from a vAppTemplate typically have a metadata entry whose key is
vapp.origin.id and whose value is the ID of the vAppTemplate. Note that this is persisted during instantiation, but can be removed by end-users (with proper permissions), so is not in fact guaranteed to be present.
There are some audit events that are raised during vAppTemplate instantiation, but you cannot rely on those (because they cover other types of things happening to those Templates...).
You can always create an empty vApp and then use the ImportIntoExistingVApp REST API.
This bus type is not known to vCD, and currently the set of known types is hard-coded in vCD.
So adding support for this is a feature request..
did you try the H5 UI
No this is not available at all in the vCD API. One needs to go directly to vSphere for this.
I think what may be happening here is that vCD's placement engine finds a "better" solution by putting the disk on the other datastore: it suffices that the other datastore have more free space for this to be true. We currently (I believe but will verify) do not have a soft affinity constraint to tie the disk to its original datastore when feasible (i.e. when that datastore has enough free space to accommodate the disk delta requirement).