...
VmWare Virtual Switch | CS Physical Network | VmWare PortGroup Name | Network | Subnet | Gateway | VLAN TAG | CS Traffic Type | Network IP Range |
---|---|---|---|---|---|---|---|---|
vSwitch0 | vSwitch0-CS-Dev-MGMT-PN | Management Network | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | NONE | CS Management | 10.25.243.140 - 10.25.243.146 |
vSwitch0 | vSwitch0-CS-Dev-MGMT-PN | Management Network | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | NONE | CS Storage | 10.25.243.147 - 10.25.243.149 |
vSwitch2 | vSwitch2-CS-Dev-Public-PN | MGMT | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | 1045 | Public | 10.25.243.195 - 10.25.243.199 |
vSwitch2 | vSwitch2-CS-Dev-Public-PN | DEV | 10.28.18.0 | 255.255.254.0 | 10.28.18.1 | 1075 | Public | 10.28.19.195 - 10.28.19.199 |
vSwitch2 | vSwitch2-CS-Dev-MGMT-PN | MGMT | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | 1045 | Guest | 10.25.243.150 - 10.25.243.194 |
vSwitch2 | vSwitch2-CS-Dev-DEV-PN | DEV | 10.28.18.0 | 255.255.254.0 | 10.28.18.1 | 1075 | Guest | 10.28.19.150 - 10.28.19.194 |
...
Before you begin - you can see my cluster network setup in Virtual Center. I've removed all remnants of existing CS network setup as iI've done this several times before.
...
To test it, run "list zones" command, the example screenshot is below.
...
In order for VMs to have network functinality we need to create a network offering and networks.
...
In order to create the Network Offerings, we must first Tag our Guest Traffic in Physical Networks in CloudStack.
Navigate to Infrastructure, Zones, choose your Zone and press on Physical Network.
...
Press on each Physical Network that has a Guest Traffic Type and define a tag. My setup has only 2 Guest Traffic Types, 1 in each Physical Network respectively. In the example below, you will see that I use {Physical Network Name}-Guest-tag, this naming convention is optional and only my preference. Make sure to leave VLAN information blank, we will do this portion through API/CLI shortly.
RAW IMAGES - NOT YET DOCUMENTED
...
Upon completion, navigate to Service Offerings and choose Network Offering from the drop down menu and press on "Add network offering" button. In this example, I kept it very basic and only enable DHCP, DNS and UserData services that are offered by Default Virtual Router system offering that comes with CS. For the proof of concept, i suggest keeping it simple - you can revisit this section and add more services once you get your environment functional with VLAN tagging.
Once you service offering has been created, open it by pressing on its name and enable it.
In order to create the networks for each of our Guest Traffic Types, we need to get the following information from API/CLI.
ZoneID - the ID of the zone you've created in Step 3
NetworkOfferingID - the ID of the network offering created in Step 5
PhysicalNetworkID - in this example i have 2 physical network ID
Network Information - this includes ip range, subnet mask, gateway and vlan for each Guest Traffic.
Below is the set of screenshots and commands i run in order to get the required IDs.
Code Block |
---|
list zones | grep -iE 'id|name|----'
list networkofferings | grep -iE 'id|name|----'
list physicalnetworks
|
Note the required IDs and keep them handy for the next step of creating a network. You can see the command i've executed below. This screenshot shows an example of how I created the CS-DEV-vSwitch2-DEV-Network
One more run for the CS-DEV-vSwitch2-MGMT-Network
If all is done correctly, you can navigate to a Networks in CS and see your Networks displayed.
Almost done, in order to activate these networks, we will need to deploy an instance from one of the templates and choose the network offering you've created. I'm not putting any screenshots for that part - as I assume you know how to do that.
If for some reason, the deployment did not go as expected, here are some pointers of what you can do to understand and correct the issue.
How to get more help?
CloudStack community is very involved and helps users fairly quickly.
First, please search the existing mailing lists for cloudstack-users and cloudstack-dev on http://markmail.org/
Reach out to cloudstack-users mailing list and join our IRC channel on irc.freenode.com - channel #cloudstack
This document is written and maintained by ilya musayev, IRC: serverchief