%BOOK_ENTITIES; ]> As we noted before we will be using security groups to provide isolation and by default that implies that we'll be using a flat layer-2 network. It also means that the simplicity of our setup means that we can use the quick installer.

To get access to CloudStack's web interface, merely point your browser to http://172.16.10.2:8080/client The default username is 'admin', and the default password is 'password'. You should see a splash screen that allows you to choose several options for setting up CloudStack. You should choose the Continue with Basic Setup option. You should now see a prompt requiring you to change the password for the admin user. Please do so.

A zone is the largest organization entity in CloudStack - and we'll be creating one, this should be the screen that you see in front of you now. And for us there are 5 pieces of information that we need. Name - we will set this to the ever-descriptive 'Zone1' for our cloud. Public DNS 1 - we will set this to '8.8.8.8' for our cloud. Public DNS 2 - we will set this to '8.8.4.4' for our cloud. Internal DNS1 - we will also set this to '8.8.8.8' for our cloud. Internal DNS2 - we will also set this to '8.8.8.4' for our cloud. CloudStack distinguishes between internal and public DNS. Internal DNS is assumed to be capable of resolving internal-only hostnames, such as your NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve public IP addresses. You can enter the same DNS server for both types, but if you do so, you must make sure that both internal and public IP addresses can route to the DNS server. In our specific case we will not use any names for resources internally, and we have indeed them set to look to the same external resource so as to not add a namerserver setup to our list of requirements.

Now that we've added a Zone, the next step that comes up is a prompt for information regading a pod. Which is looking for 4 items. Name - We'll use Pod1 for our cloud. Gateway - We'll use 172.16.10.1 as our gateway Netmask - We'll use 255.255.255.0 Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20 Guest gateway - We'll use 172.16.10.1 Guest netmask - We'll use 255.255.255.0 Guest start/end IP - We'll use 172.16.10.30-172.16.10.200

Now that we've added a Zone, we need only add a few more items for configuring the cluster. Name - We'll use Cluster1 Hypervisor - Choose KVM You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed. Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server. Username - we'll use 'root' Password - enter the operating system password for the root user

With you cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields: Name - We'll use 'Primary1' Server - We'll be using the IP address 172.16.10.2 Path - Well define /primary as the path we are using

If this is a new zone, you'll be prompted for secondary storage information - populate it as follows: NFS server - We'll use the IP address 172.16.10.2 Path - We'll use /secondary Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize.