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 may 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 

...

• If you've tried previously to configure CS within your environment and it has not worked, before you begin, make sure you environment is clean from all previous attempts. I will use VSphere 5 as an example, translate it to a hypervisor of your choice.
• Remove all network modifications on your Hypervisors/Cluster created by CS
• Remove all storage modifications on your Hypervisors/Cluster created by CS
• Remove all the content from NFS primary and secondary datastore (i'm making assumption that data is not needed) or present a new primary and secondary NFS datastore
• Remove all the references from CS about the zone/pod/cluster/storage/networks/hosts you attempted to add but failed
  If there are remnants of previous setup - there is a chance your Zone Deployment may fail - therefore, please confirm that your environment is pristine is in pristine state as it was pre-CloudStack CloudStack Zone Deployment operation

Pretext

The example environment in this tutorial consists of:

Physical gear and OS:

• 3 x HP BL465 G8 Servers as hypervisors
• Each hypervisor has 6 NICs
• VmWare vSphere 5.0 u1 and Virtual Center 5.0

Hypervisor Network Layout -  same on all 3 hosts:

---------------------------------------------------------------

• vSwitch0 - Virtual Switch for Management - 2 Physical NICs assigned 

  ...

  • • Management Network - Portgroup for Management vnic vmk0

    ...

    • • • NO VLAN TAGGING

    ...

    • vSwitch1 - Virtual Switch for vMotion Network - 2 Physical NICs assigned

    ...

    --------------------------------------------------------------

    • • vMotion - PortGroup for vMotion operations
        • NO VLAN TAGGING

    ...

    • vSwitch2 - Virtual Switch for Guest VMs TRUNK Network - 2 Physical NICs assigned
      • MGMT - PortGroup for VMs on Management Network
        • VLAN TAG/ID 1045

    ...

    • • DEV - PortGroup for VMs on Development Network
        • VLAN TAG/ID 1075

    Step 1: Import system template

    ...