Leveraging the power of Powershell, its easier than ever for an EMC customer to leverage their on-premise investment in Hyper V and EMC VNX, say, and the power of Microsoft's cloud offering, Azure. While many of our customers are leveraging Hyper V 2012 to manage their INTERNAL cloud, the embrace of a Hybrid model is still in the very early stages.
Here's how to get your feet wet and see how this thing drives.
Please note that you will need a Windows Azure account with an active subscription. You can start a free trial subscripting by visiting the following site:
It will require a credit card, but this is primarily for Identity Verification!
Once the account is active and you have an active subscription, you can proceed with your Powershell experimentation pretty easily. Download the powershell bits and bobs at the following location:
You are looking for Windows Powershell under the command line tools section. Once the installation has completed, you are ready to rock and roll! Open up the appropriate Powershell window by going to the Windows Azure folder in you start button programs and clicking on Windows Azure Powershell:
Execute a get-module command and you will see that there is a loaded module – appropriately named Azure – ready for business. Now, I want to connect it to my active Azure account. To achieve this, it’s as easy as typing:
PS C:\> Add-AzureAccount
Without parameters, it will open up an Authentication window that you enter your Windows Live Azure account credentials to:
That’s it. You are now ready to run some stuff against your Azure cloud account. Let’s say you want to see what locations are available to place my planned new VM. To see what’s available, I simply type:
PS C:\> $location = Get-AzureLocation
To see what VM Images are available in the service catalog, simply type:
PS C:\> $images = Get-AzureVMImage
At the time of this blog post, there are over 209 VM base images that are available – right out of the gate. Windows and Linux are the available platforms (multiple flavors of each). Take a look at the list of whats available by typing something like the following:
PS C:\> $imagelist | format-list label,description,imagename,os
This will list some descriptive fields of the object list. There are images with SQL Server 2012 Preview Edition pre-loaded, SQL 2014 Data Warehouse Preview Edition, etc. Obviously you could search the labels for what you need to make this very dynamic (but that’s outside of the scope of what we are doing today). Platforms and OS listed below:
SQL Server 2008
Windows 2012 and R2
SQL Server 2012
SQL Server 2013
SUSE Linux Enterprise 11SP3
BizTalk Server 2013
Oracl Linux 64
Oracle 11 and 12 are available, running on the Windows Platform. We know this by checking the underlying OS in the list provided above. Very interesting seeing what’s available in the catalog. Now that I have an idea of what’s available in the catalog, as well as the possible locations for them to reside, I need to start defining the service name and the password of the Administrative account. These can be simple strings.
PS C:\> $mySvc = "myservicename"
PS C:\> $myPwd = "yourpassword"
Ready to deploy a VM! Here is what the command line looks like:
PS C:\> New-AzureQuickVM -Windows -name "SomeVMName" -ImageName $imagelist.imagename -ServiceName $mySvc -Location $locations.name -Password $myPwd
Pretty simple, powerful – and ready to play with. I literally had this up and going in around 15 minutes – from opening the account, downloading the powershell bits, to deploying workstations in the “Cloud”.
You have the option of uploading your own sysprepped images to cloud BLOB storage, and leveraging your own optimized images as well. With Orchestrator Runbooks and System Center Operations Manager plugins, its an interesting approach to Hybrid Cloud.