Introduction to DoC Private Cloud

http://cloudstack.doc.ic.ac.uk/client

DoC Requirements

• Easily provisioned VMs• GUI & API available to complete tasks e.g. creating

accounts & Virtual Machines (VMs)• Availability of Shared (NetAPP) & Local disk offerings• Configure memory/cpu/storage, and choose which

supported OS to install (eg. Ubuntu, CentOS).• Accounting system for recording and resource-usage.• Users can be root on VMs and install packages.

Available Hardware:• 4 x Dell PowerEdge C6220 compute servers. This is a very dense compute

server, with four independent nodes in a two unit chassis. Each node contains two Intel Xeon E5-2690 8-core 2.9GHz processors (32 threads with hyper-threading), 128GB of RAM and two 1TB hard drives.

• 2 x IBM System x3750 M4. Each server has four Intel Xeon E5-4650 8-core

2.7GHz processors (64 threads with hyper-threading), 512GB of RAM, two 300GB hard drives and twelve 1TB hard-drives.

• 4 x Dell PowerEdge R720. Each server has two Intel Xeon E5-2640 2.50GHz six-

core 2.5Ghz processors (24 threads with hyper-threading), 64GB of RAM, two 300GB hard drives and 24 1TB hard-drives.

• 1 x NetApp NetApp F2240A-2 dual-controller Filer and disk-shelf; raw storage

capacity 60TB. • 4 x Extreme Summit X670 10GbE switches.

Software used for the setup:For CloudStack Management Nodes:• Hardware HA: CentOS Linux Cluster (2 nodes) ==> controls

resources: VIP, HAProxy, CS (MGMT & Usage services) & MySQL DB share via iSCSI NetApp LUN.

• CloudStack Management Interface Load Balanced: HAProxy • Database - MySQL Virtualised Management Farm• Hypervisor: Xen Cloud Platform v1.6 (XCP) • Support VM migration from local -> shared storage & vice

versa

API coding

• Cloudmonkey : Python-based command line utility for interacting with Apache CloudStack IaaS clouds

• HTTP encoded queries via perl/python/php scripts

CloudStack Lingo• Zones• Pods• Clusters• Domains• Projects• Accounts• Users• Templates/ISO images• Service offerings: System (CPU & RAM) & Disk• Instances (VMs)

Zone

Etiquette

• Provide a meaningful display name (hostname).

e.g. <userid>-vmxx• Unused VMs should be deleted. • Limit the creation of VMs (as it takes up

unnecessary resources and bandwidth)• VMs are not backed up.

User accessibility:

• via API commands using API & Secret Keys for authentication

• User logins currently linked to LDAP • Local users could be created in a separate

domain.• S3 and EC2 API compatibility

Future improvements

• CSG Maintained VM Templates• Setup MySQL Galera Cluster (Master - Master)

setup • Upgrade CloudStack -> 4.2 (July 2014)• System Usage Accounting

And Finally ...

• 3rd year project is currently using it.• Q & A• Demos

http://cloudstack.doc.ic.ac.uk/client