Welcome back. Let's jump into our next Asher Resource with an introduction to virtual machines.
Our objectives include talking about virtual machine basics when we're creating them, and also taking a look at the pricing and how that works
to start off. What are virtual machines? Virtual machines are a scalable and on demand compute resource available inside of azure.
These are gonna be very similar to the Lennox and Windows servers found in your on premises data center. Except the underlying physical hardware is managed by Microsoft. This alleviates the need to plan for capacity like you might need to in your on premises. Data center.
Virtual machines are deployed throughout Microsoft data centers across the globe, so you can locate them closer to your end users
when creating a verge machine. There are several things to consider.
The first is the operating system of the virtual machine. You can choose from a variety of Windows and Lennox managed images provided in the azure marketplace, or you can upload your own image like you currently might be using in your on premises Servers.
Next is choosing a size when building a virtual machine. You do get to choose how many CPU cores, ram and disturb prevision, but this is based off of pre built sizes. Thes. They're different sizes, depending on what kind of virtual machines your building.
There are different sizes, depending on what kind of virtual machine you're building, such as Compute Optimized, where there is a higher CPU to memory ratio
or storage. Optimize where the disk have higher performance for data intensive workloads.
Next is choosing a location. The location is the Azure Data Center, reason where the virtual machine will be deployed and where its virtual hard disk will be stored. Choose a location that makes sense either for performance to your end users or for having a globally dispersed workload.
Networking is the next topic. You can employ a virtual machine with the public I P address so it is accessible from the Internet. Or you can leave this off and simply deploy so is only accessible on an internal azure virtual network. The virtual machine could also be placed behind a public load balancer or firewall to provide access from the Internet. Finally,
choose a deployment method
as your virtual machines can be created in a variety of ways, such as through the azure portal or through um, or programmatic way, such as Power shell Arrest, a P I or azure command line interface, or CLI.
On this slide. Here is a screenshot of what it looks like to create a virtual machine, and you can see some of the components that we just talked about, such as the virtual machine name, region, image and size. And also, along with other Azure resource is we have to select a subscription and a resource group to place it in.
Let's jump out to some azure documentation pages toe look at virtual machine sizes and how pricing works.
Here's a page for Microsoft's documentation that describe some of the sizes and options for virtual machines inside of Azure. This particular page is specific for Windows verse machines, but there's also a clinics virtual machines page for reference. But let's take a look at what we have here.
If you remember from our screen shot, we had a D S V three selected, which is a general purpose image for our virtual machine. This has a balanced CPU to memory ratio and says it is ideal for testing and development, small to medium databases and loaded medium traffic Web servers,
you know, so see some of the other ones we have.
Like we mentioned, the slides like compute, optimize memory, optimize storage, optimize GPU and high performance. Compute. Now, you don't necessarily need to memorize each and every one of these for the exam, but I recommend being familiar with the different types and the size acronyms that they have here.
For each type, you might be asked what would be an appropriate type for deploying a virtual machine
or when looking in the performance based labs, it might ask you to deploy a virtual machine to meet specific scenarios. Now let's take a look at virtual machine pricing by following this link here. In the article
here, this article describes some different options for Windows virtual machine pricing, and these will probably also apply to Lennox. Let's scroll down and see what our options are.
1st 1 is Paige, you go, which is what we're using for these demos. Basically, you end up paying for the compute used by the second, and as soon as the resource is done, you can tear it down and you won't be paying for the resource any further There are also reserved virtual machine instances.
This is basically paying up front for compute Resource is for a specific period of time, in this case, one or three years. In exchange, you get a reduction in the cost of the virtual machine because you're making that commitment upfront,
scrolling down a bit further. You can see some examples of that per our pricing for our different virtual machine sizes. For example, the burst of all of'em, or B one s is 10.4 cents per hour. Again, you don't have to memorize the pricing
for the exam. But I would definitely understand the different compute profiles that are available in which ones you would use in different scenarios
that does it for our introduction to virtual machines. Let's jump back over to the slides to wrap this up.
Coming up next, we're actually gonna jump back into our azure portal and will work at creating some virtual machines. See you in the next episode.