As a part of our continued backend enhancements, we have now developed a sooner strategy to resize digital machines on our platform and considerably lower downtime throughout routine upkeep when transferring a VM to a special host. This was achieved partly by means of our objective to design dwell and chilly migrations to make use of the identical job kind. 

All through the lifetime of your server, it’s possible you’ll have to resize your VM, change your plan kind, and even transfer to a different Akamai knowledge heart. Periodically, Akamai might also want to maneuver VMs to rebalance hosts or carry out routine upkeep.

Earlier than as we speak, there have been two kinds of migrations on Akamai’s compute platform:

• Stay Migrations – With a VM powered on, we will transfer it to an identical host inside the similar knowledge heart with no down time.
• Chilly Migrations – With a VM powered off, we will resize it or transfer it to a special knowledge heart. This usually incurs vital downtime, particularly for bigger VMs.

We added a 3rd migration kind: heat migrations. Heat migrations enable VMs to stay powered on by means of most of a transfer, decreasing the downtime to lower than one minute. Like most cloud suppliers, Akamai runs a combined fleet atmosphere, and we now have an answer to relocate VMs rapidly to totally different hosts. This will even allow a quick resizing or altering from shared or devoted plans to premium situations, which assure a selected processor mannequin or newer.

Heat migrations got here from the method of streamlining and growing the reliability of chilly migrations, which is one other replace we will proudly announce as we speak. All of those make up our unified migration platform. 

Stay and chilly migrations now use the identical job kind and run as a single job slightly than a number of unbiased jobs that may succeed or fail. This removes any potential errors brought on by a VM current on two methods after a migration job completes and the method won’t regulate the state of the report or the supply host till the disk and state have been efficiently synced to the vacation spot host. This considerably decreases the potential want for handbook intervention from our help crew when transferring a VM to a different area.

In abstract, we have now much less overhead to keep up and can have a better time with upkeep and rebalancing duties. For you, this implies:

• Heat migrations can transfer a VM to a different host in the identical knowledge heart in below one minute.
• Considerably much less downtime when resizing a VM or altering your plan.
• Considerably much less downtime once we rebalance or improve our fleet.
• Vastly elevated reliably when migrating from one knowledge heart to a different.

Sources