19 Characteristics, Advantages, Disadvantages, Software Stacks of Public and Private Cloud Types

Hello students,

In this blog we dig deeper into Public and Private Cloud. 

Every cloud has the same IaaS, PaaS, SaaS services but the difference in cloud types is who actually provides the cloud. Whoever provides the cloud also has the data.

As we know Public Cloud is provided by a third party company outside the organization to everyone on this earth. Private Cloud is provided by the organization for the organization only.

Characteristics/Advantages of Public Cloud

The four characteristics of Public Cloud are

1. Low cost, flexible availability of resources, ease of implementation
2. Multitenancy
3. Quality of Service (QoS)
4. Different types of service offering


Disadvantages of Public Cloud

The disadvantages of Public Cloud are

1. Security concerns of private and government organizations to implement any software or store any data in public cloud, as the multitenant feature of public cloud provide everyone on earth to reside their software and data in the same cloud, even though each customer uses different accounts. 

Public clouds work in a shared responsibility model where infrastructure is protected and is responsibility by the cloud provider such as AWS but customer is still responsible to implement security such as logins, network firewalls etc. 

Cloud providers have the responsibility of the cloud, but customer have the responsibility in the cloud.

2. USA Patriot Act allows government the right  to look into any data residing in US regions, if necessary. So privacy of data is also a concern. To address such concerns, clouds try to provide the option of "regions" that you would like to include to store your data.. Example AWS has a Mumbai region. So any criticial India's data should ideally be chosen to reside in the Mumbai data centers only.


Advantages of Private Cloud

The three advantages of Private Cloud are

1. Customer Information Protection
2. Infrastructure ensuring SLA
3. Compliance with standard procedures and operations


Software Stacks that drives Private clouds

There are different software stacks utilized by organizations to build private cloud
 

1. Data centers, grids and clusters are used to provide the physical infrastructure
 

2. KVM, Xen and VMware are used to provide virtual machines
 

3. Eucalyptus, OpenNebula, VMware vCloud, OpenPEX, Intergrid provide the software to manage the infrastructure


4. Data Synapse, Zimory Pools, Elastra CloudServer,


Aneka provide the software to create , control and manage platforms

Federated clouds are cloud architecture where customer includes multiple clouds to run their systems

Example I can have my .Net applications installed on Microsoft Azure cloud whereas all my static html files may be saved on AWS S3 bucket.

Each cloud works within its own administrative domain.

Migration of platforms, softwares are still an issue between clouds in a federated environment.


With time, there will be more open cloud standards
without having to worry about which cloud we are connecting too.

For more details, look at the presentation on 2 TYPES OF CLOUD - PUBLIC & PRIVATE PART 11 - SEM 3 - MSC 2

Thank you.

Comments

Post a Comment

Popular posts from this blog

11 Computing Platforms

Welcome students ! Introduction to Unit 2  In Unit 2, we look at platform architectures that have evolved over time from the days of  earlier main frame architecture into today's cloud service platform architecture. Today we have cloud computing platform which use and provide cloud technologies   ( Parallel Computing, Distributed Computing, Service Oriented     Computing, Virtualization, Web 2.0 (soap, rest, ajax, mashup),  Utility Computing ) cloud delivery services reference model  ( IaaS,PaaS, SaaS ) cloud deployment types  ( Public, Private, Hybrid, Community ) In Unit 1 we already introduced ourselves to cloud technologies such as Parallel Computing, Distributed Computing, Service Oriented Computing and Virtualization.  Just like evolution theory says a monkey became man over many phases, this blog summarizes the Computing Platform architecture for enterprises that has evolved over time in four phases  (computing platform: e...
Read more

15 Four layers of Cloud Architecture (Reference Model)

Hello students, In today's blog we look deeper at cloud reference model architecture that generally applies in any cloud environment Any Cloud architecture is based on a four layers of this reference model 1. System Infrastructure 2. Core Middleware 3. User-level Middleware 4. Cloud Applications Each layer is on top of the previous layer System Infrastructure System infrastructure is the most underlying layer in the architecture and it provides physical machines, network, storage needs such as network adapters, routers, SAN disks etc. Core Middleware Core Middleware sits on top of System Infrastructure layer. It provides virtual machines, network virtualization, storage virtualization, hypervisors etc. Both System Infrastructure and Core Middleware essentially provides a way to implement IaaS (Infrastructure as a service) In our assignment, this layer would ideally be Oracle Virtual box User Level Middleware User Level Middleware sits on top of core middleware and provides run-ti...
Read more

25 Task Computing : HTC-HPC-MTC

Dear students, In our last blog, we came across concurrent computing, where the focus was how a single program can be computed faster by decomposing either based on data sets (Domain Decomposition) or based on functionality (Function Decomposition). Once the decomposition is planned properly in the program, it can be assigned to multiple cores or multiple threads. Concurrent computing is a form of parallelism on the same machine. When we talk about task computing, we are looking at executing not single program, but multiple programs. Each program can be considered as a task with lot of data or consisting of many work units. These tasks can be executed using multiple machines. Task Computing is a form of parallelism on multiple machines. It is a network of machines, where one machine (called local node) becomes responsible to submit the task, then one machine schedules it , checks status on all submitted tasks (access nodes) , one machine provides any resources such as files, data...
Read more