Visit the Architecting Microsoft Azure Solutions course recordings page
United Arab Emirates - Architecting Microsoft Azure Solutions
WEBVTT
-->
And this is the number space.
-->
8 seconds to go.
-->
5 seconds to go.
-->
4, 3, 2,
-->
1, 0.
-->
Okay, perfect.
-->
So, yeah.
-->
This is the former Azure Active Directory.
-->
Nowadays,
-->
we know like
-->
Azure Entry ID
-->
for the new name
-->
for the traditional Azure Active Directory.
-->
But this is the one,
-->
this is a directory
-->
that handles and releases
-->
and the number space
-->
and control the access
-->
to any resource
-->
within Azure.
-->
So, this is the
-->
right answer.
-->
The policy is how to handle
-->
the resources,
-->
the access to the resources.
-->
So, this policy
-->
applies to objects
-->
that were created
-->
within the directory.
-->
So, this is like
-->
an approach
-->
and a policy
-->
account that you create
-->
and you decide
-->
what can be done
-->
with the resources
-->
of my cloud
-->
and who
-->
can do that.
-->
And that is who
-->
is still in the directory.
-->
So,
-->
this is the center.
-->
Well, it's nice.
-->
But it's more
-->
regarding security.
-->
The firewall is just from the works.
-->
So, the right answer
-->
was that.
-->
So, let's see.
-->
The top three
-->
are like fighting for the first
-->
place.
-->
we are really close. This is the last
-->
question. So, this is the
-->
one. So, let's see
-->
how it goes, guys.
-->
Let's read it.
-->
Azure infrastructure
-->
handling.
-->
What Azure service
-->
will you extend
-->
to a
-->
network into the Microsoft
-->
cloud?
-->
Okay.
-->
Okay.
-->
Five seconds.
-->
Three, two,
-->
one, zero.
-->
Okay.
-->
So, there were
-->
three options here. So,
-->
first of all,
-->
the CDN, the content delivery
-->
network.
-->
The question here was
-->
how to extend
-->
your own privacy
-->
network into the cloud.
-->
with Azure
-->
CDN, what you do
-->
is that you
-->
place an email
-->
your website. You have your website.
-->
In this website, you have
-->
previous files,
-->
you have images,
-->
you have videos,
-->
you have content,
-->
and you want
-->
that content to be
-->
closer to
-->
your customers, to your
-->
website users.
-->
So, the Azure CDN
-->
is a network
-->
of proxy
-->
caches around the
-->
world, geographical
-->
located
-->
all over the world,
-->
in all places all over the world,
-->
and with a copy of those
-->
files, of those images,
-->
of those videos. So,
-->
this is a way to
-->
max the
-->
throughput of your
-->
website. So,
-->
it's not properly to connect your
-->
or extend your privacy
-->
network. So, it's a helper
-->
for the performance
-->
of your website.
-->
The blog storage is
-->
a storage of objects
-->
of privacy
-->
in the cloud.
-->
The app service is the web hosting service
-->
that we discussed.
-->
So, the last one is ExpressVault,
-->
which by default will be
-->
the right answer.
-->
But, just to discuss,
-->
ExpressVault is a
-->
facility that is
-->
available to certain
-->
data centers around the world
-->
that gives you, that provides
-->
you connection
-->
or connectivity, last mile
-->
connectivity, you can say,
-->
with Azure. So, it's
-->
a really good way
-->
to have direct access
-->
to the network
-->
in the cloud. So,
-->
you can have like
-->
you can say like
-->
if another hub
-->
within your network
-->
to the
-->
cloud itself,
-->
Azure itself.
-->
So,
-->
congratulations
-->
we
-->
just
-->
finished
-->
this
-->
little quiz.
-->
Let's see the results.
-->
So, very good views.
-->
Here's Alexander
-->
and
-->
very good guys.
-->
Really good. Amazing.
-->
Over 2,000 points.
-->
That's huge.
-->
And congratulations
-->
to everyone.
-->
Very good guys.
-->
Very good.
-->
That works.
-->
So, that's it.
-->
That's what I wanted
-->
to share with you
-->
initially or to discuss with you
-->
initially.
-->
What we are going to do
-->
is to discuss a little
-->
more about what we
-->
shall see in this
-->
little
-->
quiz.
-->
Let me know if you have any doubts
-->
about
-->
the question that
-->
we have or
-->
if we are
-->
good to go.
-->
Let me know that.
-->
That is very nice.
-->
No worries.
-->
Let's move on.
-->
Okay.
-->
So, as I told you
-->
my name is Andres
-->
Mujica. I will be
-->
trying out
-->
these codes.
-->
I've been
-->
working with IP
-->
for 3 years
-->
by now.
-->
So, hopefully I will be able
-->
to share my experience
-->
and knowledge with you guys.
-->
That's why
-->
I'm here.
-->
Anyone
-->
or another one
-->
are having this mission.
-->
Okay.
-->
So, I'm going to try to let me see
-->
like this.
-->
Like this.
-->
Are you feeling better like this?
-->
Okay. But I'm going to leave it like this.
-->
Okay. Good. Thank you.
-->
Thank you.
-->
Okay.
-->
So, regarding
-->
regarding our
-->
scheduling and organization
-->
the idea is that we store the name
-->
until
-->
5 PM. We are going to
-->
have to coffee breaks
-->
at 15 minutes
-->
each. And
-->
I'll just leave it.
-->
I'll just share here.
-->
Okay.
-->
So, we are going to have
-->
our two coffee breaks.
-->
per day.
-->
The idea is that the first one to have
-->
it at 10.45
-->
time.
-->
And then the lunch break
-->
to have it at one
-->
PM real time.
-->
And the second coffee break at
-->
3.45 PM real time.
-->
So, let me know
-->
if the lunch break at one
-->
PM is okay for you.
-->
Or if you want it to be
-->
either later
-->
or earlier.
-->
So, we can accommodate
-->
if it's okay
-->
at one PM.
-->
So, let me know
-->
if you have to do
-->
for this
-->
we need to check.
-->
So, regarding the
-->
activity training, we received
-->
an evaluation point so you can
-->
give us some feedback regarding
-->
how this training goes
-->
went.
-->
So, we can improve for
-->
future opportunities. However,
-->
if you think
-->
that there is something that
-->
needs to be changed or that
-->
you want to see or something that
-->
is not due to execution
-->
and it's due today
-->
and tomorrow. Please don't
-->
hesitate and raise your hand
-->
and let us know so
-->
we can improve
-->
and not hesitate after
-->
this has ended because
-->
there will be another point
-->
to be done.
-->
And also we will get
-->
certificate of attendance.
-->
Okay, so this will be
-->
Azure architecture or
-->
architecture solutions for
-->
Azure.
-->
The objective of this training
-->
in general is to
-->
improve your design
-->
skills of Azure solutions
-->
to understand
-->
the features
-->
capabilities of different
-->
Azure services
-->
to have the ability
-->
to make decisions
-->
regarding how to
-->
design a public and hybrid cloud
-->
how to handle
-->
the infrastructure and the
-->
different features
-->
that we have available
-->
with Azure as well.
-->
The audience is
-->
basically you guys. You are
-->
the kind of
-->
git nerds and IT
-->
people that will love this training
-->
because no other people
-->
in the world will like this.
-->
Only those as
-->
us. So that
-->
is important.
-->
And now regarding the outline
-->
we have different modules
-->
to this training
-->
the design principles.
-->
We are going to discuss
-->
web services, web apps
-->
storage, secure
-->
resources, the infrastructure
-->
advanced applications
-->
management monitoring and
-->
business continuity strategy.
-->
The idea of
-->
this training is
-->
this
-->
training is
-->
more regarding
-->
architecture.
-->
It's not that
-->
lack of
-->
hands on training
-->
in the sense of
-->
deploying workloads
-->
or stuff like that.
-->
It's more like making
-->
choices, making decisions
-->
about which workload
-->
to deploy, how to deploy
-->
that workload
-->
more than how
-->
to deploy that workload.
-->
However
-->
as time
-->
and we here are
-->
from the leaders
-->
of the best way
-->
of learning is to
-->
do it with your hands
-->
so that you can give it
-->
a try by yourself.
-->
So we are going to
-->
or we have
-->
a lot of labs
-->
for this training so you
-->
can
-->
get in touch with the
-->
actual
-->
platform.
-->
So actually
-->
we have 40 labs.
-->
However
-->
the time is
-->
not enough to
-->
execute all of those labs
-->
but you will have
-->
access to the material and
-->
even to the platform
-->
so you can execute
-->
the labs
-->
that you didn't
-->
execute during the training
-->
by yourself.
-->
Yeah, so that is
-->
important to know.
-->
So the labs that we have here
-->
highlighted are the ones
-->
that we are going to execute
-->
during these two days
-->
but
-->
perhaps if we have the time
-->
or if you think
-->
that one of the other labs
-->
that we have highlighted
-->
is
-->
interesting enough
-->
to let's do this
-->
and we can do that
-->
and there is nothing to do at all
-->
and some of the labs perhaps I can show you
-->
really quick about
-->
some of the public stuff that is in here
-->
so you can give it a try
-->
later.
-->
So the idea is to
-->
enjoy, to learn
-->
and to
-->
have the
-->
most of the time that we can
-->
have this training.
-->
So the first
-->
part is mostly
-->
important too.
-->
There are some
-->
tools here in the first part
-->
regarding all the designing stuff
-->
and the
-->
other ones are more like face
-->
studies
-->
that cover the different
-->
segments or models
-->
of the training. These face
-->
studies, the idea is that
-->
we have a
-->
real life face
-->
scenario and we
-->
design a solution for that
-->
real face
-->
scenario. So actually
-->
that is
-->
something that we need
-->
to have in mind
-->
because the idea
-->
of this training at the end
-->
is that we will be able
-->
to design a solution. So actually
-->
this one, the
-->
code,
-->
the architectural diagrams
-->
you can see the code in that
-->
file. It's
-->
a
-->
really
-->
loud but important one
-->
because with this one we can
-->
create architectural diagrams
-->
for all of the other
-->
applications. So
-->
some recommendations
-->
please don't
-->
hesitate to ask
-->
any questions
-->
out loud.
-->
It's not that easy
-->
for me to see
-->
if you raise your hand
-->
or if you know that
-->
perhaps I can use that.
-->
So don't
-->
be shy in interrupting me.
-->
If you have
-->
any experience to share
-->
please go ahead and do it. It's
-->
important.
-->
I mean
-->
I'm not the only
-->
one that is learning
-->
today. And you are not the only
-->
one that are learning today. I'm
-->
myself. I'm learning today
-->
with your experience as well.
-->
So this is
-->
a small suggestion for you.
-->
So it's important as well.
-->
Also the design
-->
of an actual solution
-->
is not
-->
like there is only one
-->
valid
-->
design or valid
-->
solution. Not
-->
at all. I mean there can
-->
be plenty of solutions
-->
for any case study. So
-->
we are going to present
-->
one possible solution
-->
but that is not the
-->
only right
-->
or the only truth. I mean you
-->
can approach the solution
-->
in a lot of ways
-->
different ways. This is what happens
-->
in real life. So have
-->
that in mind.
-->
You are welcome to keep your camera on
-->
so we can see each other if you
-->
want to. Not mandatory
-->
but if you want to
-->
you are welcome
-->
to do it. And
-->
if you need something to be
-->
further clarified or whatever
-->
just tell me. It's important
-->
for us.
-->
All the material
-->
of this training
-->
will be available in this
-->
repository.
-->
So
-->
you can clone this repository.
-->
I'm going to show you in just a few
-->
minutes how to access
-->
here. And this
-->
is already available
-->
with a desktop
-->
machine. So you can also
-->
if you don't want to clone it
-->
you can also just
-->
copy that to your
-->
email account
-->
or to your inbox or whatever
-->
directly from the database
-->
machine. So you can have a copy of the
-->
material as well.
-->
And actually that is what we are
-->
going to do in this
-->
precise moment. So
-->
let me
-->
go here.
-->
So
-->
let me see.
-->
Okay.
-->
We are supposed to go to
-->
our
-->
first copy break but
-->
let's wait a minute so we
-->
can do this now.
-->
So the idea of this map
-->
is so we can get familiar with
-->
what we have here
-->
and we can see the flight.
-->
So just go to your
-->
desktop machine
-->
and you will find here the
-->
explorer, the prize
-->
explorer.
-->
So
-->
here in
-->
your desktop
-->
if you go to your desktop
-->
and materials
-->
you will find
-->
a few
-->
files that are part
-->
of these things that we are going
-->
to take a look later
-->
but there is one that
-->
you may want to open
-->
if you want to because
-->
it is the slides
-->
that we are working with.
-->
And
-->
you can have them here so
-->
you can check
-->
any
-->
stuff.
-->
So this is the one
-->
that you are taking a look at.
-->
So the materials folder.
-->
So in this folder
-->
there are some stuff
-->
which is actually
-->
more interesting. They
-->
are the architectural
-->
framework, the
-->
scene taken framework
-->
and some
-->
examples files
-->
for adoption or strategy
-->
and some architectural
-->
diagrams that we are going to go through
-->
as well as the official items
-->
for item.
-->
So take a look into those
-->
files.
-->
If any of you guys
-->
have access to the
-->
Vex.com website or Vex.com website
-->
please
-->
discover the information.
-->
Here are the
-->
slides
-->
The other folder that you may want to take a look at, here in this panel, is the Azure
-->
The other folder that you may want to take a look at, here in this panel, is the Azure
-->
The other folder that you may want to take a look at, here in this panel, is the Azure
-->
The other folder that you may want to take a look at, here in this panel, is the Azure
-->
The other folder that you may want to take a look at, here in this panel, is the Azure
-->
This is the Azure Architecture Labs to Workspace
-->
And here we cannot introduce the code
-->
We don't have anything yet there, so no worries about it
-->
And there is another tool that you may want to open, which is the DrawIU
-->
So in activities, you just write DrawIU, and it will show up there
-->
So, we can concept here, I guess
-->
For example, we can take a look into the diagrams that we found
-->
We want to open a diagram from the materials folder
-->
So we can take a look here
-->
So those tools are the ones that you may want to use
-->
So those tools are the ones that you may want to use
-->
Or you can go to this directory
-->
The Azure Architecture Labs Workspace
-->
And then open the code
-->
Go to the home folder, the desktop
-->
Make sure to open those two examples
-->
We have a library of the official Azure items
-->
So you can import those in your environment
-->
We are going to do that in the course coming back
-->
So you can transfer that in the authentication
-->
This is more complex
-->
But it's quite nice, it's quite beautiful
-->
And it's designed with an architecture, actually
-->
It's like playing with Lego
-->
So I can't really see what I'm solving
-->
Because what I'm going to do is to play with different components
-->
And calculate the logical and physical relationships between them
-->
So that is one of the leader modes for an architecture design
-->
But it's kind of the most important one
-->
No, it's already in the next question
-->
It's already in there, so you don't need to clone
-->
So if you want to clone that, that will be in your own machine
-->
In your local machine
-->
So you can clone it wherever you want
-->
But it's already in the index
-->
So you don't need to do that
-->
If you want to explore the materials folder
-->
Go to your home folder, to desktop, to materials
-->
And there you will find the slides and additional material
-->
And also if you open the drawRU application
-->
You can open one of those diagrams
-->
So let's have a topic break for 15 minutes
-->
So we will meet again in 15 minutes
-->
So see you in 15 minutes
-->
Okay
-->
Thank you guys
-->
Thank you
-->
Thank you
-->
Thank you
-->
Thank you
-->
Okay, so that was our environment
-->
So we are going to use some of that stuff in there
-->
And what we are going to do is
-->
Well, we already did that
-->
We are going to create an Azure account
-->
I think someone asked a question
-->
John?
-->
So let me know guys
-->
Do you have an Azure account with a subscription available for you to use?
-->
Either personal use or corporate use?
-->
Because I mean we are going
-->
We are not really going to deploy a lot of stuff
-->
So it's not like we are going to spend a lot of money
-->
To be honest
-->
I don't think it goes over $1, $5
-->
But we do need a subscription because otherwise it won't let us deploy some of the stuff
-->
So let's do the following
-->
Let's check that
-->
So if you want to access the desktop that will be nice
-->
Because that way I can see what we have in the system
-->
But if you want to access the desktop it's okay as well
-->
So I'm going to share my screen again
-->
So I can show you what we want to have here
-->
So let's see
-->
So we are going to
-->
We will be the last number two
-->
Or one
-->
Last number one
-->
The previous one was the last two
-->
So here we are going to just check if we have our subscription
-->
So here is the purpose of using the desktop
-->
So what we want to do here is to access portal
-->
Azure account
-->
Azure account
-->
Then you can do it outside
-->
That's for sure
-->
So what we need to do here once we have logged into Azure account
-->
Is to go to subscriptions
-->
And see if you have any subscription or not
-->
One of the questions that involves some of the stuff that we want to do is like an election track or a track
-->
So we may require to have that subscription
-->
We don't have a subscription
-->
We can only create one for free
-->
So if you want I'm going to go to that link
-->
So subscribe to that link
-->
So you should go to that link
-->
The only thing that it requires is
-->
So I mean you need to take the first part
-->
It's not that it's going to show if you create anything
-->
It's going to be the subscription
-->
Oh yeah
-->
If you don't have a subscription you can do that for sure
-->
And that's because for example for the
-->
There are some of the last two in the Azure part
-->
That require Azure FDID
-->
Or if you want to deploy the web app or add an advanced application
-->
You may want to take that right away
-->
And I think that you also can add
-->
That you can add a subscription for free
-->
But you need to check in your own account because in my case
-->
The application has a basis for the web app
-->
It's the basic tool
-->
So if you don't have a subscription
-->
You can create that later on
-->
With the free option available
-->
Or I can give you access to a subscription from my side
-->
But it will take a while to do that
-->
So what you can do is please let me know if you do that or not
-->
A subscription
-->
You can let me know through the chat
-->
So I can know how many of you guys have a subscription or not
-->
If you don't have one
-->
I'll see what you know if you come to the free account
-->
If you have a facility for passing the courses
-->
Or otherwise if you want a subscription
-->
So we are going to do that later
-->
Okay
-->
Absolutely
-->
Yeah absolutely
-->
Yeah you can create a free
-->
I mean
-->
Actually you can
-->
With the corporate account you can create a free subscription
-->
And use that one
-->
Or you can have a personal account
-->
And create a free subscription with a personal account
-->
And I do agree with you that the corporate subscription
-->
Will not be used for the training
-->
Until the comments that we are going to do
-->
So be aware of that as well
-->
I'm going to show you really how to create a free account here
-->
So in this link that I sent you guys
-->
There is this option
-->
You have three ways to use it
-->
So this is what is offered here
-->
And the start free option
-->
Or review the option to review the free account
-->
I think that it's only a moment to do that
-->
Because I have done a lot of
-->
Let me see if it shows
-->
Okay yeah
-->
Or with the corporate account
-->
Okay yes
-->
So let's move on
-->
When we reach the labs
-->
We can see them
-->
We are going to provision some of
-->
The subscriptions
-->
Okay
-->
So let's continue
-->
So the first thing that we are going to discuss
-->
Is something called the cloud adoption framework
-->
So there is
-->
Actually let me drop this
-->
To this slide
-->
So there are like three critical
-->
Tools on Microsoft's strategy
-->
To designing solutions for the cloud for Azure
-->
And in the Microsoft Docs side
-->
I'm going to show you in a little bit
-->
You will find everything that you need to know
-->
About those three files
-->
The first is the cloud adoption framework
-->
Which is the first one that we are going to discuss
-->
Then is the world architect framework
-->
That allows you to see if what you have architected
-->
Follows the rules or the pillars to be a good design
-->
And then finally the Azure architect example
-->
Which provides you with two or three assessments
-->
With anything that you need
-->
In order to fulfill the guidelines
-->
Provided by these two frames
-->
So the cloud adoption is
-->
If your customer or your company
-->
Is going to move into the cloud
-->
So how to adopt it from the business
-->
From the view
-->
Of the technical point of view
-->
And the world architect framework
-->
Is the guidelines to design
-->
To architect and check what you have already
-->
Designed and architected
-->
If it follows the expectations
-->
So those places
-->
Those websites are here
-->
So I'm going to show the link for you guys
-->
And I'm going to open the link in the direct submission
-->
So this is a blank
-->
Microsoft.com
-->
Microsoft.com
-->
And as
-->
And as for
-->
And as for
-->
So this is the actual
-->
So this is the actual
-->
And it's actually in the materials folder
-->
And I'm going to show you
-->
All the different things
-->
So you see in the materials folder
-->
You'll see that
-->
By the cloud adoption framework
-->
And the Azure architect file
-->
The whole project
-->
So I'll show you that
-->
So those are like the basics of this thing.
-->
Okay, thank you.
-->
Okay, thank you.
-->
Okay, so this is
-->
And this is the way
-->
Work from
-->
And they were able to
-->
So from this study
-->
This has been done by Microsoft
-->
And you need to take this as a way of sale, because Microsoft will always
-->
And any cloud provider, Amazon and Google as well, will always tell you that it's cheap to go into the cloud
-->
But that is true, only if you compare how much will it cost for your company or your customers to have all the features and benefits that are already available in the cloud
-->
How much will it cost for your company or your customers to have all the features and benefits that are already available in the cloud
-->
The cloud is actually much more expensive than what you have now
-->
The difference is that what you have now, to make that scalable, to make that flexible, to make that resilient at the same level of what is available in the cloud
-->
That is something that you have to be clear about, because if the financial guy in your company thinks that moving from apprentices to the cloud will save him money or health money, that is not true, to be honest
-->
I mean, usually what happens is that companies believe that, but people shut and they hit themselves against the wall and they realize that it costs a long time
-->
So it's a bit tricky, but it's important to be aware of it
-->
There is something that you may have heard about, that is called cloud application
-->
And that is companies that have moved away from the cloud because they realized the costs of moving data, applications and all that stuff from apprentices to the cloud
-->
Some people say a lot, and it was a bad move from them, so they just decided to move back
-->
So one example is Roblox, who moved away from Amazon to the Honda Display Decentre
-->
And there they saved about 75 million dollars just the first two years
-->
And the most recent example is our friend Musk with a computer, but they did the same
-->
We don't know how much money they have saved, but probably it was a lot of money, so you have to cut that
-->
So the benefits of the cloud are that what is already in there, the reliability, scalability, to reach out those levels, it doesn't make sense to have those apprentices
-->
So that is a parenthesis
-->
This is something that no cloud provider will help you with
-->
So now going back to CAF
-->
So the cloud adoption framework
-->
Our frameworks that help you to adopt and architect actual solutions in this space
-->
CAF gives you the guidelines for how to properly adopt the cloud
-->
Regarding documentation, how to implement the best practices
-->
It provides you tools that allow your organization to integrate this theory to the cloud
-->
And it answers the why, the why, the why, the how, to manage and help to operate the cloud
-->
So that is what CAF is about
-->
Now the WAF, the low architecture framework, it's more in the technical operational aspect of this cloud joining
-->
So the WAF guides cloud architects as well
-->
It will secure high-performance infrastructure for the application
-->
So it gives you capabilities, allows you to assess how are you to optimize your architecture
-->
And it gives you, I mean, it is fundamental in five pillars
-->
That gives you the right approach to evaluate and improve any cloud system
-->
Every major cloud vendor has a different version of these two frameworks
-->
Their own version, Azure, Amazon Cloud, Google Cloud
-->
But in the end, those are very similar to each other
-->
In this case, we're discussing specifically the architecture as well
-->
So this cloud adoption framework from Microsoft gives you
-->
So this
-->
So this gives you the business strategy, it allows you to talk about the business strategy
-->
Today the cloud strategy and the business strategy on how to adopt the cloud
-->
So it will give you one way to do this, a unified way to do it
-->
And how to motivate or how to align the adoption of the cloud with the requirements of your business
-->
Which outcomes you expect
-->
And allows you to process all through this adoption lifecycle
-->
In order to do that, they have some basics like documentation
-->
So you can have a standard documentation for your cloud adoption
-->
A set of tools that helps you to process the adoption of or start this cloud learning
-->
Some things that you can use to leverage them in order to, I mean
-->
The basic idea here is to have a repeatable process in order to adopt the cloud
-->
That now to be able to leverage what you have done in the past
-->
And what Microsoft has done in the past in order to do your own move or help your customers to do their moves
-->
So those are the things that we see behind the scenes
-->
And the best practices to follow when adopting the cloud
-->
The idea is to have a good balance between the control and stability of the adoption
-->
The modernization and have a good enough speed of results regardless
-->
This cloud adoption framework has several steps
-->
The first of them is the strategy
-->
This strategy is why are you moving to the cloud
-->
Why you are going to or what are you going to do after moving to the cloud regarding the business
-->
And how should you do the first step
-->
How to solve the chicken versus egg dilemma here
-->
So which product to choose in order to move into the cloud
-->
After the strategy is done, there is a set of steps
-->
Which usually are, I mean, recycle around these steps
-->
Regardless of those projects that you choose to move on
-->
And these steps are the plan, the planning stage
-->
Which could be different what is what you are going to do
-->
How this allows the organization
-->
Or just set up a series of plans
-->
And are there disputes that you can have
-->
Because are they outed of the cloud in particular
-->
Once that planning is ready to go to the second step
-->
Or third step, I don't know
-->
Which is the ready step
-->
And you start to do something that is called the warning zone
-->
Which puts you into the cloud
-->
How to validate the status
-->
How to start doing out of the cloud
-->
And once that is done, you start to adopt it
-->
And there are two strategies here
-->
The first one is the integration
-->
The most popular one is the lift and shift
-->
Which is just to move workloads to the cloud
-->
To work on servers
-->
To be honest, I don't really like that approach
-->
Because this is the most expensive one
-->
Because if you are going to move the same server
-->
That you have on premises to the cloud
-->
Without innovation or modernization
-->
You will end up just changing hosting providers
-->
And the country is not
-->
Or Amazon or Google are not
-->
They are not characterized
-->
For being the cheapest hosting provider out there
-->
So you can use this as a first step
-->
But you should always aim to innovate
-->
To break down that information that has a database
-->
That has a web application
-->
And put that web application into an app service
-->
And to put that database into an Azure SQL database
-->
So you destroy that information
-->
And start using local cloud service
-->
So that is the innovation approach
-->
And that will give you all the advantages of using Google
-->
So this is a cycle that you start and repeat
-->
For every form
-->
Depending on how you define your strategy
-->
But basically that is how it works
-->
And once we have completed this part of this one cycle
-->
We will start to manage that cloud
-->
And to grow and run that cloud
-->
So from the business outcome
-->
That you can make from your family discovery
-->
Or your team because we have all of you
-->
And how to operate that cloud web app
-->
As well as the governance of that
-->
Regardless of the costs
-->
And the amount of stuff like that
-->
So this is what I just talked about
-->
So this is what we do
-->
With the business journeys
-->
We define the server dynamics
-->
The plan, we define that actionable time
-->
For cloud adoption
-->
The ready, we define the time
-->
For adoption, to innovate or innovate
-->
We define the workloads
-->
Automation of the governance
-->
And the baseline of operations
-->
And then finally this is doing all the work
-->
To secure the background of what we are doing
-->
So this is how you do it
-->
And it should be
-->
I mean this is not something that you do once
-->
And for that it is something that is supposed to be
-->
Sticked in mind and ready for them
-->
Depending on the situation
-->
So in order to use this cloud adoption framework
-->
We have an assessment procedure
-->
And we will use a series of Microsoft assessments
-->
That allows you to know where into this
-->
And to meet what visual on these steps
-->
You are or your organizations are
-->
So you can be an assessment
-->
To first evaluate your studies
-->
To see what you have already had
-->
A very large diagnostic
-->
Regarding what you need to do
-->
Or how good are you
-->
Or which gaps you have in your workflows
-->
And create an action plan
-->
Based on the reality
-->
So you can follow and update action
-->
Regarding that plan
-->
You can check your score
-->
And see how to improve
-->
And keep running on your surface
-->
So these tools are where you go
-->
For you to use
-->
And actually we are going to start using one of these tools
-->
This is the cloud journey tracker
-->
This will be our next lab
-->
So this cloud journey tracker allows you
-->
To capture the current state of your cloud adoption journey
-->
So I understand that you guys are like an IT consulting services firm
-->
So you probably have customers
-->
That are going to move into the cloud
-->
Or you are getting ready in order to do that
-->
So what I would suggest you to do for this lab
-->
Is either choose your own company
-->
As an example and do this cloud adoption journey
-->
Thinking about that
-->
When we see what it provides
-->
Or think about a customer
-->
And try to match it like that
-->
So this cloud adoption journey
-->
Will give us a framework to work with that
-->
So saying that
-->
We are going to this lab too
-->
This lab too will give us
-->
We first are going to explore the assessments
-->
That are available from Microsoft
-->
And we are going to do the cloud journey tracker as well
-->
So let me share that again
-->
So we can go down
-->
I am going to do it from here
-->
So this is the slide
-->
So this will be the slide
-->
So this first one is the Microsoft assessments
-->
So here you can see the different assessments that are available
-->
For example for health care
-->
So depending on this page
-->
That you are using the cloud adoption study
-->
Or framework
-->
You can choose which assessment to do
-->
So this is a full framework
-->
But you do it for 10 pages in the process
-->
So this is really really good
-->
For up and down with the organization
-->
As the lab will start
-->
They will update the review
-->
This is five years later
-->
And this is the second
-->
This is the one that we are going to use
-->
However if you want to check any of the other ones
-->
You can just go ahead and review
-->
This is super valuable
-->
So in this case we would want to do the cloud journey tracker
-->
So this cloud journey tracker
-->
It just takes about 15 minutes
-->
There are multiple choices and multiple response
-->
And it will give you a result at the end
-->
So you can have some guidance on how to act
-->
And what steps to follow
-->
So please let me know if you are able to access this
-->
And I would recommend you to sign in
-->
Because signing in you will be able to save these results
-->
Because remember that the idea that after a while
-->
You will see this and see if you have closed the gaps
-->
That you can type in this first tracker
-->
And work with that
-->
So saying that let's have 15 minutes
-->
So we can execute the cloud journey tracker
-->
We can save this, give this a name
-->
So go ahead and give the name that you want
-->
I'm going just to give it a name here
-->
So we can have these 15 minutes
-->
Feel free to ask any questions
-->
I will try to do it by myself for the first 10 minutes
-->
And after that I will just jump in to discuss the questions that you have
-->
So please go ahead
-->
And if you have any questions regarding what we discussed
-->
I'm going to go ahead and open it up
-->
Thank you
-->
Thank you
-->
Thank you
-->
Thank you
-->
Thank you
-->
Okay, last time
-->
So this program is a way to tackle the cloud adoption in your country
-->
So it starts in Spain, then goes to France
-->
Where the adoption is going, management has to do it
-->
So the issue is to see how are you standing
-->
How would you describe your cloud journey?
-->
So if you already are settled for Azure
-->
Or if you are trying to choose different cloud providers
-->
If you already have the cloud-based machines or platform-based service workloads
-->
But not specific production workloads
-->
Or stuff that is supporting the actual operations of your business
-->
If you have workloads to play
-->
Which means that if you have production assets that are given service to your clients
-->
Well, to your clients
-->
Let's say a CRM or a website or ERP or a database
-->
Stuff like that
-->
Or if you have multiple workloads already deployed
-->
So if you think about these questions or these options
-->
It will clearly give you where are you right now
-->
If you have to also choose one of these
-->
The first one is the very beginning of the journey
-->
If you are already here, it is like an advanced stage of your journey
-->
Depending on what you would like here
-->
It will change the other options that are available
-->
I'm going to shoot the second option
-->
So let's say that I'm already sold into Azure
-->
But I'm just starting
-->
So to see how this goes
-->
What does interest you?
-->
So again, these questions depend on how you use the Google
-->
So when you are at the stage of this journey
-->
Usually what you need to know is
-->
Okay, how much does this book cost?
-->
I wish that is the hardest part to be honest
-->
Because you are talking about cloud
-->
There are so many things that you need to be aware of
-->
For example with storage
-->
You need to be aware that
-->
Okay, one thing is how much does it cost to keep a certain number of gigabytes or terabytes per month
-->
But you need to ask how much gigabytes or terabytes or whatever are you adding to that
-->
Or how much are you downloading for that
-->
Or in network, it's not how much an IP address costs per month
-->
But how much gigabytes of transfer or value are you using in-bound network
-->
Or the virtual machine or the Azure Q1X
-->
There are a lot of variables here
-->
That makes sometimes this hard to estimate with precision
-->
And usually when you face inside your own company with finance or with your customer
-->
Is that they want
-->
Okay, well I need to know how much that is
-->
And they are expecting a close number
-->
And the reality is that there is no way to give a close number
-->
So for example when you are dealing with government
-->
It's super hard because the government has a fixed budget
-->
And that fixed budget doesn't adapt easily to a viable cost expense
-->
As it works in the cloud, the operating system, the OPEX
-->
So Azure came with the idea of okay I'm going to sell subscriptions
-->
So you commit to spend 100k or 150k per year or 10k per year or whatever
-->
So what you face usually is that you have a fixed amount of credits for the year
-->
And you need to make all Azure infrastructure to fit into that budget
-->
So you don't overspend
-->
And that is hard
-->
So that is usually what happens at the end
-->
You have a fixed amount and you need to make it happen at the end of the year
-->
So this is in my experience
-->
This is the most tricky part
-->
Because the business always has to do that
-->
And they don't understand that
-->
But this varies depending on the usage
-->
There was this case, this situation
-->
Actually it was the government
-->
That they had a vulnerability in their applications
-->
And this vulnerability was exploited by a lab pack
-->
And this lab actor was able to inject a workload that started to
-->
Actually it's a super common exploit
-->
Or use of exploit
-->
They installed a mining agent to these cryptocurrencies
-->
I don't remember the coin so I don't remember
-->
But it was like a JavaScript
-->
They injected something to a JavaScript vulnerability
-->
And this agent was able to start mining cryptocurrencies
-->
Using the CPUs or the power that they had available
-->
In the services that were running these websites
-->
And the amount of money that they spent
-->
I think it was for one month or so
-->
It was like the same budget that they had for the whole year
-->
So it was crazy because
-->
They didn't have a cost monitoring set up in place
-->
So they weren't aware of what was happening until it was too late
-->
So that is stuff that you need to take into account
-->
Anyway, these are the costs
-->
The architecture, how to get ready
-->
How to get the workload, operations, fitness
-->
So you can go from there
-->
So the motivations
-->
So the motivations, so capital expenses
-->
So this is also super important regarding business
-->
Because when you have the on-premises approach
-->
Almost everything is a capital expense
-->
So your finance guy would think about
-->
Okay, we need to invest X amount of dollars
-->
Into building this data center
-->
Or into building these servers
-->
Or this infrastructure to run our applications
-->
And that is a one-time charge
-->
Which is an investment
-->
And that's it
-->
With the cloud, there is no such thing as one-time investment
-->
There is operational expense
-->
That every month it varies
-->
In theory, aligned to your revenue
-->
Aligned to your operations
-->
So because the idea here is that
-->
If your revenue is like this
-->
Your operational expenses
-->
Your variable costs are like this as well
-->
Because if you spend one dollar here
-->
You're expecting to earn or to have a revenue equal to X dollars
-->
That is like the general idea
-->
So that is OPEX
-->
So the OPEX is the research
-->
So they change the OPEX against OPEX
-->
So this is where the point is here
-->
Which is also one of the points here
-->
There are other reasons to be a company
-->
Is reaching remote markets
-->
And they need to provide service for the remote markets
-->
And the startup, for example
-->
Or be more agile
-->
Or the operations or the security
-->
I'm going to keep this part
-->
Because the finance part is usually
-->
What we as technicians or architects or engineers
-->
Used to ignore the most
-->
But it's sometimes the hardest part to solve
-->
To explain so that is why I'm going to do that
-->
So there are some more additional things
-->
Which are important
-->
For example, sometimes going into the cloud
-->
It's as a response to a critical business
-->
For example, there was a ransomware attack
-->
In your company
-->
So okay, you need to start over again
-->
Or there was a pandemic
-->
For example, two years ago
-->
So you need to move into the cloud
-->
And deploy VDIs
-->
So your workers were able to work from home
-->
For example, that is happening
-->
Or you want to change your data center
-->
You are moving out from the current data center
-->
Or your company was acquired by another company
-->
Or vice versa or emerging
-->
So that is what happens here
-->
This is one of the triggers that you should take
-->
Or there is a new project
-->
So okay, why don't we do this new project in the cloud
-->
Instead of doing it here
-->
So that is the reason that you can see
-->
So regarding this, you can see the different options
-->
So depending on this
-->
Okay, let's go to the next slide
-->
And that is the strategy one
-->
So regarding plan planning
-->
And I'm going just to
-->
I'm not going to go into deep with all of this
-->
But the ideas, I think that we have the ideas here
-->
Because this tool is something that you may want to do
-->
With your customers or with your own company
-->
Because this gives you the general process
-->
So let me go back here
-->
So I can show you
-->
So there is, when you finish this process
-->
You will have a results page
-->
So this will give you an overall result
-->
Of how are you scoring against a specific category
-->
Or a specific step
-->
And how do you need to improve
-->
If in strategy you are in a high score
-->
So if you have a material strategy
-->
Or if you need to work more in your plan
-->
Or your readiness or your governance
-->
So this is like a status of how are you done
-->
So when we are talking regarding your customers
-->
You can start with doing this first step
-->
And this will be the baseline
-->
Like the first action that you take with the customer
-->
And you say, okay, this is our baseline
-->
This is how we start
-->
And at the end of our consulting services
-->
Or providing our service
-->
We run this check again
-->
And we compare how did we improve at all
-->
And what else needs to be done
-->
So this assessment will provide you with several actions
-->
To act accordingly
-->
And that's it
-->
This is like the guidance that you can use
-->
So this is the closed-on factor
-->
Let me know please if you have any additional
-->
Or any questions available as well
-->
This can be exported, right?
-->
I mean, I want to finish this
-->
This can be exported as a CSD line
-->
That can be later be imported into another platform
-->
Into a project file or just in itself
-->
Into part of the course as well
-->
So that is the closed-on factor
-->
I mean, it takes a while to discuss
-->
And to create as well
-->
But it's like that baseline that is important
-->
Let me know guys if you have any questions
-->
If any of you finished the whole assessment
-->
And want to share the results
-->
That would be super cool as well
-->
Let me know if any of you guys have it
-->
Thank you
-->
Okay
-->
So as we have discussed in this webinar
-->
We have discussed a lot about it
-->
But there are these four items which are super important
-->
The motivations, the justification for the business
-->
The outcomes for the business that we have at the end of the process
-->
And okay, cool
-->
These are the overall results
-->
Okay, super nice, five of ten, moderate
-->
Thank you for sharing
-->
I've seen the change
-->
Oh, there is another one here
-->
And this is, yeah, I mean
-->
This is like the real life
-->
You can see if you guys are seeing what is being shared in the chat
-->
So yeah, usually that is the starting process
-->
There is a lot of stuff to work
-->
And that is data
-->
And that is where this assessment comes from
-->
Awesome, thank you
-->
And there is an item here that allows you to identify the first project as well
-->
Oh, let me see this one
-->
Okay, this is excellent
-->
Thank you for sharing
-->
So this identify that first project
-->
This is a super nice way to step into the cloud adoption journey
-->
Because it will be like a low-high-effect project
-->
So it will help you with that
-->
So this strategy is the first, is the why
-->
The answer to the question
-->
Now, the next step is the planning
-->
So this planning is to understand who in the organization should be leading the workforce
-->
What is the structure that you might apply
-->
If you are going to have something that is called the cloud center of excellence
-->
Or the center of excellence
-->
Which is a business concept that applies to a lot of different frameworks
-->
Or companies in IT
-->
Because those centers of excellence are like gatherings among key stakeholders within the company
-->
That allows you to have a full overview of what is needed in order to excel into the adoption of any technology
-->
Or any new processing system or technology that you are developing within your company
-->
So for monitoring, for cloud, for data management, for security
-->
So this is that center of excellence
-->
And also this plan will give you like a backlog of work that you will need to work on in order to advance into this
-->
So this plan includes the identification of the digital state, the alignment of the organization
-->
To identify that gap and the readiness of how ready are you
-->
And are you ready to deploy the cloud adoption plan as well
-->
Regarding this step-by-step strategy
-->
There are some examples of what needs to be covered here
-->
The strategy is not really documentation
-->
So from the executive motivation, the outcome, what you want to achieve
-->
These are examples of the strategy as well
-->
There are some stuff that needs to be done always
-->
To perform challenges, to compliance
-->
The outcomes expected by the stakeholders and that is the motivation that we already discussed
-->
And this one which is important is how to prioritize the project
-->
So which criteria you should use in order to choose this project
-->
The expectations that needs to be settled
-->
And some examples
-->
So for example, have a disaster recovery backup of a steel server
-->
Not a grid server, but a testing environment as well
-->
Now as I just told you about the plan
-->
So this is how we put that strategy in place
-->
So when we discuss the plan, the first thing is the inventory
-->
So this is the first part of any plan to know which are the digital assets
-->
That are going to be touched by this cloud adoption plan
-->
Here you will have to create a quantitative analysis and a qualitative analysis
-->
So you can see, for example, if you are planning to move your workloads as virtual machines into the cloud
-->
For sure you will need a list of all of your virtual machines, your current virtual machines
-->
Sized by memory, by hard disk drive requirements, by number of cores for these requirements
-->
By operating system, by application, by function
-->
So that is what is first
-->
Also the alignment of your organization
-->
So regarding who has the strategy of the journey to the cloud
-->
From business, from IT, in governance, in vendors
-->
So which vendor is working with and how they are included in your strategy
-->
How are you going to handle the management
-->
How are you going to align the governance
-->
So that is a part of this
-->
The readiness regarding skills
-->
Because actually I would say that in this case you are covering this step
-->
In the sense that you are getting ready for increasing your skills
-->
So this is a critical part of this process
-->
And finally the adoption plan with the 5R strategy
-->
Which is the internal strategy for moving into the cloud
-->
With the house, the factory, the architecture, the union, the place
-->
Which are the options to integrate into the cloud
-->
How to integrate infrastructure, applications, how to integrate the data and stuff
-->
So all of these are part of those plans
-->
In the most important part
-->
The issue here is to start deciding what are you going to do
-->
If you are going just to fast business
-->
Let's move the virtual machine as it is into the cloud
-->
Or if we are going to restore
-->
So move the database to a platform as a service solution for example
-->
Or if you are going to retire something that is too old
-->
And change that with something new that is already
-->
For example let's get rid of the CRM
-->
Which is too old and move to a CRM that is already in the cloud
-->
That is like an example
-->
So this is the rationalization that you need to do
-->
Applying the 5Rs into these other things
-->
What to do and what to expect
-->
So this is the incremental approach
-->
That usually there is like a subset of applications
-->
That you start moving into the cloud
-->
So that is like not going to everything at once
-->
But you start with a first project
-->
Once that is done and you have like execute all this stuff
-->
Other than that you have the adoption
-->
You move into packs of 5 or 10 applications
-->
And start repeating the cycle again
-->
So that is like the general way
-->
Regarding this community business plan
-->
So you need to close the gap
-->
So have different skills that are like basic for you
-->
That are, how do you say that?
-->
Like are common enough or are totally common in the stuff or in the team
-->
However when you move to the cloud
-->
You perhaps will need to have additional skills
-->
Not really available
-->
For example moving from the role of DBA or a statistic analyst
-->
To a data scientist
-->
So you can provide insights to the business or the information article
-->
How to move data between the different systems within your company
-->
So this is super nice
-->
In the sense that the paradigm usually is to have a file server and a database
-->
That's it
-->
But when you are into the cloud
-->
There is something new which is the messaging
-->
The messaging systems or the book subscription systems
-->
Which you share data by having like a queue system
-->
Like a training issue
-->
Polish data and your applications are stripped to that same bus
-->
In order to bring the data
-->
So there are some architectures or artifacts
-->
That appear here that usually weren't available
-->
Or weren't that commonly used in the traditional approach
-->
Yeah
-->
Also the networking data center
-->
Makes to move to the cloud or usually moves to the cloud
-->
And to the edge networking
-->
And all the DevOps team which is a huge part into the cloud
-->
So all the systems move in order to automatize all the workloads
-->
And the process that they put in previously by hand
-->
So they do it by automatic
-->
So there is a lot of use and improvement to work with that
-->
The cloud data plan
-->
Which gives you like a checklist to move on to the cloud
-->
Having the prerequisites ready
-->
The workloads prioritized
-->
The assets aligned
-->
The rationalization
-->
If we are all on board and agree on what we are going to do
-->
In grade or in grade
-->
Which iterations we are going to do
-->
And the timelines that we need in order to do that
-->
So here we are going to do our next lap
-->
Which is the creation of a cloud adoption plan generator
-->
Because in this tool what we are able is to have
-->
Let's say like a template for a cloud adoption plan
-->
That we can use and we can adapt to our needs
-->
And it's super useful
-->
And it leverages all the stuff available within Azure Azure
-->
So let me go back to the virtual machine that I showed
-->
And please let me know if you have any questions so far
-->
Do you have any questions?
-->
Are you sure?
-->
So let's see
-->
Okay
-->
So
-->
Okay
-->
So
-->
Okay
-->
So we are going to
-->
Go back to the cloud adoption plan
-->
So here we have
-->
The subscription
-->
Let's see if we can
-->
So this is the page
-->
Let me see
-->
I think it's this one
-->
Page 53
-->
So we are going to do
-->
Azure DevOps demo generator
-->
So here we are going to create
-->
A DevOps account
-->
Azure DevOps
-->
Which is a DevOps platform
-->
For all the DevOps stuff
-->
And this gets linked to your
-->
Azure account
-->
And they work like together
-->
So please go here to this URL
-->
Let me
-->
I got it here
-->
Let me show the link
-->
Hello
-->
Okay so I see that some of you are already there
-->
Okay
-->
So here if you are already in this page
-->
You will need to sign in
-->
So use the same credentials
-->
Accounting credentials for your
-->
Azure account
-->
And you will
-->
After a few seconds
-->
You will create or provision your account
-->
If you haven't have an account yet
-->
But you will
-->
Go here so what you need to do is
-->
Click on choose template
-->
Because by default it starts with this template
-->
But this is not the one that we want
-->
So we are going to choose template
-->
Please sign in
-->
So how are we doing?
-->
Any of you have any issues logging in here?
-->
Resting out this place?
-->
So if you need any help
-->
Getting into this location let me know please
-->
So here you choose a template
-->
You will find a lot of options
-->
These are super nice
-->
I highly recommend you guys to take the time
-->
To check on this
-->
Because these are super cool
-->
Really really good templates
-->
So you can work, play, learn a lot
-->
So all of these are super nice
-->
So there is one
-->
That we are going to use here
-->
For this training
-->
That is the Cloud Adoption Framework template coming
-->
So here you will find multiple templates
-->
Multiple templates
-->
For the Cloud Adoption Framework
-->
So this one, the Cloud Adoption Framework
-->
The one that we are going to use right now
-->
Before going there
-->
We will talk about the others
-->
So this is the Cloud Adoption Framework
-->
Which is our lab format
-->
But there is also this cap
-->
This full cap which is a checklist
-->
That complements to the assessment that we just did
-->
Because this covers the whole cap framework
-->
So that is it
-->
So we are starting it now
-->
We are leaving it as the bonus
-->
There is another for server integration
-->
That allows you to execute them in a great part of the strategy
-->
The web and the ready part
-->
There is this one regarding Kubernetes
-->
Which is super nice
-->
Because Kubernetes is gathering
-->
Or is getting a lot of cloud
-->
All over the world
-->
And it is being adopted more and more
-->
So this helps you to adopt formats as well
-->
SQL integration
-->
This is another hot topic
-->
A lot of companies need to get cloud-based databases
-->
And usually this creates a lot of fear
-->
And they have fear
-->
But it is okay to migrate their databases into the cloud
-->
So this helps you with that
-->
The virtual desktops
-->
Which also were a really important protagonist of the pandemic
-->
Thanks
-->
There is some stuff regarding knowledge
-->
The governance
-->
The data warehouse
-->
We pay
-->
IoT
-->
Secure
-->
So secure research
-->
Governance
-->
Analytics
-->
So in this case
-->
We are going to use the cloud adoption plan
-->
So let's just select that template
-->
And here in cloud adoption plan
-->
We are going to deploy that
-->
So this create this
-->
Create a project for this
-->
This name should be unique
-->
Across your organization
-->
So here I am going to call this
-->
Graph
-->
Plan
-->
Azure Artifact
-->
Azure Artifact here
-->
And their organization
-->
In my case I have multiple organizations
-->
In your case
-->
You have both one or multiple ones
-->
Depending on if you have ever used the Rops on that
-->
Let me know if you have any issues there
-->
Or if you have any issues
-->
So I can help you
-->
Once you have this
-->
Create the project
-->
And it will take a while to create
-->
Not much
-->
But let me know if you have any assistance please
-->
No, not really
-->
This is free
-->
And if it does
-->
It won't accept
-->
It won't even raise you one dollar
-->
Because this doesn't create a machine or anything
-->
This is free
-->
With this subscription
-->
You have access to Azure DevOps
-->
To a certain limit
-->
For free
-->
So it doesn't cost
-->
When you start using additional features for Azure DevOps
-->
Which usually is the
-->
The pipeline machines
-->
The available
-->
And when you have pipelines in Azure
-->
You need a temporary machine
-->
To build and deploy the code into Azure
-->
So those machines are the
-->
Usually these are the ones where the costs
-->
For using Azure DevOps
-->
Appears for us
-->
Usually
-->
If you are not using these getting the organization
-->
It should be free for you
-->
Okay
-->
This may be an issue
-->
Because if you just needed an organization
-->
You may have to do this
-->
Okay, yeah
-->
Please be sure of that
-->
Because I mean I have my
-->
My
-->
So
-->
So let me know
-->
Let me know if you have it or if you need assistance
-->
Okay
-->
Let me see what happens here
-->
I try to open
-->
Oh, but that is for the eShop on web
-->
Which is not
-->
This is a different template
-->
This eShop on web creates
-->
An eCommerce website
-->
It's super cool, it's nice
-->
It creates a lot of stuff
-->
But yeah, it's different
-->
No problem
-->
You can deploy the cloud template as well
-->
Just do
-->
So
-->
So you just need to
-->
Choose template
-->
And go to cloud adoption framework
-->
And use this
-->
You can just remove
-->
These projects afterwards as well
-->
Okay
-->
So by now you already
-->
Deployed
-->
You will have a project
-->
An Azure DevOps project
-->
With the name that you choose
-->
Awesome
-->
I can see that you will do this
-->
Let me see
-->
Okay
-->
Let me see your screen there
-->
So
-->
Sorry, I wasn't able to see
-->
Who talked to me
-->
So you pointed to your machine
-->
Which one is it
-->
So share your screen
-->
So we can see from there
-->
Go
-->
Okay
-->
So let me see
-->
Give me this one
-->
Okay
-->
In the notes
-->
I mean
-->
There is a column at the right
-->
With some red text on it
-->
Okay here
-->
And
-->
Okay, yeah
-->
Can you click on here
-->
Triple group
-->
Okay
-->
You know what
-->
It seems that all of you guys
-->
Are using the same organization
-->
Triple group
-->
Okay
-->
Yeah
-->
For yourself actually
-->
Yeah
-->
Or just give a different name
-->
Because perhaps someone else
-->
Had that name
-->
And that is why
-->
It's calling it
-->
Dash
-->
Jason
-->
Exactly
-->
And choose the organization
-->
Perfect
-->
I need to
-->
Yeah
-->
What is it
-->
Below
-->
Or is this here to create
-->
Your organization perhaps
-->
Go to Jason Delgado
-->
No
-->
No, no, no
-->
We're there
-->
Yeah
-->
So Jason Delgado on the
-->
Up
-->
And
-->
That
-->
Click there
-->
To see
-->
No, no
-->
We don't want to create
-->
No
-->
Just open then
-->
webassure.com
-->
In a different tab
-->
In a new tab
-->
webassure.com
-->
No
-->
They have the developer
-->
Yeah
-->
No worries
-->
The
-->
The
-->
Developer
-->
Like developer
-->
No
-->
D-E-
-->
D-E-
-->
D-E-
-->
D-E-
-->
D-E-
-->
D-E-
-->
D-E-
-->
I should
-->
Remove all of that
-->
No
-->
Remove all of that
-->
Because
-->
Okay
-->
Awesome
-->
And now
-->
You
-->
Let's wait
-->
Because probably
-->
You are not
-->
Admin
-->
No worries
-->
No worries
-->
That is the
-->
This is the idea
-->
And
-->
You can create
-->
A new
-->
Project
-->
Where is
-->
A new organization
-->
Uh-huh
-->
Uh-huh
-->
Click on there
-->
New organization
-->
And you can create
-->
Uh-huh
-->
And actually
-->
I-I really
-->
Recommend you guys
-->
To each one of you
-->
To have your
-->
Organization
-->
For
-->
Like
-->
To have
-->
For having a playground
-->
Because there is
-->
A lot of stuff
-->
That you can do
-->
That you can do
-->
With Azure DevOps
-->
And
-->
The best
-->
I mean
-->
In my opinion
-->
The best way is
-->
That you should have
-->
Uh
-->
Your own
-->
Azure account
-->
And your own DevOps
-->
Uh
-->
So you can work with it
-->
Or you can
-->
Convince
-->
Your
-->
Your boss
-->
To write
-->
A subscription
-->
For you
-->
A small subscription
-->
I mean
-->
It doesn't have to
-->
Be
-->
A huge
-->
Spence
-->
Of all
-->
So you can be
-->
Uh
-->
On top of that
-->
Subscription
-->
You can create
-->
Uh
-->
Uh
-->
Attainment
-->
A directory
-->
For your
-->
Accounting use
-->
And
-->
Working there
-->
I mean
-->
This is super flexible
-->
And it's super powerful
-->
And all the demos
-->
That are in
-->
Azure DevOps
-->
Are amazing
-->
I really do
-->
Create an organization
-->
Oh man
-->
Oh
-->
Let me see
-->
No
-->
Or
-->
We can give it a try
-->
Jason
-->
Let's give it a try
-->
Go to portal
-->
Azure as well
-->
Because they see
-->
That you have a
-->
Visual Studio
-->
Professional subscription
-->
That means
-->
That you have
-->
Your own subscription
-->
This
-->
Yeah
-->
You have your own subscription
-->
So you can have
-->
I mean
-->
What we can do
-->
Is that
-->
We can create
-->
A new
-->
Directory
-->
For you
-->
So
-->
Your own
-->
Instance
-->
Uh
-->
So
-->
Yeah
-->
You have a subscription
-->
So
-->
You are the master
-->
Of your domain
-->
There is no such
-->
Let's
-->
Let's go to the
-->
Upper corner
-->
The right one
-->
No
-->
Where
-->
Where your account
-->
Is
-->
Jason Delgado
-->
At the top
-->
Right
-->
And go to
-->
Let's view account
-->
Let's see
-->
Where did you
-->
Okay
-->
Organization
-->
Yeah
-->
Let's start
-->
Okay
-->
Okay
-->
Okay
-->
No worries
-->
Go back to the
-->
Portal Azure tab
-->
No
-->
Go to
-->
Here
-->
Uh
-->
Okay
-->
Yeah
-->
You don't have
-->
Uh
-->
Okay
-->
Okay
-->
Okay, no worries
-->
So we're going to create
-->
A new tenant
-->
So
-->
And this is
-->
Free
-->
And we can do that
-->
For sure
-->
So go back to the
-->
Top left
-->
Corner
-->
To the menu
-->
Yeah
-->
And go to
-->
Create a resource
-->
Right
-->
Yeah
-->
Create a resource
-->
No
-->
Create a resource
-->
Uh huh
-->
Uh huh
-->
And
-->
Create
-->
Entry
-->
Write down
-->
Entry
-->
Or
-->
Active directory
-->
But
-->
I can see
-->
In the
-->
Search
-->
Box
-->
You can just type
-->
Entry
-->
Right
-->
Entry
-->
Yeah
-->
No
-->
No
-->
Let's
-->
Let's search for
-->
Azure Active Directory
-->
Instead of
-->
Azure Active Directory
-->
Azure Active Directory
-->
Oh
-->
I didn't see it either
-->
Can you click on
-->
Azure Services only
-->
In the
-->
Just
-->
You need
-->
Uh huh
-->
There
-->
Actually
-->
The check is not
-->
There is a
-->
Checkbox
-->
That says
-->
Azure Services only
-->
Just behind
-->
The
-->
Actually
-->
The search box
-->
Right there
-->
Uh huh
-->
Uh huh
-->
Okay
-->
Now
-->
Oh
-->
It's not there
-->
No
-->
Okay
-->
Let's go back to
-->
Let's go back to
-->
Home
-->
And go to
-->
I can see
-->
It either
-->
Let's
-->
In the
-->
Search box
-->
Uh
-->
Look for
-->
Entry
-->
ID
-->
Type
-->
Entry
-->
ID
-->
Uh
-->
Entry
-->
Entry
-->
Entry
-->
There
-->
Uh
-->
That means
-->
Doesn't have
-->
And
-->
In
-->
As
-->
As in the
-->
But in the
-->
Top
-->
There is
-->
In the
-->
Top
-->
In the
-->
Top
-->
As
-->
There
-->
Okay
-->
Let's go back
-->
To
-->
Home
-->
And Azure
-->
Services
-->
Because
-->
We need
-->
Search for
-->
Let's
-->
Look for
-->
Create
-->
No worries
-->
No worries
-->
Entry
-->
Where you
-->
In the
-->
Menu
-->
Go back to the
-->
Menu
-->
Uh huh
-->
And create a resource
-->
In the
-->
Class
-->
And
-->
Entry
-->
Right there
-->
Entry
-->
Okay
-->
This
-->
Fine
-->
Uh huh
-->
Uh huh
-->
So
-->
This will be
-->
A new
-->
Tenant
-->
With
-->
Your subscription
-->
And
-->
Oh
-->
You don't have access
-->
Okay
-->
So
-->
So
-->
Yeah
-->
Only option then
-->
Uh huh
-->
Uh huh
-->
Uh huh
-->
Is to create
-->
A free one
-->
Uh huh
-->
Ah
-->
Well that's okay
-->
So
-->
No worries
-->
And if you guys
-->
If any of you guys
-->
Have the same issue
-->
Please
-->
This is the moment
-->
To do that
-->
Uh huh
-->
Uh huh
-->
Uh huh
-->
Uh huh
-->
Yeah
-->
No worries
-->
So in the meantime
-->
I'm going to
-->
Show you guys
-->
The
-->
What
-->
An app
-->
Is
-->
Here
-->
Yeah
-->
Let's see
-->
So, at the end of that process, what you will end up with is, you will end up with
-->
this project, this DevOps project that has, I mean, not sure if you are familiar with DevOps,
-->
but this has like four or five components, which is one of the overview. It's a wiki
-->
dashboards for knowledge management, the boards for the agrarian methodology, so you can track or follow
-->
the progress of your projects, the web host stories, so you can commit the source code
-->
and store all the source code of what you need, pipelines to automate all the process of deployment
-->
or CICD pipelines that you can create. You have also access to best plans to
-->
automate the quality assurance process of your code, and a repository for artifacts
-->
to store binaries or libraries that are required by your
-->
deployment as well. So, in this case, what this can do is to create a board with our backlogs,
-->
with our assist backlogs, that has all in place, all that is needed in place. So,
-->
well, this is supposed to be like a template that you can modify and adjust to the
-->
specific requirement that you need, but it will give you like the general idea, the general
-->
process, everything that you may need in order to make this cloud adoption plan a reality.
-->
And also, which is cool, as this is deployed in this framework and in this DevOps environment,
-->
you will have access to the full experience of the agrarian methodology using the
-->
tools provided by Microsoft. So, here you will find, let's see,
-->
you will have the ethics for this plan, which are the basics of the
-->
framework, the generation, the readiness, the plan, the strategies. So, these are four
-->
components that we are discussing today. This will be the ethics of this one.
-->
You will have the features of each one of those. So, these features is, for example,
-->
to reach the strategy, to reach the plan, to have the landing zone, to have a 10.3
-->
degree workload, to the first cost migrated, the first workload migrated. Remember the
-->
difference between workload and cost, because the workload is something that is used by your
-->
customers, by your trauma clients, and cost is just an issue that you report.
-->
So, these are like the basics, or like the first needs of the strategy. And after that,
-->
we will have the user stories. So, these are all the user
-->
stories that allow you to, or that needs to be completed in order to execute this whole plan.
-->
So, for example, the user story. So, here is where the inventory and the rationalization
-->
of those digital assets are. So, this actually points to the documentation
-->
and explaining each one of these, each one of these components that are here.
-->
And also, it may point to artifacts that will be used for the use of assets or files.
-->
So, you see where this is used. Let me go back here.
-->
And finally, the tasks which are the specific operational tasks
-->
that needs to be executed one by one in order to fulfill this plan as well.
-->
So, feel free to explore these. Let's have like five planning steps for this.
-->
So, you can explore a little bit and see how it accommodates.
-->
The only stuff that is here is a different complex.
-->
Okay, well now you've got any questions?
-->
Okay, so let's continue.
-->
Outcomes, listed folders, the alignment of the company, the readiness plan,
-->
and all the stuff that is required in order to adopt the framework and the process.
-->
Okay, so that is useful for all the process that we have done here.
-->
So, once that is done, is where you go to the ready step in which we have also different tools.
-->
And this ready step, the most important component, is the landing zone, which is like the first deployment or the dish holding or hold that we will have in order to enter into the cloud.
-->
So, this is the foundation or also called the adoption target.
-->
And this will give you like the process and the way in which the organization will adopt the cloud and how all the other deployments should look.
-->
So, this is like the footprint of how this works.
-->
So, this is where you define how are you going to manage your resources, your subscriptions, your resource views, your hierarchy, the name of the standard, the tags.
-->
And actually, what we just said here is that, for example, within your organization, you will have a subscription and a lot of stuff in there, and you have some policies, some permissions, but here is where you, for example, decide, okay, we will have a subscription for our internal IT team so they can deploy these items.
-->
And that stuff, or they will be able to have a service group, so management, so this is where you define that kind of stuff, just is a really good example for that.
-->
Also, here in this readiness step is where you design the network, which is a big important step in the sense that, okay, how are we going to reach the workloads that are deployed in the cloud?
-->
How are we going to handle the subnetting of those IT addresses?
-->
There is a firewall, there will be a VPN, there will be an expert world and other stuff.
-->
How are we going to design the storage, which kind of storage are we going to use?
-->
The compute, how are we going to go server-levels, how are we going to design our data, so all of this, as well as the identity, how to manage the resource, how are we going to handle the cost of everything?
-->
And all the items we are going to use, the groupings that are available, actually, to our own use case.
-->
So actually, this is, these components, we are going to discuss these components during these two days, because in the readiness step is just for the land and soil.
-->
However, these will be like the groupings for all the deployment of the whole cloud structure, so those are the things that we are going to discuss.
-->
So that is it.
-->
So first of all is the first project, remember that in the previous step we defined it as a first project.
-->
So there is this setup guide, pass a checklist in order to do that, and that provides you with several or a series of groupings that you can use to adapt to what is specific these days, and use those groupings as a template or a reference for your implementation,
-->
and also to use the best practices already in place.
-->
So there is this actual setup guide and the navigation guide, so this setup guide is the one that helps you organize the resources, controlling the costs, securing and managing how the organization creates that land and soil.
-->
So there is this lab, and as we do only two days, sadly we won't be able to execute all the labs, which I would love to, but the time is up, so we're going just to, let me show you what is this, so you can have an idea.
-->
I'm going to do that in the direct stop connection, so you can take a look to the next step, and let's see, this is here, this is the lab 16, so here.
-->
So this is the quick start center, so this quick start center has the, it's like a checklist, a live checklist, which each, okay, let me show it again.
-->
Okay, so this is the quick start center, so this is a checklist, like a live checklist, or a practical checklist that you can follow in order to create that land and soil by yourself.
-->
So in this first lab, you get started with the Azure portal, which is like creating an account, create a free account, you start architecting solutions, organize resources, select the Azure region for your deployment, and this is like the first lab, and later in the training,
-->
you will have this other part as well, so I'm just going to show you how this works, so this gives you like a brief explanation of what this works, what you need to do, if you want to get deep in this step,
-->
and that is like, this is the way that this checklist works, so it gives you like a guideline to work with, and there are, I mean, the most beautiful part is this, for example, in the architecture, this is even the trainings that we are going to see this workflow,
-->
because these decision trees allow you to define what to use for each one of your workloads, so how to manage the storage, so these are super useful, so we do have those in here, or you can just go there and open these images,
-->
and have a copy of those, because these, again, these decision trees are super useful for the compute design and for the storage design, so those are two parts of this process.
-->
Also, in the management of the organization, so how to manage the group, the subscriptions, everything, we are going to see this as well later, how to select the regions for your deployments,
-->
because it depends on the geographical location of the resource of your deployment and the costs as well, so a lot of stuff in there, and well, later we will see this part, but that is the general idea of these deployments.
-->
So, that's it, you can give it a try later as well, so in this step of the cloud adoption framework, the divestories are the fundamentals, they are the words, they are the identity, the storage, the database, and the post-conference as well, just so you know.
-->
Now, let me know if there is any questions, so, the next step in this framework is the assault stage, which has two sub-steps, one is to integrate, or two options, one is to integrate, and one is to emulate,
-->
and the second is to integrate the components, but in this step of, or this option of migration, what did you see, do you ever assess what do you have, what are the reasons for this migration, or this specific asset, and depending on all these factors,
-->
you define the weight of migration, if you are going just to replicate, if you are going to use the migration guide, which actually is, going back to this,
-->
so, in this case, there is another guide for that migration part, so, it helps you as well, and then, the optimization of this process, so, as this has costs involved,
-->
when you are on premises, usually, when you need more performance, what you do is to scale up, which is to just add more CPU, or more RAM to the machine, but here in the clouds, doing that may have a lot of impact on the tasks,
-->
so, you need to check that, be aware of that, so, you have the project, so, you need to pay more attention to that, so, you're going to see the project as well, so, this is where you can resize the VM, the storage,
-->
and actually, it will be surprising to be aware that, perhaps, all the 16 gigabytes of RAM that you assign to that virtual machine are not needed at all, but it works with just 8 gigabytes, so, with just 4 gigabytes, so, that is what you play with in this system,
-->
and finally, the security management of this narrated asset, so, you can do that when you, I mean, when it's already narrated, and we want the team, the corresponding team, to start operating that asset as well,
-->
now, when you innovate, the approach is quite different, because when you innovate, and this is, I insist, this is what you should do, I mean, obviously, it is way harder to integrate to the cloud and innovate at the same time,
-->
because it changes a lot what you need to do, if you just, if you just integrate, it's moving a machine from one side to another side, and that's it, and that is simple, it's hard, complex, but for me, it's simple,
-->
but when you innovate, it means that you take a deeper look into the application, into the workload, and you, I mean, mix that, or separate all the components, and leverage over the cloud is suffering in order to deploy your workload,
-->
so, the most basic example is, you have this application with a database, with a web component, and instead of having a virtual machine with both, with a MySQL and Apache in the same virtual machine, what you do is to deploy the work in an app service on the database, in an Azure SQL database, and that's it, so that is what you should innovate means,
-->
and that is the simplest use case, you can go up to keyword nets, or functions, or wherever you want to do, so, but this is the power and the value of cloud, so, here is where you need to think about what are we going to do, so, we are going to leverage on what the cloud has to offer,
-->
the global scale, and that is something that you, I mean, there is no way that a normal company gets global scale without the cloud, or without investing tens of millions of dollars, so, the global scale is like a good example of that,
-->
but each company really needs global scale, I mean, yeah, Peter, Dropbox, Netflix, for sure, but the standard company that sells only to the local market, probably doesn't need global scale, unless there is a strategic plan to reach other markets, and that is why, so, that is what you need to think about,
-->
the other part is the refactoring, and the other are the refactoring, the re-architecting, and the build processes, so, the refactoring is the example that I just gave you, so, use pass, use serverless, and that's it,
-->
the re-architect is, okay, let's change the concept, let's move into containers, our application, when we choose this option, we start leveraging on the full power of DevOps, because when you have, I mean, it doesn't make any sense to adopt containers if you don't adopt DevOps,
-->
if you don't automate the CIC deployments, I mean, you can do that, but the power of that is the combination, so, being able for your developers to commit codes, and when the code is committed, by default, it will be deployed to the development environment, so, your developers can check and work with the results,
-->
and when they are ready to deploy the QA, they commit in the QA branch, and it will get deployed to QA, where you can run automated tests, if you are in an advanced stage, or where you can check manually if the application is good enough, to move that into production, so,
-->
that is the huge power of using containers, the automation that comes with DevOps, so, this is the agility, the escalation that you may want, and this is where your company gives a big step into the cloud-native approach and innovation,
-->
and the other part is the rebuilding, in which, I mean, you discard the old code base of the application, and use, or adopt a new application, a completely new application, to do that, it's useful that you just move rate, this kind of workloads that you're going to review,
-->
but at first, you just move rate though, and they keep running in their big and traditional approach, while at the same time, you are reviewing, and there is a moment in which this will really face up, and this will be entered into production,
-->
and well, I just talked about DevOps, but DevOps is a key, actually, this is essential to all of this, and especially with architecture, because DevOps is what gives the developer the power, so, that is the company, the adoption part, and now we are going to the management part,
-->
the adoption is where the framework is an iterative process, and this is important, this is iterative, it's a self-worked out, deployed workloads, released workloads, and it depends on the technologies, and once that is done,
-->
this is where, I mean, like this is a cycle, when you are deploying into production, when the application is into production, it goes into management, so, here is where there are some stuff to define, regarding the baselines, the server level expected, the owners of these products, so, this is important, you know,
-->
and this is another tool, which I will use to ensure the immigration readiness, the immigration readiness tool is similar to the one that we just did, but it scores all the processes that you have regarding the different categories for the immigration,
-->
the company, or the customer, so, that is it, this is one of the last that we have, I think, okay, I think that we can do that, let me check the page,
-->
let me see, okay, so, this will be this one,
-->
let's see the following, let's just keep this black for now,
-->
just let me show you,
-->
so, this is the color of the framework that we have here, that we have been discussing with you, and this is the strategic immigration system, so, this is kind of the same as before,
-->
and similar to the one that we took earlier, so, I'm just going to show you, but it's the same as before,
-->
is there a business reason, so, depending on the answer that you give, that you choose here, it will change, I'm just going to randomly choose different options,
-->
but this process shows you how to process this, and we'll give you that score,
-->
so, there are the results of this assessment,
-->
so, before, you can explore this, and we will give you like actions, specific actions for each one of these aspects that you can use in order to join the focus, so, it is useful to you, so,
-->
so, in order to successfully enter this stage, you will have to fulfill some requirements,
-->
which are the strategy depending on the readiness state, and you need to understand that this is executed in a way, so, it's not like you just do one thing and after you finish that, you will start by workload, or by pack of workloads,
-->
so, this will take, this will take years, I mean, it's not like one month, or two, three months, no, this is six months, one year, or multiple years,
-->
that takes a long time to fulfill, depending obviously on the size of your company, or your customer's company,
-->
so, that is important to be aware, so, those are the iterations, and the assessment of workload, the deployment, and the release of those,
-->
there are some tools that can be used for the assessment, for data, for SQL Server,
-->
the service of migration, the Azure Data Box, which is a super cool gadget to migrate data,
-->
and you are talking about terabytes or petabytes of data, and you want to move those to the cloud, so, this is just like an external did right, that you can plug into your
-->
premises data center, copy of the data, and once it's ready, you can send these back to Azure, and they connect that to your workload,
-->
and you have the data locally, so, you can copy that, and it will save you a lot of time copying huge amounts of data,
-->
as well, and the tools that you will need when you release, for cost, for advice regarding
-->
workloads, the monitoring, and the security center, so, we are going to look into some of those.
-->
There is another lab, which is the immigration guide, that helps you to
-->
have a relationship of process, as well.
-->
I've changed my phone recently, and my account indicator app is not working.
-->
And that is a pain in the ass, you know, so, that's lovely.
-->
Gladly, I had the message and service, and I did as well. Otherwise, I will have to do this.
-->
Okay, so, this is the immigration guide. So, this immigration guide allows you to
-->
wax through all the process that needs to be done in order to execute this immigration process,
-->
and we are talking about complete database, which usually is a big part of immigration.
-->
Also, they have services, they have apps, and the immigration has data. So, this is a
-->
guide to help you go through the process. Also, the costs, so, how to estimate the cost
-->
of the immigration process, as well, and how to get to the release of workloads,
-->
to put those workloads in production should be done.
-->
So, it shows you how to get assistance to them. So, that is a big part.
-->
Okay, and finally, there is the government component, or step component, or the final
-->
is the governance of this platform. So, here, you will have like two big components. One is
-->
the policy that you will use or implement in the cloud to handle the risks for the business,
-->
the compliance, and the policies to avoid or minimize these risks, and the processes
-->
that we're going to use to monitor how these policies are being complied. So,
-->
you have to minimize it. The Azure Monitor is a tool that allows you to monitor how these
-->
policies are in place and how they are working, as well. So, that is a component of the
-->
governance in the cloud. And regarding these governance, there are five filers or disciplines
-->
that need to be taken into account, and a lot of times are
-->
not ignored, but perhaps they are not given the importance that they need to have.
-->
So, the first one is the cost management. Usually, what happens is that after the fact,
-->
the organization has to take in a close notice into the cost management. So,
-->
this doesn't need to be painful. It doesn't need to be handled since the beginning.
-->
So, here are some tools that help you. The blue pins, which are examples of how our workload
-->
should be deployed in Azure. So, the policies, the cost management, the advisor. So,
-->
those tools help you to handle the cost management. And also, the other is the
-->
baseline. So, how to comply with every security requirement. So, the blue pins. So,
-->
blue pins allows you to do that with both the policy, the security center, and the sentinel,
-->
which allows you to monitor what is happening in that regard. The consistency of your
-->
resources. So, you have, for example, is something that you may think is silly,
-->
but at the end, it's important over time, which is, for example, the naming conventions
-->
for the workloads, the tagging of those workloads. So, that is important as well.
-->
The baseline regarding identity. So, how are you going to handle the role-based access controls
-->
with your active directory? So, the identities, the rules, the permissions, all that stuff.
-->
And the process to accelerate deployments or to simplify the deployments using templates,
-->
which is highly related to all the infrastructure as a code paradigm that we are using now.
-->
So, here comes the blue pins, which at the end are those, are infrastructure as a code
-->
examples or templates. And all this stuff regarding how to group resources and tag
-->
resources, the templates that are available, and the advisor as well, with some other tools.
-->
There are some considerations that needs to be, or that need to be addressed in order to
-->
handle this and the way that the management of your organization needs to be set up.
-->
So, the business unit, the geographic locations of the company, the environments as a field
-->
level, and after that, the subscriptions. So, usually what happens is that there is
-->
like the business unit and the subscription. And that way happens when we just witness it,
-->
that we don't have enough flexibility to work with our resources or that we cannot
-->
expand for that subscription because that is the subscription for our production systems
-->
and other stuff. So, the way to address those issues and to not have those limitations that
-->
explains what you can do is to establish how the organization will be mapped into
-->
an Azure cloud. So, this is like the standard way to do this. If you don't have multiple
-->
locations, what you just do is handle environments or, which is the best practice,
-->
just leave one geography, which is the headquarters geography, because in the future,
-->
in five years, in two years, in ten years, if you don't know, perhaps there is a new
-->
location or they are part of the world. So, if you design it this well, you will be able
-->
to do it without too much effort. If you don't, you will be missed. So, that is why
-->
this is important. So, in this case, you will have multiple subscriptions. So, for the
-->
critical, which no one can even think about using this for anything not related to the
-->
core applications of your business. So, I'm suggesting for the data and other production
-->
stuff and non-production stuff. So, this is, if you take a look, you will see that
-->
you will have three to four different subscriptions within your Azure account.
-->
Again, this is not commonly seen because we used to just assign the subscription to
-->
business units and that's it. But the best practice is to do this granularity. So,
-->
you can work with this in a more flexible way. But this is just an example. There is
-->
different ways to do this handling of subscriptions per application. Well, actually,
-->
it's not here, but a fairly common approach is to use subscriptions per
-->
cost center within the organization. So, the cost center will have a subscription for
-->
all the workloads. So, that is a common approach as well. And the resource groups,
-->
usually those are per application. So, you have a resource group for a specific
-->
application without which of that application needs as well. There is this tool,
-->
the workshop for readiness at government. Remember the previous one that we just
-->
discussed. But this is a workshop that has two sessions, two big sessions, one for
-->
governance, and it's the accelerator and the benchmarks that allow you to work with
-->
this stuff. And the final outcome of this will be like the complete overview
-->
of the architectural guidelines for the lightning zone in this case,
-->
and the governance for the account as well. So, there is this another lab for the benchmark
-->
of the governance within your company. It's the same as before. We are going just to
-->
show you how it is, but it's the same as before. So, what do you want to check?
-->
So, I'll ask this one. It depends on the responses that you are giving here.
-->
So, just for the cleanup. And at the end of the process, we will
-->
resolve the sample, which is exactly like the one that we did before,
-->
that we can start and act upon as well. So, that is the process.
-->
So, once you have executed your migration race, you will have the subsection to
-->
work out those rules to the governance and operations team. So, that is well
-->
managed, and these guys doesn't have to work with other communities that are
-->
here. That is something also that is usually not clearly stated, and the migration list
-->
track, because the team that was migrating suddenly is in charge as well of handling
-->
and operating the workloads. So, they can do both. So, the best practice is to have a team
-->
here and a different team here. So, that is the way to go. So, that is important to notice.
-->
So, just finishing this part. So, this here is where you define all the policies that allows
-->
you to have a consistency across all the adoption process, and all the key components
-->
that allows you to make this happen across the security, the consistency of the resources,
-->
the identity, and the deployment process as well. And also, this way, you can have
-->
the responsibilities separated, so you can have a natural under of each one of the processes
-->
that we are running as well. And just finally, once that governance is in place, the
-->
management of operations is stopped. So, the management, the monitoring, the resiliency into
-->
this platform is where this belongs. So, here is the workshop of this adoption management process.
-->
So, all the overview of the migration, and wakes, and all the stuff, the methodology,
-->
the solutions, who should be there, the tools that we can use, and the operations team,
-->
how this is going to be managed, how the workloads are going to be optimized.
-->
And please notice that here we can start seeing the well-architected framework,
-->
the web, which is the technical part of this, what we are discussing here. So, that workshop
-->
part there. Obviously, there is something additionally that actually is part of the
-->
framework as well. And this is the security component as well. But we are going to
-->
discuss this in the well-architected framework. So, just let me finish this first
-->
with the success story, which is an example of applying this stuff into a real company.
-->
So, this is a multinational company of media and digital market communications. So, this company
-->
and they work with Microsoft Barnett to integrate about 300 applications from four
-->
data centers into Azure. So, they have these goals for how to or what they wanted to reach
-->
with this integration. What was the strategy that they used? What was the business strategy?
-->
And what was the technical strategy? So, here you can take a look into one of the drivers,
-->
the exit of those level data centers, centralized IP, and the main tech debt, which is
-->
a joke because in the real life, no one eliminates all the technical debt they have.
-->
And the enablers to do this, the rapid integration of the model, the landing
-->
zones automated, the governance, the contact situations. So, these were the drivers.
-->
And how they use the cap. So, the strategy that they use, how they use it, the plan
-->
that they created with all the components, the readiness part with the KPIs, for example,
-->
defined it, and the integration at scale. So, they created like an integration factory
-->
to integrate the workloads to the cloud. And finally, they govern and manage components of
-->
the process as well. So, applying this framework allows them to move in one geo.
-->
They were able to integrate 300 applications. They were able to choose four data centers.
-->
They use an agile integration process. They required 20% of their application. And they
-->
saved 30% of total cost ownership in the first gear, which is what they achieved at the end.
-->
So, that is like an example of the cap framework. And what we are going to do now is
-->
we are going to have our lunch break. And when we get back, we are going to start with the
-->
world architect framework to see from the technical side how this world architect framework
-->
applies and in which steps it applies as well. So, let me get guys know if you have any
-->
questions at all at this point, as well as if there is something additional that you may want
-->
to share. Otherwise, we can go to our lunch break. I will tell you that let's have, I mean,
-->
let's see. Right now, you should have like 1.17 in the afternoon, right?
-->
Okay. So, if you are okay, we can meet at 2 p.m.
-->
your time. So, in about 153 minutes, something like that. Okay. Awesome, awesome guys.
-->
Let me know also if you have any questions or something. Okay, cool. Okay, okay, cool.
-->
Okay, guys. So, see you at 2 p.m. Thank you.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
All right.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
Okay.
-->
So, yeah, it's really good.
-->
So, okay, let's go into
-->
the well-architected framework as well.
-->
This is the other
-->
framework that we have available. So,
-->
whereas the first framework gives you, like,
-->
the way
-->
you should cover your adoption,
-->
your cloud journey, the well-architected framework helps
-->
you to secure
-->
and to assess how
-->
the main well-architected
-->
cloud is. So, if you're following the best practices,
-->
if you are taking into account all the requirements, if you
-->
are having, like, a good practice in the
-->
cloud journey. So, this framework
-->
leverages on five
-->
pillars, which are like the basics of the
-->
Azure on the cloud adoption.
-->
And these basics, all these pillars,
-->
are the essence of any good
-->
cloud effort in any organization. So,
-->
the first pillar is the reliability. So, it's
-->
the how good your design
-->
and your production
-->
workloads in Azure, in the cloud, are able to recover
-->
from any failure and being able to function.
-->
So, if you cover
-->
this pillar, you will have high availability
-->
no matter where you work.
-->
Security, this pillar, is basically how to
-->
keep the applications data secure.
-->
This is one of the weakest points in any
-->
adoption. I think that you have
-->
here about how many data links
-->
have happened all over the years, because
-->
usually you see more about Amazon
-->
with S3. So, the most
-->
common issue out there is that the S3
-->
bucket gets exposed publicly
-->
to the internet, and sensitive
-->
information is available there, and there
-->
is a leak of data that has happened
-->
a lot of times. Another common issue here with
-->
security is with Kubernetes, that the
-->
control plane is exposed, publicly exposed, and
-->
it gets hacked or unavailability is
-->
exploited from there. So, that is also super
-->
common. So, this is really important, and it
-->
can be disregarded.
-->
The other pillar is the cost optimization.
-->
So, this is what I explained to you at the beginning,
-->
is how to
-->
deliver the trust of the cloud
-->
with all this finance, and all the
-->
stuff that we discussed previously, within our budget,
-->
using control of how much
-->
you need to spend. So,
-->
keep that control. So, that is the cost optimization
-->
pillar, which is super important because of that.
-->
Also, there is the operational excellence
-->
pillar, which is how to manage
-->
the operations, so your system is running
-->
production as expected. So, if it's a file, or if it's
-->
a place, it can recover, or it can have the
-->
availability provided by the cloud.
-->
And finally, the performance efficiency.
-->
So, how do you
-->
websites, how do you database this, how do
-->
your systems, your applications, are able to
-->
escape when there is changes in loads,
-->
or actually how that can
-->
reduce the footprint when there is not
-->
enough load, so you can manage the costs. So, these findings
-->
are what makes the work expected.
-->
The basics of cloud
-->
implementation, because this way you will be
-->
covering all of this, you will be having
-->
a full control, and you will realize
-->
all the value of the cloud.
-->
Okay, so, in order to
-->
do this, or to apply this, well,
-->
there are some
-->
requirements. One is
-->
what we call the functional requirements, in the sense, what is the
-->
application should be in regards to the business,
-->
in regards to both functions of the project.
-->
And the other are the architecture characteristics
-->
of the application. So, these are basically
-->
how the designing of the application, how
-->
we operate the application. So, it can add
-->
the best performance, the best
-->
availability, the best resourceful
-->
process available.
-->
So, following these principles
-->
is how to avoid this kind of things, because this is
-->
the same example, and actually this is from about
-->
over ten years ago, 1991,
-->
because all of these
-->
are like small look homes
-->
that are at different levels
-->
within an organization that creates
-->
something that either a security incident,
-->
or that a loss issue
-->
within any domain. And those
-->
are like examples of what may affect
-->
or why bad things happen to the platform, to the
-->
systems. So, actually this was kind of
-->
before the cloud was happening,
-->
but now this shows
-->
how this is so relevant in today's world.
-->
So, for example, at the distribution level.
-->
So, when there are no complete procedures, that is a home
-->
that when it's exploited, it fails,
-->
or it mostly fails. When there is some issue with
-->
regulations, when there are mixed messages
-->
to follow and not to follow a procedure or a regulation,
-->
then there is this speed.
-->
When there is production issue,
-->
I mean, everyone wants to go live right now,
-->
and nobody wants to go live, and there is
-->
a big expose happening, because
-->
we tend to oversee critical issues
-->
because of pressure, so that is usual.
-->
Also, in pointing, oh no, the developers
-->
were the ones that had
-->
the responsibility of checking
-->
the code was secure or not, and the developer
-->
says no, it was the operation, they were supposed to check
-->
the application for security issues.
-->
Either way, another hole was exploited.
-->
Or the other issue is no, we were never trained
-->
for this kind of stuff, we didn't know that we had to do
-->
any quality assurance, or we didn't know how to do that, or we thought that
-->
what we were doing wasn't up, so another hole, so that is
-->
a good one. It may happen,
-->
I'm sorry for the word, but it should happen, so
-->
I made a mistake, and
-->
I will say that one of the most famous
-->
mistakes ever committed in the world,
-->
in the IT world, was like, I think two, three
-->
years ago, we
-->
did that, or good luck, I don't remember right now,
-->
but they erased the production,
-->
I think it was good luck, they erased
-->
by accident the production
-->
database, so everything,
-->
everything that was committed, every project,
-->
everything was lost because it was the production that
-->
was, it was a mistake of the
-->
operator in which he had to, he was
-->
I don't remember if he was doing a backup or something, and
-->
he removed the backup because he needed the space for another backup,
-->
what he needed was to remove the production database.
-->
So I bring this space to the table
-->
because it was super well documented,
-->
everything that happened and everything of how they recovered
-->
from that issue, it took them
-->
no more than three days, but it was kind of
-->
longer than one day to recover from this issue, and it was
-->
also possible
-->
because they confused the terminal,
-->
so, but it was beautiful, the
-->
block was super beautiful because it shows all the
-->
procedures that they have taken in place in order to recover
-->
from a failure of this level, so that is important.
-->
And finally, finally, is the
-->
technical part, can you
-->
have such a melody that is not too loud, or that is
-->
too loud, or there is a lot of dissonance, or because
-->
you didn't do the right thing, and you took too long
-->
through it, and all of this stuff is what
-->
happens. So,
-->
the idea of having a framework here, a well
-->
articulated framework here, is to avoid
-->
that kind of stuff. So on the
-->
top, or on the shoulders, or on the calf,
-->
we use the well articulated framework
-->
in order to be there.
-->
So it depends on
-->
who is the one that is working here, so
-->
on the IT, or up to the founder of the system
-->
workloads, they apply and do this stuff.
-->
The well articulated framework is mostly
-->
the adopt and manage components of the calf, because
-->
those will be actually be the actual
-->
workloads as well. So this is just
-->
some guidance to improve the quality of the
-->
workload, the type I told you about, which are here.
-->
So this is also
-->
a continuous process of reviewing, and we
-->
have a review of the well articulated
-->
process that you can do with our system, and actually there is
-->
a tool that allows you to do this analysis
-->
by applying design principles, if you want
-->
to help yourself with the final or
-->
external provider to support your workflows.
-->
You may want to use reference architectures available
-->
in Azure to apply to your own
-->
systems, their documentation, which is super important.
-->
In the previous gap, we saw that
-->
there is a lot of documentation, and there is this tool that actually
-->
allows you to help yourself against any
-->
gaps that you may have.
-->
So there are some best practices to
-->
improve the quality of the workload. So in post organization,
-->
all the management of forecasting and stuff that is available
-->
in Azure, you can establish counter costs,
-->
you can handle hybrid solutions
-->
in Azure. One is that it's super common
-->
in order to make the cost
-->
creditable in the reservation of instances, instead of
-->
going, you know,
-->
instead of adopting the pay as you go model,
-->
you just pay what you have spent,
-->
you don't commit to have an instance
-->
for two years or a year, and that way
-->
you will always pay
-->
at least the same base cost.
-->
If there is
-->
an increase of use above what you have
-->
spent, you have to pay more back. This is a certain cost
-->
option, allows you to make some creditable
-->
commitments of course, and also
-->
savings, I mean savings
-->
can be up to 50% or even more
-->
in the cost of compared with previous
-->
works. They shut down
-->
and you can configure to shut down the
-->
machines in a specific
-->
schedule, so perhaps the
-->
developer environment doesn't need to be
-->
running 24-7, so
-->
you just have to do that. Or there is sizing
-->
that I mentioned previously, so
-->
you will be surprised that it turns out that you don't need
-->
those 16 weeks of time or whatever, or just moving to
-->
the past.
-->
So those are the first practices
-->
for each one of these programs.
-->
My personal experience is DevOps, and DevOps is the
-->
key here, because that is the way that you
-->
make this
-->
to be a clean
-->
process.
-->
This is what DevOps allows. The
-->
efficiency, the performance is the scalability.
-->
You are able to design for scalability, so start from the minimum
-->
required, and you are able to scale to
-->
support more workloads and other units.
-->
And reliability, you are able to
-->
support and pay you. And here there is something
-->
interesting, which is the
-->
guidance of the best practice of testing what will happen
-->
if there is an issue with moving to another region
-->
and stuff like that. So actually there is a whole
-->
new discipline, which is called the
-->
chaos engineering, which you
-->
in a colloquial way, you unplug
-->
one system randomly and see what happens.
-->
So if everything fails, or
-->
we are able to recover, or work, so this is
-->
actually something that is getting some traction
-->
in complex deployments.
-->
But it allows you to
-->
have a sense of reliability and the ability to work on that.
-->
And finally, the security part, which mostly is all the
-->
identity, all the policies, but also the application security
-->
and that encryption and all this stuff.
-->
Obviously in order to do this
-->
here is where the issue
-->
happens with the companies. You have the money
-->
the budget
-->
constant right.
-->
This is one of the biggest pieces of requirements
-->
and this will affect any decision of
-->
the architect. So for example, the cost
-->
of developing workloads,
-->
how to handle the costs, so it doesn't.
-->
In principle, this doesn't affect the business outcome
-->
and timing of these environments in the night.
-->
Because in theory,
-->
developers should not work during the night, but you know
-->
that other developers perhaps have some different
-->
strategy than normal guys. But anyway,
-->
that is a good example. But for example, in
-->
case you want to look at the performance
-->
or the availability or the reliance of this
-->
workload, the cost will increase no matter what.
-->
As well as the security
-->
and
-->
the security of the
-->
workload is probably also a huge expense.
-->
So it's important
-->
to be aware of that. And this is a message
-->
that needs to reach the higher levels of the organization.
-->
So if they want to have
-->
our systems, our workloads,
-->
security proof or hackers proof, they need to invest
-->
in Google Trust.
-->
So this is why
-->
the well-architected framework is a shared responsibility.
-->
It's not only from the
-->
technical level, but also from the business level,
-->
or the customer level as well. So anything that needs
-->
to be covered here
-->
should involve all of the other way.
-->
The process
-->
to apply for the well-architected framework is that
-->
you have four stages. The first one is a discovery
-->
stage in which you basically
-->
learn what you have deployed. And remember that
-->
this well-architected framework is when you already have
-->
stuff deployed in the cloud in Azure.
-->
So you discover what you have, you analyze
-->
everything, and once you analyze
-->
you prioritize your findings, you
-->
apply those in order to, and then
-->
based on the five items, you can
-->
apply each one of the findings of your analyze
-->
discovery analyze process, so you can fix or optimize
-->
the well-architected framework.
-->
So these review and review steps are the basics
-->
of the well-architected process.
-->
So the three outcomes of this is
-->
any risk that
-->
may apply to the design and implementation of an application.
-->
What needs to be actionable and prior
-->
to design
-->
before anything else in order to
-->
fix the framework,
-->
summarize all the findings for
-->
each one of the applications, and have a guide
-->
to solve all the issues.
-->
So the first step is the discovery.
-->
So there is an online questionnaire, similar to the
-->
ones that we have seen so far, that we can use
-->
in order to understand how and which
-->
maturity level is an organization or the customer.
-->
So that way we can see how that works.
-->
Also, have a profiling of the workloads,
-->
so how the application is
-->
whether it's an access by customers or internal application
-->
or whatever it is. See the
-->
architecture diagram of what the customer has.
-->
It is surprising, but it's just too
-->
common to see deployments in the cloud
-->
without a proper architecture diagram.
-->
The question is that
-->
there was no formal
-->
planning process or formal design process
-->
to move into the carousel. This is
-->
a red flag that means we have
-->
to address it as soon as possible, and see all the other sources that are available.
-->
This architecture
-->
diagram allows you to XML the work
-->
that you have under the light of the five
-->
guidelines of Azure, and gives you the guidelines
-->
that helps you to focus on what you need to do.
-->
The other step in the process is the architecture diagram.
-->
So one of these that will show you what is
-->
done, and also
-->
between the customer or the
-->
other responsibility is to be able to explain
-->
why they need a red section here
-->
or a function here or a
-->
here. So it should be like
-->
an explanation of one of these components in this architecture.
-->
This is what shows why this is
-->
done like that. So let's do
-->
a quick
-->
lap, and we are going to explore
-->
the Azure Items library.
-->
And I see some of the
-->
architecture diagrams available, so we can work with those
-->
in a later lap.
-->
So let me
-->
show my screen.
-->
Oh, okay.
-->
Okay.
-->
So
-->
what we are going to
-->
do first is
-->
fill in the
-->
materials folder, you should have
-->
a file that is called the Azure Public
-->
Service Items.
-->
So let me show you
-->
where this file is available.
-->
And this comes from
-->
my architecture directory.
-->
Okay.
-->
This is part of the
-->
library.
-->
Okay.
-->
I love the
-->
links.
-->
I'm going to look
-->
for it,
-->
to search it, and then I'll send it
-->
to you.
-->
But this is
-->
this set of files,
-->
because they are updated
-->
every other time. So these are
-->
the items, let's open them.
-->
Okay. So if you will
-->
double click on the zip file, it will create a folder.
-->
And in this folder, you will have access to all the items.
-->
So there are some of the items in there, and these five terms.
-->
What you can see for all of the
-->
different components that are available,
-->
all of the items that you can see.
-->
So for analogy,
-->
for example, containers,
-->
or computers,
-->
all the computer stuff,
-->
all the management, governance,
-->
everything is
-->
related to what
-->
we have discussed so far.
-->
So the idea is that
-->
whenever you do
-->
design an architecture for a solution
-->
in Azure, you can collaboration these
-->
items in order to
-->
describe what you
-->
are thinking and what you want to make a reality
-->
in the system. So all of those
-->
items are available in there. You can use them
-->
in any application of your choice, but
-->
I personally use
-->
this raw idea, which is available
-->
here, let me show you.
-->
It's open source, so you can use it.
-->
It's actually the URL now is
-->
appdiamonds.net
-->
instead of draw via.
-->
So it is a web application,
-->
but it has an installer
-->
so you can use it locally.
-->
And then it takes these values here.
-->
So by default,
-->
this already has some Azure
-->
items. So let's open
-->
this application.
-->
And here in this
-->
column, you can
-->
open that. And here you will find
-->
somewhere here,
-->
you will find
-->
Azure.
-->
So this is
-->
that set of items that I just
-->
showed you.
-->
It works updated from time to time,
-->
but sometimes if it's not the last version, you can just
-->
import the file that I
-->
showed you. Or if you are using any other application
-->
for designing this or using this
-->
you can use that. So in this case, you are going to use
-->
the Azure shapes, so you have them
-->
available here. So this way you have
-->
all the components from Azure.
-->
So you can have
-->
this one. So I'm going to just create a new file
-->
here. And for example,
-->
which
-->
let's see,
-->
so here are the icons of some
-->
of the components.
-->
So
-->
if you take a look into this example
-->
here, you can see
-->
an example architecture
-->
where users
-->
have an extra role of balance
-->
so you can see how it works.
-->
So you can create here
-->
what you are going to use.
-->
Also, there is another way
-->
here. So you can create
-->
and let's see.
-->
So here
-->
a new diagram in the cloud. Also
-->
you have nine examples of
-->
Azure architectures. So you can
-->
and actually I encourage you to do that.
-->
To open all the nine architectures so you can see
-->
different examples of architectures
-->
to see what are they.
-->
I'm not sure of what is on the specific item.
-->
You can see
-->
how to
-->
create
-->
or
-->
or
-->
I didn't see it.
-->
Or edit properties then.
-->
Oh yeah.
-->
With right button, edit properties.
-->
You can see what
-->
what object is this.
-->
So you can see
-->
how this works.
-->
So please do that. Explore all the different architectures.
-->
So you can see or try to add some objects
-->
just to get familiar
-->
with this stuff.
-->
Take a few minutes to do that.
-->
Okay.
-->
Cool.
-->
Ding.
-->
Okay.
-->
Okay.
-->
So we are going to try to do at least one of the signs that we need to do to create
-->
it here.
-->
So let me go back to the blue lights.
-->
Let me show you the visual studio capabilities.
-->
Let me show you really really quick so you have an idea.
-->
Because we do visual studio, we do visual studio.
-->
You can have this tool embedded so it will be useful.
-->
And it will be useful mostly for example when you have infrastructure as a code.
-->
When you have stuff like Terraform OSP or stuff like that, you can kind of link what
-->
you are going to deploy and what you have in the infrastructure as a code application.
-->
So in order to do that, we would need to have visual studio code based on IE 3D integration.
-->
So there are some various integrations, but this is the most popular one.
-->
It's already installed in the environment, but if you want to do that, you can do visual studio in the website.
-->
So this has almost 2 million downloads and it's qualified as 5.
-->
So it's a really good experience.
-->
So this shows you what you can do with this.
-->
So you can configure this stuff.
-->
And the nice thing is that you can work with your team doing this.
-->
So you can pass the diagram around when you are working with the team.
-->
And what I was telling you about is that you can bring this to code, to actual code.
-->
So it's interesting to use in that regard.
-->
So just like an example, what I'm going to do is to open one of those diagrams.
-->
So here we will just show up the diagram as if we were doing the same work.
-->
So this is the IE, but this is interesting.
-->
So reading the IE documentation, you can see how everything can be worked out together.
-->
So that is something I'm looking to have for you visual studio code experience.
-->
Carrying in the icons outside the desktop.
-->
Yes, for sure.
-->
So you cannot type inside the desktop.
-->
Try to reload the desktop.
-->
But yeah, you can have the icons in the end of the page.
-->
Try to reload the files you have in the box.
-->
Sometimes it gets locked by the extension of some code.
-->
Okay.
-->
So going here to do this.
-->
The first one was the discovery for architecture diagram.
-->
So this is one of the stuff that you can see here.
-->
The other is the actual work flow.
-->
So let's see which are the actual resources that are available within the subscription
-->
order of the actual protocol of the casino.
-->
Check every one of the resources that are available within the government and support the resources that have been applied.
-->
Also,
-->
here.
-->
So use our showing up in this system.
-->
That's the idea.
-->
There are some things that allow you to do this.
-->
There are for advisor, this dashboard, which is an integration between Power BI and Azure.
-->
So I'm going to show you this one.
-->
The repository and what kind of dashboard it presents.
-->
And there are some external tools.
-->
As part of this.
-->
And I said,
-->
I'm going to show you a little bit.
-->
Moving the distance to perhaps the most important one is the Azure advisor.
-->
The Azure advisor is already there.
-->
And it is.
-->
So it helps you optimize the workloads.
-->
And it's one place.
-->
So.
-->
So.
-->
So.
-->
So.
-->
So.
-->
So.
-->
This works.
-->
It monitors the workloads.
-->
And your services maps the workloads to services.
-->
And it gives you the right assignments to use those.
-->
Perhaps you have a workload that can be improved by using everything as a service or whatever.
-->
So it shows you that kind of stuff.
-->
The CCO boards.
-->
So this is the Cloud Optimization Power BI dashboard.
-->
So these are already done.
-->
And we are able to show you the information regarding each one of the.
-->
Well, at least three main information about the platforms.
-->
So the first dashboard is the Azure Interceptor dashboard.
-->
So this will give you all the information regarding the identity,
-->
the robots access control, the security of the resources,
-->
the network information, the compute information, any results, any subscription quota, any needs.
-->
So the dashboard looks like this.
-->
It's actually like this.
-->
We just need to.
-->
And this requires a Power BI license.
-->
So we cannot do it like this.
-->
But I'm going to show you.
-->
So you can see where it is.
-->
So what the only thing that we need to do is to import the dashboard.
-->
And then the Power BI to Azure so you can extract the information and have the network.
-->
So this is incredibly valuable.
-->
And sometimes it's just given and no one knows about it.
-->
So it's just a missed opportunity for the customers.
-->
The other dashboard is the governance dashboard.
-->
So this governance dashboard shows you the groups, the management groups, the subscriptions,
-->
the policies, the things, the resources that are available within the subscriptions or the current.
-->
So you can see what we discussed previously.
-->
Usually, as I told you, this is literally just a group and a subscription.
-->
Because that is the most common way of employment.
-->
Which, again, is not the recommendation.
-->
You should have like a structure so you can do well all the time.
-->
And have multiple subscriptions.
-->
So this governance dashboard is a must-have.
-->
So you can show in an easier way to the management and to the customers what they have.
-->
Also, there is this infrastructure dashboard with Kubernetes.
-->
So it has the information of the infrastructure.
-->
But it also shows you Kubernetes information.
-->
And that is because Kubernetes usually is one of the high-level resources within Azure.
-->
So it allows you to control these data.
-->
And actually, we are seeing the advice and recommendations for each one of the services as well.
-->
How this works.
-->
There is this web form.
-->
So we have this GitHub web form.
-->
And we can clone and get a copy of these templates.
-->
And these dashboard templates.
-->
You need the Azure interventions.
-->
You need access to the subscriptions.
-->
You need to do access to some endpoints.
-->
So the power goal can accept the data.
-->
And which resources are used for certain data.
-->
All of the ones that are listed here.
-->
And then all of the information will be available to the dashboard.
-->
This is the lab.
-->
It requires our BI license.
-->
Because it needs the desktop application.
-->
It also needs a Windows machine to do this.
-->
But let me show you here.
-->
So this first infrastructure dashboard.
-->
It explains how this works.
-->
It explains how this works.
-->
And there is this deployment guide.
-->
So these are all the downloads.
-->
So it has the deployment guide.
-->
So in the deployment guide, it explains step by step what needs to be done.
-->
In order to have the dashboard deployed.
-->
And to power the environment.
-->
So it's not really complex to do that.
-->
The only thing is that you need the license and the desktop.
-->
So if you have it, go for it.
-->
It's absolutely worth it.
-->
So here is the process.
-->
The link is in the slideshow.
-->
The same with the government dashboard.
-->
The deployment process.
-->
All is done.
-->
All needs to be done. All the stuff.
-->
And the reports for everything.
-->
So what reports can you get?
-->
For each one there are reports.
-->
In this case we are showing the government one.
-->
So this is for management bureau. Some subscription.
-->
This is for tax and loan funders.
-->
The regulatory funders.
-->
The security and compliance. The policies.
-->
So this is
-->
ADO.
-->
This is a new one.
-->
This one shows all the information
-->
regarding Azure DevOps.
-->
So if you are already using Azure DevOps, this also will be super useful.
-->
Because we will show you
-->
a status of the DevOps
-->
of course in the organization.
-->
So we show the contributors,
-->
the projects, how many requests are available,
-->
projects, requirements.
-->
There is another one for GitHub.
-->
That is like the same for DevOps.
-->
Remember that Microsoft bought
-->
GitHub. So GitHub and Azure DevOps
-->
kind of collide.
-->
So I'm not sure what is going to happen.
-->
We are going to keep both or just merge them in one.
-->
Because Azure DevOps has the stuff that GitHub doesn't have.
-->
So it's
-->
So either way, this is the
-->
dashboard that are available in there as well.
-->
So this is super useful to have a view of
-->
your system beyond the portal
-->
Azure. Because the portal Azure is more like
-->
operations oriented. And this kind of stuff is more
-->
management and executive level.
-->
So that is why this is actually important.
-->
So the other step in the
-->
work-participation work is to analyze a step
-->
and apply all the information that we have gathered so far.
-->
For example with those words. And we analyze
-->
all that stuff and decide on how to
-->
or what needs to be done if there is no monitoring
-->
in place, if there is no backup practices,
-->
if there is no access control. So that is what needs
-->
to be identified in order to understand
-->
what is happening. Also the cost optimization.
-->
So how to keep control to
-->
the costs. So in this case there are
-->
different levels in order to do this. One is to have
-->
the price recommendations in place to manage the cost
-->
of it. The other is to size and
-->
to define the size and transport the services that we are using.
-->
To see if what you have assigned
-->
is really what is needed or if you can down price
-->
without using performance. So that is important.
-->
The shutdown, the scaling and stuff.
-->
This spot also is useful for certain workloads
-->
because the spot is super cheap but it doesn't
-->
guarantee availability of the resource so it can be used
-->
for development environments but doesn't need to be
-->
always available.
-->
And the reservations that I was talking about
-->
another level of optimization is
-->
within the work is to identify any
-->
new resources
-->
to different levels.
-->
The way of using, the product traffic,
-->
the management of these brands.
-->
Any change in your architecture that helps you to
-->
reduce costs that is also available.
-->
So there are some different reservations.
-->
This one I've picked two. So you can look to one or two
-->
work plans. So that is probably the best way to
-->
reduce the cost over the long term.
-->
And the other pilot that I have here is
-->
how is it for the business to have
-->
a system, a solution, a workload always
-->
up. So that is what we need to know here.
-->
What is the service level target?
-->
So we will have to know what needs to be
-->
put in place for the application. So if you only need 99 percent
-->
you should be aware that that means one and a half
-->
hour of downtime per week or three days per year.
-->
Or if a customer asks you for
-->
five lines that means that in a week
-->
you can go down six seconds or five
-->
minutes in a year. So sometimes
-->
this is not something that people have in mind
-->
or customers have in mind. You will see
-->
that you will see customers asking you to write
-->
99, 99 percent of service level
-->
blah, blah, blah. Otherwise I will discount from your
-->
invoice 10 percent or whatever.
-->
But in order to reach that
-->
you want to only have 15 minutes per year in downtime.
-->
This will have final availability,
-->
multiple regions, replication, a lot of
-->
that costs a lot. So this needs to be
-->
proper information in order to be able to
-->
do. And sometimes people is not aware of that. So
-->
this is an example of how to calculate that so you can know
-->
how this works as well.
-->
In order to reach this availability target
-->
so it's important to know the architecture
-->
to identify single points
-->
of radius to calculate the SOAs.
-->
So depending on how the application is
-->
you will have several
-->
visual or not. So in this example you have a
-->
web application with one escalated race
-->
so you see these frames, every single phase.
-->
And in this second phase you have the same web application
-->
but with two escalated race so if one of these
-->
frames you still have the other one. So
-->
in the first case you have a 99
-->
so in the first case you have a 99,
-->
94 SOAs. In the second case you have
-->
a 99, 95 SOAs.
-->
So 1.01%
-->
of service people and it costs
-->
a lot so it's important to know that kind of stuff.
-->
Regarding this
-->
so this is the architecture review so the other
-->
step here is to analyze that single point of failure
-->
so I'll tell you about this, the chaos engineering, what happens
-->
if X random stuff is done
-->
or see what happens
-->
I'm plugging something, takes down everything or not
-->
and usually this chaos engineering stuff
-->
is done by people outside the IT team
-->
or not outside but independent of operations
-->
and architecture and other stuff so these guys can do
-->
without even
-->
previews
-->
or announcement and plug anything and take down
-->
the whole system and see if
-->
IT operations is able or not to recover so that is
-->
the function so these people are the most
-->
native by IT departments but it's important because
-->
that is the way to discover the failure
-->
points that no one has ever seen before. And finally
-->
the HA, the higher value computing so what needs to be
-->
done, if it's possible or not, what happens to the data
-->
so that is important. Also the
-->
business continuity or disaster recovery plan
-->
so how to keep that in mind
-->
the targets for recovering
-->
in case of a failure
-->
as well how to detect those and how to respond to those
-->
and the patterns of designs that can be applied in order
-->
to recover when there is
-->
any failure as well. Now regarding the
-->
performance, the last pilot
-->
this is
-->
teaching in the sense that
-->
usually a user will tell you
-->
this is low, sometimes it is low
-->
but one thing is that
-->
the slowness from the user
-->
but again
-->
the performance or the slowness
-->
of the application usually by
-->
proper monitors
-->
so this is important to address
-->
here is where the for example
-->
APM monitoring tools take into place
-->
within Azure, you can use Azure Monitor
-->
that is able to allow you to monitor
-->
real life this kind of problem issues as well
-->
so the view here
-->
is with tasks and performance, for example
-->
here we have the proper example of this situation
-->
this is the common situation that you
-->
provision the capacity of your workload
-->
to the extreme use case or the extreme situation
-->
but it turns out that all of this time
-->
which is over 70% of the time
-->
you have inefficient use of this workload
-->
so you are paying too much
-->
and if you go like this
-->
whenever you have the peak load and usually that is
-->
where everyone is paying attention to the application
-->
you will have performance issues, so that is what happens
-->
so the scale performance, the scalability
-->
option that you can enable
-->
is what allows you to balance like this
-->
so you can optimize so that is why this kind of stuff is
-->
common, so this could mean to add
-->
additional instances to our server or to application server
-->
to handle the load, but in order to do that your application
-->
needs to be able to do that kind of stuff
-->
there are also different levels in order to do this
-->
so in this case the performance
-->
the sizing, the IO of your
-->
the drive, the CPU, the memory, all this stuff here
-->
and networking, if you are using a CDN or that
-->
you can get a sign, if you are doing scaling
-->
or if you have your graphical deployments
-->
you can program all the users
-->
and the backing services, if you have a Karchi for example
-->
before the database
-->
or if you have replicas, some replicas for the database as well
-->
or in the design of your application if you are using
-->
a synchronization process that
-->
hangs the application until the data is written
-->
or if you are using a synchronous process in which
-->
the application sends the data and the backing process
-->
writes that down without hanging the application, so this is
-->
where the messaging systems actually will appear
-->
in the design of your applications, so all of this stuff
-->
needs to be developed and the data sharing
-->
so where is the data?
-->
I was probably one of the times for security
-->
but probably this is super important because this may be
-->
the most
-->
the one that can cause the most impact in the process
-->
and replication as well, so there are several
-->
approaches to security
-->
the first one is the approach
-->
regarding the multiple layers, so from the
-->
physical security to up to the data
-->
or if you can go from the bottom to the top
-->
from the data application, so this policies
-->
are physical security, so these are the different security
-->
layers that are available to be applied
-->
so the identity of the users, the role-based
-->
access control, the encryption of the data
-->
how to handle the networking, not to expose
-->
anything that is not needed to be exposed
-->
the handling of keys of security, the monitoring
-->
not only of the CPU, but of the
-->
security or the vulnerability of the application
-->
and also the application
-->
in DevOps, we are not doing the scanning
-->
so that is what needs to be done
-->
and
-->
there is another
-->
file here, the operational one, which is mostly DevOps
-->
so DevOps in order to be able to deploy
-->
whenever is needed, the monitoring
-->
so you can know the workloads
-->
and the automation to reduce any error
-->
so the system
-->
needs to move into DevOps in the same way that
-->
is to automate whatever you are doing manually
-->
so you can move into
-->
either responsibility things
-->
and not just doing the same commands all over
-->
so in this case you will need to monitor
-->
how to establish the network
-->
to find the resources from the naming
-->
from the groups of management that you are using
-->
how are you going to deploy, how are you going to work on the process
-->
if you are keeping the group infrastructure
-->
as a code, so if you need to deploy everything
-->
you can do it without depending on anything
-->
or how to test your systems at several
-->
levels so you can have this in mind of what is
-->
going on. Finally, the
-->
business continuity will be tested with the way it plans
-->
so whenever something happens
-->
at least we have a way to
-->
understand how to do it
-->
obviously all of that stuff is huge
-->
there is a lot of stuff in there
-->
so you need to prioritize what you need to do
-->
now versus what you need to do in the near future
-->
so having a process to do that
-->
this always will be
-->
a cycle of effort
-->
so all the information that we do is
-->
applied and we share
-->
against the data
-->
so these
-->
are, let me see, how are we
-->
...
-->
So we're going to do this lab
-->
the well-architected in green
-->
which is the same, well it's similar to
-->
the same thing that we did in the morning but as this is
-->
another framework it will be interesting for you
-->
to see the kind of questions that are
-->
here available
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...
-->
...