CODEWITHSUNDEEP
azureload-balancingazure-vm-role
Aviator
Aviator

Reputation: 92

balancing vM in azure

For my project i have to do deploy two(or more distances)VM instances in azure. I want at the start to be active just the first instances, and after some people "visiting" (example 2000) then if it comes the 2001 person to come active the second instance of VM. What i have to do this property to work. I hope you will help me about this problem! Best regards

Upvotes: 0

Views: 203

Answers (3)

jdhurst
jdhurst

Reputation: 4395

In addition to the solution @Igorek provided, there's a built-in auto-scaling & diagnostics data addon in Azure, called MetricsHub which Microsoft recently purchased. It's free with your Azure subscription, and offers a lot of real-time diagnostic information and auto-scaling based on configurable percentages. For whatever reason, the diagnostic data that MetricsHub shows you is much more current than the data that Azure's Monitor tab reveals - generally by about 20 - 40 minutes!

To find MetricsHub, navigate to the Azure portal, and choose New and then select MetricsHub in the Store section.

Upvotes: 0

Igorek
Igorek

Reputation: 15860

If you're not looking to do the actual coding yourself and would prefer to outsource the auto-scaling and monitoring to a 3rd party, consider using AzureWatch @ http://www.paraleap.com - it has support for a gazillion way to aggregate and execute scaling actions, send alerts when stuff goes wrong, monitor not only your CPU utilization but also SQL Azure, Azure Storage, and a ton of other stuff.

Upvotes: 0

David Makogon
David Makogon

Reputation: 71121

The easiest way to get started is with the auto-scale application block (Wasabi). You can easily add this to your project via Nuget in Visual Studio:

Install-Package EnterpriseLibrary.WindowsAzure.Autoscaling

Here's the menu item to get to the package manager commandline: enter image description here See this Nuget page for more information.

Wasabi lets you easily set up rules for scaling. Rules can be time-based, perf-couter based (maybe you can examine one of the asp.net counters to measure current activity?), queue-size based (though that doesn't fit your requested scenario), custom perf counters, etc. the Wasabi page I pointed to above has full documentation on setting it up.

Upvotes: 1

Related Questions