UNIT 2 Cloud Computing CS334
UNIT 2 Cloud Computing CS334
UNIT 2 Cloud Computing CS334
i) Public cloud
ii) Private cloud
iii) Hybrid cloud
iv) Community cloud
i) Public cloud
In the public cloud, systems and services are accessible to the general public. For
It is easy to combine public cloud with private cloud so it gives the flexible approach to the
customer.
It is reliable because it provides large number of resources from various locations and if anyresource
fails, another is employed.
ii) Private cloud
In the private cloud, systems and services are accessible within an organization.
As compared to the Public cloud, Private cloud has more control on its resources and hardware
because it accessed only in the boundary of an organization.
Disadvantages of Private Cloud:
Private cloud is very difficult to deploy globally and it can be accessed locally only.
Private cloud's cost is more than that of Public cloud.
In hybrid cloud, critical activities are conducted using Private cloud and the non-criticalactivities
1) Software-as-a-Service (SaaS)
SaaS is known as 'On-Demand Software'.
It is a software distribution model. In this model, the applications are hosted by a cloudservice
provider and publicized to the customers over internet.
In SaaS, associated data and software are hosted centrally on the cloud server.
User can access SaaS by using a thin client through a web browser.
CRM, Office Suite, Email, games, etc. are the software applications which are provided as a service
through Internet.
The companies like Google, Microsoft provide their applications as a service to the end users.
Advantages of SaaS
SaaS is easy to buy because the pricing of SaaS is based on monthly or annual fee and it allows the
organizations to access business functionalities at a small cost, which is less thanlicensed
applications.
SaaS needed less hardware, because the software is hosted remotely, hence organizations donot need
to invest in additional hardware.
Less maintenance cost is required for SaaS and do not require special software or hardware versions.
Disadvantages of SaaS
SaaS applications are totally dependent on Internet connection. They are not usable withoutInternet
connection.
It is difficult to switch amongst the SaaS vendors.
3. Platform-as-a-Service (PaaS)
PaaS is a programming platform for developers. This platform is generated for the
programmers to create, test, run and manage the applications.
A developer can easily write the application and deploy it directly into PaaS layer.
PaaS gives the runtime environment for application development and deployment tools.
Google Apps Engine(GAE), Windows Azure, SalesForce.com are the examples of
PaaS.
Advantages of PaaS
PaaS is easier to develop. Developer can concentrate on the development and innovationwithout
worrying about the infrastructure.
In PaaS, developer only requires a PC and an Internet connection to start building applications.
Disadvantages of PaaS
One developer can write the applications as per the platform provided by PaaS vendor
hencethe moving the application to another PaaS vendor is a problem
4) Infrastructure-as-a-Service (IaaS)
i) IaaS is a way to deliver a cloud computing infrastructure like server, storage, network and
operating system.
ii) The customers can access these resources over cloud computing platform i.e Internet as anon-
demand service.
iii) In IaaS, you buy complete resources rather than purchasing server, software, datacenter
space or network equipment.
iv) IaaS was earlier called as Hardware as a Service(HaaS). It is a Cloud computing platform
based model.
v) HaaS differs from IaaS in the way that users have the bare hardware on which they can deploy their
own infrastructure using most appropriate software.
Advantages of IaaS
In IaaS, user can dynamically choose a CPU, memory storage configuration according to need.
Users can easily access the vast computing power available on IaaS Cloud platform.
Disadvantages of IaaS
IaaS cloud computing platform model is dependent on availability of Internet and
virtualization services.
Cloud Reference Model
The cloud computing reference model is an abstract model that divides a cloud computing environment
into abstraction layers and cross-layer functions to characterize and standardize its functions. This
reference model divides cloud computing activities and functions into three cross-layer functions and five
logical layers.
Each of these layers describes different things that might be present in a cloud computing environment,
such as computing systems, networking, storage equipment, virtualization software, security measures,
control and management software, and so forth. It also explains the connections between these
organizations. The five layers are the Physical layer, virtual layer, control layer, service orchestration
layer, and service layer.
1. SaaS
Software as a Service (SaaS) is a form of application delivery that relieves users of the burden of software
maintenance while making development and testing easier for service providers.
The cloud delivery model's top layer is where applications are located. End customers get access to the
services this tier offers via web portals. Because online software services provide the same functionality
as locally installed computer programs, consumers (users) are rapidly switching from them. Today, ILMS
and other application software can be accessed via the web as a service.
In terms of data access, collaboration, editing, storage, and document sharing, SaaS is unquestionably a
crucial service. Email service in a web browser is the most well-known and widely used example of SaaS,
but SaaS applications are becoming more cooperative and advanced.
The cloud consumer has full control over all the cloud services.
The provider has full control over software applications-based services.
The cloud provider has partial control over the implementation of cloud services.
The consumer has limited control over the implementation of these cloud services.
2. PaaS
Platform as a Service is a strategy that offers a high level of abstraction to make a cloud readily
programmable in addition to infrastructure-oriented clouds that offer basic compute and storage capabilities
(PaaS). Developers can construct and deploy apps on a cloud platform without necessarily needing to know
how many processors or how much memory their applications would use. A PaaS offering that provides a
scalable environment for creating and hosting web applications is Google App Engine, for instance .
The cloud provider has entire rights or control over the provision of cloud services to consumers.
The cloud consumer has selective control based on the resources they need or have opted for on the
application server, database, or middleware.
Consumers get environments in which they can develop their applications or databases. These
environments are usually very visual and very easy to use.
Provides options for scalability and security of the user’s resources.
Services to create workflows and websites.
Services to connect users’ cloud platforms to other external platforms.
3. IaaS
Infrastructure as a Service (IaaS) offers storage and computer resources that developers and IT
organizations use to deliver custom/business solutions. IaaS delivers computer hardware (servers,
networking technology, storage, and data center space) as a service. It may also include the delivery of OS
and virtualization technology to manage the resources. Here, the more important point is that IaaS
customers rent computing resources instead of buying and installing them in their data centers. The service
is typically
paid for on a usage basis. The service may include dynamic scaling so that if the customers need more
resources than expected, they can get them immediately.
The consumer has full/partial control over the infrastructure of the cloud, servers, and databases.
The consumer has control over the Virtual Machines' implementation and maintenance.
The consumer has a choice of already installed VM machines with pre-installed Operating systems.
The cloud provider has full control over the data centers and the other hardware involved in them.
It has the ability to scale resources based on the usage of users.
It can also copy data worldwide so that data can be accessed from anywhere in the world as soon as
possible.
The principle of NIST Cloud computing reference architecture are:
1. Public
This is the model where cloud infrastructure and resources are given to the public via a public network.
These models are generally owned by companies that sell cloud services.
2. Private
This is the model where cloud infrastructure and resources are only accessible by the cloud consumer.
These models are generally owned by cloud consumers themselves or a third party.
3. Community
This is the model where a group of cloud consumers might share their cloud infrastructure and resources
as they may have the same goal and policies to be achieved. These models are owned by organizations or
third-party.
4. Hybrid
This model consists of a mixture of different deployment models like public, private, or community. This
helps in the exchange of data or applications between various models.
There are five major actors in NIST cloud computing reference architecture. They are:
1. Cloud Consumer
2. Cloud Provider
3. Cloud Carrier
4. Cloud Auditor
5. Cloud Broker
The below image will explain cloud computing reference model with a neat diagram.
Each actor is an entity that participates in the process and/or completes duties in cloud computing. This
entity could be a person or an organization.
1. Cloud Consumer
The end user that the cloud computing service is designed to support is the cloud consumer. An individual
or corporation with a working relationship with a cloud provider and utilizing its service s is referred to as
a cloud consumer. A cloud customer peruses a cloud provider's service catalog, makes the proper service
request, enters into a service agreement with the cloud provider, and then utilizes the service. The cloud
customer may be charged for the service provided, in which case payment arrangements must be made.
They need to have a cloud Service Level Agreement (SLA).
2. Cloud Provider
Any individual, group, or other entity in charge of making a service accessible to cloud users is a cloud
provider. A cloud provider creates the requested software, platforms, and infrastructure services, manages
the technical infrastructure needed to supply the services, provisions the services at agreed -upon service
levels, and safeguards the services' security and privacy.
Through service interfaces and virtual network interfaces that aid in resource abstraction, the cloud
provider implements the cloud software to make computing resources accessible to cloud consumers that
use the infrastructure as a service.
3. Cloud Carrier
A cloud carrier serves as an intermediary between cloud providers and customers, facilitating connectivity
and transport of cloud services. Customers can access the cloud through the network, telecommunication,
and other access equipment provided by cloud carriers. Customers of cloud services, for instance, can get
them through network access devices, including laptops, mobile phones, PCs, and mobile Internet devices
(MIDs), among others. Network and telecommunication carriers typically handle the distribution of cloud
services, while a transport agent is a company that arranges for the physical delivery of storage devices
like high-capacity hard drives.
Remember that a cloud provider will establish service level agreements (SLAs) with a cloud carrier to
provide services at a level consistent with the SLAs offered to cloud consumers. The cloud provider may
also demand that the cloud carrier provide dedicated and encrypted connections between cloud consumers
and cloud providers.
4. Cloud Auditor
An unbiased evaluation of cloud services, information system operations, performance, and the security of
a cloud computing implementation can be done by a cloud auditor. A cloud auditor can assess a cloud
provider's services in terms of performance, service level agreement compliance, privacy implications, and
security controls.
The management, operational, and technical precautions or countermeasures used inside an organizational
information system to ensure the privacy, availability, and integrity of the system and its data are known
as security controls.
To do a security audit, a cloud auditor can evaluate the information system's security controls to see how
well they are being implemented, functioning as intended, and achieving the required results in relation to
the system's security needs. Verifying compliance with law and security policy should be part of the
security audit.
5. Cloud Broker
An organization called a "Cloud Broker" controls how cloud services are used, performed, and delive red
and negotiates contracts between cloud providers and cloud users. The integration of cloud services could
become too difficult for cloud consumers to handle as cloud computing develops. Instead of contacting a
cloud provider directly in certain circumstances, a cloud consumer may request cloud services through a
cloud broker. A single point of access for controlling numerous cloud services is offered by cloud brokers.
The capacity to offer a single consistent interface to numerous different providers, w hether the interface is
for commercial or technical objectives, separates a cloud broker from a cloud service provider. Cloud
Brokers provide services in three categories:
1. Cloud Scalability
In cloud computing, cloud scalability refers to the ability to increase or reduce IT resources as required to
meet evolving demands. One of the hallmarks of the cloud and the key factor of its burgeoning popularity
with companies is scalability.
Using existing cloud computing technology, data storage space, processing power and networking can all be
escalated. Better still, scaling, usually with little or no interruption or downtime, can be achieved rapidly and
easily. Third-party cloud providers now have the entire infrastructure in place; in the past, the process could
take weeks or months to scale with on-site physical infrastructure and entail enormous costs.
To set up a personalized, scalable cloud solution via a public cloud, private cloud, or hybrid cloud,
businesses have several options.
In cloud computing, two specific forms of scalability exist vertical and horizontal scaling.
We can add or subtract power to an existing cloud server memory upgrade, storage, or computing power
with vertical scaling, also known as "scaling up" or "scaling down". This generally indicates that scaling has
an upper limit based on the scaling capability of the server or machine; scaling above that also includes
downtime.
We can add more resources like servers to our system using horizontal scalability to spread the workload
across computers, which in turn improves efficiency and storage space. For companies with high-availability
services that need limited downtime, horizontal scaling is essential.
In cloud computing, fault tolerance is conceptually the same as in private or hosted environments. In other
words, it means the infrastructure's ability to continue to provide service/services to underlying applications
even when one or more component fails. To continue to work through failure or repair, we do not need to
configure certain facilities for our infrastructure to use.
The fault-tolerant system uses backup components that take the place of failed components automatically,
ensuring no service loss. They include:
Hardware systems
Hardware systems can be backed up using identical or equivalent systems. For instance, using an
identical server running in parallel, with all operations mirrored to the backup server, a server can be
made fault-tolerant.
Software systems
Software systems can be backed up using software instances. For example, it is possible to
continuously replicate a database with customer information on another machine and operations can
be mechanically redirected to another database in case a primary database goes down.
Power sources
Power sources use alternative sources using fault-tolerant. In many instances, organizations have
power generators that can be used in case the electricity fails.
Similarly, using redundancy, any system or component that is a single point of failure can be made
fault-tolerant.
Security Breach Occurrences
Owing to security failures, there are many explanations about why fault tolerance exists. The server's
hacking adversely affects the server and results in a leak of data. Ransomware, phishing, virus attack,
etc. are other explanations for the need for fault tolerance in the form of security violations.
Replication
For every operation, the fault-tolerant system operates on the principle of running many other
replicates. Therefore, if one aspect of the device goes wrong, it has other instances that can be put to
keep it going instead. For example, a database of clusters that has 3 servers with the same
information on each of them. All the acts are written on each of them, such as adding data,
upgrading, and deleting. The redundant servers will be in inactive mode unless and until the
availability of them is requested by any fault tolerance scheme.
Redundancy
If any part of the system fails or moves to a downstate, then it is necessary to have backup systems.
For example, due to some hardware faults, a website programmer that has MS SQL as its database
can fail in between. In the redundancy principle, a server works with an emergency database
comprising many backup resources.
When developing a fault tolerance scheme, all the facilities have to be given priority. Special priority needs
to be given to the database since it drives many other units.
The enterprise has to work on the test after deciding the objectives. Take the company's forum website, for
example, which allows users to log in and make comments. If any problem causes the authentication
services to malfunction, users may not be able to log in. The platform then becomes a read-only one and
does not fulfill the objective. But remediation can be assured with fault-tolerant systems, and the user will
search for details with minimal effect.
Cloud Solutions:
Cloud solutions, also known as cloud computing or cloud services, deliver IT resources on demand over the
Internet. Cloud service providers such Amazon Web Services, Microsoft Azure and Google Cloud
Platform can deliver everything from applications to data centers on a pay-for-use basis to their subscribers.
With cloud solutions, IT resources can scale up or down quickly to meet business demands. Cloud solutions
enable rapid access to flexible and low-cost IT resources without large upfront investments in hardware or
time-consuming installation and maintenance. Businesses can provision exactly the type and size of computing
resources they need to power a new initiative or operate their IT departments more efficiently.
Most cloud solutions fall into three categories: Infrastructure-as-a-Service (IaaS), Platform-as-a-
Service (PaaS), and Software-as-a-Service (SaaS). IaaS allows businesses to essentially rent their IT
infrastructure from a cloud provider. PaaS supplies an on-demand environment for software development.
SaaS delivers applications over the Internet. Businesses of all sizes use cloud solutions to reduce hardware,
software and IT maintenance costs. As cloud solutions evolve beyond IaaS, PaaS and SaaS offerings,
enterprises are relying on the cloud for software-defined technology. Data center resources – including
compute, storage and network resources – can be virtualized and centrally managed as software-defined pools.
Cloud providers are now offering pre-built cloud solutions with the agility to deploy abstracted, software-
defined resources to workloads as needed
Cloud Ecosystem:
A cloud ecosystem is a complex system of interdependent components that all work together to enable cloud
services. In nature, an ecosystem is composed of living and nonliving things that are connected and work
together. In cloud computing, the ecosystem consists of hardware and software as well as cloud
customers, cloud engineers, consultants, integrators and partners.
Werner Vogels, CTO at Amazon, first compared the cloud to an ecosystem in a keynote address at the Cloud
Connect 2011 conference. At the time, enterprise cloud computing was usually thought of in terms of three
broad service areas -- infrastructure-as-a-service (IaaS), platform-as-a-service (PaaS) and software-as-a-
service (SaaS). Vogels proposed that the cloud was really more complex and its description also needed to
include the array of service providers that companies rely on to operate in the cloud.
The center of a cloud ecosystem is a public cloud provider. It might be an IaaS provider such as Amazon Web
Services (AWS) or a SaaS vendor such as Salesforce. Radiating out from the center of the cloud are software
companies that use the provider's anchor platform, as well as consultants and companies that have formed
strategic alliances with the anchor provider.
There is no vendor lock-in because these companies overlap, making the ecosystem more complex. For
example, AWS is the center of its own ecosystem, but it's also a part of the Salesforce ecosystem. Salesforce
runs a number of its services on AWS's infrastructure, and Salesforce customers can gain access, through
devices called connectors, to pieces of AWS, such as its Simple Storage Service (S3).
A robust ecosystem provides a cloud provider's customers with an easy way to find and purchase business
applications and respond to changing business needs. When the apps are sold through a provider’s app store
such as AWS Marketplace, Microsoft Azure Marketplace (for cloud software) or Microsoft AppSource (for
business applications), the customer essentially has access to a catalog of different vendors' software and
services that have already been vetted and reviewed for security, risk and cost.
The benefits of a cloud ecosystem
Companies can use a cloud ecosystem to build new business models. It becomes relatively easy for a medical
device manufacturer, for example, to launch a heart-monitoring service on its cloud service provider's cloud
infrastructure and then sell the service alongside its main business of manufacturing heart monitors for
hospitals.
In a cloud ecosystem, it is also easier to aggregate data and analyze how each part of the system affects the
other parts. For example, if an ecosystem consists of patient records, smart device logs and healthcare provider
records, it becomes possible to analyze patterns across an entire patient population.
BPM Cloud is a cloud-based implementation of a Business Process Management (BPM) platform. It allows
organizations to manage their business processes over the internet without needing expensive hardware and IT
infrastructure.
1. Minimized Errors
Cloud BPM solutions help you keep error rates minimal. Say goodbye to mountains of paperwork and manual
data entry riddled with errors. Multiple records are also eliminated since changes are synced and visible to every
Legacy systems store data on a local drive. This can be rather limited in terms of access.
Cloud BPM, on the other hand, stores information in a centralized database thereby making access possible any
time from any location. Further, stakeholders can access the application from any device.
3. Secure Data
Data security is an often-expressed concern from organizations when presented with the opportunity to move to
cloud BPM. Limiting access to confidential information is high on the list of requirements.
Cloud BPM applications such as Kissflow come with a wide range of security features such as role-based access,
conditional visibility, data encryption, and more. Reputed cloud business process management service
providers host their applications on reliable platforms such as Amazon Web Services or Google Cloud Platform,
Legacy systems don’t enjoy great reputation in terms of the experience they provide. At best, they are cumbersome
and time-consuming. Users are constantly threatened by the possibility of server downtime and virus or malware
attacks.
With cloud BPM, vendors provide ample backup to ensure that there’s minimal downtime if at all. They also
When you use on-premise software, you’re saddled with endless details like installation, configuration, storing
data, ensuring adequate space to run the software, buying additional hardware, and arranging for backups. As for
updates, installing them on each system and scheduling required downtime becomes your responsibility.
Whatever the software needs to function, it becomes your burden to bear. Needless to say, your IT department’s
With cloud BPM, the vendor assumes responsibility for all day-to-day operations of the application. This includes
aspects such as performance, memory, storage, hosting, backups, and downtime. In case of new releases or bug
fixes, they are immediately implemented for all users. This means that your IT department can focus on other
pressing matters. Meanwhile, any issues you encounter are easily addressed by round-the-clock support from your
6. Better Collaboration
Collaboration is incredibly easy with cloud BPM, irrespective of whether your teams are on the same office floor
or different continents. Centralized documentation, digital checklists, and automated process flow make it
Cloud BPM applications feature reporting capabilities that provide comprehensive insights. Given that all data is
stored in a central database, it becomes simpler to monitor and analyze patterns. Information gathered from these
reports can then help refine strategies and make critical decisions.
Legacy BPM systems can no longer help organizations stay abreast with rapid developments in your industry.
Your organization needs a solution that is simple, easy to use, and optimized for your processes.
The management of cloud infrastructure products and services is cloud management. Public clouds are
operated by public cloud service providers, which provide the servers, storage, networking and data centre
operations of the public cloud environment. With a third-party cloud management tool, users can also
choose to manage their public cloud services.
Public cloud service users can typically choose from three categories of specific cloud provisioning:
User self-provisioning: Users, usually via a web form or console interface, buy cloud services
directly from the provider. On a per-transaction basis, the client pays.
Advanced provisioning: A pre-determined sum of services scheduled in advance of operation is
contracted in advance by customers. A flat fee or a monthly fee is charged by the consumer.
Dynamic provisioning: When the client requires them, the provider allocates resources, and then
decommissions them when they are no longer required. On a pay-per-use basis, the client is paid.
The purpose and scope of the management of cloud services are listed below:
Purpose: Establish suitable techniques for managing and running cloud-based services. Insert cloud
service management techniques into current frameworks for IT creation and support.
Scope: Oversight of cloud-based service design, development and change. Cloud-based service
management and operation.
In a design for handling cloud environments, cloud management incorporates applications and technologies.
With a range of cloud management platforms and instruments, software developers have responded to the
management challenges of cloud computing. These solutions include native tools provided by public cloud
providers, as well as third-party tools designed by various cloud providers to provide consistent functionality.
With access to various native features within individual cloud platforms, administrators must balance the
conflicting requirements of efficient consistency across various cloud platforms. The need for transparent
cross-platform management is motivated by increasing public cloud adoption and increased multi-cloud use.
For those technical professionals responsible for maintaining IT systems and facilities, the rapid adoption of
cloud services presents a new set of management challenges.
In the following categories, cloud-management systems and instruments should be able to have minimum
functionality.
Service request: receiving and fulfilling user requests to access and deploy cloud services.
Cost management and optimization: Cloud spending monitors and accurate sizes and aligns
resources and efficiency with real demand.
Security and compliance: handling cloud providers' role-based access and implementing security
settings.
Inventory and classification: discover and maintain pre-existing cloud infrastructure in the
brownfield plus track and handle modifications.
Cloud Analytics
Cloud analytics is a service that runs data analysis and business intelligence operations in a public or private
cloud. Cloud analytics companies help enterprises scale quickly by reducing the costs and administrative
burden of on-premises hardware.
Cloud for analytics types:
Public cloud — Storage and data processing is publicly accessible on multi-tenant architecture that
shares IT systems but not data.
Private cloud — Accessible only to one company and acts as an extension of the company’s IT
infrastructure. Used when data privacy and security is paramount.
Hybrid cloud — A combination of public and private clouds and most effective when only a small
amount of sensitive data needs to be in a private cloud.
Data sources — Original data sources that can include social media analytics or website usage data.
Data models — Created with structured data types to make sense of and standardize how data points
are related to each other.
Processing applications — Large volumes of big data are processed in a data warehouse.
Computing power — Raw computing power to ingest, structure and analyze data at scale.
Analytic models — Closed function mathematical models for predicting outcomes. They require
strong computing power.
Data sharing and storage — Data warehouses as a service that let organizations quickly and easily
scale.
Virtual desktop infrastructure (VDI) is a virtualization solution that uses virtual machines to provide
and manage virtual desktops. VDI hosts desktop environments on a centralized server and deploys
them to end-users on request. accessed over the network with an endpoint device (laptop, tablet, and
so on).
With a VDI solution in place, organizations can realize a number of benefits. The desktop computing
takes place on the host server, rather than at the endpoint device, so the hardware requirements for the
endpoint are lower. This potentially makes the investment in an endpoint device lower, and it may be
easier to support a diverse range of remote and mobile devices. As the hardware needs of the desktop
software change, it may also be easier to reallocate CPU and memory from the server side than from
the endpoint devices.
Security and configuration management are additional benefits of the VDI solution. Because all data
lives in the data center, any loss of an endpoint device limits the exposure of the data that is not stored
in the device. In environments with standardized desktop configurations that do not need to be
customized for each user, a VDI instance offers strict controls to eliminate deviation from
organizational standards.