piyushcc
piyushcc
LAB MANUAL
Cloud Computing
(BTCS 604-18)
ii
Aim 1 : Introduction to Cloud Computing.
But if we choose Cloud Computing, a cloud vendor is responsible for the hardware
purchase and maintenance. They also provide a wide variety of software and
platform as a service. We can take any required services on rent. The cloud
computing services will be charged based on usage.
1
The cloud environment provides an easily accessible online portal that makes handy
for the user to manage the compute, storage, network, and application resources.
Some cloud service providers are in the following figure.
2
Advantages of cloud computing
o Cost: It reduces the huge capital costs of buying hardware and software.
o Public Cloud: The cloud resources that are owned and operated by a third-party
cloud service provider are termed as public clouds. It delivers computing resources
such as servers, software, and storage over the internet
o Private Cloud: The cloud computing resources that are exclusively used inside a
single business or organization are termed as a private cloud. A private cloud may
3
physically be located on the company’s on-site datacentre or hosted by a third-party
service provider.
o Hybrid Cloud: It is the combination of public and private clouds, which is bounded
together by technology that allows data applications to be shared between them.
Hybrid cloud provides flexibility and more deployment options to the business.
4
Office 365, and Amazon Kindle. SaaS is used to minimize the operational cost to the
maximum extent.
5
Dropbox
6
Aim 2: Installing Linux inside Windows using
VMWare.
Requirements
Good internet connection to download software and Linux ISO. (You can also
use some other computer with an internet connection to download these
files.)
Windows system with at least 20 GB of free space. A 25GB+ Free space is
good for installing the latest version of Ubuntu.
Windows system with 8 GB of RAM. (It can work with less RAM as well, but
your system will start to lag while using Linux in the virtual machine.)
Make sure to enable virtualization in the BIOS
7
You have installed VMWare and you have downloaded the ISO for Linux. You
are now set to install Linux in VMware.
Now, start VMWare and click on Create New Virtual Machine.
8
Installing Ubuntu in VMWare
9
Next, you need to set your Keyboard Layout, which by default is set to English US.
Once done with your settings, you can press the Install Now button. This will ask you to
provide a time zone.
10
Pressing Continue will ask you to provide user credentials like name, password etc. Provide them all
and press Continue.
11
Aim 3: Introduction to Cloudsim.
CloudSim is a simulation toolkit that supports the modelling and simulation of the
core functionality of the cloud, like job/task queue, processing of events, creation of
cloud entities(datacenter, datacenter brokers, etc.), communication between different
entities, implementation of broker policies, etc. This toolkit allows to:
This simulation toolkit is an API that allows a developer to run any server hardware
model as a software simulation, to analyze its behavior for real-world workloads.
12
Therefore it is clear that it allows a researcher to simulate the Infrastructure as a
Service(IaaS) layer.
This includes software models of data centers, hosts, storage, virtual machines,
Cloud datacenter brokers, allocation & scheduling policies for the virtual machines as
well as tasks, power management policies including migrations and consolidation of
the virtual machines over different hosts, defining the workload attributes for its
execution simulation over the cloud systems, etc.
It is not applicable/suitable where you are looking to analyze any service related to
Platform as a Service(PaaS) or Software as a Service(SaaS) for example real-time
applications, security algorithms, platform implementations, etc
No, not at all. The cloudsim is a software simulation toolkit and is developed using
Java programming language, Therefore, any computer system with a dual-core
processor, 2 GB RAM, and 1 GB storage is good enough to simulate the cloud-
based systems using the cloudsim as this is required to support the JRE working.
Also, the hardware requirements may differ on the basis of which IDE you are using
for JAVA development.
By default, the project page displays the source code(based on the maven build tool)
of the current release, which is currently released version 5.0(beta) and the page
displays the basic information about the project along with the publication details.
Every version except 6.0 and 5.0(still under development) contains 4 asset files.
cloudsim-4.0.tar.gz: This file contains the compiled JAR file that can
be directly used in the custom simulation implementation where there
13
is no need to change the source code of the cloudsim simulation
engine. This version is Linux-specific.
Source code(tar.gz): This file contains a similar structure as
mentioned above, but it is specific to Linux
How to install Cloudsim?
Cloudsim setup is very easy, and I encourage you to start with version 3.0.3.
This link describes in detail all the steps required to configure the Cloudsim 3.0.3
version successfully and can help you to also understand the core architecture of
this cloudsim simulation tool.
The cloudsim 3.0.3 version is best to start with that once you understand the basic
working and architecture then you can move to the latest version.
As it is already mentioned that the cloudsim allows modeling and simulate the cloud
system components, therefore to support its function different set of classes has
been developed by its developers:
14
keeps track of all the task assignments among the different simulated
cloud components.
How to run my first cloudsim simulation scenario?
Once you have completed your installation/setup and understand the basic workings
of the cloudsim, the next step is to implement your custom scenario.
Initialize the CloudSim with the current clock time and this will also
initialize the core CloudInformationService entity.
Create Datacenter(s) as Datacenters are the resource providers in
CloudSim. We need to list one of them to run a CloudSim simulation.
Create a Broker to simulate the user workload scheduling as well as
virtual machine allocation and placements.
Create one/more virtual machines and submit them to the broker for
further submitting it to the respective DataCenters for placement and
execution management during the simulation run.
Create one/more Cloudlets and submit the Cloudlet list to the broker for
further task scheduling on the active virtual machines for its processing
during the simulation run.
Starts the simulation, this will initiate all the entities and components
created above and put them into execution for supporting various
simulation operations.
Stop the simulation, concludes the simulation, and flush all the entities
& components before the exit of a simulation run.
Print results when the simulation is over, where you will be able to
display which cloudlet executed on which virtual machine along with
how much time it spent in execution, its start time as well as its finish
time.
15
Aim 4 : Implement Cloudsim and Create data center and
brokers.
let us see how to implement cloudsim and how to create a datacenter and run a
cloudlet with a broker and virtual machines .
16
Output:
17
A example showing how to create a datacenter with one host and run two
cloudlets on it. The cloudlets run in VMs with the same MIPS requirements.
The cloudlets will take the same time t complete the execution.
18
A simple example showing how to createtwo datacenters with one host each and
run cloudlets of two users on them.
19
Output:
20
Aim 5 : Explore Cloudanalyst.
21
3. configure simulation: change the region of user base
22
5. Configure Simulation: change the region of data centers .
23
7. Configure Simulation: Choose service Broker Policy ( like: closest data center) &
add more user base
24
9. Overall Response Time Summary :-
25
Aim 6 :- To study cloud security management.
Organizations of all sizes have adopted cloud strategies to varying degrees. While
beneficial in many ways, the cloud also has its risks, which organizations should fully
assess before placing assets there. In this comprehensive guide, complete with links
to more information, we lay out the challenges in securing the cloud environment as
well as how to develop best practices for managing cloud security.
26
Why is security management in the cloud
important?
Far too often, organizations place their trust in cloud providers to ensure a secure
environment. Unfortunately, that approach has numerous problems -- namely, that
cloud providers don't always know the risk associated with a customer's systems and
data. They don't have visibility into other components in the customer's ecosystem
and the security requirements of those components. Failing to take ownership of
cloud security is a serious downfall that could lead organizations to suffer data loss,
system breaches and devastating attacks.
The irony here is that many organizations approach cloud computing thinking that
the business can offload the problems and responsibilities of everyday computing.
While this is true to an extent with issues such as facilities maintenance and capital
expenditure mitigation, it's not true with issues such as data compliance and security.
A business bears responsibility for the security and compliant use of its data in the
cloud -- just as a taxpayer bears responsibility for the accuracy and completeness of
their tax returns, even when those documents are prepared by someone else.
The Cloud Security Alliance (CSA) shared the most common cloud security
challenges to give organizations a sense of the massive attack surface cloud
computing presents. In addition to the potential for data breaches and lack of
visibility, the following are some of the most egregious problems the alliance found
With a private cloud environment, an organization might gain more control over
security, but cloud costs and complexity will likely rise as a result. And while a hybrid
approach -- part public, part private -- might seem like the perfect compromise, it
presents challenges, too, including policy enforcement across environments.
28
Shared responsibility. Clouds operate on a shared responsibility model, but
there are often misunderstandings about responsibilities and definitions that lead
to critical gaps in security management. It's important to understand the shared
responsibility model clearly and work with providers to ensure that each side
meets its obligations.
Limited visibility. If you can't see it, you can't manage it: It's an old axiom that
perfectly suits cloud security efforts. A business must be able to see where all of
their applications and data are located in the cloud, and this can be problematic
with such decentralized control over different business teams and divisions that
might use the cloud. There must be a means of discovering, tracking, and
reporting on the assets present in the cloud.
Compliance challenges. A business is obligated to know what assets it has
available, where those assets are located, and how they're being used. When a
cloud provider obscures this information (or a user does not bother to access this
information), the business could experience a costly breach in regulatory
compliance. It's important to understand the tools and visibility offered by a
provider and to understand how that information can meet compliance
requirements.
Limited control. Businesses do not own the cloud infrastructure. While a user
can assert considerable control over some security issues like user authorization
and authentication, users typically do not assert control over the underlying cloud
infrastructure as they would within a local data center. This can lead to security
concerns in how data is accessed and shared.
Cloud differences. Every cloud is different. As businesses explore hybrid and
multi-cloud environments, there are bound to be differences in tools, services,
configurations and capabilities that might cause an inconsistent or incomplete
security posture for the business. This is another case where consultations with
the providers can be extremely beneficial for business users.
29
Understand the business drivers and goals. This is another way of "starting
with the end in mind." Cloud security -- and its proper management -- are there
for a purpose, which is to serve the business and facilitate business interests.
Any implementation of cloud security management should be in response to
business needs. For example, compliance might be a primary security goal for a
highly regulated business.
Create security principles and practices. Consider how the business should
approach cloud security, such as accessing and protecting data. Chances are
that cloud security and security management will vary from traditional data center
security, so think ahead and evaluate how cloud security processes should best
work for the business.
Select and implement tools. There are plenty of tools, platforms and services
available to help implement and manage cloud security. One size does not fit all,
and each product offering has unique strengths and tradeoffs. However, knowing
the business goals and intended practices makes the job of finding and validating
cloud security management tools considerably easier. This could still require
some adjustments to principles and practices, but the underlying ideas should be
consistent.
Encrypt data and monitor. Data should ideally be encrypted at rest and in flight.
User and workload access should adopt zero-trust and other highly restricted
postures. Monitor network traffic and watch for intrusion. Scan for malicious
activity, such as unauthorized data access. Oversee end users and devices.
Report. Use the alerting and reporting features of the cloud security
management system to deliver timely security reports to cloud workload
stakeholders and business leaders. Recognize the threats (e.g., an unpatched
operating system) and take proactive action to mitigate those risks on an ongoing
basis.
Reevaluate. Threats and business needs are always changing, and so should
cloud security. As cloud security evolves, the cloud security management effort
should also change in order to address new and emerging threats. This is often a
team effort that involves business, technology and legal leadership from across
the business.
30
Aim 7 :-To study and implementation of identity
management.
31
Components of Identity and Access Management (IAM)
1. Users
2. Roles
3. Groups
4. Policies
With these new applications being created over the cloud, mobile and on-premise
can hold sensitive and regulated information. It’s no longer acceptable and feasible
to just create an Identity server and provide access based on the requests. In current
times an organization should be able to track the flow of information and provide
least privileged access as and when required, obviously with a large workforce and
new applications being added every day it becomes quite difficult to do the same. So
organizations specifically concentrate on managing identity and its access with the
help of a few IAM tools. It’s quite obvious that it is very difficult for a single tool to
manage everything but there are multiple IAM tools in the market that help the
organizations with any of the few services given below.
IAM Policies
IAM Policies can manage access for AWS by attaching them to the IAM Identities or
resources IAM policies defines permissions of AWS identities and AWS resources
when a user or any resource makes a request to AWS will validate these policies and
confirms whether the request to be allowed or to be denied. AWS policies are stored
in the form of Jason format the number of policies to be attached to particular IAM
identities depends upon no.of permissions required for one IAM identity. IAM identity
can have multiple policies attached to them.
32
Figure – Services under IAM
IAM Features
1. Shared Access to your Account: A team working on a project can easily
share resources with the help of the shared access feature.
2. Free of cost: IAM feature of the AWS account is free to use & charges are
added only when you access other Amazon web services using IAM users.
3. Have Centralized control over your AWS account: Any new creation of
users, groups, or any form of cancellation that takes place in the AWS account
is controlled by you, and you have control over what & how data can be
accessed by the user.
4. Grant permission to the user: As the root account holds administrative
rights, the user will be granted permission to access certain services by IAM.
33
Aim 8 :-Case Study - Amazon Web Services/Microsoft
Azure/Google cloud services.
34
Maximum 3904 3800 1433
memory in VM
(GiB)
35