Azure Cloud

Autoscaling using custom image

I_vanl — Wed, 22 Feb 2017 14:33:47 GMT

With recent announcements like Managed Disks and Images, I thought it would be cool to put a script together. It will provision a VM Scaleset using a custom image that is captured from an existing server with existing applications and add autoscaling to it! The general steps are to

take a copy of the existing virtual machine. I use Azure Storage Explorer as my favourite tool.
run sysprep and generalise it. "Sysprep /generalize /shutdown /oobe"
run the powershell to set it generalise.
Set-AzureRmVm -ResourceGroupName $rgName -Name $vm.Name Generalized
In Azure Portal, Images, create a new image pointing it to the generalised VM.
in Azure Portal, Templates (Preview), add the attached custom deployment template and deploy it

Once the VM Scaleset is provisioned, you can see the Overview for the autoscaling information. RDP into the VM using the public IP address shown but set the port to 50000. Then download a CPU Stress tool and run it. After a few minutes, autoscaling will provision more instances. This is a POC script so feel free to modify it. Let me know if you have any questions. -- I-van;

Renaming a vhd or blob file

I_vanl — Thu, 18 Feb 2016 18:17:11 GMT

Here is another useful script I use when the portal or Storage Explorer doesn't have the ability to rename files. Remember to replace all the highlighted in red and italics with the correct names. Warning: This creates a copy with the new name and deletes the original blob.

#obtain the storage account context $Context = New-AzureStorageContext -StorageAccountName "storage1" -StorageAccountKey "ExampleKeyk1213hi2" #obtain the access key from settings of the storage account. Start-AzureStorageBlobCopy -SrcContainer "SourceContainerName" -DestContainer "DestinationContainerName" -SrcBlob "SourceVMOS.vhd" -DestBlob "NewVMOS.vhd" -Context $Context -DestContext $Context Remove-AzureStorageBlob -Container "SourceContainerName" -Context $Context -Blob "SourceVMOS.vhd"

Disclaimer: The sample scripts are not supported under any Microsoft standard support program or service. The sample scripts are provided AS IS without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages.

Registering and launching a VM from a vhd file

I_vanl — Thu, 18 Feb 2016 18:03:40 GMT

Once a vhd file is uploaded or migrated to the target blob container, you may be wondering how to register and launch the VM. Here is the powershell script which I use. This method doesn't require sysprep. Disclaimer: Note that there are no warranties and these and other scripts are shared for personal use only. If you do find any improvements or bugs, please provide comments and feedback. Steps: Launch Powershell ISE. Copy and paste the script below. Replace the highlighted text in red with the correct names before executing the script.

Login-AzureRMAccount Select-AzureRmSubscription -SubscriptionName SubscriptionName $resourceGroupName = "ResourceGroupName" $location = "australiaeast" #this is an example location for Australia East region $vmName = "TestVM" # Specify the VM name $virtualNetwork = "VNet1" # Specify the virtual network name $publicIPAddressName = "TestVMPIP" $networkInterfaceName = "TestVMNIC" $vmSize = "Standard_A1" # Specify the OS disk $diskName = $vmName #suggestion is to use the VM name $osDiskUri = 'https://storage1.blob.core.windows.net/vhds/TestVMOS.vhd' #you can obtain this from properties of the vhd file using Storage Explorer $vnet = Get-AzureRmVirtualNetwork -Name $virtualNetwork -ResourceGroupName $resourceGroupName $pip = New-AzureRmPublicIpAddress -ResourceGroupName $resourceGroupName -AllocationMethod Dynamic -Location $location -Name $publicIPAddressName $nic = New-AzureRmNetworkInterface -ResourceGroupName $resourceGroupName -Location $location -Name $networkInterfaceName -PublicIpAddressId $pip.Id -SubnetId $vnet.Subnets[0].Id $vm = New-AzureRmVMConfig -VMName $vmName -VMSize $vmSize $vm = Add-AzureRmVMNetworkInterface -VM $vm -Id $nic.Id $vm = Set-AzureRmVMOSDisk -VM $vm -Name $diskname -VhdUri $osDiskUri -CreateOption Attach -Windows $result = New-AzureRmVM -ResourceGroupName $resourceGroupName -Location $location -VM $vm

Moving, copying and uploading VHDs between Azure Subscriptions

I_vanl — Tue, 09 Feb 2016 23:13:15 GMT

Good day, One of the easiest tools I found to move, migrate or upload VHDs between different or up to storage accounts is Storage Explorer found at the bottom of the page at https://azure.microsoft.com/en-us/downloads/. Its a simple copy and paste from source to destination blob vhds containers. With this tool, you can right click to Get Shared Access Signature on the blob file to provide a time limited secure link to download the file for example. Next up is I will share a powershell script on registering and launching the VM once you have migrated the vhd file to the target container.