Resource pooling

Resource pooling refers to the practice of aggregating and effectively

managing computing resources such as storage, processing power, and
memory and networking to serve multiple users or applications.

It enables efficient utilization of resources by dynamically allocating

them based on demand. This helps in optimizing overall resource usage
and minimizing idle time.
Pooling of Physical and Virtual
servers
 Resource Pooling Architecture
• A resource pooling architecture is designed to combine multiple pools of
resources where each pool groups together with identical computing resources.
• Computing resources can broadly be divided into three categories as
Computer/server,
Network
Storage.
• Hence, the physical computing resources to support these three purposes are
essential to be configured in cloud data centers in good quantity.
 Computer or Server Pool
• Server pools are developed by building physical machine pools installed with
operating systems and necessary system software.
• Virtual machines are built on these physical servers and combine into virtual
machine pool.
• Physical processor and memory components from respective pools are later linked
with these virtual servers in virtualized modes to increase capacity of the servers.
• Dedicated processor pools are made of various capacity processors. Memory
pools are also built in similar fashion. Processor and memory are allotted to the
virtual machines as and when required. Again, they are returned to the pools of
free components when load of virtual server decreases.
Resource pool comprising of three sub pools
 Storage Pool
• Storage pools are made of block-based storage disks. They are configured with
proper portioning, formatting and are available to consumers in virtualized mode.
Data having stored into those virtualized storage devices are actually saved in
these pre-configured physical disks.
 Network Pool
• Elements of all of the resource pools and the pools themselves owned by a service
provider remain well-connected with each other. This networking facilitates the
cloud service at provider’s end.
• The pool of physical network devices are also maintained in data centers. Pools of
networking components are composed of different preconfigured network
connectivity devices like switches, routers and others.
• Consumers are offered virtualized versions of these components. They can
configure those virtual network components in their own way to build their
network.
Hierarchical Organization
• With a very large number of resource components, a resource pool may become
very complex to manage if not organized properly. Generally hierarchical
structures are established Virtual server pool Processor pool Memory pool to
form parent and child relationships among pools.

• The hierarchical pool organization with nested

sub-pool architecture makes the cloud resource
pool free of any single point of failure.
 COMMODITIZATION OF THE DATA
CENTER
• Commodity hardware components are those which are inexpensive, replaceable
with similar component produced by other vendors and easily available.
• Commoditization of resource pools at data centers has been an attracting feature
of cloud computing, especially for the data center owners. Specialized
components are not required and commodity components are used to build the
pools of (high performance) servers, processors, storage disks and else.
STANDARDIZATION, AUTOMATION
AND OPTIMIZATION
• virtualization layers provide opportunities to standardize, automate and optimize
deployments of cloud environment.
• Standardization: Commodity resource components of a pool may come with
various architectural standards. Resource virtualization decouples the application
instances from underlying hardware systems.
• Automation: Automation is implemented for resource deployment like VM
instantiation is used to bring VMs off-line back online and to remove them rapidly
and automatically based on their previously set standard criteria.
• Optimization: This is the process which optimizes the resource usage.
Optimization is performed to get optimal resource performance with limited set
of resources.
 RESOURCE SHARING
• Resource sharing leads to higher resource utilization rate in cloud computing.
• As a large number of applications run over a pool of resources, the average
utilization of each resource component can be increased by sharing them among
different applications since all of the applications do not generally attain their
peak demands at same time.
• Resource sharing in utility service environment does not come without its own set
of challenges. The main challenge is to guarantee the Quality of Service (QoS).
• Resource sharing prevents performance isolation and creates the need for new
resource management strategies to produce quality service in cloud computing
environment.
 Multi-tenancy
• The characteristic of a system that enables a resource component to serve
different consumers (tenants), where by each of them being isolated from the
other is referred to as multi-tenancy.
• It enables the service provider to provide computing service to multiple isolated
consumers using single and shared set of resources.
• Multi-tenancy in cloud computing has been materialized
based on the concepts of ownership free resource sharing
in virtualized mode and temporary allocation of resources from
resource pool.
• Resource components are allotted to users and applications solely on-availability basis. This
increases resource utilization rate and in turn decreases investment as well.
 Types of Tenancy
• Tenants of a system (multi-tenant system) can either be outsides or even insiders
within an organization (like multiple departments within an organization) where
each of the tenants needs their own protected zones.
• Multi-tenancy in its actual sense allows co-tenants external or unrelated to each
other. While existence of external co-tenant is a unique feature of public cloud, the
private cloud only allows sub-co-tenants under one tenant.
Tenancy at Different Level of Cloud Services
• In a computing environment, the idea of tenancy applies at different levels from
infrastructure (like storage) at the lowest layer up to application interface at the
top.
• is evident that by incorporating multi-tenancy at the infrastructure level, all layer
of cloud services automatically become multi-tenant to some degree; but that
should not encourage anyone to limit multi-tenancy at IaaS level only, rather it
should be implemented to its highest degree.
• At IaaS level, the multi-tenancy provides shared computing infrastructure
resources like servers, storages etc. At this level, multi-tenancy is achieved
through virtualization of resources.
• At PaaS level, the multi-tenancy means sharing of operating system by multiple
applications. Applications from different vendors (tenants) can be run over same
OS instance.
Cont..
• At SaaS level, the multi-tenancy refers to the ability of a single application
instance and/ or database instance (that is one database instance being created in
some database servers) in order to serve multiple consumers.
• In order to serve multiple consumers. Consumers (tenants) of SaaS share same
application code base as well as database tables and codes (like procedure,
functions etc.). Data of multiple consumers which are stored in same set of tables
are differentiated by the respective consumer numbers. Here, the separation of
data is logical only although consumers get the feeling of physical separation
• Not only at IaaS layer, multi-tenancy also works at all other levels of
cloud services.