Juju on Azure does not support Availability Sets

Bug #1229411 reported by Antonio Rosales
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Andrew Wilkins

Bug Description

On Azure if two VMs are part of a highly available set then they need to be placed in the same cloud service and be a named availability set. Otherwise Azure may take down all VMs that are providing high availability at the same time. In fact, Azure will today attempt to take down all VMs that are not in a named availability set at one time in order to quickly update the VMs that appear to Azure as single instance VMs.

Without support for availability sets in Azure Juju cannot be used for any application that requires high availability at all times.

More information at availability sets on Azure can be found at:
http://www.windowsazure.com/en-us/manage/windows/common-tasks/manage-vm-availability/

-thanks,
Antonio

John A Meinel (jameinel)
Changed in juju-core:
importance: Undecided → High
status: New → Triaged
tags: added: azure
Curtis Hovey (sinzui)
tags: added: azure-provider
removed: azure
Andrew Wilkins (axwalk)
Changed in juju-core:
assignee: nobody → Andrew Wilkins (axwalk)
milestone: none → 2.0
Andrew Wilkins (axwalk)
Changed in juju-core:
status: Triaged → In Progress
Andrew Wilkins (axwalk)
Changed in juju-core:
status: In Progress → Fix Committed
milestone: 2.0 → 1.19.0
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.