Correct Yiping - at the time we initially wrote Trillian a couple of years ago
we didn't have all the modules required, but since we could do everything with
a CloudMonkey script we simply templated this and triggered a bash script run
from Ansible. We could possibly rewrite now with the
Hi, Dag:
Thanks for the quick reply.
Yea, that is it!. The custom attribute "cloud.zone" was set to true for the
datacenter in vCenter. Once I delete that attribute, or change its value to
"false", I could re-associate the datacenter with new CloudStack zone. If I
delete the VMware
Hi Yiping,
See
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-EC0F7308-96AE-4089-9DD4-B42AF50AABDC.html
You should find a custom attribute to your virtual DC called something like
"cloud.zone" which I believe you have to wipe before you can re-add it to a
Hi, all:
I am creating a new CloudStack 4.11.2.0 instance with VMware hypervisors. I
have some general questions regarding such a set up:
My first attempt had some errors, so I decided to blow away the CloudStack
database and start from scratch again. Now when I try to add VMware datacenter
