Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
LAB MANUAL
List of experiments
SN Title CO
1 Registration with IaaS cloud service provider (e.g. AWS / Cisco etc.) List and CO1
compare different CSPs based on the services provided.
2 Registration with PaaS cloud service provider (e.g. Google App Engine, CO1
Force.com, etc). List and compare different CSPs based on the services
provided.
3 Registration with SaaS cloud service provider (e.g. SalesForce.com, Google+, CO1
etc). List and compare different CSPs based on the services provided.
4 Developing and deploying an application in cloud using Google App engine. CO3
5 Installation of hosted and/or bare metal hypervisor and create multiple VM. CO2
6 Communication between different Virtual Machines. CO2
7 Installation of Private or Public cloud using Eucalyptus / Open Stack CO4
8 Case study: Cloud Service Provider (CSP) Infrastructure CO5,CO6
Aim: Registration with public cloud service provider (IaaS, PaaS, SaaS) like Salesforce / AWS/
Google / Zoho/ etc. List and compare different CSPs based on the services provided.
Objective: To make learners aware of public cloud service providers and registration process
Experiment No 2
Aim: Developing and deploying an application in cloud using Google App engine
Objective: To make Learners aware of cloud Infrastructure Service model
Procedure: Learner develops application local or remotely and deploy it on google App Engine
Experiment No 3
Experiment No 4
Outcome: Learners can show multiple virtual machines running different operating systems
simultaneously using hypervisor.
Experiment No 5
Aim: To create multiple Virtual Machines and communication with each other.
Objective: To make Learners aware of VM networking
Outcome: Learners can show multiple virtual machines communicating different operating
systems simultaneously using hypervisor.
Experiment No 6
1. Configure the Eucalyptus package repository on each host that will run a Eucalyptus
component:
yum install
http://downloads.eucalyptus.com/software/eucalyptus/4.0/centos/6/x86_64/eucalyptus-
release-4.0.el6.noarch.rpmEnter y when prompted to install this package.
2. Configure the Euca2ools package repository on each host that will run a Eucalyptus
component or Euca2ools:
yum install
http://downloads.eucalyptus.com/software/euca2ools/3.1/centos/6/x86_64/euca2ools-
release-3.1.el6.noarch.rpm
3. Configure the EPEL package repository on each host that will run a Eucalyptus
component or Euca2ools:
yum install
http://downloads.eucalyptus.com/software/eucalyptus/4.0/centos/6/x86_64/epel-release-
6.noarch.rpm
4. If you are using Walrus as your object storage backend configure the ELRepo repository
on each machine that will run Walrus. Otherwise, skip this step.
yum install
http://downloads.eucalyptus.com/software/eucalyptus/4.0/centos/6/x86_64/elrepo-
release-6.noarch.rpm
5. For RHEL 6 systems only, you must enable the Optional repository in Red Hat Network
for each NC, as follows:
a. Go to http://rhn.redhat.com and navigate to the system that will run the NC.
b. Click Alter Channel Subscriptions.
c. Make sure the RHEL Server Optional checkbox is checked.
d. Click Change Subscriptions.
6. If you are a Eucalyptus subscriber and use VMware Broker, install the VMware Broker
packages on the hosts that will run your Cluster Controller (CC) and Cloud Controller
(CLC), as follows:
7. Note: Clouds that use the VMware hypervisor do not have NCs; if you plan to use
VMware then skip this step.
Install the Eucalyptus node controller software on each planned NC host:
ls -l /dev/kvm
Verify the output shows that the device node is owned by user root and group kvm.
crw-rw-rw- 1 root kvm 10, 232 Nov 30 10:27 /dev/kvm
8. On each planned CLC host, install the Eucalyptus cloud controller software
9. Install the Imaging Worker image package on the machine hosting the primary CLC:
10. Install the software for the remaining Eucalyptus components. The following example
shows most components being installed on the same host. We recommend that you use
different hosts for each component:
11. If you would like Load Balancer support enabled in your Cloud, you will need to install
the Load Balancer image package on the machine hosting the primary CLC:
12. After you have installed Eucalyptus, test multicast connectivity between each CLC and
Walrus, SC, and VMware broker host.
a. Install the the network tomography package on the Cloud Controller, Cluster
Controller, Storage Controller, and any machines running Walrus or VMware
Broker.
Experiment No 7
Experiment No 8
Aim: Case study any Cloud Service Provider (CSP) Organization’s Infrastructure
Objective: To make Learners aware of commercial cloud service providers infrastructure
(Google, Amazon, Rackspace etc )