CLOUD

COMPUTING
ARCHITECTURE
AND
MANAGEMENT
TOPICS
• CLOUD ARCHITECTURE LAYER
• ANATOMY OF THE CLOUD
• NETWORK CONNECTIVITY IN CLOUD COMPUTING
• APPLICATIONS ON THE CLOUD
• MANAGING THE CLOUD
• MANAGING THE CLOUD INFRASTRUCTURE
• MANAGING THE CLOUD APPLICATION
• MIGRATING APPLICATION TO CLOUD
• PHASES OF CLOUD MIGRATION
• APPROACHES FOR CLOUD MIGRATION
 INTRODUCTION
• Architecture is the hierarchical view of describing a technology. This usually
includes the components over which the existing technology is built and the
components that are dependent on
the technology.
• Anatomy describes the core structure of the cloud.
• Cloud management discusses the important management issues and ways in
which the current cloud scenario is managed. It describes the way an application
and infrastructure in the cloud are managed.
 1) CLOUD ARCHITECTURE LAYERS
• Any technological model consists of an architecture based on which the model
functions, which is a hierarchical view of describing the technology.
• The cloud also has an architecture that describes its working mechanism. It
includes the dependencies on which it works and the components that work
over it.
• The cloud is a recent technology that is completely dependent on the Internet
for its functioning.
• The cloud architecture can be divided into four layers based on the access of
the cloud by the user. They are as follows.
 LAYER 1 (USER/CLIENT LAYER)
• This layer is the lowest layer in the cloud architecture. All the users or client belong
to this layer.
• This is the place where the client/user initiates the connection to the cloud. The client
can be any device such as a thin client, thick client, or mobile or any handheld device
that would support basic functionalities to access a web application.
• The thin client here refers to a device that is completely dependent on some other
system for its complete functionality. In simple terms, they have very low processing
capability.
• Usually, a cloud application can be accessed in the same way as a web application.
But internally, the properties of cloud applications are significantly different. Thus,
this layer consists of client devices.
 LAYER 2 (NETWORK LAYER)

• This layer allows the users to connect to the cloud. The whole cloud infrastructure
is dependent on this connection where the services are offered to the customers.
• This is primarily the Internet in the case of a public cloud. The public cloud usually
exists in a specific location and the user would not know the location as it is
abstract. And, the public cloud can be accessed all over the world.
• In the case of a private cloud, the connectivity may be provided by a local area
network (LAN). Even in this case, the cloud completely depends on the network
that is used.
• This layer does not come under the purview of service-level agreements (SLAs),
that is, SLAs do not take into account the Internet connection between the user and
cloud for quality of service (QoS).
 LAYER 3 (CLOUD MANAGEMENT LAYER)

• This layer consists of softwares that are used in managing the cloud. The softwares can
be a cloud operating system (OS), a software that acts as an interface between the data
center (actual resources) and the user, or a management software that allows managing
resources.
• These softwares usually allow resource management (scheduling, provisioning, etc.),
optimization (server consolidation, storage workload consolidation), and internal cloud
governance.
• This layer comes under the purview of SLAs, that is, the operations taking place in this
layer would affect the SLAs that are being decided upon between the users and the
service providers. Any delay in processing or any discrepancy in service provisioning
may lead to an SLA violation.
 LAYER 4 (HARDWARE RESOURCE LAYER)
• Layer 4 consists of provisions for actual hardware resources. Usually, in the case of a public
cloud, a data center is used in the back end. Similarly, in a private cloud, it can be a data center,
which is a huge collection of hardware resources interconnected to each other that is present in a
specific location or a high configuration system.
• This is the most important layer that governs the SLAs. This layer affects the SLAs most in the
case of data centers. As mentioned, if there is any discrepancy in provisioning the resources or
application, the service provider has to pay the penalty.
• Hence, the data center consists of a high-speed network connection and a highly efficient
algorithm to transfer the data from the data center to the manager. There can be a number of data
centers for a cloud, and similarly, a number of clouds can share a data center.
• Thus, this is the architecture of a cloud. The layering is strict, and for any cloud application, this is
followed. There can be a little loose isolation between layer 3 and layer 4 depending on the way
the cloud is deployed.
 2) ANATOMY OF THE CLOUD

• Cloud anatomy can be simply defined as the structure of the cloud. Cloud
anatomy cannot be considered the same as cloud architecture.
• It may not include any dependency on which or over which the technology works,
whereas architecture wholly defines and describes the technology over which it is
working.
• Architecture is a hierarchical structural view that defines the technology as well as the
technology over which it is dependent or/and the technology that are dependent on it.
Thus, anatomy can be considered as a part of architecture.
THE MOST STANDARD ANATOMY THAT IS THE BASE FOR THE
CLOUD
THERE ARE BASICALLY FIVE COMPONENTS OF THE CLOUD:

• 1. Application: The upper layer is the application layer. In this layer, any applications
are executed.
2. Platform: This component consists of platforms that are responsible for the
execution of the application. This platform is between the infrastructure and the
application.
3. Infrastructure: The infrastructure consists of resources over which the other
components work. This provides computational capability to the user.
4. Virtualization: Virtualization is the process of making logical components of
resources over the existing physical resources. The logical components are isolated and
independent, which form the infrastructure.
5. Physical hardware: The physical hardware is provided by server and storage units.
 3) NETWORK CONNECTIVITY IN CLOUD COMPUTING

• Cloud computing is a technique of resource sharing where servers, storage, and other
computing infrastructure in multiple locations are connected by networks.
• In the cloud, when an application is submitted for its execution, needy and suitable
resources are allocated from this collection of resources; as these resources are
connected via the Internet, the users get their required results.
• For many cloud computing applications, network performance will be the key issue
to cloud computing performance.
 PUBLIC CLOUD ACCESS NETWORKING
• The connectivity is often through the Internet, though some
cloud providers may be able to support virtual private networks (VPNs)
for customers. Accessing public cloud services will always create issues
related to security, which in turn is related to performance.
• One of the possible approaches toward the support of security is to promote connectivity
through encrypted tunnels, so that the information may be sent via secure pipes on the
Internet. This procedure will be an overhead in the connectivity, and using it will
certainly increase delay and may impact performance.
• If we want to reduce the delay without compromising security, then we
have to select a suitable routing method such as the one reducing the delay
by minimizing transit hops in the end-to-end connectivity between the cloud
provider and cloud consumer.
 PRIVATE CLOUD ACCESS NETWORKING

• In the private cloud deployment model, since the cloud is part of an organizational
network, the technology and approaches are local to the in-house network structure.
• This may include an Internet VPN or VPN service from a network operator. If the
application access was properly done with an organizational network—connectivity in a
pre cloud configuration—transition to private cloud computing will not affect the access
performance.
 INTRACLOUD NETWORKING FOR PUBLIC CLOUD
SERVICES

• Another network connectivity consideration in cloud computing is intra cloud

networking for public cloud services. Here, the resources of the cloud provider
and thus the cloud service to the customer are based on the
resources that are geographically apart from each other but still connected
via the Internet.
• Public cloud computing networks are internal to the service provider and thus
not visible to the user/customer; however, the security aspects of connectivity
and the access mechanisms of the resources are important. Another issue to
look for is the QoS in the connected resources worldwide.
 PRIVATE INTRACLOUD NETWORKING
• The most complicated issue for networking and connectivity in cloud computing is private
intracloud networking. What makes this particular issue so complex is that it depends on how
much intracloud connectivity is associated with the applications being executed in this
environment.
• Private intracloud networking is usually supported over connectivity between the major data
center sites owned by the company. At a minimum, all cloud computing implementations will
rely on intracloud networking to link users with the resource to which their application was
assigned.
• Once the resource linkage is made, the extent to which intracloud networking is used depends
on whether the application is componentized based on service-oriented architecture (SOA) or
not, among multiple systems. If the principle of SOA is followed, then traffic may move
between components of the application, as well as between the application and the user.
 NEW FACETS IN PRIVATE NETWORKS
• Conventional private networks have been architected for on-premise applications and
maximum Internet security. Typically, applications such as e-mail, file sharing, and
enterprise resource planning (ERP) systems are delivered to on-premise-based servers at
each corporate data center.
• The traditional network architecture for these global enterprises was not designed to
optimize performance for cloud applications, now that many applications including
mission-critical applications are transitioning (moving) from on-premise based to cloud
based, wherein the network availability becomes as mission critical as electricity: the
business cannot function if it cannot access applications such as ERP and e-mail.
 PATH FOR INTERNET TRAFFIC
• The traditional Internet traffic through a limited set of Internet gateways
poses performance and availability issues for end users who are using
cloud-based applications.
• As the volume of traffic to cloud applications grows, the percentage of the legacy
network’s capacity in terms of traffic to regional gateways increases. Applications such
as video conferencing would hog more bandwidth while mission-critical applications
such as ERP will consume less bandwidth, and hence, one has to plan a correct
connectivity and path between providers and consumers.
 4) APPLICATIONS ON THE CLOUD
• There are several types of applications. The first type of application was developed and used as a
stand-alone application.
• A stand-alone application is developed to be run on a single system that does not use a network
for its functioning. These stand-alone systems use only the machine in which they are installed.
• The functioning of these kinds of systems is totally dependent on the resources or features
available within the system. These systems do not need the data or processing power of other
systems; they are self-sustaining.
• Change in time with respect to the requirements led to the inception of web applications that are
completely different from stand-alone applications.
• These web applications are completely based on a client-server architecture that is always
dependent on the network for its functioning.
• And also, these stand-alone applications are followed by web applications. The web application
has two most important components; the server, which is a high-end machine that contains the
web applications, and the client who will access the server.
SOME OF THE FEATURES OF CLOUD APPLICATIONS ARE AS
FOLLOWS:
 FEATURES
1) Multitenancy: Multitenancy is one of the important properties of the cloud that make
it different from other types of applications in which the software can be shared by
different users with full independence.
2) Elasticity: Elasticity is also a unique property that enables the cloud to serve better.
Elasticity can be defined as the degree to which a system is able to adapt to
workload changes by provisioning and de-provisioning resources in an autonomic
manner such that at each point in time, the available resources match the current
demand as closely as possible.
3) Heterogeneous cloud platform: The cloud platform supports heterogeneity, wherein
any type of application can be deployed in the cloud.
4) Quantitative measurement: The services provided can be quantitatively measured. The
user is usually offered services based on certain charges. Here, the application or
resources are given as a utility on a pay-per-use basis.
5) On-demand service: The cloud applications offer service to the user, on-demand, that
is, whenever the user requires it. The cloud service would allow the users to access web
applications usually without any restrictions on time, duration, and type of device used.
 5) MANAGING THE CLOUD

• Managing the cloud is the most important thing to maintain the Quality of
Service (QoS).
• Managing the cloud is broadly divided into two parts:
1. Managing the infrastructure of the cloud
2. Managing the cloud application
 6) MANAGING THE CLOUD INFRASTRUCTURE
• The infrastructure of the cloud is the backbone of the cloud. This component is
mainly responsible for the QoS factor.
• If the infrastructure is not properly managed, then the whole cloud can fail and QoS
would be adversely affected.
• The core of cloud management is Resource Management.
• Resource Management involves several tasks such as;
o Resource scheduling
o Provisioning
o Load balancing
The above tasks are mainly managed by the cloud service provider’s core software capabilities such as the
cloud OS that is responsible for providing services to the cloud and that internally controls the cloud.
•Poor resource management may lead to several inefficiencies in terms of performance, functionality, and cost.
•If a resource is not efficiently managed, the performance of the whole system is affected. Performance is the
most important aspect of the cloud because everything in the cloud is dependent on the SLAs. (Cloud service
level agreement)
•The basic functionality of the cloud should always be provided and considered at any cost. Even if there is a
small discrepancy in providing the functionality, the whole purpose of maintaining the cloud is futile.
•The reason for which the cloud was developed was cost. The cost is a very important criterion as far as the
business prospects of the cloud are concerned.
•The service providers, if they incur less cost for managing the cloud, then would try to reduce the cost so as
to get a strong user base.
•Similarly, if the cost of resource management is high, then definitely the cost of accessing the resources
would be high and there is never a lossy business from any organization and so the service provider would
not bear the cost and hence the users must pay more.
•Other issues that dealt with resource management are power consumption and optimization of multiple
objectives to further reduce the cost.
 7) MANAGING CLOUD APPLICATION
• Business companies are increasingly looking to move or build their corporate applications on
cloud platforms to improve agility or to meet dynamic requirements that exist in the globalization
of businesses.
• But this shift or moving the applications to the cloud environment brings new complexities.
• Applications become more composite and complex, which requires leveraging not only
capabilities like storage and database offered by the cloud providers but also third-party SaaS
capabilities like e-mail and messaging.
• The composite nature of cloud applications requires visibility into all the services to determine
the overall availability and uptime.
• Cloud application management is to address these issues and propose solutions to make it
possible to have insight into the application that runs in the cloud.
• These cloud-based monitoring and management services can collect a multitude of events,
analyse them, and identify critical information that requires additional remedial actions like
adjusting capacity or provisioning new services.
 8) MIGRATING APPLICATION TO CLOUD

• Cloud migration encompasses moving one or more enterprise applications

and their IT environments from the traditional hosting type to the cloud
environment, either public, private, or hybrid. Cloud migration presents
an opportunity to significantly reduce costs incurred on applications. This
activity comprises, of different phases like evaluation, migration strategy,
prototyping, provisioning, and testing
 9) PHASES OF CLOUD MIGRATION
1. Evaluation: Evaluation is carried out for all the components like current infrastructure and
application architecture, environment in terms of compute, storage, monitoring, and
management, SLAs, operational processes, financial considerations, risk, security, compliance,
and licensing needs are identified to build a business case for moving to the cloud.
2. Migration strategy: Based on the evaluation, a migration strategy is drawn—a hotplug
strategy is used where the applications and their data and interface dependencies are isolated
and these applications can be operationalized all at once. A fusion strategy is used where the
applications can be partially migrated; but for a portion of it, there are dependencies based on
existing licenses, specialized server requirements like mainframes, or extensive
interconnections with other applications.
3. Prototyping: Migration activity is preceded by a prototyping activity to validate and ensure
that a small portion of the applications are tested on the cloud environment with test data
setup.
4) Provisioning: Premigration optimizations identified are implemented. Cloud servers
are provisioned for all the identified environments, necessary platform softwares and
applications are deployed, config-urations are tuned to match the new environment
sizing, and databases and files are replicated. All internal and external integration
points are properly configured. Web services, batch jobs, and operation and
management software are set up in the new environments.
5. Testing: Postmigration tests are conducted to ensure that migration has been
successful. Performance and load testing, failure and recovery testing, and scale-out
testing are conducted against the expected traffic load and resource utilization levels.
 10) APPROACHES FOR CLOUD MIGRATION
The following are the four broad approaches for cloud migration that have
been adopted effectively by vendors:
1. Migrate existing applications: Rebuild or rearchitect some or all the applications,
taking advantage of some of the virtualization technologies around to accelerate
the work. But, it requires top engineers to develop new functionality. This can be
achieved over the course of several releases with the timing determined by
customer demand.
2. Start from scratch: Rather than cannibalize sales, confuse customers with choice,
and tie up engineers trying to rebuild existing application, it may be easier to start
again. Many of the R&D decisions will be different now, and with some of the
more sophisticated development environments, one can achieve more even with a
small focused working team.
3. Separate company: One may want to create a whole new company with separate
brand, management, R&D, and sales. The investment and internet protocol (IP) may
come from the existing company, but many of the conflicts disappear once a new
born in the cloud company is established. The separate company may even be a
subsidiary of the existing company. What is important is that the new company can
act, operate, and behave like a cloud-based start-up.
4. Buy an existing cloud vendor: For a large established vendor, buying a cloud-
based competitor achieves two things. Firstly, it removes a competitor, and secondly,
it enables the vendor to hit the ground running in the cloud space. The risk of course
is that the innovation, drive, and operational approach of the cloud-based company
are destroyed as it is merged into the larger acquirer.
THANK YOU…