Page History

This guide is geared more towards CS 4.0 (build 140) and vSphere5, however, the same concept should apply to other hypervisors types like KVM and XEN. This is NOT a beginners guide, please use your judgement and substitute values as necessary.

Disclaimer

The CS4.0 build 140 is defined on purpose in this document - there are known UI issues that have been already addressed - however, since no update/patch has been officially released to address these issues (at the time of this writing)  - in order to configure Advanced Networking - we must use API calls to substitute what GUI could not accomplish. The newer releases

...

should address the UI limitations and API calls may not be necessary. Nevertheless, its a good learning experience.

What This Guide Covers

• CloudStack Advanced Network Concepts
• Physical Networks and Mapping
• VLAN Tagging
• Usage of Virtual Switches
• Network Offerings
• API Usage and CloudMokey CLI
• Troubleshooting 

...

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 this example, we have a 3 node VmWare vSphere 5 cluster

...

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. If you would like to move your CS Management VMs to VLAN TAGed 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. 

Network we need to define before we begin:

• CloudStack Networks
  • Management  - used by management nodes
  • Storage - used by secondary storage node
• VM Instance Networks 
  • Public - network used for VMs and Internet
  • Guest - network used for internal VM communication

Below is the sample table created for easy of IP space accounting