dsccommunity / FailoverClusterDsc

This module contains DSC resources for deployment and configuration of Windows Server Failover Cluster.
MIT License
60 stars 54 forks source link

Support for Cloud Witness #37

Closed michaelseto closed 6 years ago

michaelseto commented 7 years ago

Hey All!

Are you working on adding a DSCResource for adding a cloud witness for those in Azure?

Thanks!

Michael

michaelseto commented 7 years ago

Any updates on this?

johlju commented 7 years ago

No work is being done what I know of. But we are happy if you suggest how a resource could work. Should this be added to an existing resource, or is it an entire new resource. Do you have suggestion on the parameters needed?

brwilkinson commented 7 years ago

The documentation for the cloud witness is here: https://docs.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness

The following Cmdlet supports setting the cloud witness

FailoverClusters\Set-ClusterQuorum -CloudWitness -AccountName -AccessKey -Endpoint

Parameters should be:


The current resource xClusterQuorum could likely not just be extended, by adding CloudWitness to the Type. (Since the parameters don't match, since the key would not fit on the current Types) [Type = [string]{ CloudWitness | DiskOnly | NodeAndDiskMajority | NodeAndFileShareMajority | NodeMajority }]

So new resource would most likely be required:

xClusterQuorumCloudWitness [String] #ResourceName
{
      AccountName = [String]
      [EndPoint = [String]]
      StorageAccountAccessKey = [Credential]
      [Cluster = [String]]
}

To test and validate use the following:

Get-ClusterQuorum | select *
Cluster QuorumResource QuorumType
SQL01 Cloud Witness Majority
johlju commented 7 years ago

@brwilkinson Thanks for that detailed information. Agree that this suits best as a new resource.

To all: Any takers making this resource? 😄

flouwers commented 6 years ago

Hello ! I made some adaptation on a local branch and implemented this functionality. How can I publish this ?

johlju commented 6 years ago

@brwilkinson do you have any thoughts on PR #153?