WEBVTT

0:00:02.800000 --> 0:00:08.160000
 Hi, in this video, we're going to take
 a look at virtual machine fundamentals.

0:00:08.160000 --> 0:00:11.720000
 The topics that we're going to cover
 are looking at the overall virtual

0:00:11.720000 --> 0:00:13.260000
 machine architecture, right?

0:00:13.260000 --> 0:00:15.840000
 What is a virtual machine
 in the Azure context?

0:00:15.840000 --> 0:00:21.160000
 Then we'll drill a little bit into the
 virtual machine elements, and what

0:00:21.160000 --> 0:00:24.000000
 you need to know about those
 and how to set that up.

0:00:24.000000 --> 0:00:28.200000
 Then we'll talk about virtual machine
 sizing, which is really one of the

0:00:28.200000 --> 0:00:32.140000
 key decisions that you're going to make
 when you provision a virtual machine

0:00:32.140000 --> 0:00:39.120000
 in Azure. Let's go ahead and let's start
 out by taking a look at the virtual

0:00:39.120000 --> 0:00:40.620000
 machine architecture.

0:00:40.620000 --> 0:00:45.440000
 When we're looking at the architecture,
 we start with the idea, of course,

0:00:45.440000 --> 0:00:47.360000
 of a virtual machine.

0:00:47.360000 --> 0:00:53.380000
 Now, when I have a virtual machine, and
 we will take a look at this, virtual

0:00:53.380000 --> 0:01:02.340000
 machine here, there are a few key attributes
 of the virtual machine that

0:01:02.340000 --> 0:01:04.400000
 are tied to the size.

0:01:04.400000 --> 0:01:08.560000
 The size is going to be the first really
 big decision that you make with

0:01:08.560000 --> 0:01:09.960000
 a virtual machine.

0:01:09.960000 --> 0:01:16.180000
 The size is going to define the
 number and type of VCPUs.

0:01:16.180000 --> 0:01:19.260000
 What's your processing power?

0:01:19.260000 --> 0:01:24.420000
 It is going to define
 the amount of RAM.

0:01:24.420000 --> 0:01:28.780000
 It's going to define
 your temp drive size.

0:01:28.780000 --> 0:01:38.660000
 It's going to define the number and
 type of disks that you can use, and

0:01:38.660000 --> 0:01:47.640000
 it's going to define the number
 and performance for your NICs.

0:01:47.640000 --> 0:01:50.040000
 I'm going to say NIC because
 it went over there.

0:01:50.040000 --> 0:01:53.900000
 That's really going to be the first
 thing when you are provisioning a

0:01:53.900000 --> 0:01:56.260000
 virtual machine that you need
 to think about is the size.

0:01:56.260000 --> 0:01:58.360000
 How does everything play together?


0:01:58.360000 --> 0:02:01.840000
 What are the basic components
 of a virtual machine?

0:02:01.840000 --> 0:02:05.160000
 Obviously, you have the virtual machine,
 the physical representation.

0:02:05.160000 --> 0:02:06.240000
 Of course, it's all virtualized.

0:02:06.240000 --> 0:02:13.460000
 But separate from the virtual machine
 itself, you also have at least two

0:02:13.460000 --> 0:02:23.480000
 disks. You're going to have at least
 an OS disk and a temp disk.

0:02:23.480000 --> 0:02:32.140000
 I'm going to have at least
 my OS disk and temp.

0:02:32.140000 --> 0:02:34.860000
 The temp disk is interesting.

0:02:34.860000 --> 0:02:40.420000
 The temp disk is locally attached storage
 and it's low latency locally

0:02:40.420000 --> 0:02:48.300000
 attached SSD. The OS disk can
 be a number of types of disks.

0:02:48.300000 --> 0:02:49.400000
 Which types are allowed?

0:02:49.400000 --> 0:02:50.440000
 It's based on the size.

0:02:50.440000 --> 0:02:53.480000
 We'll take a look at that
 when we get to sizes.

0:02:53.480000 --> 0:03:00.440000
 That could be what we would
 call a premium SSD.

0:03:00.440000 --> 0:03:05.660000
 Now what we call a standard SSD.

0:03:05.660000 --> 0:03:09.860000
 Or it could be a standard HDD.

0:03:09.860000 --> 0:03:14.660000
 As I go down that list, I'm going down
 in terms of performance specs but

0:03:14.660000 --> 0:03:17.280000
 also in terms of cost.

0:03:17.280000 --> 0:03:23.400000
 There is another tier of disks that
 you can use for the OS under certain

0:03:23.400000 --> 0:03:30.220000
 circumstances. That is
 now the ultra SSD.

0:03:30.220000 --> 0:03:32.880000
 I put it down at the bottom because right
 now at the time of this filming,

0:03:32.880000 --> 0:03:36.520000
 that is still in preview.

0:03:36.520000 --> 0:03:39.980000
 It's got limited release in terms of
 where you can use it and what size

0:03:39.980000 --> 0:03:43.120000
 VMs virtual machines
 you can use it with.

0:03:43.120000 --> 0:03:45.920000
 Those are basic storage.

0:03:45.920000 --> 0:03:51.660000
 In addition to that and these have the
 same rules as the OS, you can also

0:03:51.660000 --> 0:04:04.620000
 implement multiple data disks.

0:04:04.620000 --> 0:04:11.240000
 They have been really raising the size
 of the maximum size of your OS

0:04:11.240000 --> 0:04:15.400000
 disk and data disks to the point where
 honestly it's like go and take

0:04:15.400000 --> 0:04:17.740000
 a look. I don't even talk
 about these specific size.

0:04:17.740000 --> 0:04:23.460000
 Not long ago it was four terabytes was
 the maximum size you could have.

0:04:23.460000 --> 0:04:26.480000
 Now it's far beyond that.

0:04:26.480000 --> 0:04:30.180000
 You do have the ability to sort of large
 amounts of data on a single drive

0:04:30.180000 --> 0:04:36.280000
 but you may want to have multiple data
 drives to increase the performance

0:04:36.280000 --> 0:04:40.520000
 and throughput of your data operations
 because each disk is going to have

0:04:40.520000 --> 0:04:45.020000
 certain limitations in terms
 of its overall performance.

0:04:45.020000 --> 0:04:47.000000
 That's on the storage side.

0:04:47.000000 --> 0:04:50.480000
 A lot of time spent on that.

0:04:50.480000 --> 0:04:56.940000
 I've got my virtual machine so I've
 got my compute, I've got my storage,

0:04:56.940000 --> 0:04:58.580000
 I've got my memory.

0:04:58.580000 --> 0:05:03.020000
 The other thing that you will typically
 have with a compute environment

0:05:03.020000 --> 0:05:05.720000
 is some kind of networking.

0:05:05.720000 --> 0:05:14.300000
 We certainly have within
 Azure virtual networks.

0:05:14.300000 --> 0:05:18.720000
 But you don't connect the virtual machine
 directly to a virtual network.

0:05:18.720000 --> 0:05:24.980000
 Instead I have a NIC network interface
 card and the network interface

0:05:24.980000 --> 0:05:30.200000
 card is associated with a virtual machine
 and the network interface card

0:05:30.200000 --> 0:05:35.360000
 is associated with
 a virtual network.

0:05:35.360000 --> 0:05:46.120000
 You can have multiple NICs.

0:05:46.120000 --> 0:05:49.620000
 The NICs have to be associated
 with the same virtual network.

0:05:49.620000 --> 0:05:53.280000
 However they can be associated
 with different subnets.

0:05:53.280000 --> 0:05:59.580000
 Really that's the basics of the
 virtual machine architecture.

0:05:59.580000 --> 0:06:03.440000
 Fairly straightforward, all of this
 can be set up at the same time as

0:06:03.440000 --> 0:06:08.580000
 you go through the portal or if you're
 using a template or if you're using

0:06:08.580000 --> 0:06:12.300000
 the command line, you can set all of
 this up and configure this as you

0:06:12.300000 --> 0:06:14.520000
 define your virtual machine.

0:06:14.520000 --> 0:06:16.000000
 But these are the
 major components.

0:06:16.000000 --> 0:06:22.340000
 Now what I want to do is a little bit
 of a drill down into the components

0:06:22.340000 --> 0:06:26.840000
 that you would need to really fully
 generate your virtual machine.

0:06:26.840000 --> 0:06:30.700000
 The first thing that you need to know
 is that every virtual machine that

0:06:30.700000 --> 0:06:34.820000
 is provisioned is
 based on an image.

0:06:34.820000 --> 0:06:38.520000
 The image is the starting point
 for your virtual machine.

0:06:38.520000 --> 0:06:40.640000
 There are two types of images.

0:06:40.640000 --> 0:06:42.440000
 There are marketplace images.

0:06:42.440000 --> 0:06:47.280000
 Those are ones that have already been registered
 within the Azure environment.

0:06:47.280000 --> 0:06:53.380000
 People worked with Microsoft to get
 those in the Azure marketplace.

0:06:53.380000 --> 0:06:54.840000
 There are thousands of these.

0:06:54.840000 --> 0:06:57.820000
 I haven't counted them, but at one
 time I did it was over a thousand.

0:06:57.820000 --> 0:06:59.260000
 I can say thousands.

0:06:59.260000 --> 0:07:03.800000
 In any case, many different virtual
 machine images that are sitting in

0:07:03.800000 --> 0:07:06.540000
 the Azure marketplace so you
 can just pick and use.

0:07:06.540000 --> 0:07:08.920000
 You can also have custom images.

0:07:08.920000 --> 0:07:13.460000
 Custom images are going to be images
 where you have built up a virtual

0:07:13.460000 --> 0:07:16.100000
 machine the way you want it and then
 you've captured an image of that.

0:07:16.100000 --> 0:07:21.160000
 Then you're using that to create additional
 instances of that virtual

0:07:21.160000 --> 0:07:23.820000
 machine or virtual machines
 that are based on that.

0:07:23.820000 --> 0:07:27.460000
 For example, you might have a standard
 software load that you have for

0:07:27.460000 --> 0:07:30.300000
 all of your machines
 in your organization.

0:07:30.300000 --> 0:07:34.980000
 You could create a custom image that
 already comes with all that software

0:07:34.980000 --> 0:07:39.620000
 loaded so that every time you create
 a new VM it has that baseline.

0:07:39.620000 --> 0:07:41.540000
 There are lots of things
 you can do there.

0:07:41.540000 --> 0:07:44.700000
 In addition to starting with the image,
 you're going to specify your OS

0:07:44.700000 --> 0:07:52.460000
 disk. In most cases, the OS disk is actually
 really defined by the image.

0:07:52.460000 --> 0:07:57.680000
 If I take a marketplace image, that marketplace
 image has an OS disk that's

0:07:57.680000 --> 0:08:01.940000
 128 gigabytes and that's
 going to be the size.

0:08:01.940000 --> 0:08:06.660000
 Even with that, because the OS disk
 really is a clone or a copy of the

0:08:06.660000 --> 0:08:10.160000
 image, but even with that, you have
 some decisions, for example, what

0:08:10.160000 --> 0:08:13.060000
 storage tier do you want
 for your OS disk.

0:08:13.060000 --> 0:08:16.860000
 You also have the ability
 to attach an OS disk.

0:08:16.860000 --> 0:08:21.880000
 If I had a virtual machine in which,
 let's say I need to move that virtual

0:08:21.880000 --> 0:08:25.180000
 machine from one region to another,
 there's not a built-in approach for

0:08:25.180000 --> 0:08:30.500000
 that. What you can do is deprovision
 a virtual machine and then copy its

0:08:30.500000 --> 0:08:35.280000
 OS disk to another region and then
 simply create a new virtual machine

0:08:35.280000 --> 0:08:36.940000
 based on that same OS disk.

0:08:36.940000 --> 0:08:39.780000
 Which is going to be the
 same virtual machine.

0:08:39.780000 --> 0:08:43.280000
 When you think about virtual machines
 and the definition of the virtual

0:08:43.280000 --> 0:08:47.140000
 machine and the software, that's
 all about what's on the OS disk.

0:08:47.140000 --> 0:08:51.100000
 Which of course is true for any machine
 that you're working with.

0:08:51.100000 --> 0:08:55.500000
 In addition to the OS disk, you can
 define one or more data disks that

0:08:55.500000 --> 0:08:58.040000
 are associated with your
 virtual machine.

0:08:58.040000 --> 0:09:02.120000
 Data disks can be created as blank data
 disks or I can attach an existing

0:09:02.120000 --> 0:09:04.040000
 data disk to a virtual machine.

0:09:04.040000 --> 0:09:06.000000
 I used to do that all the time.

0:09:06.000000 --> 0:09:09.000000
 I used to teach SharePoint a lot and
 had a lot of different software that

0:09:09.000000 --> 0:09:11.380000
 I wanted to bring up on
 different machines.

0:09:11.380000 --> 0:09:14.880000
 So I just put all that software on a
 virtual disk and would just attach

0:09:14.880000 --> 0:09:19.280000
 that virtual disk to any machine
 that I needed to install.

0:09:19.280000 --> 0:09:20.640000
 So that's what we have.

0:09:20.640000 --> 0:09:23.500000
 Now, when you're defining your virtual
 machine, you also need to define

0:09:23.500000 --> 0:09:27.940000
 the OS profile. And you think, okay,
 well didn't I start with an image?

0:09:27.940000 --> 0:09:29.040000
 Absolutely you did.

0:09:29.040000 --> 0:09:36.200000
 Maybe you started with a Windows
 Server 2016 data center image.

0:09:36.200000 --> 0:09:38.040000
 But there's certain things
 that you need to set.

0:09:38.040000 --> 0:09:39.080000
 What is the server name?

0:09:39.080000 --> 0:09:41.000000
 That's going to be unique
 regardless of the image.

0:09:41.000000 --> 0:09:42.280000
 What's the admin user?

0:09:42.280000 --> 0:09:44.200000
 What's the admin password?

0:09:44.200000 --> 0:09:48.320000
 What you need to set or what you can set
 is going to differentiate a little

0:09:48.320000 --> 0:09:54.000000
 bit based on whether you're using Windows
 or Linux images as your source.

0:09:54.000000 --> 0:09:57.480000
 You're also going to define within a
 virtual machine what are the network

0:09:57.480000 --> 0:10:00.160000
 interfaces that you're
 associating with.

0:10:00.160000 --> 0:10:03.280000
 And you're going to
 define availability.

0:10:03.280000 --> 0:10:05.320000
 These last three, I'm not going to
 spend a whole lot of time on right

0:10:05.320000 --> 0:10:07.980000
 now. They are covered
 in other videos.

0:10:07.980000 --> 0:10:11.900000
 But making sure that you have a highly
 available solution to manage your

0:10:11.900000 --> 0:10:14.980000
 workloads or to host your workloads
 is of course important.

0:10:14.980000 --> 0:10:20.360000
 We'll talk about extensions as a way to
 inject configuration into a virtual

0:10:20.360000 --> 0:10:24.060000
 machine. And of course you're going to
 want to think about the diagnostic

0:10:24.060000 --> 0:10:26.920000
 settings of your virtual
 machine as well.

0:10:26.920000 --> 0:10:31.900000
 Now the other key element that you're
 always going to think about when

0:10:31.900000 --> 0:10:33.500000
 you are defining your
 virtual machine.

0:10:33.500000 --> 0:10:37.000000
 I've mentioned this before and it's
 really important to get a feel for

0:10:37.000000 --> 0:10:41.320000
 this. Now I will tell you if you
 are preparing for an exam.

0:10:41.320000 --> 0:10:45.120000
 I don't think you necessarily need to
 know every individual size because

0:10:45.120000 --> 0:10:48.980000
 there are over 100 different sizes
 now that are available for virtual

0:10:48.980000 --> 0:10:53.300000
 machines. But you should at least be
 aware of the categories and ideally

0:10:53.300000 --> 0:10:56.060000
 also be aware of the
 different series.

0:10:56.060000 --> 0:10:58.080000
 And I'm going to show you
 this in just a moment.

0:10:58.080000 --> 0:11:02.940000
 Let's go through some of the kind of
 high level things and I'll show you

0:11:02.940000 --> 0:11:05.340000
 how you can get detailed
 information on this.

0:11:05.340000 --> 0:11:07.400000
 The size is what do
 the size is defined.

0:11:07.400000 --> 0:11:10.560000
 First of all, as I said, the processor
 type and the number of virtual

0:11:10.560000 --> 0:11:15.840000
 cores. Also the disk type and number
 mention that the memory, the NIC

0:11:15.840000 --> 0:11:18.360000
 capacity, the number and size.

0:11:18.360000 --> 0:11:22.360000
 And this is not the number and size
 but the number and performance specs

0:11:22.360000 --> 0:11:27.440000
 of your NIC. And also the
 temporary disk size.

0:11:27.440000 --> 0:11:36.380000
 And that temp disk again is an ephemeral
 disk that is very low latency,

0:11:36.380000 --> 0:11:40.660000
 direct attached storage
 for your VM.

0:11:40.660000 --> 0:11:44.760000
 And however, every time you deallocate
 the VM, that gets wiped out.

0:11:44.760000 --> 0:11:48.660000
 So you never put anything that you
 want to have durable storage there

0:11:48.660000 --> 0:11:53.180000
 but things like caching
 and temp files.

0:11:53.180000 --> 0:11:57.440000
 That's a great way to increase performance
 of workloads without really

0:11:57.440000 --> 0:12:01.740000
 having to do much or even
 pay for anything extra.

0:12:01.740000 --> 0:12:04.280000
 Now the categories of virtual machine
 sizes, so many different virtual

0:12:04.280000 --> 0:12:06.260000
 machine sizes that there's
 kind of a hierarchy.

0:12:06.260000 --> 0:12:07.800000
 There's a category.

0:12:07.800000 --> 0:12:11.000000
 The category is a little
 bit arbitrary.

0:12:11.000000 --> 0:12:13.200000
 But it does give you
 a way of organizing.

0:12:13.200000 --> 0:12:15.660000
 You have a category within the
 category you have series.

0:12:15.660000 --> 0:12:22.060000
 The series really defines the general
 capabilities of a set of VM sizes.

0:12:22.060000 --> 0:12:25.600000
 And then within the series, you actually
 have the individual sizes.

0:12:25.600000 --> 0:12:28.920000
 You can see the categories, general
 purpose, which is usually where I

0:12:28.920000 --> 0:12:30.540000
 am certainly for demonstration
 purposes.

0:12:30.540000 --> 0:12:35.100000
 If you've got something that is compute
 heavy or memory heavy or storage

0:12:35.100000 --> 0:12:39.760000
 heavy, there are categories with
 different series for those.

0:12:39.760000 --> 0:12:46.060000
 If you have very high end, high resource
 requirement processing for GPU.

0:12:46.060000 --> 0:12:50.700000
 So maybe you're using some kind of visual
 modeling, 3D modeling or maybe

0:12:50.700000 --> 0:12:52.560000
 for artificial intelligence.

0:12:52.560000 --> 0:12:58.700000
 There are virtual machine sizes with
 dedicated GPUs, one or more dedicated

0:12:58.700000 --> 0:13:02.980000
 GPUs. And there's also your kind of
 generic high performance compute.

0:13:02.980000 --> 0:13:06.720000
 I'm going to say generic, but there's
 multiple categories within that.

0:13:06.720000 --> 0:13:10.340000
 And the best way to see this, I think,
 is not to see the list here, but

0:13:10.340000 --> 0:13:17.320000
 to actually take a quick look at what we
 have in our Microsoft documentation.

0:13:17.320000 --> 0:13:20.640000
 I'm going to just do a quick search,
 and I'm just going to search for

0:13:20.640000 --> 0:13:25.380000
 Azure VM sizes, which I
 search for all the time.

0:13:25.380000 --> 0:13:28.620000
 And I'm going to go to Windows
 VM sizes in Azure.

0:13:28.620000 --> 0:13:32.740000
 The fact that it says Windows doesn't
 mean anything because these are

0:13:32.740000 --> 0:13:34.160000
 all standard sizes.

0:13:34.160000 --> 0:13:39.060000
 Now right here, I get the categories
 that we just talked about.

0:13:39.060000 --> 0:13:45.720000
 And I also get, I can see the different
 sizes, the different series within

0:13:45.720000 --> 0:13:49.520000
 that. And I'm going to go to general
 purpose, and I'm not going to go

0:13:49.520000 --> 0:13:50.100000
 through everything.

0:13:50.100000 --> 0:13:54.460000
 I would highly recommend that at some
 point you traipse through here,

0:13:54.460000 --> 0:13:58.300000
 if you are responsible for provisioning
 virtual machines, you want to

0:13:58.300000 --> 0:14:00.880000
 take a look because this is really where
 you're going to get your first

0:14:00.880000 --> 0:14:05.880000
 great idea of that balance between
 cost and performance.

0:14:05.880000 --> 0:14:09.180000
 And so there's a number of series.


0:14:09.180000 --> 0:14:12.620000
 And we can go down here.

0:14:12.620000 --> 0:14:17.520000
 The B series, which is burstable, that's
 actually really pretty interesting.

0:14:17.520000 --> 0:14:28.220000
 It allows you to actually have a little
 bit of auto scaling based on usage.

0:14:28.220000 --> 0:14:33.660000
 What you do is you say, okay, I am normally
 going to use 40% performance

0:14:33.660000 --> 0:14:38.420000
 of the VM, but at some point I
 may need to scale it up to 200.

0:14:38.420000 --> 0:14:41.440000
 And there's a whole process by which
 you accrue credits to allow you to

0:14:41.440000 --> 0:14:43.100000
 do that. Very cool stuff.

0:14:43.100000 --> 0:14:46.140000
 Now, the other thing I want to show
 you right here as I start going into

0:14:46.140000 --> 0:14:50.540000
 the more standard, the B series is a
 little bit of a one off because of

0:14:50.540000 --> 0:14:56.040000
 the way it works and the way
 that it is actually costed.

0:14:56.040000 --> 0:15:01.160000
 Most of the series, you'll see this
 ACU, that is an Azure Compute Unit.

0:15:01.160000 --> 0:15:04.120000
 This is a relative measure.

0:15:04.120000 --> 0:15:09.880000
 It's going to give you a composite score,
 if you will, of a given series

0:15:09.880000 --> 0:15:15.200000
 of virtual machines and allow you to
 compare them, kind of just very big

0:15:15.200000 --> 0:15:19.740000
 picture. Now, obviously you have memory
 optimized versus compute optimized,

0:15:19.740000 --> 0:15:23.100000
 so there's a workload balance
 you have to do as well.

0:15:23.100000 --> 0:15:25.780000
 But that just gives you a decent
 number to take a look at.

0:15:25.780000 --> 0:15:28.180000
 And I'm just going to go through
 one set of these again.

0:15:28.180000 --> 0:15:30.620000
 You can go through quite
 a large number.

0:15:30.620000 --> 0:15:35.160000
 But here, this is my DSV3 series.

0:15:35.160000 --> 0:15:40.820000
 It's going to tell me that it's using
 an Intel Xeon 817 2.1 Skylake or

0:15:40.820000 --> 0:15:46.120000
 an Intel Xeon, and you can see the rest
 broadwell or a Haswell processor

0:15:46.120000 --> 0:15:49.180000
 with Intel TurboBoost properties.

0:15:49.180000 --> 0:15:54.140000
 So it's going to tell you
 exactly what it supports.

0:15:54.140000 --> 0:15:59.580000
 And then you can see the different
 sizes, 24, 8, 16, 32, 48, and 64.

0:15:59.580000 --> 0:16:02.760000
 And you'll notice clearly there's a
 relationship between that and the

0:16:02.760000 --> 0:16:04.240000
 number of VCPUs.

0:16:04.240000 --> 0:16:09.200000
 You can also see the memory going up,
 the temp storage that direct attached

0:16:09.200000 --> 0:16:14.360000
 SSD storage, the max number of disks
 and the performance specs throughout,

0:16:14.360000 --> 0:16:18.440000
 including the max number of nicks that
 can be attached to that particular

0:16:18.440000 --> 0:16:25.320000
 size. And so that's a DSV3 representative
 of your kind of general compute.

0:16:25.320000 --> 0:16:28.720000
 Notice again, the ACU
 there, 160 to 190.

0:16:28.720000 --> 0:16:34.840000
 I'm going to go all the way down
 to high performance compute.

0:16:34.840000 --> 0:16:42.240000
 And the high performance compute, if
 you look at the ACUs, 199 to 216,

0:16:42.240000 --> 0:16:47.400000
 297 to 315, 290 to 300.

0:16:47.400000 --> 0:16:51.020000
 So there's three different high
 performance compute series.

0:16:51.020000 --> 0:16:55.480000
 The H series is the one that's
 been around for a while.

0:16:55.480000 --> 0:16:58.820000
 And you can tell it, I should tell you
 what the processor is right here,

0:16:58.820000 --> 0:17:03.360000
 how many CPUs, memory, etc.

0:17:03.360000 --> 0:17:08.900000
 Now, if I go up here to this very high
 processing one, it's going to be

0:17:08.900000 --> 0:17:12.360000
 a Xeon Platinum 8168.

0:17:12.360000 --> 0:17:15.280000
 With, you can see the memory, 352.


0:17:15.280000 --> 0:17:19.380000
 Also, you probably will not be surprised
 to know that that one is a bit

0:17:19.380000 --> 0:17:23.920000
 more expensive. An H-C series VM is
 going to cost you, let's just say

0:17:23.920000 --> 0:17:28.880000
 considerably more than a D2S V3.

0:17:28.880000 --> 0:17:33.560000
 Speaking of S, I want to point out
 a couple of indicators that you can

0:17:33.560000 --> 0:17:36.760000
 look for in the naming convention.


0:17:36.760000 --> 0:17:43.440000
 Anytime you've got a name, or for a
 size, it is almost always going to

0:17:43.440000 --> 0:17:44.260000
 start with standard.

0:17:44.260000 --> 0:17:49.700000
 There's, I think, basic A0 and basic
 A1, which you will likely never use.

0:17:49.700000 --> 0:17:52.360000
 Almost everything else is
 going to be standard.

0:17:52.360000 --> 0:17:55.820000
 And then you'll have the underscore and
 you'll have the series designation.

0:17:55.820000 --> 0:18:01.000000
 Then, depending on how old it is, you'll
 have the size, and then there

0:18:01.000000 --> 0:18:02.340000
 are additional designations.

0:18:02.340000 --> 0:18:07.800000
 For example, the M means that this particular
 standard H series is memory

0:18:07.800000 --> 0:18:19.380000
 optimized. And then I've got, in addition
 to that, I've got standard H16R.

0:18:19.380000 --> 0:18:26.900000
 R means that it supports RDMA, Remote
 Direct Memory Access, for message

0:18:26.900000 --> 0:18:31.980000
 processing infrastructure applications,
 and supports in Finnebam.

0:18:31.980000 --> 0:18:32.800000
 What does all that mean?

0:18:32.800000 --> 0:18:36.560000
 It means that if you see something
 within R, you can potentially have

0:18:36.560000 --> 0:18:41.840000
 applications running on that that have extremely
 low latency network connectivity.

0:18:41.840000 --> 0:18:47.120000
 There are a limited number of virtual
 machine sizes that support that

0:18:47.120000 --> 0:18:50.420000
 RDMA or in Finnebam.

0:18:50.420000 --> 0:18:53.280000
 And you can look for
 those simply put.

0:18:53.280000 --> 0:18:56.740000
 The R is the designation
 that shows you that.

0:18:56.740000 --> 0:19:00.180000
 Now, I'm actually going to go down back
 to general purpose because I want

0:19:00.180000 --> 0:19:03.980000
 to show you two additional
 designations.

0:19:03.980000 --> 0:19:06.540000
 I'm going to go down
 here to this DS3.

0:19:06.540000 --> 0:19:10.760000
 Anytime you see the S designation, that
 little small S, and I don't think

0:19:10.760000 --> 0:19:13.700000
 they'll ever have a series because it's
 named S because that would just

0:19:13.700000 --> 0:19:14.700000
 throw things off.

0:19:14.700000 --> 0:19:21.140000
 That means that it supports premium
 storage for your OS disk and your

0:19:21.140000 --> 0:19:26.040000
 data disks. You're not required to
 have that, but it does support it.

0:19:26.040000 --> 0:19:30.340000
 And then the V just means it's the third
 version of this particular series.

0:19:30.340000 --> 0:19:35.680000
 So there's a AD series, a DV2
 series, and a DV3 series.

0:19:35.680000 --> 0:19:42.660000
 And also, if you look at this DV3, notice
 ACU, 160 to 190, which is the

0:19:42.660000 --> 0:19:45.640000
 same as the DV3 app.

0:19:45.640000 --> 0:19:49.220000
 And then the sizes are actually
 all the same as well.

0:19:49.220000 --> 0:19:56.240000
 The only difference between the DV3 and
 the DSV3 is that the DSV3 supports

0:19:56.240000 --> 0:20:02.340000
 premium storage for your
 OS and data disks.

0:20:02.340000 --> 0:20:08.220000
 All right. Lot of things to digest there,
 but take it back to its simplest

0:20:08.220000 --> 0:20:11.040000
 form. You've got a virtual machine,
 you've got a size for the virtual

0:20:11.040000 --> 0:20:15.520000
 machine. The size is going to define
 the number and type of course, V

0:20:15.520000 --> 0:20:20.520000
 course. It's going to define
 the amount of RAM.

0:20:20.520000 --> 0:20:26.040000
 It's going to define the size of your
 temp DB drive, or your temp drive.

0:20:26.040000 --> 0:20:29.400000
 Sorry, that was the SQL server coming
 out of me there for a moment.

0:20:29.400000 --> 0:20:31.920000
 All right. So it'll give you
 the size of your temp drive.

0:20:31.920000 --> 0:20:37.600000
 It's going to give you the performance
 capabilities of a number of data

0:20:37.600000 --> 0:20:39.160000
 disks that you can
 associate with it.

0:20:39.160000 --> 0:20:43.480000
 And also, it's going to give you the
 number of Nix and performance specs

0:20:43.480000 --> 0:20:45.140000
 for those as well.

0:20:45.140000 --> 0:20:48.200000
 So size is of course going to be one
 of those absolute key components

0:20:48.200000 --> 0:20:51.840000
 that you want to think about when you're
 architecting or even provisioning

0:20:51.840000 --> 0:20:52.480000
 your virtual machines.