Here.
And welcome back now in today's radio will be discussing about the elastic Bienstock stocks deployment
policy, not the deployment policy, specifies how new updates for the applications that are running
in the elastic Bienstock environment are pushed.
So, for example, let's say that you are running an Android phone.
So Android basically comes with a Google Play store, which is generally used to install new applications,
update your existing applications and so on.
So in the Google Play store, you have option of it states that the new updates that are made to the
application should only happen maybe or the cellular data or it should only happen via the Wi-Fi and
so on.
So there are a lot of configuration options that are available with states on how your Android updates
should be pushed into your phone and similar would be available for iPhone as well.
Now, in a similar way, even for Elastin Bienstock, your application will also have new updates.
So depending upon your organization, some organization, they generally have new update to the application
every one month.
Some organization have every one week and so on.
So depending upon that, there are various deployment policy options that are available and depending
upon their deployment policy options, the new updates are pushed to the environment.
So there are various deployment policy options like all at once, the rolling rolling with additional
batch immutable and so on.
So let's do one thing.
Let's quickly look into one among them that will give us a foundation about the deployment policy in
Elastic Bienstock, not the one that we will be discussing in today's video, would be the first one,
which is all at once.
So what happens in this approach is that the new update is deployed to all of the two instances at once.
So, for example, let's say on the left hand side, you have a working environment and there are two
easy two instances that are running.
Now, if you decide to push new application update using the all at once deployment policy, then what
will happen is it will be pushed to both of the two instances simultaneously.
So in case, if this new application update is a faulty one, so there is some issue with this application
update, then essentially both of the E c two instances to which this faulty application update has
been pushed to will stop working.
So essentially your production website will go down.
So this is one of the risks associated with all at once based deployment policy.
So by the name itself, you can quickly identify that all at once will go Gordon and push the application
update to all of the instances at once.
So let's do one thing.
Let me give your demo about this so that the overall concept of all at once, as well as the deployment
policy is better understood.
Now, currently I have elastic Bienstock environment and there are two easy two instances that are running
as part of it, similar to the diagram that we were seeing, that there are two instances as part of
the training environment.
Now, if you look into the configuration of this Elastic Bienstock moment, there is a specific category
of rolling update and deployments.
So if you'll do added to it here, let's go back to under the deployment policy, you can select various
deployment policy like all at once, rolling, rolling with additional batch and so on.
So by default, currently you have all at once base deployment policy.
So let's go back to our environment here.
And our environment basically has a simple HDMI content, which states are welcome to sample every application.
So let's do one thing.
Let's go ahead and push a new update to this specific environment.
So I'll click on upload and deploy.
I'll click on Tuesday and this time I'll select a file called this new update Ebbitt app, Dot Zip.
So this is a new update for the application.
Let's go ahead and deploy now along with that.
It also states that the application version will be deployed using all at once policy.
So let's go ahead and deploy this specific update.
That's great.
So it took less than one minute before the application update to be pushed.
Now, if you'll quickly refresh this page, you'll see you have a new content with this new update to
the application.
And this update is pushed to both of the two instances that are running.
So this is what all at once mean.
So this is good as far as the application update that gets deployed successfully.
So everything is happy, happy year.
But what happens if this app.
It is a faulty application.
So this is where the problem occurs if you have a faulty application update and if your deployment policy
is all at once.
So let me quickly show you this.
So let's go ahead and click on upload and deploy this time.
I intentionally choose one of the application optics which will tend to fail.
So, again, I'll be uploading all of these files so that you can also try it out.
So let's click on Open and let's deploy.
Great.
So our deployment has been successful.
Now, if you look into the recent events all year, you have one error which states that instant deployment,
the Docker container, unexpectedly ended after it was started.
So basically, if you go ahead and open this DNS, you immediately see 050 to buy the gateway that is
happening now.
Again, one important thing that needs to be noted here, currently, the health is Shawna's okay.
However, this will also be decrypted within a few minutes.
So now you see your health is changed from okay to severe.
Now do note that since we had pushed the faulty application update and since it was all at once, that
essentially means that both of these two instances are running with the faulty application update.
And this is the problem because your entire production application has gone down at this moment of time.
So let's quickly do one thing.
Let's go ahead and push the new update.
So let's go ahead and push this so that our application, again, is up and running.
That's correct.
So now let's go ahead and refresh the panel.
Application again is up and running.
So at a high level overview in today's video, we discuss about the basics of deployment policy.
We looked into the all at once policy, the advantage on how it can go ahead and quickly deploy the
application versions to all the instances and also the disadvantage in terms of faulty application update
with to deployment policy.
Now, in production environment, you will not really use that all at once.
Deployment policy.
There are many other recommended deployment policies that are available which can handle this scenario
of faulty application update in much more better ways.
So we'll be discussing about this in the appropriate videos.
However, with today's video, we will conclude at this moment.