THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
VmWare Virtual Switch | CS Physical Network | VmWare PortGroup Name | Network | Subnet | Gateway | VLAN TAG | Network 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 |
...
Moreover, the concept of Public IP space in Advanced Network Shared setup does not apply - as it is meant to be used for internal Non-Isolated network. Therefore, i've allocated a very small amount of public IP space that will be used by CS management VMs only. If you are using Isolated mode, then you should assign more public IP addresses.
Step 3: Add Zone/POD/Cluster
...
via UI
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.
...
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.
RAW IMAGES - NOT YET DOCUMENTED
.
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
. 
Before we proceed, make sure that Storage VM (s-XXX-VM) and Proxy VM (v-XXX-VM) have been deployed.
At this point we are half way done and will proceed to a more sophisticated part of this tutorial.
Step 4: Creating API Keys and Signature for CloudMonkey CLI
CloudStack provides a CLI called CloudMonkey. To install CloudMonkey, please visit this CloudMonkey Tutorial for detailed instructions. Once installed, proceed with generating required keys.
Navigate to Accounts tab and select the desired user (admin privileges required)
Once on Users Tab, click on "View Users" to see additional permission and settings for this user.
Under Details Tab, press on the Key Icon to generate the API Keys.
Launch CloudMokey CLI in your ssh terminal and setup the initial settings/attributes in order for CLI to interact with CloudStack core server.
| Code Block |
|---|
> set host <CS-hostname>
> set port 8080
> set apikey <put-your-api-key-for-your-user>
> set secretkey <put-your-secret-key-for-your-user>
> set prompt mycloudmonkey>
|
To test it, run "list zones" command, the example screenshot is below.
Step 5: Creating Network Offering and Networks
In order for VMs to have network functinality we need to create a network offering and networks.
Network Offering is a collection of network services VM will have an access to. For example, if you would like to have DHCPD, DNS, LoadBalancing and UserData services offered, we need to create Network Offering with following services.
In order to create the Network Offerings, we must first Tag our Physical Networks in CloudStack.
Navigate to Infrastructure, Zones, choose your Zone and press on Physical Network.
RAW IMAGES - NOT YET DOCUMENTED
. 
Overview
Content Tools
Apps