The demonstration will feature an overview of Azure virtual machines and creating an Azure virtual machine from a template. Sharon will also discuss the virtual machine settings and configuration options both during the creation of the virtual machine and after deployment. Adding a virtual disk to the virtual machine will be demonstrated.
- [Instructor] We're gonna go ahead and create a virtual machine. As I have already mentioned, I like to do this from the resource group. We're gonna use our resource group mscloud, I'm going to go ahead and just click Add. In my case I'm just gonna go ahead and type server. I know I'm looking for Server 2012 R2, but I wanna show you some of the other templates that are available to you. You'll notice here we have Ubuntu Server, we have a full SQL Server ready to go, for those of you who like Minecraft, a Minecraft Server is available to you. We have Chef in there, and again, the list goes on.
For this demo I'm gonna go ahead and select 2012 R2. I'm going to be deploying this to the Resource Manager, and I'm gonna go ahead and give it a Name. As I already have one server called mscloud within this resource group I'm gonna go ahead, create a second one, and this will be a file server. Now we can go ahead and select the type of disk we wanna attach to this virtual machine. We can either go ahead and select an SSD, solid-state, or a hard disk, the standard magnetic drives. I'm gonna go ahead and pick the magnetic drive.
We're gonna provide a User name and Password. This is the administrative User name and Password for the virtual machine. You will have to follow Microsoft convention in assigning this User name and Password, you cannot use a User name of administrator and Password of password. Select your Subscription. Because I've gone ahead and created the virtual machine from within the resource group the resource group is already populated for me. I'm gonna click OK. Our next step is to select the virtual machine size. The algorithm will suggest a couple of sizes for us, or you can go ahead and View all.
I'm gonna go ahead and click View all. I would like to show you all the different options for your virtual machines. So a couple of the conventions here I want to point out. A D machine will be your SSD drives, and a Standard will be a production machine. If I scroll down we're gonna come across to some A drives. A series are your magnetic disks, and then you're also going to have a Basic. So these are Standards, and then we'll have our Basic disks in here as well, there we are. The difference between a Basic and a Standard virtual machine, Basic is recommend for test and dev and really light workloads.
For your regular production environment you're gonna be picking a Standard or a higher virtual machine. For our demo I'm gonna go ahead and select an A1. I also wanna point out before I go ahead and select this is you can see the specs for those virtual machines, select the virtual machine that meets your needs now and will meet your needs in the future. I'm gonna select an A1 Standard. The Storage account will be automatically provisioned for me. My Network settings will be prepopulated, again, because I have created this from the resource group, which already had that virtual network created in it.
If I wanted to change which Subnet I wanted to put this server in I can go ahead and do so. I'm just gonna leave it in the Frontend for our demonstration. I'm gonna go ahead and leave all the other settings as is, click OK. Our configuration will now be validated and we can go ahead and click OK to provision this virtual machine. This could take seven to 10 minutes, so it's a good time to go have a cup of coffee. As we can see, our server is deploying. I'm gonna go ahead and check the resource group to see if it's actually up and running at this point.
And here's our new virtual machine, and yes, we can see it is Running. We can see the Size that we selected, we can see our Public IP address, and the network the virtual machine is sitting in. Within the Settings of the virtual machine we can go ahead, look at some diagnostics, we can look at the Resource health, we could Reset the password. What I wanna focus in on is how do we attach a disk to our virtual machine? I'm gonna go ahead and click the Disks tab, and now I wanna go ahead and attach a data disk to my virtual machine.
Microsoft recommends attaching a data disk to every virtual machine. You will notice in your virtual machine you will have a D drive. That D drive is a scratch disk only and will be recreated when the virtual machine is rebooted. Therefore, if you put data on that D drive there is no guarantee that that data will be persistent. To avoid that we attach a new disk. You can go ahead and give it a Name. I'm gonna leave the default. I'm gonna go ahead with an HD disk. And then you can pick your Size.
The maximum size for a data disk for a virtual machine is one terabyte. I'm gonna go ahead and just leave it at the one terabyte limit. I'm gonna select the defaults for the rest. This will take a few moments. As that's provisioning you will also notice we have Attach existing. If you have a data disk that you have used from a previous virtual machine you can attach that to this new virtual machine. Our data disk has now been provisioned. Depending on the virtual machine that you selected you will have a specific number of virtual disks that you can actually attach to that virtual machine.
In the case of Server 2012 R2 you can go ahead and provision those disks under storage spaces. Using storage spaces will allow you to pull those disks as required. The one last thing I wanna show you here is Size. You can go ahead and resize your virtual machines as necessary. If I wanted to resize this virtual machine I would go ahead, select the size that I wanted to resize it to, and then click Select. Please note that a resize will require a reboot, so your machine will be down during this process.
The exception to this rule is if you have configured your virtual machines in an Availability set. As you will recall, an Availability set allows us to have two virtual machines configured at the same time, ensuring that if one machine goes down the other one is always up. In the case of resizing or autoscaling in an Availability set one machine is always up. And that is guaranteed by Microsoft and through the SLA. As you can see, creating virtual machines in Azure is quick and easy and completely flexible.
You can modify these virtual machines as need be as you move forward in your Azure deployment.
- Understanding cloud technologies
- Why Azure?
- Creating virtual networks and storage
- Using Azure Active Directory for identity management and protection
- Disaster recovery with Azure Backup and Azure Site Recovery
- Working with virtual machines