Experiment No.

Title:
Study of Cloud Computing & Architecture.

Objective:
Objective of this module is to provide students an overview of the Cloud Computing and
Architecture and different types of Cloud Computing.

Theory:
• Cloud Computing is a general term used to describe a new class of network based
computing that takes place over the Internet,
– Basically a step on from Utility Computing

– A collection/group of integrated and networked hardware, software and Internet

infrastructure (called a platform).
– Using the Internet for communication and transport provides hardware,
software and networking services to clients
• These platforms hide the complexity and details of the underlying infrastructure from
users and applications by providing very simple graphical interface or API (Applications
Programming Interface).
• In addition, the platform provides on demand services that are always on anywhere,
anytime and anyplace.
• Pay for use and as needed, elastic
– scale up and down in capacity and functionalities
• The hardware and software services are available to
– general public, enterprises, corporations and businesses markets

Cloud computing is the delivery of computing services over the Internet. Cloud services allow
individuals and businesses to use software and hardware that are managed by third parties at
remote locations.
• Cloud Architecture

• Examples of cloud services include online file storage, social networking sites, webmail,
and online business applications. The cloud computing model allows access to
information and computer resources from anywhere that a network connection is
available.
 Experiment No. 2

Title:
Virtualization in Cloud.

Objective:
In this module students will learn, Virtualization Basics, Objectives of Virtualization, and
Benefits of Virtualization in cloud.

Theory:
• Virtualization is a technique, which allows to share single physical instance of an
application or resource among multiple organizations or tenants (customers). It does
this by assigning a logical name to a physical resource and providing a pointer to that
physical resource when demanded.

• The Multitenant architecture offers virtual isolation among the multiple tenants. Hence,
the organizations can use and customize their application as though they each have
their instances running
• Virtual workspaces:
– An abstraction of an execution environment that can be made dynamically
available to authorized clients by using well-defined protocols,
– Resource quota (e.g. CPU, memory share),
– Software configuration (e.g. O/S, provided services).
• Implement on Virtual Machines (VMs):
– Abstraction of a physical host machine,
– Hypervisor intercepts and emulates instructions from VMs, and allows
management of VMs,
– VMWare, Xen, etc.
• Provide infrastructure API:
– Plug-ins to hardware/support structures
 Experiment No. 3

Title:
Study and implementation of Infrastructure as a Service.

Objective:
In this module student will learn Infrastructure as a Service.

Theory:
Cloud infrastructure consists of servers, storage devices, network, cloud management software,
deployment software, and platform virtualization.

Hypervisor
 Hypervisor is a firmware or low-level program that acts as a Virtual Machine
Manager. It allows to share the single physical instance of cloud resources
between several tenants.

Management Software
 It helps to maintain and configure the infrastructure.

Deployment Software
 It helps to deploy and integrate the application on the cloud.

Network
 It is the key component of cloud infrastructure. It allows to connect cloud
services over the Internet. It is also possible to deliver network as a utility over
 the Internet, which means, the customer can customize the network route and
protocol.

Server
 The server helps to compute the resource sharing and offers other services such
as resource allocation and de-allocation, monitoring the resources, providing
security etc.

Storage
 Cloud keeps multiple replicas of storage. If one of the storage resources fails,
then it can be extracted from another one, which makes cloud computing more
reliable.

Infrastructural Constraints

Transparency

Virtualization is the key to share resources in cloud environment. But it is not possible to satisfy
the demand with single resource or server. Therefore, there must be transparency in resources,
load balancing and application, so that we can scale them on demand.
Scalability
Scaling up an application delivery solution is not that easy as scaling up an application because
it involves configuration overhead or even re-architecting the network. So, application delivery
solution is need to be scalable which will require the virtual infrastructure such that resource
can be provisioned and de-provisioned easily.
Intelligent Monitoring
To achieve transparency and scalability, application solution delivery will need to be capable of
intelligent monitoring.
Security

The mega data center in the cloud should be securely architected. Also the control node, an
entry point in mega data center, also needs to be secure.
Cloud Computing Infrastructure as a Service (IaaS)
IaaS is one of the layers of cloud computing platform wherein the customer organization
outsources its IT infrastructure such as servers, networking, processing, storage, virtual
machines and other resources. Customers access these resources over internet i.e. cloud
computing platform, on a pay-per-use model.

Iaas, earlier called Hardware as a Service (HaaS), is a cloud computing platform based model.

In traditional hosting services, IT infrastructure was rented out for a specific periods of time,
with pre-determined hardware configuration. The client paid for the configuration and time,
regardless of the actual use. With the help of IaaS cloud computing platform layer, clients can
dynamically scale the configuration to meet changing requires, and are billed only for the
services actually used.
IaaS cloud computing platform layer eliminates the need for every organization to maintain the
IT infrastructure.
IaaS is offered in three models: public, private, and hybrid cloud. Private cloud implies that the
infrastructure resides at the customer-premise. In case of public cloud, it is located at the cloud
computing platform vendor's data center; and hybrid cloud is a combination of two with
customer choosing the best of both worlds.

Advantages of IaaS cloud computing layer

1) You can dynamically choose a CPU, memory and storage configuration as per your needs.
2) You easily access the vast computing power available on IaaS cloud platform.
3) You can eliminate the need of investment in rarely used IT hardware.
4) IT infra will be handled by the IaaS cloud computing platform vendors.

Disadvantages of IaaS cloud computing layer

1) There is a risk of IaaS cloud computing platform vendor by gaining the access to the
organizations data. But it can be avoided by opting for private cloud.
2) IaaS cloud computing platform model is dependent on internet availability.
3) It is also dependent on the availability of virtualization services.
4) IaaS cloud computing platform can limit the user privacy and customization options.
Cloud Computing Platform as a Service (PaaS)
PaaS cloud computing platform is a developer programming platform which is created for the
programmer to develop, test, run and manage the applications.
A developer is able to write the application as well as deploy it directly into this layer easily.

PaaS extend and abstract the IaaS layer by removing the hassle of managing the individual
virtual machine.
In PaaS cloud computing platform, back end scalability is handled by the cloud service provider
and the end user does not have to worry about to manage the infrastructure.
All the infrastructure to run the applications will be over the internet.

Advantages of PaaS cloud computing layer

1) Simplified Development

Developers can focus on development and innovation without worrying about the
infrastructure.

2) Lower risk

No requirements of up-front investment in hardware and software. Developers only need a PC

and an internet connection to start building applications.

3) Prebuilt business functionality

Some PaaS vendors also provide already defined business functionality so that users can avoid
building everything from very scratch and hence can directly start the projects only.

4) Instant community

PaaS vendors frequently provides online communities where developer can get the ideas, share
experiences and seek advice from others.

5) Scalability

Applications deployed can scale from one to thousands of users without any changes to the
applications.
Disadvantages of PaaS cloud computing layer
1) Vendor lock-in

One have to write the applications according to the platform provided by PaaS vendor so
migration of an application to another PaaS vendor would be a problem.

2) Data Privacy

Corporate data, whether it can be critical or not, will be private so if it is not located within the
walls of the company there can be a risk in terms of privacy of data.

3) Integration with the rest of the systems applications

It may happen that some applications are local and some are in cloud. So there will be chances
of increased complexity when we want to use data which in the cloud with the local data.

Cloud Computing Software as a Service (SaaS)

SaaS is a software distribution model in which applications are hosted by a cloud service
provider and made available to customers over internet. SaaS is also known as "On-Demand
Software".
In SaaS, software and associated data are centrally hosted on the cloud server. SaaS is accessed
by users using a thin client via a web browser.

Advantages of SaaS cloud computing layer

1) SaaS is easy to buy

SaaS pricing is based on a monthly fee or annual fee, SaaS allows organizations to access
business functionality at a low cost which is less than licensed applications

Unlike traditional software which is sold as a licensed based with an up-front cost (and often an
optional ongoing support fee), SaaS providers generally pricing the applications using a
subscription fee, most commonly a monthly or annually fee.

2) Less hardware required for SaaS

The software is hosted remotely, so organizations don't need to invest in additional hardware.

3) Low Maintenance required for SaaS

Software as a service removes the necessity of installation, set-up, and often daily unkeep and
maintenance for organizations. Initial set-up cost for SaaS is typically less than the enterprise
software. SaaS vendors actually pricing their applications based on some usage parameters,
such as number of users using the application. So SaaS does easy to monitor and automatic
updates.

4) No special software or hardware versions required

All users will have the same version of software and typically access it through the web
browser. SaaS reduces IT support costs by outsourcing hardware and software maintenance
and support to the IaaS provider.

Disadvantages of SaaS cloud computing layer

1) Security
Actually data is stored in cloud, so security may be an issue for some users. However, cloud
computing is not more secure than in-house deployment. Learn more cloud security.

2) Latency issue
Because the data and application are stored in cloud at a variable distance from the end user,
so there is a possibility that there may be more latency while interacting with the application
than a local deployment. So, SaaS model is not suitable for applications whose demand
response times are in milliseconds.

3) Total Dependency on Internet

Without internet connection, most SaaS applications are not usable.

4) Switching between SaaS vendors is difficult

Switching SaaS vendors involves the difficult and slow task of transferring the very large data
files over the Internet and then converting and importing them into another SaaS also.
 Experiment No. 4

Objective:
Working and installation of Microsoft Azure.

Requirement:
Account on Microsoft Azure

THEORY:

Introduction:

In this article we are going to see how to create a new database stored procedure using the
new Azure portal instead of using the SQL Server Management Studio.

Overview:

Stored procedures are created normally using the SQL Server management studio, with the
latest version of SQL Azure we have option to create a user stored procedure directly online
without need to have a local interface. This way we have some control of using it anywhere
anytime to do some updates regularly.

Let us see how to create the stored procedure in Azure portal step by step.

Steps:

Log in to the Azure portal using the below link. You can see the screen look similar to below

http://www.microsoft.com/windowsazure/
Login to the portal using your Microsoft Windows Live credentials with Azure credentials to the
management portal and you will see the screen as shown in the screen below

Now we can see the Database Menu at the bottom left, Click on that will go to the Database
Subscription window as shown in the screen below
Clicking on the subscription name will provide the complete details of the server created and
the new database created as shown in the screen below

Now we have a database created (Learn Azure) with a Max size of 1GB and ready to use it for
the application based on the requirement. To create a new Stored Procedure click on Manage
at the top menu tool bar as shown in the screen below
Check my previous article on how to connect to the manage portal using the credentials and
the firewall using the link. Once logged in you screen will look like below

To create a new stored procedure click on New Stored procedure menu at the top and we will
see a script window as shown in the screen below
Now we will write our customized stored procedure for the EmpDetails table which we created
in our earlier tutorial(Check my previous article for table creation) as shown in the screen below

Once we create the structure for the stored procedure as shown in the above screen we need
to save it. Once save we can use the stored procedure to execute the same as shown in the
screen below. We need to navigate to the new query window in the Database section and write
a execute command as shown below.
We can create n Number of stored procedure as per the requirement and use it across the
process which we normally do with the traditional SQL Server locally.
 Experiment No. 5

Title:
Securing Servers in Cloud.

Objective:
To understand how to secure web server, how to secure data directory and introduction to
encryption for own cloud.

Theory:
Security in cloud computing is a major concern. Data in cloud should be stored in encrypted
form. To restrict client from accessing the shared data directly, proxy and brokerage services
should be employed.
Security Planning

Before deploying a particular resource to cloud, one should need to analyze several aspects of
the resource such as:
 Select resource that needs to move to the cloud and analyze its sensitivity to risk.
 Consider cloud service models such as IaaS, PaaS, and SaaS. These models require customer
to be responsible for security at different levels of service.
 Consider the cloud type to be used such as public, private, community or hybrid.

 Understand the cloud service provider's system about data storage and its transfer into and
out of the cloud.
The risk in cloud deployment mainly depends upon the service models and cloud types.
Understanding Data Security

Since all the data is transferred using Internet, data security is of major concern in the cloud.
Here are key mechanisms for protecting data.
 Access Control
 Auditing
 Authentication
 Authorization
All of the service models should incorporate security mechanism operating in all
abovementioned areas.
Isolated Access to Data

Since data stored in cloud can be accessed from anywhere, we must have a mechanism to
isolate data and protect it from client’s direct access.

Brokered Cloud Storage Access is an approach for isolating storage in the cloud. In this
approach, two services are created:
 A broker with full access to storage but no access to client.
 A proxy with no access to storage but access to both client and broker.

Working Of Brokered Cloud Storage Access System

When the client issues request to access data:

 The client data request goes to the external service interface of proxy.
 The proxy forwards the request to the broker.
 The broker requests the data from cloud storage system.
 The cloud storage system returns the data to the broker.
 The broker returns the data to proxy.
 Finally the proxy sends the data to the client.
 Experiment No. 6

Title:
Fault Tolerance in Cloud Computing.

Objective:
To understand how Fault tolerance in cloud computing, how to preserve data directory from
Fault Tolerance.

Theory:

Explicating Fault Tolerance in Cloud Computing

Fault tolerance in cloud computing is about designing a blueprint for continuing the ongoing work
whenever a few parts are down or unavailable. This helps the enterprises to evaluate their
infrastructure needs and requirements, and provide services when the associated devices are
unavailable due to some cause. It doesn’t mean that the alternate arrangement can provide 100%
of the full service, but this concept keeps the system in running mode at a useable, and most
importantly, at a reasonable level. This is important if the enterprises are to keep growing in a
continuous mode and increase their productivity levels.

Main Concepts behind Fault Tolerance in Cloud Computing System

 Replication: The fault tolerant system works on the concept of running several other replicates
for each and every service. Thus, if one part of the system goes wrong, it has other instances
that can be placed instead of it to keep it running. Take for example, a database cluster that has
3 servers with the same information on each of them. All the actions like data insertion,
updates, and deletion get written on each of them. The servers, which are redundant, would be
in the inactive mode unless and until any fault tolerance system doesn’t demand the availability
of them.
 Redundancy: When any system part fails or moves towards a downstate, then it is important to
have backup type systems. For example, a website program that has MS SQL as its database may
fail in between due to some hardware fault. Then a new database has to be availed in the
redundancy concept when the original is in offline mode. The server operates with the
emergency database which comprises of several redundant services within.
Techniques for Fault Tolerance in Cloud Computing

 All the services have to be given priority when designing a fault tolerance system. The database
has to be given special preference because it powers several other units.
 After deciding the priorities, the enterprise has to work on the mock test. Take for example, the
enterprise has a forum website that enables users to log in and posts comments. When the
authentication services fail due to some problem, the users will not be able to log in. Then, the
forum becomes a read-only one and does not serve the purpose. But with the fault tolerant
systems, remediation will be ensured and the user can search for information with minimal
impact.

Major Attributes of Fault Tolerance in Cloud Computing

 None Point Failure: The concepts of redundancy and replication defines that fault tolerance can
be had but with some minor impacts. If there isn’t even a single point failure then the system is
not a fault tolerant one.
 Accept the Fault Isolation Concept: The fault occurrence has to be handled separately from
other systems. This helps the enterprise to isolate it from the existing system failure.

Existence of Fault Tolerance in Cloud Computing

 System Failure: This may be either software or hardware issue. The software failure results in
system crash or hanging situation that may be due to stack overflow or other reasons. Any
improper maintenance of the physical hardware machines will result in hardware system failure.
 Security Breach Occurrences: There are several reasons why fault tolerance occurs due to
security failures. The hacking of the server negatively impacts the server and results in data
breach. Other reasons for the necessity of fault tolerance in the form of security breaches
include ransomware, phishing, virus attack etc.
 Experiment No. 7

Title:
Cloud Business Process Management.

Objective:
To understand how Cloud Business Process Management Plays Role in Cloud Computing.

Theory:
Business Process Manager (IBM BPM) is IBM’s comprehensive, consumable BPM platform that
provides visibility and management for an enterprise’s business processes. It enables process
owners and business users to effectively engage directly in the improvement of their business
processes. Figure 1 shows how IBM BPM serves as a middleware that provides seamless
integration of business tools, processes, decisions and events. It provides users with guidance
on what process to do, how to do it and when to do it.
According to the 2012 InformationWeek 500 Survey’s “Plans to innovate this year,” making
business processes more efficient is the number one priority. When we talk about process
efficiency, we can’t help but also consider speed, agility and adaptability. The best environment
that can provide these attributes is the cloud. I am glad to know that recently IBM announced
three BPM cloud offerings which are shown in Figure 2.

IBM Business Process Manager on public cloud

 If you look closely at the middle graphics in figure two you’ll see that the full capabilities
of IBM BPM (IBM BPM Advanced) can be set up and run quickly in a managed, secure
BPM environment in the IBM Smart Cloud Enterprise (IBM SCE).

 Business analysts use the Process Designer for processes that can be easily integrated,
while the Integration Designer is used by IT Developers for more complex ones. All the
development is done in the Process Center, then deployed to the Process Servers
(stand-alone test server environment and a highly available pilot/production server
environment) where the users run their processes. To complete the lifecycle, the BPM
administration is also done in the cloud.
IBM Business Process Manager and Operational Decision Manager (ODM) application
patterns on private cloud

BPM and ODM application patterns and the IBM Pure Application System provide an
excellent platform for rapidly scaling BPM programs across the enterprise—at a lower
cost and with less resources. Figure 4 shows more of the benefits of this offering. I can
see this as the best environment for industries (retail, services and travel) where there
are peaks and lows.