Sharon shows how to connect to other repositories to deploy updates to the DevTest environment and set up schedules to reduce costs.
- [Instructor] Earlier, when I demonstrated how a user could build a virtual machine, the list of possible operating systems was long. I find it's best to reduce the number of operating systems that the user can select from. To do so, you would configure this within the configuration and policies blade of your Azure DevTest Labs. As you can see, we have three choices in which to create our basis or, I like to say, restrict those images for our users.
First we have marketplace images. This list should look very familiar. These were all the choices that we could select from when creating our virtual machine. I like to restrict this list to the base images that the users need. Otherwise it just becomes very overwhelming. I'm gonna go ahead and click no. I'm gonna deselect everything and I'm gonna pick a couple of the images that our Dev users can build from. I'm gonna take an Oracle and let's say we are still on SQL Server 2014 SP2 Web edition.
Let's grab an Ubuntu Server 16.04 LTS and let's assume we have not moved up to server 2016 as of yet. Our environment is still on Server 2012 R2, therefore I'll select that base. And then don't forget to come up to the top and click save. Next, we can go ahead and configure custom images and formulas. The difference between the two being the custom image is an image on a VHD that cannot be altered. Whereas, a formula allows you to add in artifacts and other preconfigured settings into the base image.
In custom images, as you can see, I do not have any. I can go ahead and click add. I would add a name and a description. Select your OS type. If you're running Windows, you must sysprep up that virtual machine first. And then, next you could go ahead and pick your VHD if you had one or you could upload a VHD using PowerShell. And for those of you who are not familiar with Azure, you'll notice I keep saying VHD, not VHDX. As of this recording of April 2017, VHDX is not supported.
Because I don't have a VHD to work with, I'm just gonna go ahead and close that blade. Next we have formulas. These are images that we can build in artifacts into. To do so, click add, and you will notice that immediately our list of possible operating systems to choose from is now limited to the four options that we selected previously. I'm gonna go ahead and work with Server 2012 R2. I'm gonna provide a formula name. So this would be our standard base.
I like to add some details into my description. It makes it easier for those development users to pick the correct base. I'm gonna keep this really simple and my description will be, Server 2012 R2 with Chrome and Firefox. Again, you could add in more as required. You provide a username. In this case, I'm gonna provide the username of DevUser because this will be a formula. I'm gonna go ahead and pick the password. And you'll notice here that I don't have a choice. But I have to select it from the store.
So, please set that up prior to doing this. If I like to change that standard virtual machine size, I can now do so, but again you'll notice that I'm restricted to those four sizes. I'm gonna leave it as is. Therefore, I'm gonna go ahead and click on artifacts and I said I was going to install Chrome and Firefox. And click okay. Finally, I could go ahead and configure advanced settings if I wish to do so.
So, this is where I could come in and configure all that networking and all the IP addressing. With a standard base, we cannot turn on the automatic delete options as this is just a base. And I can make this base claimable if I wish to do so. I'm not gonna make any changes here. I'm gonna go ahead and close this blade and then go ahead and create the base. This isn't a virtual machine, it's the base for the virtual machine. It only takes a few moments for that base to be created.
And before we go ahead and create a virtual machine that will be claimable, I just want to point out the external resource options here. First of all, you could add in external repositories. The Public Repo is already enabled by default and you could go ahead and fill in the required information to add in your repository. I'm gonna go ahead and close that. And that would be the same for your virtual networks. You could go ahead and add in additional virtual networks and then you could select your virtual network.
Now, keep in mind, though, the virtual network has to be in the same subscription and region as your DevTest Labs. I'm gonna go ahead and close this, as I'm not gonna change my networking. I'm gonna go ahead and close the configuration and policies blade. Next, as the IT admin, I'm gonna go ahead and create a new virtual machine that will be claimable from our DevTest users. I'm gonna go ahead and click on add. The first thing I need to do is click a base.
I'm gonna go ahead and grab that standard base VM because I've already configured it with the artifacts. Our virtual machine will be DevVM. Our user will be that DevUser. I'm going to go ahead and use that secret password. I'm gonna leave everything the same with the exception of the advanced settings. The only thing I'd like to setup in the advanced settings is the expiration date and the claim options. I'm gonna go ahead and have this virtual machine expire on May 31st.
I'm gonna go ahead and make this machine claimable. Therefore, all of our development users have to do is login and claim this machine, because it's already configured for them. And I'm going to have four of these virtual machines ready to go for our users. Click okay and then click create. It will take several minutes for those virtual machines to be created. So, to recap, we restricted the virtual machine bases that our users could use when they're creating their own virtual machines.
And those bases could be from the Azure market place or formula image or, if I had had one, a custom image. Then I quickly showed you how we could configure the external repo and networking. And finally we ended it off by creating four claimable virtual machines.
- 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