In this video, we will describe the process that need to be adopted by
CloudOps Engineer to plan and implement the principles of DevOps and
achieve continuous ops in public and private clouds.
As a CloudOps Engineer, we need to appreciate certain Qualities and Features
that can be achieved in our existing infrastructure and implementations.
Let's go through certain Qualities and
Features that we can achieve using CloudOps.
First feature is its Ability to scale.
We can expand capacity at any time.
CloudOps will help us to provision servers automatically.
And this particular feature adds a great deal of value, but yes,
sometimes it can be challenging to manage.
Second feature that we can expect when we are implementing CloudOps principle
in order to manage applications is Stateless and distributed services.
CloudOps prefers Stateless and distributed services.
Because you'll find that operations management becomes simplified
if our services are Stateless and
they are distributed across multiple different clouds.
Third quality that we can appreciate as a CloudOps Engineer is its
Infrastructure-agnostic architecture.
As a CloudOps Engineer,
we need to always plan architectures which are Infrastructure-agnostic.
Fourth is Location transparency.
We need to ensure that our architecture implements Location transparency,
which means that the physical server and its Location is not revealed.
Now we need to understand certain other Features that
can be realized by using CloudOps practices.
First is Latency tolerance and loose coupling.
You'll find that Latency can vary a great deal and
you need to focus on managing it.
You can utilize CloudOps principle in order to adopt right orchestration and
automation mechanism to define the attributes
that takes care of Latency tolerance and provides loose coupling.
Second quality is capability of setting up Automation and
self-healing capacity.
Clouds internally uses automation in order to fix multiple different
operational problems without affecting the applications or
the users of applications.
Third is focus Metered cost, which provides benefit
to end user to decide and leverage cloud resources as per their need.
After identifying the expected qualities,
we need to focus on CloudOps processes.
So let's go ahead and describe CloudOps processes that helps
streamline cloud operations and create continuous feedback solutions.
To start with, we need to always identify the requirement.
And that is done by Assessing the requirements of applications and
data that you're going to host in cloud architectures.
Second is to create and update a deployment plan,
keeping in mind availability as well as failover.
After you have created an updated deployment plan,
you need to Devise the right strategy.
There are multiple different deployment strategies which you can follow.
You can go with blue-green or canary deployment options as well.
Next is to Select the technology solutions, and
that is done after you have created the strategy.
Strategy helps you to select the right technology solution
that helps to automate provisioning mechanism of cloud platforms and
build redundant services that can function independently.
Now, we have selected the technology.
After selecting the technology,
we need to Select CloudOps tools that best suits the need.
At a minimum, you will need cloud management tools for monitoring and
automation.
And finally, you need to Adopt continuous feedback process for
which you will be building a process to receive continuous feedback and
delegate it to the right team member to manage continuous improvement.
Finally, let's try to discuss Minimum Viable CloudOps Solution.
As a CloudOps Engineer,
we would like to define Minimum Viable CloudOps Solution.
And that heavily depends on what is the existing workload,
what is the placement strategy, and what all are the capabilities that you
expect from your Minimum Viable CloudOps Solution?
Let's try to understand using a graph which is depicted as a diagram
on the current screen.
We are taking Time and Scalability as the prime factors.
We always start with Collaborate and migrate.
In short, you need to gather a team and
migrate a low-risk cloud friendly app.
Second is to conduct Multiple pilots to adopt the right Minimum
Viable CloudOps Solution.
In this particular task, you will be spending more time, but yes,
your focus will also be on scaling out.
You will be migrating more applications.
You will be doing gradual tests and focus on more control and automation.
When you are building MVC pilots, you will also add new processes and
people integration, but yes, at a small scale.
Next stage is to go for MVC self-server,
which provides the mean for self-adoption.
You'll also federate tools and processes at a higher scale.
It will also help you to identify changes and build practice communities.
And finally, you will move to the last stage, that is, Cloud capability.
Which means now you are building external awareness and
you are adopting agile principle by testing more nonfunctional
aspects of your existing CloudOps solution.
So by focusing on various different elements of CloudOps and
coming up with Minimum Viable CloudOps Solution,
applying right metrics, putting right load on the system,
testing it from various different perspectives will help you to derive
the right CloudOps solution that can be adopted by enterprises.