Page History

...

Before you begin - you can see my cluster network setup in Virtual Center. I've removed all the remnants of existing CS network setup as i've done this several times before.
 

This screenshot shows the storage setup - also clean from previous CS storage setup attempts.
 

Next is to import the System VM image for VmWare.
 

Login to CS with user that has admin privileges, this screenshot has Citrix CloudPlatform Logo - which is a bug that will be addressed in CS4.0.1
 

Navigate to Infrastructure > Zones, click Add Zone  Zone
 

Choose Advanced Zone

. 

Complete the required fields for Setup Zone page Image Removed
  Image Added

When you get to Setup Network, define your Physical Network Names, in my case I created 4 Physical Networks - as defined in Network Map above.

Note that I've placed CS Management and Storage Traffic on vSwitch0 on vSwitch0-CS-Dev-MGMT-PN

The public Public traffic on vSwitch2-CS-Dev-Public-PN

The Guest traffic for 2 of my tagged VLANs on vSwitch2-CS-Dev-MGMT-PN and vSwitch2 and vSwitch2-CS-Dev-DEV-PN.

.  

Illustration above has 3 Physical Networks - as defined in Network Topology Map.

vSwitch-0-CS-Management contains 2 CS Networks, Management and Storage. Edit both of these network by pressing Edit button and define your desired vSwitch. In my case, i pointed both to vSwitch0.

This will tell CS what vSwitch to use when these networks are created during deployment zone process.

vSwitch2-MGMT Contain 2 VM Networks, Public and Guest. By definition you can only have 1 Public network and multiple Guest networks. Edit both networks and define your vSwitch. In my case, i have vSwitch2 defined for both.

vSwitch2-DEV Contain 1 VM Network - Guest.  Edit the network and define your vSwitch. In my case, i've used vSwitch2 .

Note: I took a shortcut in this demo, more appropriate way would have been to split vSwitch2-MGMTinto vSwitch2-Public and vSwitch2-MGMT and define 1 network for each respectively, making a total of 4 physical networksPress Edit on each Traffic Type and and specify the respective VmWare vSwitch (reminder you must use non distributed virtual switch - the support for dVs will be in CS version 4.1). Image Added
Once you've defined all VMWare Traffic Labels for all of your Traffic Types, proceed to the next step.

Screenshot shows how i've defined 2 Public Networks for DEV and MGMT. This is only required of your are using Isolated Mode in your Network Offering. To make an analogy of what Isolated mode means, look at how AWS does IaaS. They offer an Internal IP address as well as External IP address. If If you are planning to run your environment in traditional manner where NATing is handled by Firewalls, your don't need to define Public Network for your guest VMs. .  A small public network IP range is required only for Management VMs.

Image Added
Define you POD on the page below as well as IP space for CS Management  Network Image Added

I've purposely left VLAN Range blank for both Physical Networks on Guest Traffic and will do this through API/CLI commands later. This function has not worked as expected through UI interface and Network has not been created. Image Added
On the Storage Traffic page, define the IP range for your storage network. For simplicity, i did not use a VLAN tagged network. Image Added
The screenshot below defined the VmWare cluster information, you will need a user that is able to login to a virtual center with administrative privileges.  Image Added
Primary storage is where your guest VMs are going to live.In this example its NFS based, make sure you have proper network access to CS and your hypervisors. Image Added
Secondary storage is where your templates are going to reside, make sure it has proper network access to CS and your hypervisors.
Image Added
Last but not least - if you've done everything properly, you should see a Ready Page to Launch a Zone. Image Added
I'd strongly recommend to open Virtual Center and look for all the progress CS makes when it goes through the setup process. At the same time, i would launch an ssh session to cloudstack server and tail the /var/log/cloud/management/management-server.log.

Note that you will be getting occasional warning and errors - as it tries to deploy multiple components - this is normal. 

The initial setup process may take upto 10 minutes depending on your environment. I'd recommend to wait it out and proceed only once the initial setup is successful. 

Here is an example of what you may see...

.  

. 

. 

. 

. 

. 

. 

. 

. 

. 

. 

. 

...