Yesterday, usage meter 3.6.1. came available, this patch release includes improved updates for SAN and vRealize operation manager metering and some additional bugfixes.
I would recommend to install this but keep the old usage meter running parallel and compare the results.
usage meter can be downloaded from: usage meter 3.6.1 downloads
Yes, In the tenant portal section i have checked the Copy API URL settings checkbox. Is there any other configuration that needs to be done apart from this? I get the same error or a blank page even after the setting.
That's what i was thinking, but i don't have environment to test it out. If you have, you can test it and let me know.
Sorry, I do not understand the question. Can you post the error produced by your snippet?
Ranjana this is tested solution. I have done this few times in production
Hello, Markus.
Exception calling "CreateNetwork" with "1" argument(s): "The server returned 'Server Error' with the status code 500 - InternalServerError." At line:1 char:1 + $orgVdc.ExtensionData.CreateNetwork($ExNetnetwork) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : CloudException
Look at this topic, please, for more information:
Guys,
Whether does vCloud Director 8.2 support one Independent Disk attach to two VMs ?
Thanks,
Rena
Please review KB Migrating VCDNI Networks to VXLAN Networks in vCloud Director (2148381)
Hi Rena,
Unfortunately not as far as I can tell in either v8.20 or the new v9.0. This is one of those frustrating things that has been supported in vCenter 5.x and 6.x for ages but isn't exposed in the vCloud Director interface or API.
You can use Independent disks and move these between VMs in vCloud Director 8.20 (and 9.0) using the API - I wrote a PowerShell module for this and a blog post: https://kiwicloud.ninja/2017/02/using-independent-disks-in-vcloud/ to make it easier to create/attach/detach/delete independent disks from vCloud VMs, but there is currently no way that I am aware of to set the bus-sharing that would need to be present to allow the same disk to simultaneously be attached to multiple VMs.
This is one of a number of vSphere features that really should be added in vCloud Director - others include UEFI BIOS selection, configuration of VM video RAM to support better console resolutions and several others imho. I've submitted feedback to VMware on many of these and hopefully they'll get added at some point.
If you need to do this for Microsoft Clustering (the usual case for bus-shared disks attached to multiple VMs), there is a supported workaround using in-guest mounted iSCSI disks, but that relies on having highly available/redundant iSCSI storage available.
Regards, Jon.
I never really got a solution, it would work for a while but it's very flaky across OS/Browser versions. In the end, I simply upload to a vSphere datastore and then import the media into the catalog.
I had this issue too, does the IP work?
For me, I had to remove http://FQDN/api from the API URL settings to solve it after lengthy conversations with support.
Hello Jon,
Thanks a lot for your information.
Does vCloud Director 8.2 support create "thick provisioned eager zeroed" Independent Disk ?
Thanks,
Rena
Guys,
Does vCloud Director 9.0 support create IPv6 Org VDC Networks on GUI?
Thanks,
Rena
CPU and Memory modifications during RecomposeVapp are ignored. You will need to:
- recompose the vapp and add the VM, do not power on the VM
- modify CPU and/or memory, see: VMware vCloud Director 8.0
- power on VM
No, vCloud Director 9.0 cannot manage IPv6 addresses for Tenant devices or networking. no GUI is available to create such networks.
You can integrate the vDC with NSX for vSphere to make this possible. For detailed explanation, see Architecting Tenant Networking with VMware NSX® in VMware vCloud Director available at https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/vcat/vmware-architecting-tenant-networking-with-nsx-in-vcd.pdf
We recently purchased and installed a new storage array to replace our existing. I have completed the migration of all resources to the new storage and removed the profile for the old storage. The old storage shows as disabled under the provider VDC and under "vSphere Resources". Is there anything further that I would need to do to remove the storage from vCloud Director or should I just continue removing it through the vCenter Server at this point? Next steps in vCenter would be to delete the profile, tags, Datastore cluster, and finally Unmount and Detach I assume.
Hi everyone.
I've faced an unexpected problem when restarting /etc/init.d/vmware-vcd service
Here is output from cell.log:
Bootstrap application: start
All required system properties are present
An unspecified error occurred during application start
All required local configuration properties are present
Successfully bound network port: 80 on host address: 192.168.100.9
Successfully bound network port: 443 on host address: 192.168.100.9
Successfully bound network port: 8999 on host address: 192.168.100.9
All required local configuration properties are present
Successfully initialized system cryptography
Successfully configured HTTP SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/certificates
Current locale "en" verified successfully.
Bootstrap application: complete
Application startup event: Waiting for subsystem 'com.vmware.vcloud.common.core'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.cloud-proxy-server'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.networking-server'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.consoleproxy'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.computeservice.broker'
Application startup event: Subsystem 'com.vmware.vcloud.networking-server' startup initiated.
Application startup begins: Subsystem 'com.vmware.vcloud.networking-server' at 1/12/18 10:29 AM
Application startup event: Subsystem 'com.vmware.vcloud.cloud-proxy-server' startup initiated.
Application startup begins: Subsystem 'com.vmware.vcloud.cloud-proxy-server' at 1/12/18 10:29 AM
Application startup event: Subsystem 'com.vmware.vcloud.common.core' startup initiated.
Application startup begins: Subsystem 'com.vmware.vcloud.common.core' at 1/12/18 10:29 AM
Error starting application: Database schema version is not compatible with this release. Requires version [ "2.1.9", "6.0.116", "7.0.0", [ "1.0.44", "45.2.0", [ "19.9.0", "11.0.0", "8.0.0" ], [ "6.0.0", "6.0.0" ], [ "14.0.0", "4.0.0", "6.0.0", "9.0.0", "5.0.0" ], [ "7.0.0", "3.0.0", "4.0.0", "12.0.0", "2.0.0", "2.0.0", "7.0.0", "3.0.0", "6.0.0", "5.0.0", "15.0.0", "5.0.0", "21.0.0" ] ], "72.0.0" ] but found version [ "2.1.9", "6.0.116", "7.0.0", [ "1.0.44", "45.2.0", [ "19.9.0", "11.0.0", "8.0.0" ], [ "6.0.0", "6.0.0" ], [ "14.0.0", "4.0.0", "6.0.0", "9.0.0", "5.0.0" ], [ "7.0.0", "3.0.0", "4.0.0", "12.0.0", "2.0.0", "2.0.0", "7.0.0", "3.0.0", "6.0.0", "5.0.0", "15.0.0", "5.0.0", "21.0.0", "84.0.0" ] ], "116.0.0" ]
I don't know what exactly caused this issue and how to fix it. Machine with vCloud Director DB (Windows Server 2008 + MSSQL) is working and accessible. Are there any ideas?
Thanks
Was this a working setup ? What is correct version of DB which we are using in this set-up ? I'm hoping there is no DB upgrades done recently in this setup ? Please double check DB compatibility
As long as there are no VCD entities showing in the datastore from vCloud perspective , you can go ahead and disable the old data-store from VCD and unmount and delete it from underlying ESXI .If you have any queries around Storage migration please do check Datastore Migrations in vCloud Director – Part 1 of 3: Introduction – Tom Fojta's Blog
Hi
Using: vCloud Director 8.2
I have a scenario were i would need to add two VMs in two different requests simultaneously. As far as I know, I have to recompose a vApp to add a VM and there is no way of adding one outside of that.
Therefore, the code I currently have is trying to start RecomposevApp with two different requests, each containing a unique vApp. However, when one request is started, and the vApp enters busy state, the second request receives a 500 error:
500: [ a7662069-f865-406e-8244-aef04f3c63c1 ] Unable to perform this action. Contact your cloud administrator.
I have read through the API and as far as I can see, there is a queued state for tasks. I assume that what I need is to have the second request added to the TaskList as a queued task, I can however not figure that out.
Does anyone know how this can be achieved? If there is another way to add a VM to a vApp which circumvents this issue, i would also be interested in hearing about that.
--
Best regards
Kristoffer