Skip to main content

Windows Azure announcement: Per Minute Billing and No Charge for Stopped VMs

I think the Windows Azure team never sleeps because they keep releasing new features at an incredible pace.

Last week Scott Guthrie announced some great enhancements to Windows Azure:

  • Dev/Test in the Cloud: MSDN Use Rights, Unbeatable MSDN Discount Rates, MSDN Monetary Credits
  • BizTalk Services: Great new service for Windows Azure that enables EDI and EAI integration in the cloud
  • Per-Minute Billing and No Charge for Stopped VMs: Now only get charged for the exact minutes of compute you use, no compute charges for stopped VMs
  • SSL Support with Web Sites: Support for both IP Address and SNI based SSL bindings on custom web-site domains
  • Active Directory: Updated directory sync utility, ability to manage Office 365 directory tenants from Windows Azure Management Portal
  • Free Trial: More flexible Free Trial offer

The one feature I liked the most(and my credit card will agree) is the Per Minute Billing and No Charge for Stopped VM's.  Before when you stopped a VM(without deleting it), Microsoft continued to bill you for the VM. With this update, when you stop a VM you are  longer charge you any compute time for it while it is stopped. And all deployment data and configuration is safely stored.

The other one is that the pricing model changed from per-hour to per-minute. Before when you ran a VM for 6 minutes, you would still be charged for a full hour of usage.  With the new pricing model, you only pay for the actual 6 minutes of compute usage.

Keep going guys!

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more