Availability set of VMS for Windows Azure experience

Today in a group to see a netizen sent a problem, the problem is described as follows:

Build four VMs on Windows Azure, all four machines are highly available
Turn off three after doing a good job, leaving a production, when the number of users to access large cup demand will increase, to a certain threshold after the automatic opening of a set of one more and then open a set, analogy down
Automatically shuts down a VM when the CPU drops to a certain threshold, then lowers and then shuts down, and then goes on.

This mechanism must be a necessary mechanism for the public cloud. On Windows Azure, this mechanism is called an availability set.

The explanation on 21V is that you can use multiple Windows Azure virtual machines to ensure the availability of your applications. Using more than one virtual machine in your application ensures that the application is still available when there are local network failures, local disk hardware failures, and any planned outages that the platform may require.

For specific details, please refer to: http://www.windowsazure.cn/zh-cn/manage/windows/common-tasks/manage-vm-availability/

Words are not much to say, good to use are verified.

1. I deployed two VMs to configure the load balancer set, so I can refer to my previous article http://gshao.blog.51cto.com/3512873/1600667

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/58/6B/wKioL1SvkY7xn66oAADDlJDxqzo704.jpg "width=" 935 "height=" 174 "/>

2. Create a new availability set

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/58/6B/wKioL1SvkY_jMEMgAAH1FQYBCsY919.jpg "width=" 1157 "height=" 564 "/>

3. Enter the name of the availability set;

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/58/6C/wKioL1SvkY_S_K14AACu2FXzMU8141.jpg "width=" 665 "height=" 305 "/>

4. Save the configuration to reconfigure the existing VMS to restart the operation.

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/58/6C/wKioL1SvkZCjV576AAFl7Vz4zOE074.jpg "width=" "height=" 402 "/>

5. Join the second VM in the availability set group

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/58/6F/wKiom1SvkM2DIB_LAAH7jX3eL6g050.jpg "width=" 1084 "height=" 616 "/>

6. Re-configuration complete

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/58/6F/wKiom1SvkM_iowOEAAFiXLuKPSU376.jpg "width=" 1168 "height=" 443 "/>

7. Configuring Auto-Scaling

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/58/6F/wKiom1SvkNDQOc_uAALHJSrms20652.jpg "width=" 1131 "height=" 564 "/>

8. The default is no scheduled time scaling

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/58/6F/wKiom1SvkNGQFWBgAAHHGGjKGOc926.jpg "width=" 1088 "height=" 535 "/>

9. Set the schedule time

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/58/6F/wKiom1SvkNHhvG32AACpmLskuqU537.jpg "width=" 1053 "height=" 164 "/>

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M02/58/6F/wKiom1SvkNLijkfPAAIY1EvPHnM933.jpg "width=" 714 "height=" 634 "/>

10. Configure how many instances are enabled, how many thresholds the CPU detects, and how many instances are scaled down when the CPU threshold reaches the scale of the instance, when the CPU decreases below the threshold.

650) this.width=650; "title=" image "style=" border-top:0px;border-right:0px;background-image:none;border-bottom:0 px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px; "border=" 0 "alt=" image "src=" http:// S3.51cto.com/wyfs02/m02/58/6f/wkiom1svkjhr1u53aahr4mjqmsq690.jpg "height=" 556 "/>

11. After saving, the second VM will be in a stopped state

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M00/58/6F/wKiom1SvkNOgWmoNAAHToWhoBMI025.jpg "width=" "height=" 537 "/>

12. After a period of 100%, the CPU triggers an autoscale mechanism to start a new VM. (PS: It took me about 50 minutes to start my own test time from the CPU at 100% to the VM boot.) It was a time of consternation . ）

650) this.width=650; "title=" image "style=" border-right-width:0px;background-image:none;border-bottom-width:0px; padding-top:0px;padding-left:0px;margin:0px;padding-right:0px;border-top-width:0px; "border=" 0 "alt=" image "src=" Http://s3.51cto.com/wyfs02/M01/58/6F/wKiom1SvkNSBQuRSAADNi7dVhu8588.jpg "width=" 945 "height=" 191 "/>

I can't find the point at which to modify this trigger mechanism at the moment, but the result of the current test is really pretty bad, and the next test session mechanism triggers the availability set. and the current Azure availability set is only for logical hardware load balancing, software synchronization data that block or need to be executed in the background, personally feel that on the basis of the availability set of the front-end, there must be a public database and database availability set.

This article is from the "Gs_hao" blog, make sure to keep this source http://gshao.blog.51cto.com/3512873/1601267

Availability set of VMS for Windows Azure experience