Skip to main content

Azure Development Environment - Control when an Azure VM runs

Azure Development Environment Series:
In the last post we talk about how we can reduce the cost of Azure development environment of a small team by using an Azure VM to store all the databases that are needed by developers.
In this post we will see how we can optimize the cost of this Azure VM, by running it only when developers are active.

Context
Usually the development team works from 08:00 AM to 07:00 PM. Don't imagine that they stay for 11 hours at work. We have colleagues that comes at 08:00 AM and leave at 04:30 PM, others are coming at 10:00 AM and will stay until 07:00 PM.
Based on this information we observe that between 07:00 PM to 08:00 AM nobody is working. This means that the Azure VM is not required to run in this time interval.
There are 12h (plus 1h buffer) when nobody is working, when we could stop our VM. This means that we can reduce the costs for this service with 50%. At 07:00 PM we could shut down the VM and at 07:30 AM to start the VM again.

Manual
One solution is to talk with the team and the last person that leave the office should shut down the VM and in the morning the first guy that arrives at the office should start the VM. It will work, but why we should do this manually.

Azure Dev-Test Labs
A clean and nice solution for our problem is Azure Dev-Test Labs. This allow us to specify a time when the VM should shut down automatically. This can be done by defining a policy related to that specific VM (https://azure.microsoft.com/en-us/documentation/articles/devtest-lab-set-lab-policy/#set-auto-shutdown). Unfortunately, it doesn't allow us to start the VM automatically. In the morning we will still need somebody to start the VM.
  

Azure Automation
Another approach to automate this tasks is to use Azure Automation. This service enable us to run any kind of power-shell script directly from Azure. On top of this, we can specify when a task to be run.
We need to create two different runbooks. One that will run every morning and will start the VM and another in the evening that will shut down the Azure VM. 
To be able to access and control your subscription, you will need to add your credentials to the Azure Automation. The most simple way is to create a new Automation account and use your certificate for credentials. 
Once you done this, you can create the runbook for starting the VM. Don't forget to link the new runbook to the automation account that you created a step before. After this, you can add the power-shell script that start the VM (script can be found at the end of the post). 
The last step is to link the runbook to scheduler (a new one or to an existing one). This can be done from the Schedule tab of the runbook.

A scheduler can run only one time (at a time specific by us), hourly or daily. In the last two cases we can specify recurrence time (hours/days) and an expiration time. We cannot specify the day of the week when we want our runbook to run, but from the script we can check if is working day or not (see in the scripts).
A nice feature of Azure Automation is the price. First 500 minutes are free. In our case, the start operation takes around 10 minutes and the stop operation takes around 5 minutes. It means that we are consuming 450 minutes. Don't bother for price per minute because is very cheap -  0.0017e per minute (0.102e per hour). 

Conclusion
We identify that we need an Azure VM that is used by development team only only for 12h per day. We looked at 3 different ways to control when the Azure VM should run (manual, Azure Dev-Test Labs, Azure Automation). In this moment Azure Automation is the one that offers us all the capabilities that we need to automate this with minimal effort.


Start the VM:
workflow start-devsql-vm
{ 
    Param (  
        [parameter(Mandatory=$true)] 
        [String] 
        $VirtualMachineName,
        
        [parameter(Mandatory=$true)] 
        [String]
        $ResourceGroupName 
    )  
    
    $day = (Get-Date).DayOfWeek
    if ($day -eq 'Saturday' -or $day -eq 'Sunday'){
        exit
    }
        
    $SubscriptionName = Get-AutomationVariable -Name "SubscriptionName" 
    $SubscriptionId = Get-AutomationVariable -Name "SubscriptionID" 
    $CertificateThumbprint = Get-AutomationVariable -Name "CertificateThumbprint" 
    
    $TenantId = Get-AutomationVariable -Name "TenantId"
  $CertificateThumbprint = Get-AutomationVariable -Name "CertificateThumbprint"
    $ADApplicationId = Get-AutomationVariable -Name "ADApplicationId"
    
    $certificateName = Get-AutomationVariable -Name "CertificateName" 
    $certificate = Get-AutomationCertificate -Name $certificateName  
    
    # Set subscription profile
    Set-AzureSubscription -SubscriptionName $SubscriptionName -SubscriptionId $SubscriptionId -Certificate $certificate

    # Select subscription as the current context
    Select-AzureSubscription -SubscriptionName $SubscriptionName
    
    # Login to Azure Resource Manager
    Add-AzureRmAccount -TenantId $TenantId -ServicePrincipal -CertificateThumbprint $CertificateThumbprint -ApplicationId $ADApplicationId  
    
    $vm =  Get-AzureRmVM -Name $VirtualMachineName -ResourceGroupName $ResourceGroupName -Status  
    
    # Starting the virtual machine  
    Start-AzureRmVM -Name $Virt$VirtualMachineName -ResourceGroupName $ResourceGroupName 
}

Stop the VM:
workflow stop-devsql-vm
{ 
    Param (  
        [parameter(Mandatory=$true)] 
        [String] 
        $VirtualMachineName,
        
        [parameter(Mandatory=$true)] 
        [String]
        $ResourceGroupName 
    )  
    
    $day = (Get-Date).DayOfWeek
    if ($day -eq 'Saturday' -or $day -eq 'Sunday'){
        exit
    }
        
    $SubscriptionName = Get-AutomationVariable -Name "SubscriptionName" 
    $SubscriptionId = Get-AutomationVariable -Name "SubscriptionID" 
    $CertificateThumbprint = Get-AutomationVariable -Name "CertificateThumbprint" 
    
    $TenantId = Get-AutomationVariable -Name "TenantId"
  $CertificateThumbprint = Get-AutomationVariable -Name "CertificateThumbprint"
    $ADApplicationId = Get-AutomationVariable -Name "ADApplicationId"
    
    $certificateName = Get-AutomationVariable -Name "CertificateName" 
    $certificate = Get-AutomationCertificate -Name $certificateName  
    
    # Set subscription profile
    Set-AzureSubscription -SubscriptionName $SubscriptionName -SubscriptionId $SubscriptionId -Certificate $certificate

    # Select subscription as the current context
    Select-AzureSubscription -SubscriptionName $SubscriptionName
    
    # Login to Azure Resource Manager
    Add-AzureRmAccount -TenantId $TenantId -ServicePrincipal -CertificateThumbprint $CertificateThumbprint -ApplicationId $ADApplicationId  
    
    $vm =  Get-AzureRmVM -Name $VirtualMachineName -ResourceGroupName $ResourceGroupName -Status  
    
    # Stopping the virtual machine  
    Stop-AzureRmVM -Name $Virt$VirtualMachineName -ResourceGroupName $ResourceGroupName -Force
}

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP