Apache Cloudstack 4.3 Installation - Part 2

Apache Cloudstack ​As the name suggests, this is the second part of two articles on how to install Apache Cloudstack.  Part 1 can be found here.

This part picks up from the point where we have managed to actually install Cloudstack and have just managed to login.  The tasks covered in this article are:

  • Create a zone
  • Create a pod
  • Create a cluster
  • Add primary and secondary storage
  • Launch the zone
  • Add XenServer 6.2 hypervisor

Create a Zone

It used to be that the Zone was the highest level way of logically grouping cloud infrastructure inside of Cloudstack.  Cloudstack now has a concept of a Region, in which multiple Zones can reside.  In fact the Zone that we create now will actually sit inside of the default Region.  For further information please refer to the official documentation.

  • Logon to Cloudstack as admin at http://192.168.4.4:8080/client/
  • Click on 'Infrastructure' from the left hand side menu
  • Click 'View all' on the Zones box in the main window
  • Click '+ Add Zone' in the upper right of the main window.  A modal 'wizard' will appear in the screen

Zone Type

  • Click 'Advanced' followed by 'Next'

Zone Setup

  • Fill in the 'Setup Zone' step as shown in the following table.  Some of the labels are a little bit cryptic.  Please refer to this page in the installation guide for more information
Zone Setup
Field Value
Name: zone01
IPv4 DNS1: 8.8.8.8
IPv4 DNS2: 8.8.4.4
IPv6 DNS1: <leave blank>
IPv6 DNS2: <leave blank>
Internal DNS 1: 192.168.4.3
Internal DNS 2: <leave blank>
Hypervisor: XenServer
Network Domain: <leave blank>
Guest CDIR: 10.1.1.0/24
Dedicated: <leave de-selected>
Local storage enabled: <leave de-selected>

Setup Network - Traffic Labels

It is important to get this configuration correct.  This is where we use the interface names we setup in the hypervisor in Part 1. 

  • Label the top network 'Cloud-Management'.
  • Drop and drag the icons of 'Management' and 'Storage' onto this physical network
  • Leave the 'Isolation method' as 'VLAN'
  • Edit the Management traffic and complete the 'XenServer Traffic label as 'Cloud-Management'
  • Edit the Storage traffic and complete the 'XenServer Traffic label as 'Cloud-Management'
  • Label the second network 'Cloud-Public'.
  • Drop and drag the icons of 'Public' and 'Guest' onto this physical network
  • Leave the 'Isolation method' as 'VLAN'
  • Edit the Guest traffic and complete the 'XenServer Traffic label as 'Cloud-Public'
  • Edit the Public traffic and complete the 'XenServer Traffic label as 'Cloud-Public'

Setup Network - Public Traffic

In theory, we should allocate a proper public IP address range.  We don't have that but in order to make things clear we are using a distinct address range.  Use this table to fill out the required information:

Public Network Config Info
Field Value
Gateway: 10.200.10.1
Netmask: 255.255.255.0
VLAN/VNI: <leave blank>
Start IP: 10.200.10.100
End IP: 10.200.10.199
  • Click 'Add and then 'Next'

Setup Network - Pod

  • Fill in the form as below
Pod Setup
Field Value
Pod name: pod01
Reserved system gateway: 192.68.4.1
Reserved system netmask: 255.255.255.0
Start Reserved System IP: 192.168.4.30
End Reserved System IP: 192.168.4.59
  • Click 'Next'

Guest Traffic

If you think back, you will remember we selected 'Advanced Networking' for this zone.  This means (among other things) that guest traffic (more specifically inter-hypervisor guest traffic) will travel over tenant specific VLANs.  For our purposes, we do not many VLANS but in a production environment careful planning of VLANs is required

  • Type 100 and 199 for the VLAN/VNI range and click 'Next'

Cluster Setup

  • The next dialogue asks us to give our first cluster a name - type 'cluster01' and click 'Next'

Host For Cluster

  • Fill in the form according to your configuration and click 'Next'.  I would confirm that the Host Name that you enter can be pinged from the Cloudstack management server

Primary Storage

Remember that we have primary storage standing by.  It is a NFS server.

  • On this page, fill in the form with the details below
Primary Storage Details
Field value
Name: primary01
Scope: Cluster
Protocol: NFS
Server 192.168.4.5
Path /data/primary_storage
Storage Tags: <leave blank>
  • Before confirming, I would recommend checking that you can ping the primary storage server and that the NFS path is exported and visible
  • Click 'Next'

Secondary Storage

Remember that we have a NFS server standing by at 192.168.4.6

  • In the dropdown, select 'NFS'
  • Fill in the form as below:
Secondary (NFS) Storage
Field Value
Provider: NFS
name secondary01
Server: 192.168.4.6
Path: /data/secondary_storage
  • Please check that you can ping the secondary storage server and that the path is available via NFS protocol
  • Click 'Next'

Launch Zone

  • You can now go ahead and click 'Launch Zone'.  This will start the process of actually configuring the zone, pod, cluster, host, primary and secondary storage as per the entered information

Enable Zone

  • At the successful completion of all the tasks associated with Zone creation and configuration a dialogue box will appear asking you whether to enable the zone.  Click 'Yes'

Next Steps

Now that we have created a zone we can now start to properly validate the installation.  Here are the next steps

  • Upload an ISO image
  • Create a virtual machine
  • Snapshot a virtual machine
  • Add another hypervisor to the cluster
  • Create a virtual machine on a second hypervisor and attempt to communicate between the two VMs via the tenant specific VLAN

What these tests will do is verify that the internal components of Cloudstack are working as expected and that we don't have any issues internally in our configuration.