I'd like to start this demo by teaching you how to
resize an Azure virtual machine.
Let's pop open our browser, and I have the portal already up and running,
and let's head on over to the Virtual machines blade.
And I'll probably want to start a machine so we can get to work on it,
so why don't I start up a couple here?
I'll select them in the list and click Start.
While we're waiting,
let's take a look at the storage subsystem of my vm1 machine,
the only one that's actually running.
I'm hesitant operate on this machine because it's
actually the one I'm teaching on, and I don't want it to suddenly go down.
So in the Azure virtual machine Overview page,
we can see just high‑level meta,
including the current size of the virtual machine.
Now I do have a public IP address on this machine,
but I have a decided reason for doing that.
We'll talk about that more in a later demo.
We can see where this VM is placed.
But I'm getting distracted.
Never mind me, never mind me.
For storage stuff, we want to come down under Settings,
Disks,
and then the portal will show us our OS disk, the type of disk it
is, size, the maximum IOPS, the throughput,
the encryption type. So, you can have only one of those, but, of
course, we can have one or more data disks. And I had mentioned that
the VM size not only controls things like the number of data disks
that you can have, but also whether you're allowed to do premium
solid‑state disk storage, which would give you more IOPS and more throughput.
How do we adjust the size of the VM in the Azure portal? Well,
you can see the setting right under Disks.
It's called, appropriately enough, Size.
And let me maximize our screen space here.
You'll want to get comfortable with these controls up here
because these filters will allow you to customize what it
is that you have as an option.
So maybe for vCPUs we know in advance that we want either a fixed number or
maybe a custom number, maybe between 2 and 4 vCPUs. And maybe for RAM, instead
of everything, we want to see maybe a range again of between 8 and say 32 GB
for RAM. And then we can Add filter more.
There's several options to choose from here.
You can choose Generation, Family. Your Ephemeral OS disk is your temp disk,
whether that's allowed and how large it is,
that kind of stuff.
Let me choose Family, and I told you that there are several different
types here, and it's going to default to General purpose.
Now you should know that depending upon your region,
you'll get slightly different runtime costs.
This reflects the fact that different areas of the world
have different costs of doing business.
So if you're like I am, I'm in the East US,
I'll have certain price ranges. And actually, not every VM size may
be available in a particular region, so these are always things to
look at. And you can see here it's looking at the same region that
my vm1 is in, the East US, so it'll only show you those sizes that
are available to you.
You can see in the list here we've got Most used by Azure users, and
then we've got various series and versions down here.
Let me choose Most used by Azure users.
And again,
the idea is that you've got some family keyword and then the number of CPU
cores, so 2, 4. You can see that reflected in the vCPUs column.
M stands for memory.
Again,
I already mentioned this, that you can just look in the docs,
and you can get a full understanding of how those short names
come to be. Number of data disks.
This answers the question specifically, how do you get that number?
The Max IOPS is a relative speed indicator for storage, but that's going to
depend upon whether you've got Premium Storage or not.
Now notice that just about all sizes nowadays support Premium. A big
important implication of premium disks, SSD disks in other words,
over the HDD mechanical type is that the mechanical storage
IOP values represent true maxes, not predictable values, but
burst levels. When you do Premium,
you really can expect to see that max value consistently.
That's one of the value propositions of paying more to get a premium
disk on your virtual machine. Now you should see lastly up here in the
blue that if the VM is currently running,
changing its size will cause it to be restarted. Stopping
the VM may reveal additional sizes.
Again,
I don't want to do this on vm1 because it's the one that I'm actually using,
but we would just choose the new size,
click Save, that VM would restart, and when it comes back from the restart,
it will reflect its current size again.
That's going to be indicated on the Overview page and the Size property, as you can see here.