Building Blocks of Private

Cloud
The three main building blocks which required to build a private cloud
are
• Physical Layer
• Virtualization Layer
• Cloud Management Layer
PHYSICAL LAYER
• The physical layer-is the foundation layer of the cloud reference model.
• The process of building a cloud infrastructure is typically initiated with the cloud
service provider setting up the physical hardware resources of the cloud
infrastructure.
• The physical layer comprises
• Compute
• Storage
• network resources,
• which are the fundamental physical computing resources that make up a cloud
infrastructure.
• Physical compute systems host the applications that a provider offers as services
to consumers and also execute the software used by the provider to manage the
cloud infrastructure and deliver services.
• A cloud provider also offers compute systems to consumers for hosting their
applications in the cloud.
• Storage systems store business data and the data generated or processed by the
applications deployed on the compute systems.
• Networks connect compute systems with each other and with storage
systems.
• A network, such as a local area network (LAN), connects physical compute
systems to each other, which enables the applications running on the
compute systems to exchange information.
• A storage network connects compute systems to storage systems, which
enables the applications to access data from the storage systems.
• If a cloud provider uses physical computing resources from multiple cloud
data centers to provide services, networks connect the distributed
computing resources enabling the data centers to work as a single large
data center.
• Networks also connect multiple clouds to one another—as in case of the
hybrid cloud model—to enable them to share cloud resources and services.
• Based on several requirements such as performance, scalability, cost, and
so on, a cloud provider has to make a number of decisions while building
the physical layer, including choosing suitable compute, storage, and
network products and components, and the architecture and design of
each system.
VIRTUALIZATION LAYER
• On a compute system, a cloud provider deploys softwares, virtualization
software, cloud infrastructure management software, and so on. The
provider also enables consumers to deploy their platform software and
business applications on the compute systems.
• Providers typically install compute virtualization software (hypervisor) on a
compute system
• create multiple virtual compute systems, known as virtual machines (VMs),
each capable of running its own OS.
• In this case, the hypervisor performs compute system management tasks
and allocates the compute system’s resources, such as processor and
memory, dynamically to each VM.
• The provider allocates the VMs running on a hypervisor to consumers for
deploying their applications.
• The provider may pre install an OS on a VM or may enable the consumers
to install an OS of their choice.
MANAGEMENT LAYER
The Management layer requires a “suite of management tools” in place to
manage the following processes of the Infrastructure layer:
• Service Reporting- a Business Intelligence application will create collaborative
reports.
• Service Management System- This is your incident management application that will
be used to open trouble tickets, track incidents and automate tasks.
• Service Health Monitoring- This application will monitor your server environments,
(physical and virtual) and report the overall health of your Windows servers, services
and applications.
• Configuration Management Systems- Can comprehensively assess, deploy, and
update servers, client computers, and devices across physical, virtual, and mobile
environments.
• Fabric Management- The single pane of glass to look at your entire virtualized
infrastructure, (VMs, Networking and Storage)
• Deployment Provisioning Management- Provides the ability to use automation to
deploy bare metal and virtual machines through an integrated management system.
• Data Protection- This is your data backups.
• Network Management- Network switches, virtual local area networks, load
balancers and the software that manages the network fabric.
• Security Management – Active Directory and Federated Trusts that are scaled across
multiple domains or platforms.
Features of Private Cloud Computing
• Economical
• The use of this cloud is limited so this will simply save to cost and energy of the host.
• Implementing a non-public cloud model will improve the allocation of resources within an
organization by making sure that the provision of resources to an individual,
departments/business functions will directly and flexible answering their demand.
• They make a lot of economical use of the computing resource and can additionally reduce an
organization’s carbon footprint
• Reliable
• When servers and networks are hosted internally, the creation of virtualized operational
environments can lead to individual failures across the physical infrastructure.
• Virtual partitions will remove their resources from the remaining unaffected servers.
• Secure
• The private cloud can be accessed by on a particular organization and firm this makes it more
secure and reliable.
• Moreover, there are certain levels of security which makes the private cloud more secure.
• Control
• Private cloud control by only a single, which leads to the fact that the organization can have
the flexibility to tack and manage it in line with their must achieve a tailored network
solution.
Challenges In Private Cloud
• Costs Involved: Private clouds are expensive especially when moving from existing public clouds
setup or traditional IT servers.
• Size: When compared to a public cloud arrangement, it has been observed that private clouds
cannot reach the scale or size of public clouds.
• Phasing out Old Hardware: While building a private cloud, the old hardware that have been part
of the legacy systems is usually rendered useless since they require a lot of manual configuration
with the private cloud setup and it would not be possible to deploy automation management to
this legacy hardware.
• Time frame: Since operational issues and hardware management of public clouds are managed
by specialized teams but while building the on premise private cloud this responsibility falls on
the internal IT team which would require a bit of time frame as well as a learning curve to be
observed.
• Resistance to Change: As mentioned before, the internal IT team might not be fully prepared for
this and there would be people who’d resist from reworking and changing the older operational
processes to give way for the newer setup for private clouds.
• Integration challenges: The private cloud to be built should be built on a hybrid model wherein if
required it could be connected to the public clouds. This does require a lot of effort including
security provisions and configurations which enable workloads to be run anywhere.
Virtual Private Cloud and its Benefits
Public Cloud: Public cloud is a public, hyperscale, multi-tenant platform where computing services can be
reserved or rented on demand. These resources are available globally over the internet and allow customers to
provision and scale services instantly without the time
• Amazon Web Services and Microsoft Azure are prime examples.
Private Cloud: A private cloud is a single tenant cloud environment that runs on dedicated infrastructure.
• This may reside on-premises, in a dedicated off-site data center or with a managed private cloud provider.
• Where public cloud is elastic and easily scalable, private cloud is constrained by fixed infrastructure.
• The advantage of the private cloud is control and exclusivity.
Multi-Cloud: The strategy of utilizing multiple cloud providers for different workloads depending on needs and
sensitivity of data.
• The Virtual Private Cloud (VPC)
• A Virtual Private Cloud (VPC) is an option that bridges the public and private cloud, offering the best of both
cloud models. VPC’s function like a private cloud that run on public or shared infrastructure.
• A virtual private cloud (VPC) is the logical division of a service provider's public cloud multi-tenant
architecture to support private cloud computing. This model enables an enterprise to achieve the benefits of
private cloud -- such as more granular control over virtual networks and an isolated environment for
sensitive workloads -- while still taking advantage of public cloud resources.
• VPCs are just as virtual as the public cloud, however instead of sharing resources and space in a public
infrastructure, these clouds operate with a certain level of isolation between customers.
• VPCs are just as virtual as the public cloud,
however instead of sharing resources and space in
a public infrastructure, these clouds operate with
a certain level of isolation between customers.

• This is achieved through a private IP subnet or

Virtual Local-Area Network (VLAN) on a per
customer basis, which provides a greater level of
security.

• This isolation is what lends itself to the term

“virtual private”—the user is in a cloud, but is not
dependent on any physical hardware, which is an
important distinction.

• On-premise clouds, sometimes referred to as

physical private clouds, are dedicated entirely to
one customer, including the hardware.
How a virtual private cloud works
• In a virtual private cloud model, the public infrastructure-as-a-service
(IaaS) provider is responsible for ensuring that each private cloud
customer's data remains isolated from every other customer's data
both in transit and inside the cloud provider's network.
• This can be accomplished through the use of security policies
requiring the following elements: encryption, tunneling, private IP
addressing or allocating a unique virtual local area network (VLAN) to
each customer.
• A virtual private cloud user can define and directly manage network
components, including IP addresses, subnets, network gateways and
access control policies.
Why virtual private cloud
• Data isolation :Virtual private clouds offer more tools to protect data than
standard, public cloud offerings.
• Improved performance: VPCs provide users private, provisioned services, so
they do not share processing time with other enterprises.
• Third-party management: VPCs do not require proprietary infrastructure, unlike
private cloud implementations. A vendor manages infrastructure on the user’s
behalf.

Considerations when using virtual private cloud

• Cost : Provisioning VPCs for a single user make them more expensive than typical,
shared public cloud services. Automation can help offset cost.
• Complexity: Virtual private cloud installations can require a complex setup
process and diligent maintenance.
• Portability : Moving private services between providers can be difficult. Open
source options such as OpenStack can help ease the process.
• Security: Different organizations have different requirements for handling data.
While some may need virtual privacy, others may not.
Benefits of a Virtual Private Cloud

Security: Information passed through a VPC stays within a customer’s control

without crossing the internet. In addition, with all customers operating on the same
back-end infrastructure, VPC providers have a highly-vested interest in keeping
things running smoothly and securely, while maintaining high levels of uptime.
Savings: Because VPCs are within a public cloud, customers still benefit from
economies of scale, sharing costs with other organizations without compromising
the aforementioned security.
Easy integration. A VPC can be integrated with other VPCs, the public cloud, or an
on-premise infrastructure. Once in place, it effectively becomes a hybrid cloud,
which by definition, is more than one cloud working in synchronization.
Seamless upgrades. With all customers operating on the same hardware, the VPC
provider can upgrade everyone incrementally and with no downtime; most
providers will refresh the underlying hardware while constantly acquiring faster and
better hardware. Over time, customers’ workloads actually get more secure and
quicker!
Eco-Friendliness. A VPC operating within a cloud hosting company leaves much
less of a carbon footprint versus running on dedicated hardware, something that
can be promoted to new clients.
Virtual private cloud providers
• Most leading public IaaS providers, including Amazon Web Services
(AWS), Microsoft Azure and Google, offer VPC and virtual network
service