MAJOR TRAINING

REPORT
ON

CLOUD ORCHESTRATION
(CLOUD INFRASTRUCTURE AND
SERVICES)

Submitted by:

NAMRATA R. SHIVAGUNDE
EC-A VII SEM
0101EC091064
 CONTENTS

CHAPTER NAME OF THE CHAPTER

NO.

1.0 INTRODUCTION

1.1 Cloud Orchestration Definition

1.2 Basic principle
2.0 NEED FOR CLOUD ORCHESTRATION
2.1 Use case

2.2 Complex business

2.2. Service provider management and control

2.3 Tenant management and control

2.4 Resources automation

3.0 CLOUD ORCHESTRATION IMPLEMENTATION AREA

3.1. Cloud services

4.0 HOW CLOUD ORCHESTRATION IS IMPLEMENTED?

4.1 Orchestration tool (Orchestrator)

4.2 Functions performed by the orchestrator

4.3 Features of the orchestrator

4.4 Factors responsible for selecting any orchestrator

4.5 Cloud service provider architecture

4.6 Orchestrator architecture- EMC Ionix IT

Orchestrator

4.7 Orchestrator working

4.8 Billing and metering services

5.0 FUTURE SCOPE FOR THE CLOUD ORCHESTRATION

REFERENCES
6.0

CHAPTER 1
Abstract
Every cloud service provider wants to provide the best quality services to their
customers. Ensuring any organisation, whether a service provider (SP) or business,
is fully realising the benefits of a cloud platform is essential to staying competitive,
flexible and agile in today’s market. But many organisations are missing the
opportunity because their infrastructure and software does not include cloud
orchestration.
Cloud Orchestration is the ability to manage all elements of a cloud platform from
physical to virtual resources.
This research work includes the concept of cloud orchestration and the orchestration
tool.
Orchestration in cloud is done using the tool called orchestrator.
This tool is an automated software that provides the managed service providers,
data center operators, hosting providers and enterprisers to provide services to their
customers.
The architecture, working, components and the billing process of the cloud
orchestrator are different from that of simple cloud service provider. They have been
discussed in the report.

CHAPTER 2

INTRODUCTION
1.1 Cloud Orchestration
Definition

“The ability to control and arrange a set of underlying technology infrastructures (hardware
and hypervisor) and match with the intended commands inputted by the users to create set
of automated events that deliver the request with the maximum efficiency”

A growing part of the market is for cross-business collaboration, again with the need
for strong integration of services and interconnectivity between new cloud-computing
offerings Cloud services today focus on providing specific horizontal capabilities.
from computing resources (in the IaaS model) to application offerings, such as
desktop virtualization, CRM or payment application services (in a SaaS model). One
can distinguish between horizontal and vertical scalability, whereby horizontal
scalability refers to the amount of instances to satisfy e.g. changing amount of
requests, and vertical scalability refers to the size of the instances themselves and
thus implicit to the amount of resources required to maintain the size. In order to
make the above-mentioned scenario real in ‘The Cloud’, it is necessary that cloud
computing go beyond current offerings to become an ecosystem of commodity and
business services that users can compose, aggregate and broker to realize end-to-
end business processes across heterogeneous added-value services, thus cloud
orchestration came into scenario.
The scope of cloud orchestration:
 To connect different components of a transaction in a business process
across different cloud environments.
 To move a component of a transaction in a business process step to a
different cloud to meet business requirements (e.g. meeting an availability
SLA during loss of connectivity, cost control through a lowest cost of
processing approach or qualitative aspects, such as compliancy rules).
 To manage a transaction end to end, making sure that:
o all components needed to execute the transaction are available,
o the transaction data and state is held until the transaction ends, and
o the associated reporting is generated to complete the business process.

1.2 Basic principle

Cloud orchestration is done by taking any cloud object then policies are added and a
unique label is given to it. Like this many other cloud objects are added .The
relationship between the objects are defined then objects having same
characteristics are grouped together. Thus a cloud orchestration is created. Now it is
possible that the Master Orchestration can drive other orchestrations (sub
orchestration) and those sub orchestration can drive real objects. This is chaining
effect or chain reaction.

CHAPTER 3
NEED FOR CLOUD ORCHESTRATION
 In virtualization entities are dynamically created, they flex up and down, they
move around, they behave and relate in unpredictable ways creating an
entirely new need for inside collaboration and control…

There is a need to correctly integrate all of the components, for the successful
offering of the services.

So Cloud orchestration is the solution.

2.1 USE CASES

To have a clear understanding from a business perspective, some use cases are
discussed here
Use Case 1:
Order Management Process

Order management and fulfillment process

It starts with a customer placing an order through a customer-facing application

sitting on a cloud (which may be just one of the applications supporting the overall
process). When the order is being placed, the product or product catalog (for
example, information on various plan types when ordering a mobile phone) may
come from an Oracle BRM system or a central system sitting on a different cloud
which stores all product catalogue information. This in turn is a separate system
managed by different departments within the organization. Customer preferences
may also need to be provided by a CRM system which is on an entirely different
cloud. In addition, order processing and approval happen through different
departments within the organization and via approval processes sitting on different
data clouds. Finally, payments are processed and reports generated in an
environment which happens to be outsourced. From a complete system and end-
user view, it is all just one process spanning multiple clouds and data centers.
Connecting and managing transactions seamlessly across these business process
components defines as Cloud Orchestration.

Use Case 2:
Disability Benefit Type Assessment Process (Disability Benefit Claim Process)

In some countries, the government provides disability benefits to claimants. The

underlying process requires that the claimant put in a disability benefit claim.
Again in this case, disability benefit types may come from a different system which
centrally manages various benefit types. The claim is pushed for initial review by a
healthcare professional. During this process, the healthcare professional may need
further medical evidence and may send the information to a diagnostic center where
the claimant may need to go for diagnosis. In order to get to the nearest diagnostic
center, the claimant may need to use a rail-road traffic communication site. The
appointment for the claimant may be done by an independent appointment
scheduling system, which may be sitting in a different data center. The practitioner
performs the examination to confirm the disability claim; but may require the
expertise of practitioners or doctors sitting somewhere in an altogether different part
of world. The practitioner’s report will be sent to an auditor or supervisory body to
verify it. Finally, the case is sent to a govern As mental body for approval, which in
turn may need to talk to a financial unit, and so on. This can be even more complex if
the government disability department provides this service to a number of different
organizations.
The common themes in the use cases are the management of business processes
across various clouds, movement of transactional data to different clouds, and the
need for each application (when isolated from the rest of the business process) to
interact in order to achieve an overall objective - a classic case of orchestration.
There is a need for a cloud-integration and aggregation delivery model that takes
into account this element of orchestration across clouds. This also suggests that
there is a need for BPaaS, Business Process as a Service; a layer on top of the
Software as a Service models that looks at making business process components
available in a way that allows for orchestration

2.2 Complex business

As the needs of the business grow, the underlying business processes will become
more complex and a conventional single-cloud environment will no longer be able to
support end-to-end processes as data and processing from other sources becomes
necessary. It therefore inevitably evolves into a heterogeneous environment of
services across multiple clouds and on-premise systems.

At the moment, each of the three cloud computing models (IaaS, PaaS and SaaS)
still focuses on singularities in their provisioning model,they provide only computing,
run-time or an application platform. This may scale very well from a quantitative point
of view (for example, talking about thousands of users accessing applications, the
number of terabytes of data, etc),but does not scale well when looking at it from
qualitative point of view (for example, business processes spanning across multiple
clouds or transactions that deal with multiple platforms and applications, etc).This is
due to the way as-a-Service models are delivered. They are a product of one
provider and the singular context is protected by that provider in order to keep the
customer inside that one delivery model, inevitably leading to vendor lock-in. Such a
lock-in model is well illustrated by Amazon that only provides support for specific
operating systems; Microsoft Azure that only supports a limited set of run-times for
application development and execution; and Salesforce.com that only provides a
CRM application3 with a very proprietary API. None of these offerings provide tools
that enable interoperability between their respective services.

Looking at the wider landscape of an enterprise’s business processes, it is clear from

a holistic view that business processes will not be confined to residing in a single
cloud, but will need to reach across clouds. Despite the growing understanding of the
need for interconnectivity between these models by exposing proprietary APIs or
adopting ‘open’ standards, it becomes apparent that no real integration is really
emerging from providers.

Present changes At the IaaS level, cloud computing based upon virtualization
technologies is rapidly adopted by traditional IT vendors and service providers, in
order to enable multi-tenancy and hitherto unheard of levels of utilization of the
infrastructure. Whilst this introduces a scalability of hardware and computing power,
it does not necessarily allow for the scalability of applications. For upper layers of the
cloud stack (PaaS, SaaS and BPaaS), new services (applications) need to emerge
that have adopted a multi-tenant architecture using a new generation of delivery and
platform technologies that are currently being developed by middleware vendors
such as Oracle/ BEA, Microsoft, IBM and Cordys among others. Even before that
happens, the market has already been shaken up by aggressive offerings, including:
o Virtualization technologies by VMware and upcoming technologies in open
and closed source.
o Google SaaS and PaaS solutions for personal productivity.
o Amazon Web Services, cloud storage solutions and computing on demand.
This has resulted in ‘The Cloud’ being composed of a variety of disparate clouds
from different providers, which do not necessarily work together as beautifully as the
‘The Cloud’ paradigm suggests.
In fact, these different cloud platforms are typically closed and proprietary by design,
and therefore are not easily extensible for integration/ interoperability with services
outside their boundaries .Interoperability, security and data management across new
cloud-based services present significant challenges and there are real reasons to
worry whether the average consumer will indeed get the services on their demand.

2.3 Service provider management and control

Providers of infrastructure services in a multi-tenant environment require

comprehensive control and complete visibility of the shared infrastructure to provide
the data protection, security, and service levels that their tenants expect. The ability
to control, manage, and monitor resources at all levels of the infrastructure requires
a dynamic, efficient, and flexible design that allows the service provider to access,
provision, and then release compute resources from a shared pool quickly and
easily, with minimal administrative effort. Service providers can leverage the portal
provided by Ionix IT Orchestrator, VMware vCloud Director, or their own chosen
portal to manage infrastructure resources and tenant organizations.

2.4 Tenant management and control

In every cloud services model, service providers delegate some elements of control
to the tenant. For some service providers, this is a matter of convenience; for others,
it is a matter of security or compliance.

Tenants have the ability to create and deploy their own virtual machines or vApps
from the service catalog available to them. This vApp catalog is presented to the
tenant via a front-end portal, such as that available with Ionix IT Orchestrator or
VMware vCloud Director. The catalog content can also be managed by the tenant
themselves if required. The tenant can develop and publish their own customized
applications and systems, which can then be used by other members of their
organization

2.5 Resources automation

Orchestration and automation go hand in hand. Orchestration automates delivery
and control. Interoperates with a number of potential vendors technologies used.
Connecting and automating of work flows when applicable to deliver a defined
service.

CHAPTER 3

CLOUD ORCHESTRATION IMPLEMENTATION AREA

3.1 Cloud services
• Private Clouds are typically owned by the respective enterprise and / or
leased. Functionalities are not directly exposed to the customer, though in
some cases services with cloud enhanced features may be offered – this is
similar to (Cloud) Software as a Service from the customer point of view.
Example: eBay.
• Public Clouds-Enterprises may use cloud functionality from others,
respectively offer their own services to users outside of the company.
Providing the user with the actual capability to exploit the cloud features for
his / her own purposes also allows other enterprises to outsource their
services to such cloud providers, thus reducing costs and effort to build up
their own infrastructure .Example: Amazon, Google Apps, Windows Azure.
• Hybrid Clouds-Though public clouds allow enterprises to outsource parts of
their infrastructure to cloud providers, they at the same time would lose
control over the resources and the distribution / management of code and
data. In some cases, this is not desired by the respective enterprise. Hybrid
clouds consist of a mixed employment of private and public cloud
infrastructures so as to achieve a maximum of cost reduction through
outsourcing whilst maintaining the desired degree of control over e.g.
sensitive data by employing local private clouds.
• Community Clouds-Typically cloud systems are restricted to the local
infrastructure, i.e. providers of public clouds offer their own infrastructure to
customers. Though the provider could actually resell the infrastructure of
another provider, clouds do not aggregate infrastructures to build up larger,
cross-boundary structures. In particular smaller SMEs could profit from
community clouds to which different entities contribute with their respective
(smaller) infrastructure. Community clouds can either aggregate public clouds
or dedicated resource infrastructures. We may thereby distinguish between
private and public community clouds. For example smaller organizations may
come together only to pool their resources for building a private community
cloud.
 CHAPTER 4

HOW CLOUD ORCHESTRATION IS IMPLEMENTED?

4.1 Orchestration tool (Orchestrator)

Orchestrator is a fully automated software suite that enables managed service

providers, hosting providers, data centre operators and enterprises to offer cloud-
computing services to their customers.
Coordinate and automate all the relevant operations in a user or administrator task
such as provisioning, alteration or decommissioning .Acts like a glue that binds the rest
of the components together in a way that makes the result unique. Exists solely to
automate the entire end-to-end stack in response to a user request or an
environmental threshold trigger.

4.2 Functions performed by the orchestrator

• When any user request occurs, the orchestrator is the component responsible
for making the appropriate calls to all of the other end point technologies within
the stack, either directly or indirectly.

• It allows the creation of an automated system that responds to user or

administrator requests through their respective portals, or to system events and
thresholds.

• Some orchestration tools provide customizable portal. Others will rely on portal
from a separate party

• Portal- A web-based defining feature of any cloud for self service .Portal has the
ability to execute and present the results of the series of workflows within the
orchestrator.

• As the cloud offerings matures and expands from its initial instantiation,
additional stack components may be added that do not have an awareness of or
integration into all of the other components in the stack.

• CMDB(configuration management database) or master database is required to

tie together all the components that a tenant owns.

• The orchestration tool handle tasks such as altering, inserting, or reading

 CHAPTER 6
FUTURE SCOPE FOR THE CLOUD ORCHESTRATION

Cloud orchestration allows for nearly effortless management of complex IT problems:

• Large-scale companies can expand as needed without concern for hardware or
budget throttling.
• Projects which require massive resources can be accomplished much faster when
spread across multiple virtual machines.
• New research projects can be undertaken for much less hard capital.
• Research and development teams can allocate their own resources through self-
provisioning rather than awaiting IT approval, allowing for more experimental
freedom.
• Cloud portals can be used for daily tasks (such as travel expense reporting) at a
fraction of the cost as opposed to maintaining in-house staff to manage and track.
• Telecommuting is more accessible than ever before, as cloud-compatible mobile
devices are more easily able to integrate with corporate data remotely.
• Cloud computing shares IT resources more quickly and efficiently, and has more
potential than traditional computing methods. It can be operated with less capital and
fewer staff, and business risks are similarly minimised. Although most businesses
have continued to increase their IT budgets, the truth is that their return on
investment is simply not proportional.
Computing in the cloud, on the other hand, will reduce IT costs while increasing
value - since there are fewer hardware, software, and staff requirements for business
ventures, while reduced resources are much more efficiently utilised. Simply put,
capacity is increased; capital is decreased. Businesses can easily expand their
networking needs without increasing their financial commitment to specialised
facilities and hardware. Enterprises can then push that capital back into the core of
their business. Additionally, cloud orchestration promotes experimentation without
the high risk (or cost). The reduced lag time between an idea and its implementation
allows for more innovative individuals to have their day in the sun, without leaving
the business vulnerable in other ways. Currently, the financial investment in existing
infrastructure has made most companies reluctant to consider experimental projects;
instead, concerns are focused on keeping existing hardware merely operational.
It is impossible to over emphasis the current effect of cloud orchestration on
increased IT productivity, not to mention the projections for years to come. In our
daily lives, both on a business and on a personal level, cloud-based technology is
rapidly becoming the norm. Through the possibilities of cloud orchestration the
computing and networking industry have been granted an immediacy and
accessibility which have never before existed, indicating that cloud solutions are not
going away anytime soon. Cloud orchestration is here to stay and without it, most
businesses are not actually benefiting from the cloud. Offering faster, self-service
provisioning and instant access to more network capacity that gives immediate
control to build and monitor cloud services will only improve a business.
By utilising cloud orchestration, SPs and businesses will be able to keep pace with
the technological landscape as they offer a market differentiation as well as assuring
revenue and new revenue streams through consultancy and new business, service
model. Cloud Orchestration is the seamless and secure intersection of business,
technology and integration in the heterogeneous cloud world in a real business
sense.

CONCLUSION

Cloud orchestration is here to stay and without it, most businesses are not actually
benefiting from the cloud. Offering faster, self-service provisioning and instant access
to more network capacity that gives immediate control to build and monitor cloud
services will only improve a business.
By utilising cloud orchestration, SPs and businesses will be able to keep pace with
the technological landscape as they offer a market differentiation as well as assuring
revenue and new revenue streams through consultancy and new business, service
models.
 REFERENCES

 EMC COMPUTE AS A SERVICE – OCT 2011http://india.emc.com/collateral/hardware/white-

papers/h8924-caas-vnx-vmax-wp.pdf

 EMC COMPUTE AS A SERVICE- DEC 2011http://india.emc.com/collateral/hardware/white-

papers/h9522-caas-vblock-vcloud-director-wp.pdf

 EMC COMPUTE AS A SERVICE – FEB 2012 http://india.emc.com/collateral/hardware/white-

papers/h10526-emc-caas-ito-vblock-vcd.pdf

 WHITE PAPER- 5 REASONS YOU NEED CLOUD ORCHESTRATION BY FLEXIANT

***