The most common method, for this, is to destroy your Basic zone and start over. Obviously that doesn't fit your needs. Would creating a second Advanced zone, and leaving the Basic zone in place, be a possibility?

Some of what you are trying to do may be possible, but there would be a lot more information required.

Starting with the ones I can think of...

What hypervisor version?
Do you have unused hypervisors or are you trying to re-purpose the same ones?
Do you have a second "management" network subnet available or are you going to have the two zones live together at least temporarily.
Were your current templates uploaded as "cross zone" templates?
Is your "Primary Storage" local or shared?
Is it possible to have downtime for the "running" instances? The IPs will likely change if nothing else.

I'm sure there are others...

--Mike

Thanks Mike, for the response. Yes it's possible to set up an advanced zone leaving the basic zone in place however I'll need to be able to move or copy the templates and ISOs across.

I'm using CloudStack 3.0.6 and so my hypervisors are currently XenServer 6.0.2 since 6.1 is not supported. I have only one hypervisor unused but we were thinking of migrating existing stuff to one or two hypervisors and repurpose the others into another cluster. For network, yes we have another management subnet that we can use. I'm not sure exactly what you mean by "cross zone" templates but all our templates were uploaded with the "All Zones" option, which I guess means "cross zone". Primary storage is shared and yes we can afford some downtime to migrate the running instances. IP changes can be managed as well.

What I've been thinking of is to have some downtime, export the running VMs, create the new zone and import them back. As for the templates we still have the original images and can register them in the new zone but I guess using the same management server the "cross zone" templates should be accessible in the new zone.

Any other thoughts?

@osay

Sorry, "All Zones" is recorded as cross_zone in the DB.

I would create a new pool, in XenCenter, with the available node has the only member. Create a new zone in CCP, with a new pod and new cluster (of one host). Make sure the new cpvm and ssvm launch and verify that the templates get downloaded properly. If they don't re-register them.

Create a new instance and a new isolated network. This assumes you will be using an isolated network, if you want to use a "shared" network, you will need to create it prior to instance creation.

Once everything looks good, you can shutdown the instances in your Basic zone and upload the disk to your advanced zone.

When you have empty hosts, in your basic zone, you can remove them, and re-install XenServer. (Remembering not to install the cloud-supplemental-pack)

Assuming they are like systems, you could then add the new host to the pool in XenServer then add the host to the cluster in CCP.

Let us know how it goes.

--Mike

Will do Mike.