Learn how to create a virtual machine for DevTest Labs pointing out the various options that would be available prior to configuration.
- [Instructor] Let's first start by showing you what a user would have to do to create a VM in DevTest Labs without IT providing any configurations or settings. I'm still logged in to DevTest Labs, and I still happen to be logged in as an IT admin. I'm gonna go ahead and create a virtual machine, and this process would be very similar to what your developers would do when they access DevTest Labs. They would create, in "My virtual machines," if they wanted to create a new one, and then click add.
The first thing we need to do is choose a base. I'm gonna go ahead and actually maximize this blade and you'll notice that we have several bases we can choose from. We have BizTalk and CentOS and Debian and HPC Pack and Dynamics NAV and Oracle and Red Hat, and the list goes on and on. Let's take a look at SQL. We have several versions of SQL to pick from. We keep going and going, couple different versions of Ubuntu, Visual Studio, and then finally we get into Windows Server.
Your developer would have to know exactly which version base to choose from. In the case of Ubuntu, would they have to pick Ubuntu Server 16.04 or 16.10? Or in a case of Server, are they looking for Server 2012, 2012 R2, or 2016? As you can see there are a lot of choices here. For our demonstration, we're gonna go ahead and pick the Server 2012 R2. I'm gonna scroll over for a little bit clearer view.
Next we have to provide a name. I'm calling mine LILVM, we'll provide a username. This would be the administrator username. Next we can provide a password. We can use one of the saved secrets that we've already used or provide a value. I'm gonna go ahead and use the secret that we already saved. As you recall, we named it password and the actual password was "password123." Next, we can go ahead and pick our disk and size.
Again, from your developer point of view, they would have to come in and actually configure this themselves. They could go ahead and pick and SSD drive, and now they have free reign to pick whichever size they would like. As you can see, they have several choices to choose from here. They could pick a nice small DS1, that's only gonna cost us about $120 Canadian a month, or they may opt to go into a DS5 at about $1700 Canadian a month, and we can even go higher than that.
Here's a nice one, a DS15 at about $2200 Canadian per month. Right now, by selecting that, your company would be charged this. I'm gonna go ahead and stay with the standard DS1_v2 because I really would like to avoid a bill of about $2200 for a month. As I am not going to make any changes here, I'm gonna go ahead and close this blade. Yes I know, my changes are not going to be saved. Good. Next we're gonna go ahead and pick out our artifacts.
You can see we have a whole list of artifacts that we can apply to this VM. This means when the VM is built, these artifacts will already be installed on that VM. This doesn't have to be done after the fact. Let's go ahead and choose a PuTTY, click add. And I like to work in Chrome, so I'll go ahead and choose Chrome as well. Click add, and then click okay. I'm gonna scroll back over a little bit. Next, we have to go ahead and configure our advanced settings.
We can go ahead and pick our network or move it into another network if we wish. Next we could go ahead and configure our subnet, and then all of our IP addressing. One of the cool things that I really like is you can actually set up when this VM will be deleted, so you can set the date and time. Finally, is this virtual machine claimable? What this means is that we create the base and then we can duplicate that base x number of times for our users just to go ahead and grab. To do that you click yes, and then the number of instances.
As I am not going to set this up here, I'm gonna go ahead and close the blade. Yes, I'm gonna be warned that my changes will not be saved. That's it, I'm gonna go ahead and click create, and it'll take about 10 minutes for this VM to be created. As you can see, this is all well and good, but our users pretty much have full reign over these virtual machines and the point of DevTest Labs is for you, as an IT administrator, to be able to control and provide the correctly sized and configured virtual machines to our users, and that's what we'll configure next.
- Configure DevTest
- Create the Azure DevTest Lab
- Create a DevTest Lab virtual machine
- Set policies, users, and schedules
- Configure and create virtual machine bases
- Remove Azure DevTest Lab