This is the process I use.

In XenCenter:

1. Pick a pool master from one of your hypervisors
2. Configure the networking/nics on this hypervisor, creating logical network labels for use in CloudPlatform.
3. Create a pool of this one node.
4. Added other hypervisors to this pool and watch their networking stuff get automatically configured.

In CloudPlatform:

1. Create Zone/Pod/Cluster, etc.
2. When adding Hosts, only add the pool master. The rest will be added for you.
3. Enjoy the glory that is CloudPlatform...

--Mike

<p>Cloud will pool XenServer when you add a second hosts into your pod.  The only configuration that you need to do before adding your hosts to the cloud is to add your networking configuration including any bonding as cloud cannot set this up.  Make sure you install the cloud supplemental pack. It is also worth applying any hotfixes as they are harder to apply once added to the cloud.</p><p>Once your hosts are updated, supp pack applied and networking applied to your first host you can add this host to the cloud.  Once all completed you can add your second host.  The cloud should now convert the first host to a pool master and add the second host to the pool which will copy the configuraton from the first host.  As this can take a few seconds especially if you have bonding your may find the the second XenServer does not respond in time and the host add will fail.  Repeat the host add and it should work the second time.</p><p>James</p>

<p>Please remember that installing the Cloud Supplemental Pack is only required when building a "Basic" zone with security groups. Unless the recommendation has changed in recent versions, having the CSP installed will cause problems with other zone types.</p><p>--Mike</p>

mlittle.redapt wrote:
This is the process I use.

In XenCenter:

1. Pick a pool master from one of your hypervisors
2. Configure the networking/nics on this hypervisor, creating logical network labels for use in CloudPlatform.
3. Create a pool of this one node.
4. Added other hypervisors to this pool and watch their networking stuff get automatically configured.

In CloudPlatform:

1. Create Zone/Pod/Cluster, etc.
2. When adding Hosts, only add the pool master. The rest will be added for you.
3. Enjoy the glory that is CloudPlatform...

--Mike

Thanks for the advice, that seems to have worked a treat... hard to tell because i now have an issue starting up the SSVM and Console Proxy VM, and i think its network related.

I believe the relevant error is..

"You tried to create a VLAN on top of another VLAN - use the underlying physical PIF/bond instead"

In Xenserver the following networks on the first node in the cluster:

Name=cloud-guest
NIC=NIC2
VLAN=400

Name=cloud-public
NIC=NIC2
VLAN=102

Name=cloud-storage
NIC=Bond3+8
VLAN=100

Name=Bond3+8 (this is the bonded network using NICs 3 and 8, created for storage traffic)
NIC=Bond3+8

Name=management
NIC=NIC1
VLAN= N/A

I have assigned two IP addresses as follows:

Interface=Management
Network=management
NIC=NIC1
IP Address= 10.103.0.x/24

Interface=cloud-storage
Network=cloud-storage
NIC=Bond 3+8
IP Address= 10.103.6.x/24

I then created a pool, which replicated these settings to the other pool members... all good so far

I then started the CloudPlatform zone configuration and setup the following physical networks:

Network1
Name - management
Traffic type - Management
Traffic label - management
IP Ranges - 10.103.0.150 - 199

Network2
Name - cloud-guest
Traffic label - cloud-guest

Network3
Name - cloud-public
Traffic type - Public
Broadcast domain - VLAN
Traffic label - cloud-public
IP Ranges - 10.103.8.0/22
VLAN 102

Network4
Name - cloud-storage
Traffic type - Storage
Broadcast Domain - Native
Traffic label - cloud-storage
IP Ranges - 10.103.6.0/24
VLAN 100

Going through the management server logs it seems as though the SSVM deployment is fine (selects a host, allocates IPs to eth, etc)... however it fails with the following:

You tried to create a VLAN on top of another VLAN - use the underlying physical PIF/bond instead
at com.xensource.xenapi.VLAN.create(VLAN.java:349)
2013-05-17 14:16:41,851 DEBUG http://xen.resource.CitrixResourceBase (DirectAgent-5:null) Creating VLAN 102 on host 10.103.0.18 on device eth2
2013-05-17 14:16:41,947 WARN http://xen.resource.CitrixResourceBase (DirectAgent-5:null) Catch Exception: class com.xensource.xenapi.Types$PifIsVlan due to You tried to create a VLAN on top of another VLAN - use the underlying physical PIF/bond instead

do i need to remove the VLAN config in Xenserver?

Thanks for any advice

Looks like you have vlans configured in two places, for cloud-public and cloud-storage. You are hitting the error on cloud-storage, but will soon hit it on cloud-public, as well. The vlan id only needs to be configure in one place, either via CloudPlatform, or directly on the XenServer. Since you already have your pool configured, I would remove it in CloudPlatform.

Remember to fix both cloud-storage and cloud-public.

--Mike

cheers mike

think i've spotted the issue... i've been trying to set up a xenserver network for each traffic type... when instead i should just set up one network tagged "guest-public" on NIC2

then in CP i need to set up the separate physical networks (with VLANs), with both "guest" and "public" pointing to the "guest-public" network

its a learning experience!

Andy