Skip to content

When deploying a Failover Configuration, create an Availability Set #48

Description

@jberkers42

Is your feature request related to a problem?

Microsoft Azure provides Availability Set functionality to place members of clustered or like servers into different failure and maintenance domains. The previous v1 templates used to place cluster members into an availability set, the v2 templates do not.

Once deployed, a vm cannot be moved to an availability set, this can only be done at deploy time.

Describe the solution you'd like

Ideally the uniqueString would be used as part of the availabilty set name, and it should be created automatically as part of the ARM Templates.

Describe alternatives you've considered

We could consider modifying the failover template to create the availability set, and add the nodes to it, however, this would also entail updating the standalone module to add a parameter when deploying the individual cluster members.

Additional context

Placing the cluster members in different failure and maintenance domains using an Availability Set reduces the chances that both members of a cluster are down due to being co-hosted within the same domains due to either maintenance or an Azure infrastructure issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions