Unit I -Fundamentals of Cloud Computing

Cloud computing concepts and its Definition – Characteristics of Cloud -Types of

Cloud Services – Parallel computing – Distributed Computing Cloud Types and
its Layers

https://www.javatpoint.com/cloud-computing-tutorial

What is Cloud?
Cloud refers to the internet or network. The processing, configuring,
accessing and storing of data and developing,deploying, delivering and
maintenance of various applications and services via the internet is
referred to as cloud computing. It includes both hardware and software
computing resources delivered through the internet.

History of Cloud Computing

Traditional- Client-Server Computing

Distributed Computing
Cloud computing
1.John MacCharty, in 1961 “ Computing can be sold as a utility
like water and electricity”.
Salesforce .com -1999 - CRM software
2022- Amazon Web Services
2009- Google Apps

Why Cloud
Traditional Systems- It needs
Computers, Db Servers, Networking servers,

Introduction to Parallel Computing

Parallel Computing :
It is the use of multiple processing elements simultaneously for solving any
problem. Problems are broken down into instructions and are solved concurrently
as each resource that has been applied to work is working at the same time.

Advantages of Parallel Computing over Serial Computing are as follows:

1. It saves time and money as many resources working together will
reduce the time and cut potential costs.
2. It can be impractical to solve larger problems on Serial Computing.
3. It can take advantage of non-local resources when the local resources
are finite.
 4. Serial Computing ‘wastes’ the potential computing power, thus Parallel
Computing makes better work of the hardware.

Types of Parallelism:
1. Bit-level parallelism –
It is the form of parallel computing which is based on the increasing
processor’s size. It reduces the number of instructions that the system
must execute in order to perform a task on large-sized data.
Example: Consider a scenario where an 8-bit processor must compute
the sum of two 16-bit integers. It must first sum up the 8 lower-order
bits, then add the 8 higher-order bits, thus requiring two instructions to
perform the operation. A 16-bit processor can perform the operation
with just one instruction.
2. Instruction-level parallelism –
A processor can only address less than one instruction for each clock
cycle phase. These instructions can be re-ordered and grouped which
are later on executed concurrently without affecting the result of the
program. This is called instruction-level parallelism.
3. Task Parallelism –
Task parallelism employs the decomposition of a task into subtasks and
then allocating each of the subtasks for execution. The processors
perform the execution of sub-tasks concurrently.
4. Data-level parallelism (DLP) –

Instructions from a single stream operate concurrently on several data – Limited

by non-regular data manipulation patterns and by memory bandwidth

Why parallel computing?

● The whole real-world runs in dynamic nature i.e. many things happen at
a certain time but at different places concurrently. This data is
extensively huge to manage.
● Real-world data needs more dynamic simulation and modeling, and for
achieving the same, parallel computing is the key.
● Parallel computing provides concurrency and saves time and money.
● Complex, large datasets, and their management can be organized only
and only using parallel computing’s approach.
● Ensures the effective utilization of the resources. The hardware is
guaranteed to be used effectively whereas in serial computation only
some part of the hardware was used and the rest rendered idle.
● Also, it is impractical to implement real-time systems using serial
computing.

Applications of Parallel Computing:

 ● Databases and Data mining.
● Real-time simulation of systems.
● Science and Engineering.
● Advanced graphics, augmented reality, and virtual reality.

Limitations of Parallel Computing:

● It addresses such as communication and synchronization between
multiple sub-tasks and processes which is difficult to achieve.
● The algorithms must be managed in such a way that they can be
handled in a parallel mechanism.
● The algorithms or programs must have low coupling and high cohesion.
But it’s difficult to create such programs.
● More technically skilled and expert programmers can code a
parallelism-based program well.

Future of Parallel Computing: The computational graph has undergone a great

transition from serial computing to parallel computing. Tech giant such as Intel
has already taken a step towards parallel computing by employing multicore
processors. Parallel computation will revolutionize the way computers work in the
future, for the better good. With all the world connecting to each other even more
than before, Parallel Computing does a better role in helping us stay that way.
With faster networks, distributed systems, and multi-processor computers, it
becomes even more necessary.
Parallel Computing:
In parallel computing multiple processors performs multiple tasks assigned to
them simultaneously. Memory in parallel systems can either be shared or
distributed. Parallel computing provides concurrency and saves time and money.
Distributed Computing:
In distributed computing we have multiple autonomous computers which seems
to the user as single system. In distributed systems there is no shared memory
and computers communicate with each other through message passing. In
distributed computing a single task is divided among different computers.

Difference between Parallel Computing and Distributed Computing:

S.NO Parallel Computing Distributed Computing

Many operations are System components are located

1.
performed simultaneously at different locations

2. Single computer is required Uses multiple computers

 Multiple processors perform Multiple computers perform
3.
multiple operations multiple operations

It may have shared or

4. It have only distributed memory
distributed memory

Computer communicate with

Processors communicate with
5. each other through message
each other through bus
passing.

Improves system scalability, fault

Improves the system
6. tolerance and resource sharing
performance
capabilities

Unit II- Technologies in Cloud

Service oriented Architecture – Virtualization – Virtualization types –
Implementation Levels of virtualizations -– Web Technology – Multitenant
Technology – Service Technology.

Service Oriented Architecture

Service-Oriented Architecture (SOA) is a stage in the evolution of application
development and/or integration. It defines a way to make software components
reusable using the interfaces.
Formally, SOA is an architectural approach in which applications make use of
services available in the network. In this architecture, services are provided to
form applications, through a network call over the internet. It uses common
communication standards to speed up and streamline the service integrations in
applications. Each service in SOA is a complete business function in itself. The
services are published in such a way that it makes it easy for the developers to
assemble their apps using those services. Note that SOA is different from
microservice architecture.
 ● SOA allows users to combine a large number of facilities from existing
services to form applications.
● SOA encompasses a set of design principles that structure system
development and provide means for integrating components into a
coherent and decentralized system.
● SOA-based computing packages functionalities into a set of
interoperable services, which can be integrated into different software
systems belonging to separate business domains.
There are two major roles within Service-oriented Architecture:
1. Service provider: The service provider is the maintainer of the service
and the organization that makes available one or more services for
others to use. To advertise services, the provider can publish them in a
registry, together with a service contract that specifies the nature of the
service, how to use it, the requirements for the service, and the fees
charged.
2. Service consumer: The service consumer can locate the service
metadata in the registry and develop the required client components to
bind and use the service.

Services might aggregate information and data retrieved from other services or
create workflows of services to satisfy the request of a given service consumer.
This practice is known as service orchestration Another important interaction
pattern is service choreography, which is the coordinated interaction of services
without a single point of control.
Components of SOA: ====
Guiding Principles of SOA:
1. Standardized service contract: Specified through one or more service
description documents.
2. Loose coupling: Services are designed as self-contained components,
maintain relationships that minimize dependencies on other services.
3. Abstraction: A service is completely defined by service contracts and
description documents. They hide their logic, which is encapsulated
within their implementation.
4. Reusability: Designed as components, services can be reused more
effectively, thus reducing development time and the associated costs.
5. Autonomy: Services have control over the logic they encapsulate and,
from a service consumer point of view, there is no need to know about
their implementation.
6. Discoverability: Services are defined by description documents that
constitute supplemental metadata through which they can be effectively
discovered. Service discovery provides an effective means for utilizing
third-party resources.
7. Composability: Using services as building blocks, sophisticated and
complex operations can be implemented. Service orchestration and
choreography provide solid support for composing services and
achieving business goals.
Advantages of SOA:
● Service reusability: In SOA, applications are made from existing
services. Thus, services can be reused to make many applications.
● Easy maintenance: As services are independent of each other they
can be updated and modified easily without affecting other services.
● Platform independent: SOA allows making a complex application by
combining services picked from different sources, independent of the
platform.
 ● Availability: SOA facilities are easily available to anyone on request.
● Reliability: SOA applications are more reliable because it is easy to
debug small services rather than huge codes
● Scalability: Services can run on different servers within an
environment, this increases scalability
Disadvantages of SOA:
● High overhead: A validation of input parameters of services is done
whenever services interact this decreases performance as it increases
load and response time.
● High investment: A huge initial investment is required for SOA.
● Complex service management: When services interact they
exchange messages to tasks. the number of messages may go in
millions. It becomes a cumbersome task to handle a large number of
messages.
Practical applications of SOA: SOA is used in many ways around us whether it
is mentioned or not.
1. SOA infrastructure is used by many armies and air forces to deploy
situational awareness systems.
2. SOA is used to improve healthcare delivery.
3. Nowadays many apps are games and they use inbuilt functions to run.
For example, an app might need GPS so it uses the inbuilt GPS
functions of the device. This is SOA in mobile solutions.
4. SOA helps maintain museums a virtualized storage pool for their
information and content.

Service-Oriented Terminologies
Let's see some important service-oriented terminologies:M
1.1K
C++ vs Java
 ● Services - The services are the logical entities defined by one or more published
interfaces.
● Service provider - It is a software entity that implements a service specification.
● Service consumer - It can be called as a requestor or client that calls a service
provider. A service consumer can be another service or an end-user application.
● Service locator - It is a service provider that acts as a registry. It is responsible
for examining service provider interfaces and service locations.
● Service broker - It is a service provider that pass service requests to one or more
additional service providers.
Characteristics of SOA
The services have the following characteristics:
● They are loosely coupled.
● They support interoperability.
● They are location-transparent
● They are self-contained.
Components of service-oriented architecture
The service-oriented architecture stack can be categorized into two parts - functional
aspects and quality of service aspects.
Functional aspects
The functional aspect contains:
● Transport - It transports the service requests from the service consumer to the
service provider and service responses from the service provider to the service
consumer.
● Service Communication Protocol - It allows the service provider and the service
consumer to communicate with each other.
● Service Description - It describes the service and data required to invoke it.
● Service - It is an actual service.
● Business Process - It represents the group of services called in a particular
sequence associated with the particular rules to meet the business
requirements.
 ● Service Registry - It contains the description of data which is used by service
providers to publish their services.
Quality of Service aspects
The quality of service aspects contains:
● Policy - It represents the set of protocols according to which a service provider
makes and provides the services to consumers.
● Security - It represents the set of protocols required for identification and
authorization.
● Transaction - It provides the surety of consistent results. This means, if we use
the group of services to complete a business function, either all must complete
or none of the complete.
● Management - It defines the set of attributes used to manage the services.

https://www.vmware.com/in/topics/glossary/content/hypervisor.html#:~:text=A%20hy
pervisor%2C%20also%20known%20as,such%20as%20memory%20and%20processing.

Virtualization In Cloud Computing and

Types
Virtualization is a technique of how to separate a service from the underlying
physical delivery of that service. It is the process of creating a virtual version of
something like computer hardware. It was initially developed during the
mainframe era. It involves using specialized software to create a virtual or
software-created version of a computing resource rather than the actual version
of the same resource. With the help of Virtualization, multiple operating systems
and applications can run on same machine and its same hardware at the same
time, increasing the utilization and flexibility of hardware.
In other words, one of the main cost effective, hardware reducing, and energy
saving techniques used by cloud providers is virtualization. Virtualization allows
to share a single physical instance of a resource or an application among
multiple customers and organizations at one time. It does this by assigning a
logical name to a physical storage and providing a pointer to that physical
resource on demand. The term virtualization is often synonymous with hardware
virtualization, which plays a fundamental role in efficiently delivering
Infrastructure-as-a-Service (IaaS) solutions for cloud computing. Moreover,
virtualization technologies provide a virtual environment for not only executing
applications but also for storage, memory, and networking.
The machine on which the virtual machine is going to be built is known as Host
Machine and that virtual machine is referred as a Guest Machine.
BENEFITS OF VIRTUALIZATION
1. More flexible and efficient allocation of resources.
2. Enhance development productivity.
3. It lowers the cost of IT infrastructure.
4. Remote access and rapid scalability.
5. High availability and disaster recovery.
6. Pay peruse of the IT infrastructure on demand.
7. Enables running multiple operating systems.
Types of Virtualization:
1.Application Virtualization.
2.Network Virtualization.
3.Desktop Virtualization.
4.Storage Virtualization.
5.Server Virtualization.
6.Data virtualization.
1. Application Virtualization:
Application virtualization helps a user to have remote access to an application
from a server. The server stores all personal information and other characteristics
of the application but can still run on a local workstation through the internet.
Example of this would be a user who needs to run two different versions of the
same software. Technologies that use application virtualization are hosted
applications and packaged applications.
2. Network Virtualization:
The ability to run multiple virtual networks with each has a separate control and
data plan. It co-exists together on top of one physical network. It can be
managed by individual parties that are potentially confidential to each other.
Network virtualization provides a facility to create and provision virtual
networks—logical switches, routers, firewalls, load balancer, Virtual Private
Network (VPN), and workload security within days or even in weeks.
3. Desktop Virtualization:
Desktop virtualization allows the users’ OS to be remotely stored on a server in
the data center. It allows the user to access their desktop virtually, from any
location by a different machine. Users who want specific operating systems other
than Windows Server will need to have a virtual desktop. Main benefits of
desktop virtualization are user mobility, portability, easy management of software
installation, updates, and patches.
4. Storage Virtualization:
Storage virtualization is an array of servers that are managed by a virtual storage
system. The servers aren’t aware of exactly where their data is stored, and
instead function more like worker bees in a hive. It makes managing storage from
multiple sources to be managed and utilized as a single repository. storage
virtualization software maintains smooth operations, consistent performance and
a continuous suite of advanced functions despite changes, break down and
differences in the underlying equipment.
5. Server Virtualization:
This is a kind of virtualization in which masking of server resources takes place.
Here, the central-server(physical server) is divided into multiple different virtual
servers by changing the identity number, processors. So, each system can
operate its own operating systems in isolate manner. Where each sub-server
knows the identity of the central server. It causes an increase in the performance
and reduces the operating cost by the deployment of main server resources into
a sub-server resource. It’s beneficial in virtual migration, reduce energy
consumption, reduces infrastructure cost, etc.
6. Data virtualization:
This is the kind of virtualization in which the data is collected from various
sources and managed that at a single place without knowing more about the
technical information like how data is collected, stored & formatted then arranged
that data logically so that its virtual view can be accessed by its interested people
and stakeholders, and users through the various cloud services remotely. Many
big giant companies are providing their services like Oracle, IBM, At scale,
Cdata, etc.
It can be used to performing various kind of tasks such as:
● Data-integration
● Business-integration
● Service-oriented architecture data-services
● Searching organizational data

IMPLEMENTATION LEVELS OF VIRTUALIZATION IN CLOUD COMPUTING

It is not simple to set up virtualization. The computer runs on an operating system that gets
configured on some particular hardware. It is not feasible or easy to run a different operating
system using the same hardware.
Hypervisor is a bridge between the hardware and the virtual operating system, which allows
smooth functioning.
There are a total of five levels of implementation that are commonly used in cloud computing.
1.) Instruction Set Architecture Level (ISA)
ISA virtualization can work through ISA emulation. This is used to run many legacy codes that
were written for a different configuration of hardware. These codes run on any virtual machine
using the ISA. With this, a binary code that originally needed some additional layers to run is
now capable of running on the x86 machines. It can also be tweaked to run on the x64 machine.
With ISA, it is possible to make the virtual machine hardware agnostic.
For the basic emulation, an interpreter is needed, which interprets the source code and then
converts it into a hardware format that can be read. This then allows processing. This is one of
the five implementation levels of virtualization in cloud computing.
2.) Hardware Abstraction Level (HAL)
True to its name HAL lets the virtualization perform at the level of the hardware. This makes use
of a hypervisor which is used for functioning. At this level, the virtual machine is formed, and
this manages the hardware using the process of virtualization. It allows the virtualization of each
of the hardware components, which could be the input-output device, the memory, the processor,
etc.
Multiple users will not be able to use the same hardware and also use multiple virtualization
instances at the very same time. This is mostly used in the cloud-based infrastructure.
3.) Operating System Level
At the level of the operating system, the virtualization model is capable of creating a layer that is
abstract between the operating system and the application. This is an isolated container that is on
the operating system and the physical server, which makes use of the software and hardware.
Each of these then functions in the form of a server.
When there are several users, and no one wants to share the hardware, then this is where the
virtualization level is used. Every user will get his virtual environment using a virtual hardware
resource that is dedicated. In this way, there is no question of any conflict.
4.) Library Level
The operating system is cumbersome, and this is when the applications make use of the API that
is from the libraries at a user level. These APIs are documented well, and this is why the library
virtualization level is preferred in these scenarios. API hooks make it possible as it controls the
link of communication from the application to the system.
5.) Application Level
The application-level virtualization is used when there is a desire to virtualize only one
application and is the last of the implementation levels of virtualization in cloud computing. One
does not need to virtualize the entire environment of the platform.
This is generally used when you run virtual machines that use high-level languages. The
application will sit above the virtualization layer, which in turn sits on the application program.
It lets the high-level language programs compiled to be used in the application level of the virtual
machine run seamlessly.
CONCLUSION
There are in total of five implementation levels of virtualization in cloud computing. However,
every enterprise may not use each one of the different levels of virtualization implementation in
cloud computing. The level used is based on the working of the company and also on its
preference for the level of virtualization. The company will use the virtual machine to develop
and test across multiple platforms. Cloud-based applications are on the rise, which makes
virtualization a must-have thing for enterprises all over the world.

Web Technology
Due to cloud computing’s fundamental reliance on internetworking, Web browser
universality, and the ease of Web-based service development, Web technology is
generally used as both the implementation medium and the management
interface for cloud services.

This section introduces the primary Web technologies and discusses their
relationship to cloud services.
Resources vs. IT Resources

Artifacts accessible via the World Wide Web are referred to as resources or Web
resources. This is a more generic term than IT resources. An IT resource, within
the context of cloud computing, represents a physical or virtual IT-related artifact
that can be software or hardware-based. A resource on the Web, however, can
represent a wide range of artifacts accessible via the World Wide Web. For
example, a JPG image file accessed via a Web browser is considered a
resource. For examples of common IT resources, see the IT Resource section.
Furthermore, the term resource may be used in a broader sense to refer to
general types of processable artifacts that may not exist as standalone IT
resources. For example, CPUs and RAM memory are types of resources that are
grouped into resource pools and can be allocated to actual IT resources.
This section covers the following topics:
● Basic Web Technology
● Web Applications

Basic Web Technology

The World Wide Web is a system of interlinked IT resources that are accessed
through the Internet. The two basic components of the Web are the Web browser
client and the Web server. Other components, such as proxies, caching services,
gateways, and load balancers, are used to improve Web application
characteristics such as scalability and security. These additional components
reside in a layered architecture that is positioned between the client and the
server.

Three fundamental elements comprise the technology architecture of the Web:

● Uniform Resource Locators (URL) – A standard syntax used for creating
identifiers that point to Web-based resources, the URL is often
structured using a logical network location.
● Hypertext Transfer Protocol (HTTP) – This is the primary
communications protocol used to exchange content and data throughout
the World Wide Web. URLs are typically transmitted via HTTP.
● Markup Languages (HTML, XML) – Markup languages provide a
lightweight means of expressing Web-centric data and metadata. The
two primary markup languages are HTML (which is used to express the
presentation of Web pages) and XML (which allows for the definition of
vocabularies used to associate meaning to Web-based data via
metadata).
For example, a Web browser can request to execute an action like read, write,
update, or delete on a Web resource on the Internet, and proceed to identify and
locate the Web resource through its URL. The request is sent using HTTP to the
resource host, which is also identified by a URL. The Web server locates the
Web resource and performs the requested operation, which is followed by a
response being sent back to the client. The response may be comprised of
content that includes HTML and XML statements.
Web resources are represented as hypermedia as opposed to hypertext,
meaning media such as graphics, audio, video, plain text, and URLs can be
referenced collectively in a single document. Some types of hypermedia
resources cannot be rendered without additional software or Web browser
plug-ins.

Web Applications
A distributed application that uses Web-based technologies (and generally relies
on Web browsers for the presentation of user-interfaces) is typically considered a
Web application. These applications can be found in all kinds of cloud-based
environments due to their high accessibility.
Figure 1 presents a common architectural abstraction for Web applications that is
based on the basic three-tier model. The first tier is called the presentation layer,
which represents the user-interface. The middle tier is the application layer that
implements application logic, while the third tier is the data layer that is
comprised of persistent data stores.

Figure 1 – The three basic architectural tiers of Web applications.

The presentation layer has components on both the client and server-side. Web
servers receive client requests and retrieve requested resources directly as static
Web content and indirectly as dynamic Web content, which is generated
according to the application logic. Web servers interact with application servers in
order to execute the requested application logic, which then typically involves
interaction with one or more underlying databases.
PaaS ready-made environments enable cloud consumers to develop and deploy
Web applications. Typical PaaS offerings have separate instances of the Web
server, application server, and data storage server environments.
Note
For more information about URLs, HTTP, HTML, and XML, visit
www.servicetechspecs.com.

Multitenant Technology
The multitenant application design was created to enable multiple users (tenants) to
access the same application logic simultaneously. Each tenant has its own view of the
application that it uses, administers, and customizes as a dedicated instance of the
software while remaining unaware of other tenants that are using the same application.
Multitenant applications ensure that tenants do not have access to data and
configuration information that is not their own. Tenants can individually customize
features of the application, such as:
● User Interface – Tenants can define a specialized “look and feel” for their
application interface.
● Business Process – Tenants can customize the rules, logic, and workflows of
the business processes that are implemented in the application.
● Data Model – Tenants can extend the data schema of the application to
include, exclude, or rename fields in the application data structures.
● Access Control – Tenants can independently control the access rights for
users and groups.
Multitenant application architecture is often significantly more complex than that of
single-tenant applications. Multitenant applications need to support the sharing of
various artifacts by multiple users (including portals, data schemas, middleware, and
databases), while maintaining security levels that segregate individual tenant
operational environments.
Common characteristics of multitenant applications include:
● Usage Isolation – The usage behavior of one tenant does not affect the
application availability and performance of other tenants.
● Data Security – Tenants cannot access data that belongs to other tenants.
● Recovery – Backup and restore procedures are separately executed for the
data of each tenant.
● Application Upgrade – Tenants are not negatively affected by the synchronous
upgrading of shared software artifacts.
● Scalability – The application can scale to accommodate increases in usage by
existing tenants and/or increases in the number of tenants.
● Metered Usage – Tenants are charged only for the application processing and
features that are actually consumed.
 ● Data Tier Isolation – Tenants can have individual databases, tables, and/or
schemas isolated from other tenants. Alternatively, databases, tables, and/or
schemas can be designed to be intentionally shared by tenants.
A multitenant application that is being concurrently used by two different tenants is
illustrated in Figure 5.11. This type of application is typical with SaaS implementations.

Figure 1 – A multitenant application that is serving multiple cloud service consumers

simultaneously.
Multitenancy vs. Virtualization
Multitenancy is sometimes mistaken for virtualization because the concept of multiple
tenants is similar to the concept of virtualized instances.
The differences lie in what is multiplied within a physical server acting as a host:
● With virtualization: Multiple virtual copies of the server environment can be
hosted by a single physical server. Each copy can be provided to different
users, can be configured independently, and can contain its own operating
systems and applications.
● With multitenancy: A physical or virtual server hosting an application is
designed to allow usage by multiple different users. Each user feels as though
they have exclusive usage of the application.
Unit III - Architecture of Cloud and its Services

Cloud Architecture – Public cloud – private cloud – Hybrid cloud – Types of Services in
Cloud – Infrastructure as a Service (IAAS) - Platform as a Service (Paas) - Software-as-
aService (SaaS)- Cloud Storage – pros and cons of Cloud Storage - Virtualization concepts –
Disaster Recovery mechanism.
 Unit IV – Cloud Platforms and its Security
Resource management in Cloud – Scheduling – Scheduling Map reduce algorithms - cloud
resource management policies - overview of cloud security -Security issues – security
principles – security in Virtual machine – standards in Cloud Security.
Resource Management System

The resource management system mechanism helps coordinate IT resources in

response to management actions performed by both cloud consumers and cloud
providers (Figure 1). Core to this system is the virtual infrastructure manager (VIM) that
coordinates the server hardware so that virtual server instances can be created from the
most expedient underlying physical server. A VIM is a commercial product that can be
used to manage a range of virtual IT resources across multiple physical servers. For
example, a VIM can create and manage multiple instances of a hypervisor across
different physical servers or allocate a virtual server on one physical server to another
(or to a resource pool).
Tasks that are typically automated and implemented through the resource management
system include:
● managing virtual IT resource templates that are used to create pre-built
instances, such as virtual server images
● allocating and releasing virtual IT resources into the available physical
infrastructure in response to the starting, pausing, resuming, and termination
of virtual IT resource instances
● coordinating IT resources in relation to the involvement of other mechanisms,
such as resource replication, load balancer, and failover system
● enforcing usage and security policies throughout the lifecycle of cloud service
instances
● monitoring operational conditions of IT resources
Resource management system functions can be accessed by cloud resource
administrators employed by the cloud provider or cloud consumer. Those working on
behalf of a cloud provider will often be able to directly access the resource management
system’s native console.
Resource management systems typically expose APIs that allow cloud providers to
build remote administration system portals that can be customized to selectively offer
resource management controls to external cloud resource administrators acting on
behalf of cloud consumer organizations via usage and administration portals.
Figure 1 – The cloud consumer’s cloud resource administrator accesses a usage and
administration portal externally to administer a leased IT resource (1). The cloud
provider’s cloud resource administrator uses the native user-interface provided by the
VIM to perform internal resource management tasks (2).

Cloud resource management (CRM) policies

1.Admission control prevent the system from accepting workload in violation of high-level
system policies.
2. Capacity allocation allocate resources for individual activations of a service.
3. Load balancing distribute the workload evenly among the servers.
4. Energy optimization minimization of energy consumption.
5. Quality of service (QoS) guarantees ability to satisfy timing or other conditions specified
by a Service Level Agreement.

Mechanisms for the implementation of resource management policies

Control theory uses the feedback to guarantee system stability and predict transient
behavior.
Machine learning does not need a performance model of the system.
Utility-based requires a performance model and a mechanism to correlate user-level
performance with cost.
Market-oriented/economic do not require a model of the system, e.g., combinatorial
auctions for bundles of resources.

Scheduling
The aim of using scheduling techniques in cloud environment is to improve
system throughput and load balance, maximize the resource utilization, save
energy, reduce costs, and minimize the total processing time. Therefore, the
scheduler should consider the virtualized resources and users’ required
constraints to get efficient matching between jobs and resources. Each
scheduling technique should be based on one or more strategies. The most
important strategies or objectives commonly that are used, are time, cost,
energy, QoS, and fault tolerance.

Resources in cloud computing are scheduled at two levels: VM-level and

Host-level.
At the VM-level, tasks are mapped for execution to the allocated VMs using a
task/job scheduler. It is called Task Scheduling.
At the host-level, a VM scheduler is used to allocate the VMs into physical
hardware. This type is usually called VM Scheduling.

Scheduling Policies

There are two policies for scheduling in cloud computing: Space-Shared

scheduling and Time-Shared scheduling. Both policies are used for VM
scheduling and Task Scheduling. In space-shared scheduling policy, only one
VM/task is allowed to be executed at a given instance of a time on host/VM. In
Time-Shared scheduling policy, it allows multiple VMs/tasks to multitask and
run simultaneously within a host/VM. It shared the time among all VMs/tasks.

Scheduling Types:
Different types and categories of scheduling in cloud computing system are
shown

Centralized / decentralized scheduling When scheduling is centralized,

decisions are made in a central node. It insures efficiency and ease of
monitoring resources. However, it is lack of scalability and fault tolerance.
Decentralized or distributed scheduling is more applied in real cloud
environment although its lack of efficiency.

Static / Dynamic scheduling In static scheduling, all timing information about

tasks is available before so the execution schedule of each task is computed
before executing any task. It is effective for applications that have fixed
demands. Moreover, in static scheduling, the consumer makes agreement
with the cloud provider for services and the cloud provider prepares the
required resources before the start of required service. In dynamic scheduling,
the timing information about the tasks is not known at runtime. So the
execution schedule of task may change as per the user demand. Dynamic
scheduling incurs runtime overhead compared to static scheduling. In
dynamic scheduling, the cloud provider cannot plan before usage. It allocates
and remove resources as per needed.

Preemptive / Non-Preemptive scheduling Preemptive scheduling allows

interrupting each task during the execution and migrating the task to another
resource. For example, when a task has a higher priority than another task
and need to be executed although it is running in the IJCSNS International
Journal of Computer Science and Network Security, VOL.18 No.2, February
2018 111 virtual machine. Therefore, this type of scheduling is mandatory if
constraints need to be imposed such as priority, deadline, and cost. In
non-preemptive scheduling, the virtual machine cannot be taken away until
the task running on it completes. It does not allow the task to be interrupted
while it is executing

Immediate mode / Batch mode scheduling In immediate mode, called also

online mode, tasks are scheduled to resources immediately without any delay.
Tasks are scheduled only once and cannot be changed. On the other hand,
the batch mode collects tasks into a set and are examined for mapping at
prescheduled times. It is called also offline mode.

Heuristic / metaheuristic scheduling Heuristic scheduling techniques are

problem dependent that can solve specific problems. Metaheuristic
techniques are high level problem-independent techniques that provide
master strategies to solve general problems and can be applied to a wide
range of problems. Both scheduling techniques do not guarantee that they will
find the optimal solution, but they provide good solution when compared with
the time spent on computation.

MapReduce algorithm
The MapReduce algorithm contains two important tasks, namely Map and Reduce.
● The map task is done by means of Mapper Class
● The reduce task is done by means of Reducer Class.
Mapper class takes the input, tokenizes it, maps and sorts it. The output of Mapper
class is used as input by Reducer class, which in turn searches matching pairs and
reduces them.
MapReduce implements various mathematical algorithms to divide a task into small
parts and assign them to multiple systems. In technical terms, MapReduce algorithm
helps in sending the Map & Reduce tasks to appropriate servers in a cluster.
These mathematical algorithms may include the following −
● Sorting
● Searching
● Indexing
● TF-IDF
Sorting
Sorting is one of the basic MapReduce algorithms to process and analyze data.
MapReduce implements sorting algorithm to automatically sort the output key-value
pairs from the mapper by their keys.
● Sorting methods are implemented in the mapper class itself.
● In the Shuffle and Sort phase, after tokenizing the values in the mapper
class, the Context class (user-defined class) collects the matching valued
keys as a collection.
● To collect similar key-value pairs (intermediate keys), the Mapper class
takes the help of RawComparator class to sort the key-value pairs.
● The set of intermediate key-value pairs for a given Reducer is
automatically sorted by Hadoop to form key-values (K2, {V2, V2, …})
before they are presented to the Reducer.
Searching
Searching plays an important role in MapReduce algorithm. It helps in the combiner
phase (optional) and in the Reducer phase.
Indexing
Normally indexing is used to point to a particular data and its address. It performs
batch indexing on the input files for a particular Mapper.
The indexing technique that is normally used in MapReduce is known as inverted
index. Search engines like Google and Bing use inverted indexing technique. Let us try
to understand how Indexing works with the help of a simple example.
TF-IDF
TF-IDF is a text processing algorithm which is short for Term Frequency − Inverse
Document Frequency. It is one of the common web analysis algorithms. Here, the term
'frequency' refers to the number of times a term appears in a document.
Term Frequency (TF)
It measures how frequently a particular term occurs in a document. It is calculated by
the number of times a word appears in a document divided by the total number of
words in that document.
TF(the) = (Number of times term the ‘the’ appears in a document) / (Total number of terms
in the document)

Inverse Document Frequency (IDF)

It measures the importance of a term. It is calculated by the number of documents in
the text database divided by the number of documents where a specific term appears.
While computing TF, all the terms are considered equally important. That means, TF
counts the term frequency for normal words like “is”, “a”, “what”, etc. Thus we need to
know the frequent terms while scaling up the rare ones, by computing the following −
IDF(the) = log_e(Total number of documents / Number of documents with term ‘the’ in it).

Cloud security
Cloud security refers to the technologies, policies, controls, and services that protect cloud
data, applications, and infrastructure from threats.\

Cloud security is a responsibility that is shared between the cloud provider

and the customer.

Cloud user
Cloud Service Provider
Computing Resources

Cloud Security Challenges

Lack of visibility
It's easy to lose track of how your data is being accessed and by whom, since many
cloud services are accessed outside of corporate networks and through third parties.
Multitenancy
Public cloud environments house multiple client infrastructures under the same
umbrella, so it's possible your hosted services can get compromised by malicious
attackers as collateral damage when targeting other businesses.
Access management and shadow IT
While enterprises may be able to successfully manage and restrict access points across
on-premises systems, administering these same levels of restrictions can be
challenging in cloud environments. This can be dangerous for organizations that don't
deploy bring-your-own device (BYOD) policies and allow unfiltered access to cloud
services from any device or geolocation.
Compliance
Regulatory compliance management is oftentimes a source of confusion for enterprises
using public or hybrid cloud deployments. Overall accountability for data privacy and
security still rests with the enterprise, and heavy reliance on third-party solutions to
manage this component can lead to costly compliance issues.
Misconfigurations
Misconfigured assets accounted for 86% of breached records in 2019, making the
inadvertent insider a key issue for cloud computing environments. Misconfigurations can
include leaving default administrative passwords in place, or not creating appropriate
privacy settings.

Approaches of Cloud Security

The way to approach cloud security is different for every organization and can be
dependent on several variables. However, the National Institute of Standards and
Technology (NIST) has made a list of best practices that can be followed to establish a
secure and sustainable cloud computing framework.
The NIST has created necessary steps for every organization to self-assess their
security preparedness and apply adequate preventative and recovery security
measures to their systems. These principles are built on the NIST's five pillars of a
cybersecurity framework: Identify, Protect, Detect, Respond, and Recover.
Another emerging technology in cloud security that supports the execution of NIST's
cybersecurity framework is cloud security posture management (CSPM). CSPM
solutions are designed to address a common flaw in many cloud environments -
misconfigurations.
Cloud infrastructures that remain misconfigured by enterprises or even cloud providers
can lead to several vulnerabilities that significantly increase an organization's attack
surface. CSPM addresses these issues by helping to organize and deploy the core
components of cloud security. These include identity and access management (IAM),
regulatory compliance management, traffic monitoring, threat response, risk mitigation,
and digital asset management.

https://www.slideshare.net/mkotari/scheduling-in-cloud

https://www.slideshare.net/mkotari/scheduling-in-cloud

Unit – V Tools and software in cloud

Apache Cloud Stack- OpenStack- ManageIQ- Cloudify- Hadoop Framework – Google App -
Map Reduce – Virtual Box – Nimbus – Develop applications based on tools and software in
cloud.

https://www.javatpoint.com/what-is-hadoop
What is Hadoop
Hadoop is an open source framework from Apache and is used to store process and
analyze data which are very huge in volume. Hadoop is written in Java and is not OLAP
(online analytical processing). It is used for batch/offline processing.It is being used by
Facebook, Yahoo, Google, Twitter, LinkedIn and many more. Moreover it can be scaled
up just by adding nodes in the cluster.
Modules of Hadoop
1. HDFS: Hadoop Distributed File System. Google published its paper GFS and on
the basis of that HDFS was developed. It states that the files will be broken into
blocks and stored in nodes over the distributed architecture.
2. Yarn: Yet another Resource Negotiator is used for job scheduling and manage
the cluster.
3. Map Reduce: This is a framework which helps Java programs to do the parallel
computation on data using key value pair. The Map task takes input data and
converts it into a data set which can be computed in Key value pair. The output of
Map task is consumed by reduce task and then the out of reducer gives the
desired result.
4. Hadoop Common: These Java libraries are used to start Hadoop and are used by
other Hadoop modules.

Hadoop Architecture
The Hadoop architecture is a package of the file system, MapReduce engine and the
HDFS (Hadoop Distributed File System). The MapReduce engine can be
MapReduce/MR1 or YARN/MR2.
A Hadoop cluster consists of a single master and multiple slave nodes. The master
node includes Job Tracker, Task Tracker, NameNode, and DataNode whereas the slave
node includes DataNode and TaskTracker.
Hadoop Distributed File System
The Hadoop Distributed File System (HDFS) is a distributed file system for Hadoop. It
contains a master/slave architecture. This architecture consist of a single NameNode
performs the role of master, and multiple DataNodes performs the role of a slave.
Both NameNode and DataNode are capable enough to run on commodity machines.
The Java language is used to develop HDFS. So any machine that supports Java
language can easily run the NameNode and DataNode software.

NameNode
● It is a single master server exist in the HDFS cluster.
● As it is a single node, it may become the reason of single point failure.
● It manages the file system namespace by executing an operation like the
opening, renaming and closing the files.
● It simplifies the architecture of the system.
DataNode
● The HDFS cluster contains multiple DataNodes.
● Each DataNode contains multiple data blocks.
● These data blocks are used to store data.
● It is the responsibility of DataNode to read and write requests from the file
system's clients.
 ● It performs block creation, deletion, and replication upon instruction from the
NameNode.
Job Tracker
● The role of Job Tracker is to accept the MapReduce jobs from client and process
the data by using NameNode.
● In response, NameNode provides metadata to Job Tracker.
Task Tracker
● It works as a slave node for Job Tracker.
● It receives task and code from Job Tracker and applies that code on the file. This
process can also be called as a Mapper.

MapReduce Layer
The MapReduce comes into existence when the client application submits the
MapReduce job to Job Tracker. In response, the Job Tracker sends the request to the
appropriate Task Trackers. Sometimes, the TaskTracker fails or time out. In such a case,
that part of the job is rescheduled.
Advantages of Hadoop
● Fast: In HDFS the data distributed over the cluster and are mapped which helps
in faster retrieval. Even the tools to process the data are often on the same
servers, thus reducing the processing time. It is able to process terabytes of data
in minutes and Peta bytes in hours.
● Scalable: Hadoop cluster can be extended by just adding nodes in the cluster.
● Cost Effective: Hadoop is open source and uses commodity hardware to store
data so it is really cost effective as compared to traditional relational database
management systems.
● Resilient to failure: HDFS has the property with which it can replicate data over
the network, so if one node is down or some other network failure happens, then
Hadoop takes the other copy of data and uses it. Normally, data are replicated
thrice but the replication factor is configurable.

What is HDFS
Hadoop comes with a distributed file system called HDFS. In HDFS data is distributed
over several machines and replicated to ensure their durability to failure and high
availability to parallel application.
It is cost effective as it uses commodity hardware. It involves the concept of blocks,
data nodes and node name.
HDFS Concepts
 1. Blocks: A Block is the minimum amount of data that it can read or write.HDFS
blocks are 128 MB by default and this is configurable.Files n HDFS are broken
into block-sized chunks,which are stored as independent units.Unlike a file
system, if the file is in HDFS is smaller than block size, then it does not occupy
full block?s size, i.e. 5 MB of file stored in HDFS of block size 128 MB takes 5MB
of space only.The HDFS block size is large just to minimize the cost of seek.
2. Name Node: HDFS works in master-worker pattern where the name node acts as
master.Name Node is controller and manager of HDFS as it knows the status and
the metadata of all the files in HDFS; the metadata information being file
permission, names and location of each block.The metadata are small, so it is
stored in the memory of name node,allowing faster access to data. Moreover the
HDFS cluster is accessed by multiple clients concurrently,so all this information
is handled bya single machine. The file system operations like opening, closing,
renaming etc. are executed by it.
3. Data Node: They store and retrieve blocks when they are told to; by client or
name node. They report back to the name node periodically, with a list of blocks
that they are storing. The data node being a commodity hardware also does the
work of block creation, deletion and replication as stated by the name node.

Features of HDFS
● Highly Scalable - HDFS is highly scalable as it can scale hundreds of nodes in a
single cluster.
● Replication - Due to some unfavorable conditions, the node containing the data
may be loss. So, to overcome such problems, HDFS always maintains the copy of
data on a different machine.
● Fault tolerance - In HDFS, the fault tolerance signifies the robustness of the
system in the event of failure. The HDFS is highly fault-tolerant that if any
machine fails, the other machine containing the copy of that data automatically
become active.
● Distributed data storage - This is one of the most important features of HDFS
that makes Hadoop very powerful. Here, data is divided into multiple blocks and
stored into nodes.
● Portable - HDFS is designed in such a way that it can easily portable from
platform to another.

What is YARN
Yet Another Resource Manager takes programming to the next level beyond Java , and
makes it interactive to let another application Hbase, Spark etc. to work on it.Different
Yarn applications can co-exist on the same cluster so MapReduce, Hbase, Spark all can
run at the same time bringing great benefits for manageability and cluster utilization.

Components Of YARN
 ● Client: For submitting MapReduce jobs.
● Resource Manager: To manage the use of resources across the cluster
● Node Manager:For launching and monitoring the computer containers on
machines in the cluster.
● Map Reduce Application Master: Checks tasks running the MapReduce job. The
application master and the MapReduce tasks run in containers that are
scheduled by the resource manager, and managed by the node managers.
Jobtracker & Tasktracker were used in previous versions of Hadoop, which were
responsible for handling resources and checking progress management. However,
Hadoop 2.0 has a Resource manager and NodeManager to overcome the shortfall of
Jobtracker & Tasktracker.

Steps in Map Reduce

● The map takes data in the form of pairs and returns a list of <key, value> pairs.
The keys will not be unique in this case.
● Using the output of Map, sort and shuffle are applied by the Hadoop architecture.
This sort and shuffle acts on these list of <key, value> pairs and sends out unique
keys and a list of values associated with this unique key <key, list(values)>.
● An output of sort and shuffle sent to the reducer phase. The reducer performs a
defined function on a list of values for unique keys, and Final output <key, value>
will be stored/displayed.

Sort and Shuffle

The sort and shuffle occur on the output of Mapper and before the reducer. When the
Mapper task is complete, the results are sorted by key, partitioned if there are multiple
reducers, and then written to disk. Using the input from each Mapper <k2,v2>, we collect
all the values for each unique key k2. This output from the shuffle phase in the form of
<k2, list(v2)> is sent as input to reducer phase.

Usage of MapReduce
● It can be used in various application like document clustering, distributed sorting,
and web link-graph reversal.
● It can be used for distributed pattern-based searching.
● We can also use MapReduce in machine learning.
● It was used by Google to regenerate Google's index of the World Wide Web.
● It can be used in multiple computing environments such as multi-cluster,
multi-core, and mobile environments.

Google App Engine

The App Engine is Google’s Platform as a Service(PaaS) offering. It is a compute
service that provides a managed platform for running applications. As this is a
managed service, your focus should be on the application only and Google will
manage the resources needed to run the application. Thus App Engine users
have less to manage, but you will have less control over the compute resources.
The applications hosted on App Engine are highly scalable and run reliably even
under heavy load.
The App Engine supports the following languages:
● Python
● Go
● Ruby
● PHP
● Node.js
● Java
● .NET
The App Engine provides two types of runtime environments: standard and
flexible.
1. The Standard environment provides a secured and sandboxed
environment for running applications and distributes requests across
multiple servers to meet the demand. The applications run
independently of the hardware, OS, and physical location of the server.
2. The Flexible environment provides more options and control to the
developers who want to use App Engine, but without the language
constraints of the standard environment. It uses Docker containers as
the basic building blocks. These containers can be auto-scaled
according to load.
Pros of App Engine:
● You need to focus only on the application code, the rest of everything is
managed by Google. Thus reducing management complexities.
● As it provides version management, thus it is easy to maintain and roll
out versions of applications.
● It has faster autoscaling as the size of instances is smaller.
● Easy to deploy and monitor.
Cons of App Engine:
● It is more constrained as the instances are smaller, thus enabling fast
autoscaling, but there can be cases when large applications require
larger instances.
● As it is a fully managed service, the user has no control over the
underlying infrastructure that may be required for some complex
applications.
● It is expensive in the long run as the cost adds up quickly.

VirtualBox
VirtualBox is open-source software for virtualizing the x86 computing
architecture. It acts as a hypervisor, creating a VM (virtual machine) where
the user can run another OS (operating system).
The operating system where
VirtualBox runs is alled the "host" OS.
The operating system running in the
VM is called the "guest" OS.
VirtualBox supports Windows, Linux,
or macOS as its host OS.
When configuring a virtual machine,
the user can specify how many CPU
cores, and how much RAM and disk
space should be devoted to the VM.
When the VM is running, it can be
"paused." System execution is frozen
at that moment in time, and the user
can resume using it later.
VirtualBox was originally developed
by Innotek GmbH, and released on
January 17, 2007 as an open-source
software package. The company was later purchased by Sun Microsystems.
On January 27, 2010, Oracle Corporation purchased Sun, and took over
development of VirtualBox.
Supported guest operating systems
Guest operating systems supported by VirtualBox include:
● Windows 10, 8, 7, XP, Vista, 2000, NT, and 98.
● Linux distributions based on Linux kernel 2.4 and
newer, including Ubuntu, Debian, OpenSUSE,
Mandriva/Mandrake, Fedora, RHEL, and Arch Linux.
● Solaris and OpenSolaris.
● macOS X Server Leopard and Snow Leopard.
● OpenBSD and FreeBSD.
● MS-DOS.
● OS/2.
● QNX.
● BeOS R5.
● Haiku.
● ReactOS.
NIMBUS
Nimbus is an open-source toolkit to convert a computer cluster into an
Infrastructure-as-a-Service cloud to provide compute cycles for scientific
communities. It allows a client to lease remote resources by deploying
virtual machines (VMs) on those resources and configuring them to
represent an environment desired by the user.
Nimbus is comprised of two products:
● Nimbus Infrastructure is an open source EC2/S3-compatible
Infrastructure-as-a-Service implementation specifically targeting
features of interest to the scientific community such as support for
proxy credentials, batch schedulers, best-effort allocations and
others.
● Nimbus Platform is an integrated set of tools, operating in a
multi-cloud environment, that deliver the power and versatility of
infrastructure clouds to scientific users. Nimbus Platform allows
you to reliably deploy, scale, and manage cloud resources.

The Nimbus cloud client allows the user to provision customized

compute nodes, called a workspace, and maintain full control over it
using a leasing model based on the Amazon’s Elastic Compute Cloud
(EC2) service.

The Nimbus cloud-computing infrastructure allows scientists working on

data-intensive research to create and use such virtual machines with a
cloud provider.
Nimbus also allows users to create multiple virtual machines to complete
specific computational jobs that can be deployed throughout the cloud
and still work in tandem with each other. This flexibility allows a user to
configure a virtual machine and then connect it to resources on a cloud,
regardless of who is providing the cloud.

Having this kind of flexibility and on-demand computing power is vital to

projects that are extremely data-intensive, such as research efforts in
experimental and theoretical physics. Nimbus has already been
deployed successfully to support the STAR nuclear physics experiment
at Brookhaven National Laboratory’s Relativistic Heavy-Ion Collider.
When researchers there needed to turn the massive amounts of data
they had generated into viable simulations for an international
conference, they used Nimbus to create virtual machines that were run
through commercial cloud computing providers.