Orchestration

Hi readers. Here I am back again with some interesting facts about automation.  Let’s have a look on the topics that we have discussed in the last blog. In the last blog we have discussed about various ways of doing automation. On that we have learned about some basics of the orchestration, programming language and scripting language.

Now today we are going to learn about orchestration in details.

So here we are talking about the generic term – orchestration and orchestrator.

What is orchestration and orchestrator?

Orchestration is the automated arrangement, coordination, and management of computer systems, middleware, and services.

Now let’s go through an example to understand the same in a proper way.

As we have discussed previously also, orchestrator is used to designed flows and that same flows can be triggered. Once the flows will get triggered, it is start progressing as the flow is designed. For example, if you want to create an user in your domain then the process goes as follows:

So here the same flow we can design in orchestrator also.

Normally orchestrators will have:

Workflow Engine

Repository

Web Server

Flow processor

So we will design the flow in the workflow designer. Once that is designed, it will be stored in the repository. Whenever we need to trigger the flow, we can fetch the flow form the repos and trigger the same. Once all the necessary inputs are given, the flow will continue as per the designed steps and complete the tasks in seconds like magic.

Normally the orchestrators can be accessed from the workflow designer as well as through web service also. So to access that from web service, we need the web service to be always up and running.

Once the flow is completed, it will intimate the user and it will quit.

The task, that the orchestrators does, are knows as orchestration.

TYPES:

There are many orchestrators available in market. But among them some are mostly used and the names are as follows:

HPOO

SNOW (Service Now)

Vcentre

Scorch

Among those, SNOW is cloud based. All the data used for SNOW are being stored in cloud.

HPOO is manufactured by HP. This is a client environment based orchestrator. The Scorch and VCentre are also as same as HPOO. The main difference is HPOO is mainly used for UNIX automation where Scorch is used for Windows automation and VCentre is made by VMWare so it is mostly used for Virtual System Automation.

That was the generic details about orchestrators. In our next blogs we will discuss about all the orchestrators (Mainly SNOW and HPOO).

Keep reading my blogs. for more information and please do post comments for any query or feedback.

You can drop mail in anik.raj004@gmail.com.

The next blog will be coming soon (Wednesday, Friday and Sunday).  Thanks for reading.