CS8711-Cloud Computing Lab
CS8711-Cloud Computing Lab
Komarapalayam - 637303
of the VII semester B.E CSE branch during the academic year 2021-2022 in
held on________________________________
Experiment
Date Name of the Experiment Marks Signature
No.
Install Virtualbox/VMware Workstation
1 22/09/21 with different flavours of linux or
windows OS on top of windows7 or 8.
Install a C compiler in the virtual machine
2 06/10/21 created using virtual box and execute
Simple Programs
Install Google App Engine. Create hello
3 13/10/21 world app and other simple web
applications using python/java.
Use GAE launcher to launch the web
4
20/10/21 applications.
OBJECTIVES:
LIST OF EXPERIMENTS:
Course Objective:
To develop web applications in cloud
To learn the design and development process involved in creating a cloud based application
To learn to implement and use parallel programming using Hadoop
Exercises:
1. Install Virtualbox/VMware Workstation with different flavours of linux or windows OS on top
of windows7 or 8.
2. Install a C compiler in the virtual machine created using virtual box and execute Simple
Programs
3. Install Google App Engine. Create hello world app and other simple web applications using
python/java.
4. Use GAE launcher to launch the web applications.
5. Simulate a cloud scenario using CloudSim and run a scheduling algorithm that is not present in
CloudSim.
6. Find a procedure to transfer the files from one virtual machine to another virtual machine.
7. Find a procedure to launch virtual machine using trystack (Online Openstack Demo Version)
8. Install Hadoop single node cluster and run simple applications like wordcount.
Course Outcome:
TOTAL: 45 PERIODS
CLOUD COMPUTING
DATE: 22/09/21
Aim:
Find procedure to Install Virtualbox/VMware Workstation with different flavours of linux or
windows OS on top of windows7 or 8.
PROCEDURE TO INSTALL
At the end you will see installation complete dialog box. Click finish and you are done with
the
installation process. You may be asked to restart your computer. Click on Yes to restart.
Step 11- Launch VMware Workstation
After the installation completes, you should see VMware Workstation icon on the desktop. Double
clickon it to launch the application.
o Please note that this is “NOT” a required part of the course and is not a
homework.
o This manual is written for someone who has never programmed / never
used Linux before.
o If you have background knowledge, you can ignore this.
1. Visit http://www.virtualbox.org/wiki/downloads
2. Download VirtualBox platform packages for your OS
3. Open the Installation Package by double clicking
MAC PC
Install VirtualBox
MAC
PC
CLI
CK
Install Linux using Virtual Box
MAC PC
Install Linux usingVirtual Box
MAC PC
Install Linux using Virtual Box
MAC PC
Install Linux using Virtual Box
MAC PC
Install Linux using Virtual Box
MAC PC
Install Linux using Virtual Box
MAC PC
Install Linux using Virtual Box
I2. Click the folder icon and choose the ubuntu isofile you
downloaded.
I3. Select the size of the Virtual Disk (I recommend
choosing 8 GB) and click continue
MAC PC
Install Linux using Virtual Box
MAC PC
Running Linux
MAC & PC
Running Linux
MAC PC
Running Linux
2. Click the folder icon and choose the ubuntu isofile you
downloaded and click continue and start
MAC PC
Running Linux
4. Choose “Erase disk and install Ubuntu” and click Forward (Don’t
worry, it won’t wipe your computer)
5.Type “gcc helloworld.c” to compile, and type “ls” to confirm that a new
executable file “a.out” is created
C Programming on Linux
This document describes the installation of the Google App Engine Software
Development Kit (SDK) on a Microsoft Windows and running a simple “hello world”
application.
The App Engine SDK allows you to run Google App Engine Applications on your local
computer. It simulates the run-time environment of the Google App Engine
infrastructure.
If you don't already have Python 2.5.4 installed in your computer, download and
Install Python 2.5.4 from:
http://www.python.org/download/releases/2.5.4/
You can download the Google App Engine SDK by going to:
http://code.google.com/appengine/downloads.html
1
Double Click on the GoogleApplicationEngine installer.
Click through the installation wizard, and it should install the App Engine. If you do
not have Python 2.5, it will install Python 2.5 as well.
Once the install is complete you can discard the downloaded installer
2
Making your First Application
Now you need to create a simple application. We could use the “+” option to have
the launcher make us an application – but instead we will do it by hand to get a
better sense of what is going on.
Make a folder for your Google App Engine applications. I am going to make the
Folder on my Desktop called “apps” – the path to this folder is:
And then make a sub--folder in within apps called “ae--01--trivial” – the path to this
folder would be:
Using a text editor such as JEdit (www.jedit.org), create a file called app.yaml in the
ae--01--trivial folder with the following contents:
application: ae-01-trivial
version: 1
runtime: python
api_version: 1
handlers:
- url: /.*
script: index.py
Note: Please do not copy and paste these lines into your text editor – you might end
up with strange characters – simply type them into your editor.
Then create a file in the ae--01--trivial folder called index.py with three lines in it:
Once you have selected your application and press Run. After a few moments your
application will start and the launcher will show a little green icon next to your
application. Then press Browse to open a browser pointing at your application
which is running at http://localhost:8080/
Paste http://localhost:8080 into your browser and you should see your
application as follows:
Just for fun, edit the index.py to change the name “Chuck” to your own name and
press Refresh in the browser to verify your updates.
Watching the Log
You can watch the internal log of the actions that the web server is performing when
you are interacting with your application in the browser. Select your application in
the Launcher and press the Logs button to bring up a log window:
Each time you press Refresh in your browser – you can see it retrieving the output
with a GET request.
With two files to edit, there are two general categories of errors that you may
encounter. If you make a mistake on the app.yaml file, the App Engine will not start
and your launcher will show a yellow icon near your application:
To get more detail on what is going wrong, take a look at the log for the application:
In this instance – the mistake is mis- indenting the last line in the app.yaml (line 8).
If you make a syntax error in the index.py file, a Python trace back error will appear
in your browser.
The error you need to see is likely to be the last few lines of the output – in this case
I made a Python syntax error on line one of our one--line application.
Reference: http://en.wikipedia.org/wiki/Stack_trace
When you make a mistake in the app.yaml file – you must the fix the mistake and
attempt to start the application again.
If you make a mistake in a file like index.py, you can simply fix the file and press
refresh in your browser – there is no need to restart the server.
To shut down the server, use the Launcher, select your application and press the
Stop button.
Vm vm = new Vm(vmid, brokerId, mips, pesNumber, ram, bw, size, vmm, new
CloudletSchedulerTimeShared())
9. Submit the VM list to the broker:
broker.submitVmList(vmlist)
10. Create a cloudlet with length, file size, output size, and utilisation model:
Cloudlet cloudlet = new Cloudlet(id, length, pesNumber, fileSize, outputSize, utilizationModel, utilizationMode
11. Submit the cloudlet list to the broker:
broker.submitCloudletList(cloudletList)
12. Start the simulation:
CloudSim.startSimulation()
Sample Output from the Existing Example:
Starting CloudSimExample1...
Initialising...
Starting CloudSim version 3.0
Datacenter_0 is starting...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>null
Broker is starting...
Entities started.
0.0 : Broker: Cloud Resource List received with 1 resource(s)
0.0: Broker: Trying to Create VM #0 in Datacenter_0
0.1 : Broker: VM #0 has been created in Datacenter #2, Host #0
0.1: Broker: Sending cloudlet 0 to VM #0
400.1: Broker: Cloudlet 0 received
400.1 : Broker: All Cloudlets executed. Finishing...
400.1: Broker: Destroying VM #0
Broker is shutting down...
Simulation: No more future events
CloudInformationService: Notify all CloudSim entities for shutting down.
Datacenter_0 is shutting down...
Broker is shutting down...
Simulation completed.
Simulation completed.
========== OUTPUT ==========
Cloudlet ID STATUS Data center ID VM ID Time Start Time Finish Time
0 SUCCESS 2 0 400 0.1 400.1
*****Datacenter: Datacenter_0*****
User id Debt
3 35.6
CloudSimExample1 finished!
EX NO:6 Find a procedure to transfer the files from
DATE: 27/10/21 one virtual machine to another virtual machine
1. You can copy few (or more) lines with copy & paste mechanism.
For this you need to share clipboard between host OS and guest OS, installing Guest Addition on
both the virtual machines (probably setting bidirectional and restarting them). You copy from guest
OS in the clipboard that is shared with the host OS.Then you paste from the host OS to the second
guest OS.
2. You can enable drag and drop too with the same method (Click on the machine, settings,
general, advanced, drag and drop: set to bidirectional )
3. You can have common Shared Folders on both virtual machines and use one of the
directory shared as buffer to copy.Installing Guest Additions you have the possibility to set
Shared Folders too. As you put afile in a shared folder from host OS or from guest OS, is
immediately visible to the other. (Keep in mind that can arise some problems for date/time of
the files when there are different clock settings on the different virtual machines).If you use
the same folder shared on more machines you can exchange files directly copying them in this
folder
4.You can use usual method to copy files between 2 different computer with client-server
application. (e.g. scp with sshd active for linux, winscp... you can get some info about SSH servers
e.g. here)You need an active server (sshd) on the receiving machine and a client on the sending
machine. Of course you need to have the authorization setted (via password or, better, via an
automatic authentication method).
Note: many Linux/Ubuntu distribution install sshd by default: you can see if it is running with
pgrep sshd from a shell. You can install with sudo apt-get install openssh-server.
5. You can mount part of the file system of a virtual machine via NFS or SSHFS on theother,
or you can share file and directory with Samba.You may find interesting the article Sharing
files between guest and host without VirtualBox shared folders with detailed step by step
instructions.
You should remember that you are dialling with a little network of machines with different
operative systems, and in particular:
Each virtual machine has its own operative system running on and acts as a physical
machine.
Each virtual machine is an instance of a program owned by an user in the hosting operative
system and should undergo the restrictions of the user in the hosting OS.
E.g Let we say that Hastur and Meow are users of the hosting machine, but they did not
allow each other to see their directories (no read/write/execute authorization). When each of
them run a virtual machine, for the hosting OS those virtual machine are two normal
programs owned by Hastur and Meow and cannot see the private directory of the other user.
This is a restriction due to the hosting OS. It's easy to overcame it: it's enough to give
authorization to read/write/execute to a directory or to chose a different directory in which
both users can read/write/execute.
Windows likes mouse and Linux fingers. :-)
I mean I suggest you to enable Drag & drop to be cosy with the Windows machines and
the Shared folders or to be cosy with Linux.
When you will need to be fast with Linux you will feel the need of ssh-keygen and to Generate once
SSH Keys to copy files on/from a remote machine without writing password anymore. In this way it
functions
bash auto-completion remotely too!
EX NO:7 Find a procedure to launch virtual machine
DATE: 24/11/21 using trystack (Online Openstack Demo Version)
TryStack.org Homepage
I assume that you already join to the Facebook Group and login to the dashboard. After you log
in to the TryStack, you will see the Compute Dashboard like:
OpenStack Compute Dashboard
In this post, I will show you how to run an OpenStack instance. The instance will be accessible
through the internet (have a public IP address). The final topology will like:
Network topology
As you see from the image above, the instance will be connected to a local network and the local
network will be connected to internet.
Step 1: Create Network
Network? Yes, the network in here is our own local network. So, your instances will be not
mixed up with the others. You can imagine this as your own LAN (Local Area Network) in the
cloud.
I guess you already know what router is. In the step 1, we created our network, but it is isolated.
It doesn’t connect to the internet. To make our network has an internet connection, we need a
router that running as the gateway to the internet.
Floating IP address is public IP address. It makes your instance is accessible from the internet.
When you launch your instance, the instance will have a private network IP, but no public IP. In
OpenStack, the public IPs is collected in a pool and managed by admin (in our case is TryStack).
You need to request a public (floating) IP address to be assigned to your instance.
1. Go to Compute > Instance.
2. In one of your instances, click More > Associate Floating IP.
3. In IP Address, click Plus [+].
4. Select Pool to external and then click Allocate IP.
5. Click Associate.
6. Now you will get a public IP, e.g. 8.21.28.120, for your instance.
OpenStack has a feature like a firewall. It can whitelist/blacklist your in/out connection. It is
called Security Group.
1. Go to Compute > Access & Security and then open Security Groups tab.
2. In default row, click Manage Rules.
3. Click Add Rule, choose ALL ICMP rule to enable ping into your instance, and then click Add.
4. Click Add Rule, choose HTTP rule to open HTTP port (port 80), and then click Add.
5. Click Add Rule, choose SSH rule to open SSH port (port 22), and then click Add.
6. You can open other ports by creating new rules.
Now, you can SSH your instances to the floating IP address that you got in the step 4. If you are
using Ubuntu image, the SSH user will be ubuntu.
EX NO:8 Install Hadoop single node cluster and run
DATE: 24/11/21 simple applications like wordcount.
Install Hadoop
Step 1: Click here to download the Java 8 Package. Save this file in your
home directory.
Step 5: Add the Hadoop and Java paths in the bash file (.bashrc).
Open. bashrc file. Now, add Hadoop and Java Path as shown below.
Command: vi .bashrc
Fig: Hadoop Installation – Setting Environment Variable
For applying all these changes to the current Terminal, execute the source command.
To make sure that Java and Hadoop have been properly installed on your system
and can be accessed through the Terminal, execute the java -version and hadoop
version commands.
Command: cd hadoop-2.7.3/etc/hadoop/
Command: ls
Step 7: Open core-site.xml and edit the property mentioned below inside
configuration tag:
core-site.xml informs Hadoop daemon where NameNode runs in the cluster. It contains
configuration settings of Hadoop core such as I/O settings that are common to HDFS &
MapReduce.
Command: vi core-site.xml
1
<?xml version="1.0" encoding="UTF-8"?>
2 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <configuration>
4 <property>
5 <name>fs.default.name</name>
6 <value>hdfs://localhost:9000</value>
</property>
7 </configuration>
8
Step 8: Edit hdfs-site.xml and edit the property mentioned below inside
configuration tag:
hdfs-site.xml contains configuration settings of HDFS daemons (i.e. NameNode,
DataNode, Secondary NameNode). It also includes the replication factor and block size
of HDFS.
Command: vi hdfs-site.xml
1
2 <?xml version="1.0" encoding="UTF-8"?>
3 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration>
4 <property>
5 <name>dfs.replication</name>
6 <value>1</value>
7 </property>
8 <property>
<name>dfs.permission</name>
9 <value>false</value>
10 </property>
11 </configuration>
12
Step 9: Edit the mapred-site.xml file and edit the property mentioned below
inside configuration tag:
In some cases, mapred-site.xml file is not available. So, we have to create the mapred-
site.xml file using mapred-site.xml template.
1
<?xml version="1.0" encoding="UTF-8"?>
2 <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
3 <configuration>
4 <property>
5 <name>mapreduce.framework.name</name>
6 <value>yarn</value>
</property>
7 </configuration>
8
Step 10: Edit yarn-site.xml and edit the property mentioned below inside
configuration tag:
Command: vi yarn-site.xml
Fig: Hadoop Installation – Configuring yarn-site.xml
1
2
<?xml version="1.0">
3 <configuration>
4 <property>
5 <name>yarn.nodemanager.aux-services</name>
6 <value>mapreduce_shuffle</value>
</property>
7 <property>
8 <name>yarn.nodemanager.auxservices.mapreduce.shuffle.class</
9 name>
1 <value>org.apache.hadoop.mapred.ShuffleHandler</value>
0 </property>
</configuration>
1
1
Step 11: Edit hadoop-env.sh and add the Java Path as mentioned below:
hadoop-env.sh contains the environment variables that are used in the script to run
Hadoop like Java home path, etc.
Command: vi hadoop–env.sh
Command: cd
Command: cd hadoop-2.7.3
This formats the HDFS via NameNode. This command is only executed for the first
time. Formatting the file system means initializing the directory specified by the
dfs.name.dir variable.
Never format, up and running Hadoop filesystem. You will lose all your data stored in
the HDFS.
Command: cd hadoop-2.7.3/sbin
Either you can start all daemons with a single command or do it individually.
Command: ./start-all.sh
Start NameNode:
The NameNode is the centerpiece of an HDFS file system. It keeps the directory tree of
all files stored in the HDFS and tracks all the file stored across the cluster.
Start DataNode:
Start ResourceManager:
ResourceManager is the master that arbitrates all the available cluster resources and
thus helps in managing the distributed applications running on the YARN system.
Its work is to manage each NodeManagers and the each application’s
ApplicationMaster.
Start NodeManager:
The NodeManager in each machine framework is the agent which is responsible for
managing containers, monitoring their resource usage and reporting the same to the
ResourceManager.
Start JobHistoryServer:
JobHistoryServer is responsible for servicing all job history related requests from client.
Command: jps