cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag Sonstebo <>
Subject Re: questions on cloudstack and VMware hypervisors
Date Wed, 22 May 2019 16:27:00 GMT
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 available modules - but if you check the jinja template there are a lot of conditionals
in there which would be painful to handle in Ansible, hence we're happy with how this works
for now.

Dag Sonstebo
Cloud Architect

On 22/05/2019, 17:07, "Yiping Zhang" <> wrote:

    Hi, Dag:
    Thanks for the quick reply.
    Yea, that is it!. The custom attribute "" 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 datacenter from zone in web
UI, its value will be set to false.
    Regarding the ansible modules,  I am wondering why did you choose to generate a shell
script to deploy a CloudStack env, instead of directly do it with Ansible?  Is it because
the Ansible module for CloudStack is still incomplete to fulfill all tasks or for some other
historic reasons?  For example, I could have missed it,  but I could not find a module to
add a VMware datacenter to a zone.
    On 5/22/19, 1:49 AM, "Dag Sonstebo" <> wrote:
        Hi Yiping,
        You should find a custom attribute to your virtual DC called something like ""
which I believe you have to wipe before you can re-add it to a new CloudStack instance. If
the above doesn't work you may have to drop to command line and do it with something like
        With regards to deploying a full zone this is part of what Trillian;;sdata=wL65BH1bbJdG54fOlkRE5F1iRcSyT24p1aj0VqPUBFg%3D&amp;reserved=0
does in it's cloudstack-config role - but please be aware this role simply populates a ""
jinja template with the right options before running this as a normal bash script.
        Dag Sonstebo
        Cloud Architect
        On 22/05/2019, 06:31, "Yiping Zhang" <> wrote:
            Hi, all:
            I am creating a new CloudStack 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 to the zone, I receive
an error message saying that: “Failed to add VMware DC to zone due to : This DC is being
managed by other CloudStack deployment. Cannot add this DC to zone”
            This sounds like my last try has left something on the datacenter in vCenter so
that I can’t associate it to another zone any more. If this is true, do I have to blow away
the datacenter in vCenter as well to start over again? Is there any way to clean up on the
vCenter side without rebuilding the datacenter?  In hindsight, I should have deleted all CloudStack
objects from web GUI instead of taking the nuclear option of blowing away the database!
            A related question,  has anyone used CloudStack ansible module to deploy a complete
zone (including all necessary objects zone/pod/physical networks/cluster/host/primary_storage/secondary_storage
etc)?  If so, would you mind sharing your ansible playbook(s)?
        Amadeus House, Floral Street, London  WC2E 9DPUK
Amadeus House, Floral Street, London  WC2E 9DPUK

View raw message