OUTCOME

BASED LAB
TASK REPORT
 TITLE OF THE TASK
CLOUD COMPUTING LAB TASK

OUTCOME BASED LAB TASK REPORT

Submitted by

NAMITHA.P
202IT174

BANNARI AMMAN INSTITUTE OF TECHNOLOGY

(An Autonomous Institution Affiliated to Anna University,
Chennai) SATHYAMANGALAM-638401

OCTOBER 2022
 DECLARATION

I affirm that the lab task work titled “CLOUD COMPUTING LAB TASK” being
submitted as the record of original work done by us under the guidance of
GAYATHRI K.NAME OF THE SUBJECT HANDLING FACULTY, Designation,
Department of INFORMATION TECHNOLOGY.

NAMITHA.P
(202IT174)
STUDENT NAME
(Roll No)

I certify that the declaration made above by the candidates is true.

GAYATHRI K
NAME OF THE LAB HANDLING FACULTY
 TABLE OF CONTENTS

S.NO TASK PG.NO

1. Install Linux Inside Windows Using 5
VirtualBox

2. 10
VMwareEngine
private clouds

3. Transferring Files to 14
and from Virtual
Machines

4. Implement the 18
procedure
to create and deploy
a simple web
application in public
cloud environment
LAB TASK - 1
Install Linux Inside Windows Using VirtualBox:
There are several ways to install Linux. You can clean everything from your system
and install Linux. You can dual boot Linux with Windows and choose one of the
operating systems at the boot time. You can even install Linux within Windows
from Microsoft Store (though this only provides you with the command line version
of Linux).But if you want to use Linux without making any changes to your
Windows system, you can go the virtual machine route. Basically, you install and
use Linux like any regular Windows application. When you just want to try Linux
for limited use, virtual machines provide the most comfortable option.
Installing Linux inside Windows using VirtualBox:
VirtualBox is free and open source virtualization software from Oracle. It enables
you to install other operating systems in virtual machines. It is recommended that
your system should have at least 4GB of RAM to get decent performance from the
virtual operating system.

Requirements:
1. Good internet connection to download software and Linux ISO. (You can also use
some other computer with an internet connection to download these files.)
2. Windows system with at least 12 GB of free space.
3. Windows system with 4GB of rRAM. (It can work with less RAM as well, but
your system will start to lag while using Linux in the virtual machine.)
4. Make sure to enable virtualization in the BIOS.
Step 1: Download and install Virtual Box
Installing Virtual Box is not rocket science. Just double-
click on the downloaded .exe file and follow the instructions on the screen. It is like
installing any regular software on Windows.
Step 2: Download the Linux ISO
Next, you need to download the ISO file of the Linux distribution. You can get this
image from the official website of the Linux distribution you are trying to use.
Step 3: Install Linux using Virtual Box
You have installed Virtual Box and you have downloaded the ISO for Linux. You
are now set to install Linux in Virtual Box. Start Virtual Box, and click on the New
symbol. Give the virtual OS a relevant name.Allocate RAM to the virtual OS. My
system has 8GB of RAM and I decided to allocate 2GB of it. You can use more
RAM if your system has enough extra.Create a virtual disk. This serves as the hard
disk of the virtual Linux system. It is where the virtual system will store its
files.You can choose either the “Dynamically allocated” or the “Fixed size” option
for creating the virtual hard disk.The recommended size is 10 GB. However, I
suggest giving it more space if possible. 15-20 GB is preferable.Once everything is
in place, it’s time to boot that ISO and install Linux as a virtual operating system.If
VirtualBox doesn’t detect the Linux ISO, browse to its location by clicking the
folder icon.Soon you’ll find yourself inside Linux. You should be presented with
the option to install it.Things from here are Ubuntu-specific. Other Linux
distributions may have slightly different looking steps, but it won’t be complicated
at all.
Select ‘Erase disk and install Ubuntu’. Don’t worry. It won’t delete anything on
your Windows operating system. You are using the virtual disk space of 15-20GB
that we created in previous steps. It won’t impact the real operating system.Just
click on Continue.Things are pretty straightforward from here.Try to choose a
password that you can remember. You can also reset the password in Ubuntu if you
forget itYou are almost done. It may take 10-15 minutes to complete the
installation.Once the installation finishes, restart the virtual system.If it gets stuck
on the screen below, you may close the VirtualBox.And that’s all. From now on,
just click on the installed Linux virtual machine. You’ll be able to use it directly.
The installation is a one time only process. You can even delete the Linux ISO that
you downloaded earlier.
I strongly recommend using VirtualBox Guest Additions on Ubuntu for it provides
better compatibility and you would be able to use copy-paste and drag-drop
between Linux and Windows.

Troubleshooting: AMD-V is disabled in the BIOS

If you face this error while using the virtual machine:
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}This means that virtualization
is blocked on your system. You’ll have to activate it in your BIOS settings first.
Reboot your system and as soon as it powers up, press F2/F10/F12 to access BIOS
settings. You have to look for the virtualization option in the BIOS and enable it.
First Program:
Setup
First we need to make sure that we have the setup for compilation and build.
⚫ Open Terminal.
⚫ Run this command from the command line:

$ sudo apt-get install build-essential

⚫ Once installed you should be able to type:

$ cc --version.

Editor:
First of all, we are not going to use any fancy IDE. You can choose any text editor.
Here are some of the options:

• Atom in Windows or OSX.

• Gedit on Linux and OSX.
• Emacs and Emacs for OSX.
• Vim in Linux.

Install Vim

⚫ In terminal run this command:

$ sudo apt install vim

⚫ Once installed you should be able launch vim:

$ vim

⚫ Press 'i' to start insert mode and edit:

First C Program
Let us write our first program in C. Let us name the file hello.c.

#include

/* This is a comment. */
int main(int argc, char *argv[])
{
// this is another comment
printf("Hello World");

return 0;
}

Compile and Run:

In terminal run this command in the same directory where you wrote the program:

$ make hello

Now run:

$ ./hello

• The first command make is a tool that knows how to build C programs. When
you run it and give it hello you are telling make to look for the hello.c file, run
the compiler to build it, and leave the results in a file named hello.
• This hello file is an executable that you can run with ./hello, which outputs
your results.
LAB TASK - 2:
VMware Engine private clouds:
bookmark_border
A Google Cloud VMware Engine private cloud is an isolated VMware stack that
consists of the following VMware components:
⚫ ESXi hosts
⚫ vCenter Server
⚫ vSAN
⚫ NSX
⚫ HCX
Private clouds help you address a variety of common needs for network
infrastructure:
Growth.
Add nodes with no new hardware investment when you reach a hardware refresh
point for your existing infrastructure.
Fast expansion.
Create additional capacity immediately when temporary or unplanned capacity
needs arise.
Increased protection.
Get automatic redundancy and availability protection when using a private cloud of
three or more nodes.
Long-term infrastructure needs.
Retire data centers and migrate to a cloud-based solution while remaining
compatible with your enterprise operations. This is especially useful if your data
centers are at capacity or you want to restructure to lower costs.
Private cloud environment
You manage your private clouds through the VMware Engine portal. Each private
cloud has its own vCenter Server in its own management domain, and all nodes in a
given private cloud reside in the same region. The VMware stack runs on dedicated,
isolated bare metal hardware nodes in Google Cloud locations. You use the stack
through native VMware tools, including vCenter Server and NSX Manager.

Private clouds are also designed to eliminate single points of failure:

Clusters of ESXi hosts are configured with vSphere High Availability (HA) and
sized to have at least one spare node for resilience. vSphere HA protects against
node and network failures.
vSAN provides redundant primary storage. vSAN requires at least three nodes in a
private cloud to provide protection against a single failure. You can configure
vSAN to provide higher resilience for larger clusters.
You can connect the private cloud to your on-premises environment using the
following connections:
⚫ Cloud VPN
⚫ Cloud Interconnect
⚫ Point-to-site VPN
⚫ Single-node private clouds
For pilot testing and proofs of concept with VMware Engine, you can create a
private cloud that contains only a single node and cluster in any region where
VMware Engine is available. All VMware Engine features are available in a single-
node private cloud, but there are specific limitations on VMware stack features due
to cluster size.

The following are common use cases for a single-node private cloud:
Proof of concept: evaluating VMware Engine and its capabilities
Disaster recovery testing: deploying your application from recent backups to
periodically validate disaster recovery preparedness
Application upgrade testing: test and validate application component upgrades
before upgrading your application in production
VMware Engine deletes single-node private clouds after 60 days, along with any
associated workload VMs and data. However, you can prevent this deletion and
receive production-ready SLA coverage by expanding to at least 3 nodes within 60
days. The expansion process won't disturb your VMs or access to vCenter, and it
initializes vSAN data replication after the nodes are successfully added to the
cluster. For single-node private clouds, the default vSAN storage policy uses a
Failures to Tolerate (FTT) value of FTT=0. When you expand a single-node private
cloud, VMware Engine changes the default vSAN storage policy. The default
vSAN storage policy changes to use FTT=1 for 3–4 node private clouds and to use
FTT=2 for private clouds with at least 5 nodes.

Custom core counts

Some licensing agreements, such as those for Windows Server and SQL Server,
charge you based on the number of CPU cores on the underlying physical node or
in the cluster. Whenever you create a new cluster, you can reduce the number of
available cores for each node in the cluster to meet the application license
requirements. VMware Engine also creates any new nodes added to that cluster
with the same number of cores per node, including when replacing a failed node.
Custom core counts are available for both the initial cluster as well as for any other
clusters created in a private cloud. Reducing the number of available cores doesn't
affect node pricing.

Limitations
Each private cloud has resource limits for its nodes and clusters. Refer to VMware
in a private cloud for a list of these limits.

Single-node private cloud limitations

For single-node private clouds, the following limitations apply to the VMware
stack:
Features or operations that require more than 1 node won't work. For example, you
won't be able to use vSphere Distributed Resource Scheduler (DRS) or High
Availability (HA).
The default vSAN storage policy uses FTT=0, so node failure results in data loss.
Additionally, the following VMware Engine limitations apply:
You cannot add a single-node cluster to an existing private cloud.
An existing private cloud cannot be converted to a single-node private cloud.
Node adjustments by autoscale policies aren't supported with a single-node private
cloud.
VMware stack upgrades involve a downtime for your single-node private cloud.
VMware Engine doesn't encrypt data on vSAN on a single-node private cloud by
default.
A private cloud must contain at least 3 nodes and complete vSAN data replication
to be eligible for coverage based on the SLA. You cannot adjust the number of
cores per node with a single-node private cloud. Custom core count limitations
The following limitations apply to a cluster that has a custom core count:
All nodes added to the cluster after initial creation also use the custom core count.
The number of cores per node can't be changed after cluster creation. To change the
number of cores per nodes in the cluster, you must delete the cluster and create a
new one.
The number of cores per node must be a multiple of 4 (like 4, 8, 12, or 16).
Custom core counts aren't available for single-node private clouds.
LAB TASK - 3
Transferring Files to and from Virtual Machines:
Creating a Shared Folder in VirtualBox
A shared folder is a folder that makes its files available on both the guest machine
and the host machine at the same time. Creating a shared folder between the guest
and the host allows you to easily manage files that should be present on both
machines. The course virtual machines are ready to use shared folders right away,
but if you are using the virtual machine on your personal computer, then you will
need to specify which folder to use as shared storage.
Shared Folders on SCS Lab Computers using Course VMs
If you are using a course VM on a lab computer, it is likely that a shared folder has
already been set up for you. On the desktop of your course VM, you should notice a
folder titled SharedFolders. Inside this folder, you will find any folders that have
been shared between the course VM and lab computers.
You should see two folders that have already been configured for you:
Z_DRIVE and Temp.
Z_DRIVE gives you access to your Windows Account Z:\ drive. This is storage that
is persistent to your SCS account and available as a network drive on the lab
computers.Temp gives you access to the folder found at D:\temp on the lab
computer. Files stored in this folder are local to the machine, meaning that they can
be accessed faster but will delete from the system when you log out. If you are
working with data that you will need to use again, use the Z_DRIVE for your
shared folder. If you need a faster read/write speed, use the Temp folder, but
remember to back up your files, or they will be deleted when you log off the
computer.
Shared Folders on Personal Computers
If you are using your own personal machine, you will need to configure VirtualBox
to look in the right place for your shared files.
Quick Start Guide
First, click on the guest machine you intend to share files with. From there, you can
select the guest Settings and navigate to Shared Folders on the left side menu. To
create a new shared folder, either click the New Folder icon on the right menu or
right-click the empty list of shared folders and click Add Shared Folder. From here,
there are six options:
Folder Path: The folder name on the host machine. Click the drop-down menu and
navigate to the folder you would like to share.
Folder Name: This is the name of the folder as it will appear on the guest machine.
Read-Only: If you check read-only, the guest machine will be unable to write
changes to the folder. This is valuable when you only want to send files to the
virtual machine, but do not want to risk having the files modified by the guest.
Auto-Mount: When any external storage is connected to a computer, it must be
mounted in order to be used. It is recommended that you turn on auto-mounting
unless you are familiar with the process of mounting a drive yourself.
Mount Point: Unless you already know about mount points, leave this blank.
Make Permanent: If you check this, the shared folder will be a permanent machine
folder. If it is not checked, the folder will not be shared after a shutdown.
On the course virtual machines, when you load into the desktop, you should see a
folder labelled SharedFolders. In there, you will see any folders that are currently
mounted and being shared.
Dragging and Dropping Files in VirtualBox
If you only need to transfer a few files quickly, you can simply drag and drop the
files in. On the top bar of the running guest machine, click on Devices > Drag and
Drop and make sure that Bidirectional is selected. This means that you will be able
to drag files from the host to the guest and from the guest to the host. Once
bidirectional drag and drop is checked, you should be able to begin dragging and
dropping files.
NOTE: Sometimes when dragging files into the course VM, we may not be able to
drag them into the file browser directly. If we encounter this issue, we should drag
our files onto the Desktop and move the files around from there. We should see the
cursor change when it is ready to drop files.We can also drag files from the guest
machine into the host. To do this, simply open the file browser on the host to where
you would like to drop the files and drag the files from the virtual machine into the
file browser of the host. File transfers should be pretty quick; if the virtual machine
seems stuck when transferring, simply cancel the transfer and try again.
Managing Files with NextCloud
On any virtual machine, including VirtualBox, VMWare, or the virtual machines
hosted on the SCS OpenStack, you can access the SCS NextCloud services to move
files between multiple machines and your SCS Windows Account storage.
NextCloud offers we all of your SCS storage in one remote location, similar to how
you might use other file hosting services like Dropbox or Google Drive. Before
trying to use NextCloud, we should check that we can access the service by logging
in here.If we can access the NextCloud services, we can browse the various file
storage services available to you:
Linux Home: These are the files from your SCS Linux Account
Windows Home: These are the files from your SCS Windows Account and your
lab Z:\ drive.
NextCloud: In addition to the other storage accounts provided to you by the SCS,
you can also upload up to 20GB of files directly to NextCloud.
With NextCloud, you can upload your files from any machine with an internet
connection and download them onto any other machine with an internet connection.
For example, you can move project files off of your virtual machine, onto the
NextCloud storage, and then download them on your personal laptop. Alternatively,
you can upload files from your personal PC onto the NextCloud storage, place them
into the Windows Home folder, and access those files from either the lab Z:\ drive
or download them on a virtual machine like VirtualBox or OpenStack.
Uploading Files to NextCloud from a Lab Computer
If you would like to upload files from a lab computer, the easiest way to do this is to
place the files you would like to transfer into your Z:\ drive. These files will be
automatically backup into your NextCloud storage under the Windows Home folder.
After that, you can move them into the main NextCloud storage or choose to keep
them in your Z:\drive.
Uploading Files to NextCloud from a VM or Other PC
If you would like to upload files from either a VM or any other computer, you can
log in to the NextCloud service using any of the available interfaces, such as the
web interface. Press the “+” icon in the top left of the file browser and select
Upload File. From here, you can choose to keep it in the main NextCloud storage,
move it into your Windows Account storage (the Windows Home folder), or into
your Linux Account storage (the Linux Home folder).
Downloading NextCloud Files to a VM or Other PC
Once your files are uploaded, you will be able to download those files onto any
machine, which can connect to NextCloud. First, log in to your preferred
NextCloud interface (e.g. the web interface). Navigate to the folder which contains
the files you would like to download. Once you are in the target folder, click the
checkbox next to each file you would like to download. Above the file listing, you
should notice the context bar changing to tell you how many files you have selected
and a button labelled Actions. Click Actions > Download.
If you selected a single file, it will prompt you to confirm the download. If you have
chosen more than one file, NextCloud will place all of the selected files into a zip
archive. Before you can use the files, you will need to extract them from the archive.
Once you have downloaded your file or extracted your archive, you are ready to use
your files on your machine.
LAB TASK - 4:
Implement the procedure to create and deploy a simple
web application in public cloud environment:
Before we begin
⚫ Create a Cloud project with an App Engine app.
⚫ Write a Node.js web server ready to deploy on App Engine.
⚫ Install Google Cloud CLI, which provides the gcloud command-line tool.
Ensure gcloud is configured to use the Google Cloud project you want to deploy
to.
Key points
Use gcloud app deploy and gcloud app browse to deploy and view your service.
Deploying your service
In our my-nodejs-service folder, where the app.yaml file is located, run the
following command in our terminal:
gcloud app deploy
our source files are then uploaded to Google Cloud Storage. Cloud Build builds our
app and deploys it to App Engine. For information about other ways to build and
deploy our app, see Testing and deploying our app.
Note: Files listed in your .gcloudignore file will not be uploaded.
If we don't have one, a .gcloudignore file is created to ensure that your
node_modules folder is not uploaded.
Node.js modules are installed in the cloud as listed in your package.json and
package-lock.json files and your service is started by using npm start.
Important: For the best performance, our start script should be lightweight,
because it runs whenever a new instance of your application is created.
Deploying multiple services
we can add multiple services in our project by creating an app.yaml file for each
service. Include the service attribute in each app.yaml file to specify the name of the
service.
To learn more about structuring our app using multiple services, see Structuring
Web Services in App Engine. To deploy multiple services, follow these instructions.
Each deployed service will have its own assigned URL.

Viewing your service

To quickly launch your browser and access your web service at
https://PROJECT_ID.REGION_ID.r.appspot.com, use the following command:
gcloud app browse

Services and versions

We've just created and deployed a service on App Engine. We can specify the name
of our service in the app.yaml file. If the name is omitted, it is treated as default.
The first service we deploy must be the default service. We can update our service
at any time by running the gcloud app deploy command again. Each time we deploy,
a new version is created and traffic is automatically routed to the latest version.
 OUTCOME BASED LAB TASKS
RUBRICS FORM (*to be filled by the lab handling faculty only)

Student name: NAMITHA.P

Register number: 202IT174
Name of the laboratory: CLOUD COMPUTING
Name of the lab handling faculty: GAYATHRI K
Name of the task:
Experiments mapped:
1.
2.
3.

S.No Rubrics Reward points

awarded
1
2
3
4
5
Total (150 reward points)