Microsoft Azure Training - [34] Azure Cloud Services -Part 3- Cloud Services Configuration 70-533 Video Lecture | Microsoft Azure: A-Z Guide - Database Management

hi everyone welcome to cloud Rangers
Microsoft Azure training I am Shawna
smell I'm a cloud architect with too
late and that's my contact information
there my Twitter email as well as
LinkedIn if you wish to connect today is
part 3 of Azure cloud services and what
we are going to discuss about is cloud
services configuration so in the last
couple of sessions we went over what
cloud services was and you know how you
can create them what are the different
role services you have and today we are
going to get into some details of how to
configure some of this role services ok
so let's get started so before we do
anything today regarding the
configuration I want to do this a little
differently so we will be going to my
client server machine as well as the
slides off and on so the first thing I
want to do is actually get a clamp
service created in the backend before we
come to the slides so let's go ahead and
first create a cloud service so I met my
client computer here connected to my
subscription by now you should be quite
comfortable with creating a cloud
service so what we are going to do is
rather than coming to the portal here
I'm going to use Visual Studio and
create the cloud services from here so
you can pause it you can follow along at
this point and the first thing I'm doing
to do is create a project as your cloud
service 1 I'm going to keep it the same
name choose that as your cloud service
here it's like ok and I'm going to have
a web role as well as a worker role and
I'm going to name them Ranger web roll 1
and Ranger worker roll one you can name
whatever you want to identify your ones
click on OK and it's asking us for the
new SP net project will have this as
empty
and the project has been created okay so
we're going to leave this at this point
over here go back to slides and carry on
with our conversation there okay so the
first thing I want to talk about in
configuring cloud services is the roles
instances right so what we know is that
there are two roles in a cloud service
obviously the web role and worker role
and the wave role and the worker role
can have multiple instances as we know
so the thing that I want to emphasize on
for both exams as well as production is
that these roles can be scaled
independently so you could have a cloud
service with just one web role for
example and have maybe two worker roles
or three and you can do this
independently of each other so you don't
have to have like one web web role one
worker role it's not a one-to-one it
could be any ratios and the reason for
doing that and these rules to be scaled
independently one good reason is that
it's very well suited to multi tier you
know web applications so you might have
a web site where the people come to the
website and the web application goes
connects at the backend does some sort
of processing connects to databases so
the web world might not be you know as
busy as the worker roles and to serve
all the users you could have one web
role which you know displays the web
application or brings the front end of
the web application and have like about
five worker roles working in the back
and in tandem to make sure that
everything happens properly so you can
independently scale them and utilize
them based on obviously your environment
your needs your audience and everything
like that
so that's one thing the other thing
that's very very important to remember
is the capacity of subscriptions so each
instance of this web role utilizes like
at the back end basically these web
roles as worker roles are virtual
machines
these virtual machines have their course
they have their CPU cores they have
their memory they have disks so you have
to remember that the subscription that
you have
from Microsoft Azure actually has
limitations
as much as we say that your cloud is
elastic which is true you can add and
remove resources as you want which is
true as well but there are limitations
per subscription basis how to be very
careful when they do that when I say
that so you have to remember what is the
capacity of your subscription because
you might want five web roles and five
worker roles and each of them will have
to course age so all of a sudden you
need 20 course total right for your for
your project what will happen is maybe
your subscription is not going to allow
you more than 20 course per subscription
Microsoft actually has limitations that
are put in place so you have to be very
aware of that when you are creating this
worker role web role instances that your
subscription can hold that and before we
actually go anywhere they actually
demonstrate what what I mean by you know
that you have to understand it you have
to be aware of what your subscription is
allowed and how much it is allowed to do
so let's go ahead and view how you can
check that I do have the PowerShell
scripts here but I mean the command
lives here but we'll go and talk about a
little bit in a demonstration on how to
find this information for your
subscription ok so let's go to our
client system here and we'll come over
here let me first see what subscription
I'm connected to you so that would be
get is your subscription tab ok looks
like Ranger pay-as-you-go subscription
looks like I'm connected to the right
one so the command that is quite simple
is the same command lit here and the
only thing you have to do is current
which if you have multiple subscriptions
it will take the current subscription so
if you look at this it'll be same
because I'm just connected to one
subscription here and I want the
extended details ok
so let's let get the extended details of
my subscription here you will find at
least some of the most important things
you have to remember are the capacities
you have to be aware of ok so the first
thing we are going to look over here is
the current core tell
so my current core count is zero and my
maximum core count is 20 so I created I
mean I did not publish this web service
here so currently that's why it's
showing that I do not have any core
count means I'm not utilizing anything
but I can go up to 20 okay so let's go
ahead and publish this or web
application this web service and we'll
see what happens to those changes and
how it utilizes that okay so the first
thing first I need to put in some
resource here so let's go to my ranger
web roll one I'm going to add a new item
I'm going to add an HTML page and I'm
gonna call this one default of that HTM
okay so basically the first page do an
add on this and from here I already know
I have one roll each right so let's come
over here go to properties and see the
instance count is one one core so one
core is going to be used for the Ranger
web role ranger work role let's do the
properties of this one and it will see I
mean we can see it's one role over here
as well as you can see you can change
this over here right I mean this is a
sizing that will come to this later but
that's what it is for now so let's go
ahead and publish this one so the way we
do that is come over here go to publish
this is going to be okay the
subscription that I've connected to
you'll obviously see your one here so
it's asking for a cloud service I'll
just call it Ranger store sorry Ranger
web site one and this could be East us
two and I'm going to make the storage so
this is doing the cloud service and
storage account so the tram services
would be Ranger web site one and this
could be locally redundant store up here
so when you already know that so let's
create this and you can see this is the
cloud service that it's going to create
first because I do not have anything
over here
so far right I mean there's nothing in
my subscription so it's doing everything
for us you can do it the other way
around - I'm not going to be able to
remote desktop let's leave it the way it
is and it's going to be in release the
environment or the slot is production so
you know all of this stuff already so
nothing new here loads go ahead and go
ahead and publish this so I'm going to
pause and come back when this is done
alright so looks like the cloud services
up and running over here it says it's
complete so let's go ahead and look at
what's our core count right now so
current core count is zero and the max
is 20 actually you know what let me let
me do a little bit of this select
current oops current core count and I
need max core account okay so as
expected you can see the current core
account became two from zero and the max
is 20 now I want you to understand that
why this is important so you might have
multiple instances of a web application
of a web service or even multiple web
services and this court count will keep
increasing and at one point we'll notice
that it has reached 20 and you won't be
able to create anymore anymore ruled
services because you are out of your
core accounts at that point you will
either call up Microsoft support and
have them lift or increase the core
account or you use a different
subscription as you know from my you
know sessions on the subscriptions is
that you could have one account
Microsoft account with multiple
subscriptions so you could have multiple
subscriptions so to do that so this is
something that's very important for you
to remember that you know this core
count does not go high and it's
important both for exams as well as
production work ok so if you cross that
at that point it will start throwing
errors ok so let's go back to our slide
we have talked about
the capacity of subscription being
important the other thing I want to talk
about is actually the requirement of
having multiple instances so when we
build cloud services and when we publish
that we have seen before where we had to
put that checkbox to say that I am okay
for this to be published even if there's
one instance of a role in the cloud
service so currently the cloud ruled
that we had created was only with one
web role and with one worker role
however that is not that is not
sufficient for it to have the proper SLA
or the service level agreement from
Microsoft so Microsoft provides a
financially backed service level
agreement saying that your service is
always going to be up for at least
ninety nine point nine five percent of
the times and if it is isn't for
whatever reason they they will actually
compensate you financially and that's
that's quite important for Microsoft
because a lot of people are gaining
faith that Microsoft is quite in like
quite confident that they're going to
have the service up and running at least
four ninety-nine point nine five percent
of the time but at the same time
Microsoft wants you to remember is that
your architecture as much as flexibility
it may have should also support high
availability and this is where multiple
role instances are responsible for two
important things one important thing and
we have talked about this when we were
doing virtualization and high
availability set of I mean virtual
machines that hive liability sets is
that upgrade and fault
domain so if you have multiple instances
in a cloud service Microsoft guarantees
you that when it is upgrading the hosts
what this virtual machine is located it
will make sure that it is going to do
one host at a time so if you have two
instances of a web role it will make
sure at least one web role is up and
running when Microsoft is doing one up
one thing that is upgrade and the other
thing is if there is any hardware
failure so having
multiple roll instances will ensure that
the upgrade Microsoft does and if
there's any hardware failure you are not
going to be affected okay
architectural II obviously you can have
one and one just like we just did right
now but my cursors actually makes sure
it reminds you that if you don't do more
than one it might not be able to back
you up for that easily so that's another
thing that's very important to know so
let's go ahead and try to look at a
couple of things one we are going to use
PowerShell right now and the command X
you can see is right down here with
we're going to use this to increase the
count of our web role to two and our
worker role to two as well and by doing
this will ensure that we actually have
to upgrade and default domains taken
care of so Microsoft SLA is supported
obviously this is something that's
important for production right I mean
you want to make sure that you are
within their slay and you are not good
to have any downtime so let's go to our
client computer and get that done
all right I met my client computer here
so the first thing we want to do is go
and browse our roll instances and we
know that it's going to be one in what
so Ranger website one is our cloud
service let's go in there once this
loads up if you scroll down over here
you can see roles and instances we can
see that there is one way we roll one
work role and these are the names and
these are the sizes so click on the
whole thing not on on this guy's
separately but click on this instances
over here once you click on that this is
what one to show you
so Ranger web roll 1 and Ranger work
around want these are the two roles
sizes a status you can see update and
fault are at 0 0 so that means that if
right now there is a failure on the host
that Microsoft is running this virtual
machine on it'll fail because there is
there's no redundancy for this virtual
machine update and fault they're all at
0 0 there's there's no redundancy there
at all so it goes for the worker role as
well so let's do something we would use
PowerShell to increase the roll count
the instance counts for the web roll
here and we'll use the management coral
or the preview
portal to actually increase the one over
here okay so let's let's get let's
increase one of the instance counts
directly one way to do that of course is
that when you are deploying it you can
say it directly that hey I need more
than two instances are you know I need
more than three instances or whatever we
can do this from the cloud configuration
directly so let's actually before we get
started here show that so you can see
the instance count from the ranger web
role here is one we could have said this
to two and over here it's one as well we
could have sent this to two as well so
when we are publishing this it would
have gone and published this with two
instances rather than one that was one
way to do it and the information is
actually located here so let's put a
configuration file here you can see the
instance count is one and one so these
properties that you see over here by
right-clicking over here and going
properties it basically reads from the
service configuration configuration file
here okay so it picks this one and one
from here and this is where it is if it
changes to two this will change over
here as well so for your exam and
production both it is important for you
to remember that this information is
located at the configuration file what
the instances countess okay so one way
we took out of the way is that you could
have done this while publishing let's
assume it's already published so one way
to do this is from the powershell so
let's go over here let's first get her
as your role so this is one command late
that's pretty neat and i'm going to say
the service name is going to be i think
it was ranger website one that's what we
called it range your website what yep
Ranger website one that's what the
service name is okay let's hit enter
okay it's showing us that the role named
range of April one has one instance and
Ranger worker role one has one instance
as well so another neat way to view
whatever it is so let's set one of these
roles so set as your role and what we
are going to do is we were set a service
name and the service name we know is
Ranger website one and what we are going
to say over here is let
go to the role name so the rule name is
going to be let's do the worker role
okay so our role for the worker is
Ranger
worker role one worker one just want to
make sure we're not making any titles
here okay and we have to say which slot
it is in we know that the slot when we
are deploying was production so let's go
ahead and put the slot is production
okay that's important for you to put and
the count is going to be let's put it
has to hit enter on that this actually
takes time and the reason this actually
takes time if you think about it is
because it has to now go back and
totally reconfigure and create a new
virtual machine for our worker roles
right so it creates a second instance
means it's spinning up a virtual machine
at this time in fact if we come over
here at one point we will see that it is
a spinning over here and trying to
create one obviously it's working and
doing its stuff at the back end but I'm
gonna pause and come back when this
shows up over here that it's working on
it
alright you talk about like four or five
minutes and I can see that over here is
started creating a virtual machine so
let's expand this a little bit we can
see the worker role one instance zero
while it's an unknown state because it's
all in a flux because it's doing a lot
of things in the background to ensure
that this instance one is actually
starting up right now it was creating
and look it changed right now the web
role started running and this has
started just running that so let's click
on the instances here show you something
here look at this it already went and
changed the update and default domain to
one for the new instance so technically
for the Ranger worker role or the worker
role itself we are now quite under I
mean we are at at par in a par with
Microsoft's 99.95 SLA requirement
because now that we have more than one
Microsoft will ensure when they update
one of this hosts underlying hosts of
this virtual machines or if there is a
failure for Hardware or whatever we are
actually
so that's what basically what I meant by
having multiple instances to make sure
the update and the fault was taken care
of so we will let this settle down and
once this settles down we are going to
use the portal to go and increase the
count over here okay all right looks
like it's all up and running right now
so the new instance is there it's all
built so let's go over here and click on
instances okay to worker instances and
one ranger so I just demonstrated how to
do this using partial you see that this
command that actually succeeded as well
so if we run the command over here get
as your role and the service name
obviously we are going to see that the
worker role for the Ranger worker role
actually has two instances so let's go
ahead and change this one now and we are
not going to do this with PowerShell
we're going to do this from the preview
portal the way you do this is actually
not click here but click on the ranger
web role here directly and you can see
over here that there's there's a pin
here for scale so let's go ahead and
click this one so auto scale is often
instances one don't worry about the auto
scaling we'll talk about it at some
point in the future session but we are
now concentrating on instance one we can
see that right now the instance is 1d at
one and this is something we want to
change so not go 244 let's come over
here let's not get carried away
let's go to for example three okay so
we're going to have three so it's good
create two more so let's go ahead and
click on save and of course this is
going to take some time for this to
happen once again so I'll be I'll be
back when things are up and running okay
just aren't pausing here to actually
show you that it's actually creating
those two extra virtual machines because
we said that they're going to be three
instances right so already one was there
actually this is a good one for example
point of view when we mentioned over
here let's go up over here count equals
to two so it went and created one more
so this two over here does not mean it's
going to create two extra it just saying
that they're going to be two total so
one was already there it just went and
created one more extra here when we
pulled the slider and we said three
already one was there so it's just
creating two more when we said three it
did not mean go add three more you just
said it's total so if one was created
two more just want to put it down put it
out there so you understand what it
actually means already looks like all of
them are done okay so let's come over
here click on instances I want to see
what's happening here
as you can see over here to update
domain and the fault domain they all
have updated with the information here
so you know if one of them goes down you
still have the other two running in this
one and here you have one whilst this is
done we have used up quite a bit of the
number of course we are allowed to do
that so let's go and explore that
command late once again so it was what
was that command late it was get as your
subscription okay so the current
subscription and I need the extended
details okay let's write this okay look
at this the current Corps count has gone
to five and the total that we are
allowed is 20 so we can have five more I
mean we have fifteen more cores in our
subscription before it starts the
screaming so this is important to
remember okay and this is the total
number of core count that's then in your
subscription so if you have other
virtual machines which are using coal
for something else it will be counted
over here as well not all the time so
over here we have five virtual machines
now rate because there are five of them
one two three four five instances not
all the virtual machines will have the
total size of core as one right I mean
each virtual machine has one core but we
might have virtual machines where the
core might be more than one so that's
something I want to get to right now so
let's go to our slides and let's move on
the configuring the cloud service role
size so we are we talked about the
number of instances now we talk about
the size of the instances when we
created our cloud service and we'll go
back in there momentarily we created our
rules as one instance with one core and
the size of the virtual machine was a
small because the size was a small it
was actually giving us one core that
size can obviously change the thing to
remember here is that this size of the
web service role VM is not the same as
the IAS or I as virtual machine size
these sizes are actually different so if
you go today and create a regular
virtual machine on your subscription or
you know in Azure
that size may not be the same as the
size of a web service roles virtual
machine ok as much as you think that
these virtual machines might be of the
same size they're actually not and I'll
I'll show you how to find out what the
sizes are and how they're different
it's not a whole lot different but there
is some difference that you have to be
aware of at certain levels the history
behind is your if you remember is that
you know first they actually started
with cloud services those nothing called
as infrastructure as a service virtual
machine as URIs do not even provide that
service ok it was running past platform
as a service so whatever we are doing
right now is as stuff so it was giving
you access to that and there was the
requirement for virtual machines were
different then when they started
providing the service for into is and
they said that you know we would allow
you to make your own virtual machines
for other worker load workloads what
happened is they change the virtual
machines slightly to do that so let's go
ahead and discover that and find out
where we can find all this information
so going back to our subscription here
let's close all of this
close the sir okay let's leave that on
if we come to one of the worker roles so
let's come to the ranger worker role
here you can see that we had one
instance count and a small virtual
machine by small we meant one core with
you know seventeen hundred megabytes of
RAM this can be obviously changed so if
we come over here we can see that you
could have put other virtual machine
sizes over here as well you could go as
far as like 16 cores for your virtual
machine you know that's a standard d-141
of the d-series virtual machines but
what I'm trying to get at is that these
sizes are not the same as the
infrastructure as a services size and
the one way to find out that what this
actually constitutes off or what this
means is actually over here so if we
come over here let's clean this up and
we go to get as your role size hit enter
you can see it's throwing us a lot of
stuff that stuff that we want from here
really are
select instance size and we need the
course okay let's do the course and
we'll do the memory as well let's hit
enter on that so when we say it's going
to be something small as you can see
it's one and it is this okay if we went
and said that we need something large it
would be like four cores and you know
it'll be about seven gigs then a little
bit more in memory okay so this is
something you have to remember that not
only the instance sizes can be changed
the instance contents can be sent change
the instance sizes can be changed as
well and if you come to the service
configuration file over here you will
see that we say the instance count the
name and everything the size is not here
the size is actually defined in the
service definition file okay so if you
click the service definition file you
can see this is the worker role and this
is the size and when we say small it
means something like this so Kate as
your roll size is a very important
command that you have to remember
this and these sizes or this
specification that you are seeing over
here is not exactly same as the is
virtual machine and you know what let me
actually show that to you just give me
one sec here okay so I'm at this URL as
your Microsoft comm it's in
documentation articles virtual machine
size specs so these are the virtual
machine sizes for infrastructure as a
service or is and what happens is if you
look over here I could not find much
difference like the small size still has
one CPU core and it has about 1.7 gigs
of memory that's fine
but you can see that there's a lot of
more option over here a nine it has 70
course look at the options that we have
for our virtual machines here if you
look over here I don't even see a size
well ni-nice here it's 16 cores there's
a standard there's basic size so this is
the same wine for the standard I wonder
what basic size is out there 1 2 a 4
basic size is 1 2 3 4 so it has most of
it standard here let's see if the B
sizes are here D s 1 2 3 4 14 we have up
to d s 14 well they're almost the same
but as you can see the listing is quite
different so this was listed under the
virtual machine size of specs and here
the command let it's quite obvious that
you are looking at the rule sizes and
Microsoft makes this distinction to make
sure to just give you an understanding
that hey this virtual machines can be of
different sizes and they have different
you know they have different resources
at the back end the course of memory
might match the disks might not match
the eye ups might not match or something
so far I've seen that it does match in
most rooms like the cores and memory I
found out that they caught up quite a
bit since they started I mean we are I
mean all the D sizes are now available
here which they weren't before
so I'm saying that most of them have
matched up but Microsoft actually in all
its purposes you know it's one to make
that it creates a separate distinction
between the rule sizes and the virtual
machine sizes okay so this is something
that we have to remember is different
and this information is located in the
definition file here the VM size okay so
that's something we have to remember and
this is the screen shot I had put over
there where I was showing that it is the
small size that was picked up for our
one okay all right so so much for that
let's actually move on to the next slide
and what we are going to talk about is
the cloud service role operating system
so all these virtual machines just like
infrastructure-as-a-service you can
choose the operating system that goes on
this virtual machine the thing to
remember here a couple of things
remember here is that the operating
system setting configuration it applies
for all the roles so just to keep it
consistent you cannot have one role in
your way one role in a worker and you
know different operating systems no it
has to be the same setting for all the
roles across the cloud service so once
you say that hey I want Windows 2012 r2
and the latest release you have to make
sure that it is for all of them there
are two settings that are applicable for
the for choosing the operating system of
the virtual machines that will be the
role virtual machine in your cloud
service one is the operating system
family which is identified numerically
and will I'll show you how what I mean
by that and the operating system version
so you can choose the family of the
operating system as well as the version
and we'll go to the client machine real
quick and I'll show you what I mean by
that so when we come to the service
configuration so the cloud service
configuration over here under the
element service configuration here if
you scroll all the way to the right you
can see two things there's an OS family
which is for an OS version which is
pretty much just start and Astrix over
here basically means that the latest
version that's what it actually means
but oh it's family for I want to run a
couple of command lists to actually show
what that actually means and you know
how the changes over here can reflect
what the version and the operating
system firm
for your role service it's going to be
so let's clear this screen the command
like that I want to run over here and
want you to remember it's called git as
your OS version it's pretty simple to
remember actually if you click OK with
that it throws a lot of information the
information that we are interested in is
you know something like Windows Server
2012 r2 right so we need something like
Windows Server 2012 r2 let's assume that
that's the latest one and let's go up
over here so looks like that number 3
means Windows Server 2012 number for the
family 4 means Windows Server 2012 r2 so
by that we know that the virtual machine
we have for our cloud services all our
Windows Server 2012 r2 and then you have
the version so you can see the version
over here is actually named a little
differently but this versions actually
show that when they were released right
and the release version there are
multiple release versions that are there
for you to ensure that you get different
updates so some organizations they're
like hey I I don't want to go at a
cutting age and you know have the latest
updates yet because I know my web
application runs on this platform with
this updates well so Microsoft always
makes available few versions with the
latest updates to ensure that you know
you have that option to change the other
important thing to remember is this key
over here is active so you might have a
lot of listing in here when you run that
gate as your OS version there might be a
family of operating system which is
which has the right version you need but
it might not be active and the reason
it's not activist as your says that you
know it's too old you know even if it's
2012 r2 there might have been some
critical security patches that came
after that I do not want you to go back
and you know choose one of that with
some sort of a you know there is a
security flaw or whatever so not all
these versions or family of operating
systems over here are actually active so
let's actually filter this a little bit
at
bring it to a point where it's more
visible for us on what we want so let's
get as your OS versions I'm gonna get
the version four because I know that I
want 2012 r2 obviously depending on your
project it might be 2012 it might be
2008 doctor so you can go up and you can
see that it actually has family for a
lot of other things too like family one
is 2012 r2 so depending on your project
and your requirements obviously you can
do that but for our purposes we want the
family for so let me go and select all
the versions where I need the family of
the operating system oops I need the
family of this operating systems to be
well I'll just put like probably good
pretty equal but I'll just put like over
here and let's see what I get okay so I
should get all the operating systems
with 2012 r2 so let's go ahead and
select some information from there okay
let me select the family obviously I
want to also select the family level
because it will give me which server it
is good I want to check the version
obviously and let me also find out if it
is active okay let's hit enter of that
okay so all the family for over came
over here this all our Windows Server
2012 r2 and you can see these are all
the versions and obviously you only like
I don't know four of them are active the
other are not active okay so you can
only choose one of this four so let's
let's clean up the filter a little bit
not only it's going to be is active
actually let's do this serious so not
only I need this to be active let's
let's sort it okay let's sort it and
find out
start by is active okay let's hit enter
okay so looks like these are the only
four versions that you can actually use
because everything else over here for
2012 r2 have already it's no longer
active so it's not expired they don't
didn't do that and you can see that the
reason behind that is they have got over
here okay let's let's do one more thing
I know I'm going a little bit more than
required but let's do this let's do this
in descending order okay I will sort
this by is a clip and go descending so
this would be the latest one and I know
this is the latest one because this was
released sometime in May 2015
okay May 2015 this came out and then
there was one on the 20th and then there
was actually there's one in July over
here as well where is this sorting
volume oh it's going descending over
here so I can see what happened okay so
the latest one that came over here right
this would be our latest one okay so
this is the version let's see what
version we had over here this over here
actually means go do not do any
guesswork go pick up the latest one so
we did pretty well over here put Asterix
here so it went and picked up the latest
one so the wizard here knew that hey go
get the latest operating system you can
find so it's very 2012 r2 and it's going
to be the latest version that it can
find over here so it went and picked
that one okay let's clear the screen and
you can see there were others from 2014
and all that and this is the reason
they're inactive heck I can even see one
that's from 2014 here there's one from
2013 Wow
so you know these are the ones that were
expired okay no worries let's go ahead
clear the screen
so the thing that I want to do over here
is do this once again what if my
developer came and told me that hey the
latest update is not working because we
needed an update or we needed a version
from a different with different updates
right so rather than the latest one over
here let's go pick up one that was from
April or something like that so the
thing that we do over here is take this
version okay take this version and what
we would do is rather than the OS
version being automatic or pretty much
the Asterix here means pick the latest
we could have done something like this
okay this will work as well so when this
operating system was going to be
deployed for this virtual machine or
this role it will pick this version
specific for the deployment okay so this
is important to remember that we have
the control over the operating system
here and we also have to remember that
this operating system is across all the
roles right so all the roles you can see
over here that when you were doing the
service configuration you cannot do this
on a role basis or instance basis it's
for the total service configuration okay
so that's something we have to remember
all right so we came over here these are
the two things I mentioned how to
identify this numerically and OS version
and I do have in the slide the command
lid here to ensure that you have access
to this as well and you can practice law
okay so I do think I covered everything
for cloud services configuration for now
these are the ones like instances
playing with the operating systems
playing with the role the instance
County instance sizes as well as making
sure that you are not crossing the
subscription boundaries those are the
important ones the things to remember
here is also to ensure that you have at
least more than one instance count so
the SLA is you know it is going to be
honored because you have more than one
count of instances for both the roles so
this is something important to remember
as well okay so I think that pretty much
concludes
our our session for today in the next
one we are going to get into more deeper
configurations of the cloud services
with the other aspects but these are the
core configurations for cloud services
that you need to work on ok so as usual
our training site is at cloud Ranger
dotnet and forward slash as your
training you are viewing this most
likely on YouTube channel cloud Ranger
Network feel free to follow me at
twitter at Shawn as well an email Shawn
at cloud range at net and you can
obviously connect with me to link on
LinkedIn and be part of my network ok
well thank you for viewing and I will be
seeing you in the next session