Page History

...

/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary/ -u http://download.cloud.com/templates/burbank/burbank-systemvm-08012012.ova -h vmware

Step 2: Create a network

...

topology map for your reference

It is recommended to create layout of how you believe CloudStack IP allocation will take place, hence a quick write up of what networks get what assignments is very helpful. In my case, i wanted to be able to deploy DEV and MGMT VMs on vSwitch2 that uses VLAN tagging, while CS Managment/Storage VMs would reside on vSwitch0 (w/o VLAN tag). If you would like to move your CS Management VMs to VLAN tag'ed network -  you will need to confirm that you meet minimum requirements for CS described in Setup Guide and alter the CS Global Settings to change the default portgroup name "Management Network" for vmware - if its different. 

...

Navigate to Infrastructure > Zones, click add a zone

Image Added

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

.  Image Added
e Image Added
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.