In my previous post I showed how easy it is to start or deallocate machines using C# and Azure Functions.
Azure VirtualMachines can be handy but very costly if you forget to turn them off∗ and leaving them running for 24/7.
But, what if you have dozens of existing VMs and are looking for a quick way to schedule the on/off times for those machines to save money?
In this post I will show a very simple script to use with Azure Automation that enables you to get this up and running, literally within the hour.
Note: I would advise to use Azure DevTest labs if you have development virtual machines. That will give you the opportunity to reuse, claim or share VMs within a group of users.
* In this blogpost I will use the word Stop in code and comments, but in fact that will Deallocate the machines, and will stop incurring costs.
Continue reading “Cost optimization in Azure”
Managing VirtualMachines is often done using Azure Automation or PowerShell. But what if you want to do this using C#, in an Azure Function? This post shows a very simple example on how to implement this in a .Net Core 2 Azure Function.
This post contains my slides of my talk ‘ARM and Cloud Infra – The Secret Life of a Developer in a Infra World’ at devNetNoord.
Click here to download
In my current project I’ve stumbled upon a problem. We have many ARM templates and need to add tags to all resources. Doing this within templates can be cumbersome, so I’ve created a small VSTS extension that adds tags to all resources within a specific resource group.
The extension can be installed from https://marketplace.visualstudio.com/items?itemName=PeterRombouts.autotagging-extension
The working is pretty simple; enter the values for your subscription, and resourcegroup, and then add the tags.
The tag pairs should be entered, one pair per line, comma separated. The extension will add these tags to all resources in the given resource group, and will not do anything to the existing tags.
Remarks? Please do give feedback! The project is available on Github if you want to contribute!
In my work as Cloud Solution Architect I often find teams struggling with the exact same problem. In this blogpost I will highlight one of those problems; passing on ARM output variables within a VSTS pipeline.
Many developers have Powershell or other scripts in place, that fix this problem, but I want to highlight an extension, which is freely available and does this for you, for free!
This extension enables you to use the ARM Deployment outputs in your VSTS environment.
This step will use the last successful deployment within the selected resource group. If this deployment has outputs, all of them are copied to VSTS variables by the ARM Output key.
These outputs can then be used by default VSTS ways:
Usually this task is ran directly after the ‘Azure Resource Group Deployment’ task.
So my pro-tip; Stop using your own scripts and implement this handy extension!
PS: On a sidenote, Kees is also a great guy, give him a tweet after you install this in your project 😉
Link to Marketplace: https://marketplace.visualstudio.com/items?itemName=keesschollaart.arm-outputs
Kees on Twitter: https://twitter.com/keesschollaart
Azure Cosmos DB is a globally distributed, multimodel database service designed to help you achieve fast, predictable performance. It scales seamlessly along with your application as it grows.
This blog explains exactly how it works and what to do in some scenarios. But in my work as Cloud Architect I sometimes need to dig deeper and figure out if my solution scales for a particular case.
For example, a ‘partition’ has a maximum size of 10GB, so it is really, really important to understand how this works, and how you can figure out your partition size over the time.
This blog will explain, using a recent real-world scenario, how you can determine your partition key and scaling.
Please note that your scenario can differ hugely, but there are some takeways in this blog that could help you when designing your solution.