Learn how the Azure DevTest Labs environment looks and feels from the viewpoint of the developer. Discover how to claim and customize a virtual machine for the developer, as well as create a new virtual machine.
- [Instructor] Everything we've done so far has been as me, the IT admin. Now let's go ahead and take a look at what Azure Dev Test Labs looks like to the development user. I'm going to go ahead and sign out. I will now go ahead and login as Watson. As you may recall we setup Watson as a user for Dev Tests Labs. As Watson I will go ahead and launch the Dev Test Lab and Watson's screen will look very similar to the screen that I had.
With the exception of Watson does not have any current virtual machines and he can also not change anything within the configuration and policies. So you'll notice that he cannot make any changes here. I'm going to go ahead and close this blade and back to the overview. Remember those claimable virtual machines we created in the last lesson. These are now available to our users. Watson can now go ahead and claim this virtual machine. So he can pick one and then go ahead and click claim.
Now this virtual machine will be Watson's and our list of claimable virtual machines will have dropped down to three from four. This virtual machine will now be assigned to Watson and will be put into the running state. Once the virtual machine has been claimed and is put into the running state that virtual machine is now moved under my virtual machines or Watson's virtual machines, and you'll notice that the number of claimable virtual machines, like I said, will now be reduced.
Let's go ahead and take a quick look at this virtual machine. You'll notice that Watson did not have to do anything to this virtual machine at all. The resource group is already assigned as is a network. The RDP port has already been configured. The size in the operating system have also been configured and remember we set an expiration date on this virtual machine on May 31 of 2017 this virtual machine will expire. Let's go ahead and take a look at the artifacts.
We included the two artifacts into the base that we used for this virtual machine. So Chrome and Firefox are already installed, but what if Watson wants to add in another artifact. To do so you would click on apply artifacts and then go ahead and choose the artifact that he would like to apply. Let's go ahead and use seven zip. Click add and apply and now that artifact will be applied to this image.
And that'll take a few moments. Next let's go ahead and click on disk. If you have taken any of my Azure courses you've probably heard me talk about attaching disks to your virtual machines. That is a Microsoft best practice and I would highly recommend that you do that here as well. Microsoft recommends that you do not install anything on the OS disk that is included with your virtual machine. To add a disk you would go ahead and click attach new, provide a name for your disk, and the size, and click okay.
That data disk will now be attached to that virtual machine. When you need to delete that virtual machine you could actually detach that data disk and then use it again on another virtual machine. One thing I do want to point out here there seems to be a little bit of a glitch. If you do not see the attach new and attach existing sign out and sign in again. Watson could also create a reusable base based off this image that he has been creating and working with. So his new base would be the server 2012 R2 with Firefox and Chrome installed and the artifact seven zip, which we just added.
I'm not going to go ahead and do that so I'll close the blade. As you can see Watson had a virtual machine already up and running based off an image that we created as the IT admin. I'm going to go ahead and close this blade and finally Watson can go ahead and create his own virtual machine and I can do that using add. Watson can now ago ahead and choose any of the four marketplace Azure images that we allowed as the IT admin or he could go ahead and pick the standard base VM.
For our demo Watson will go ahead and create one off the 2012 R2. Here he can add in all that customization that he needs. So this will be Watson's VM, his user name will be Watson, he can provide his own password. Next he can go ahead and pick his virtual machine size. Again, remember that we restricted these. For our demonstration purposes I'm going to go ahead and just close this blade.
He can add in the artifacts for this virtual machine for his needs. So let's go ahead and add in Azure Powershell. Click add and then click okay. Watson still has the ability to configure the advanced settings. I'm going to go ahead and close that and then he can go ahead and create that image. So within a few minutes Watson was able to claim a virtual machine that we had already pre-configured and he was able to create a virtual machine based specifically for his needs.
From the developers point of view this is fantastic, this is self service, everything is there simply setup and ready to go. This makes it incredibly easy for our developers to focus on development and not configuring 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