Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Cloud Witness #37

Closed
michaelseto opened this issue Mar 14, 2017 · 6 comments · Fixed by #153
Closed

Support for Cloud Witness #37

michaelseto opened this issue Mar 14, 2017 · 6 comments · Fixed by #153
Labels
enhancement The issue is an enhancement request. resource proposal The issue is proposing a new resource in the resource module.

Comments

@michaelseto
Copy link

Hey All!

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

Thanks!

Michael

@michaelseto
Copy link
Author

Any updates on this?

@johlju
Copy link
Member

johlju commented Jun 8, 2017

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?

@johlju johlju added enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community. resource proposal The issue is proposing a new resource in the resource module. labels Jun 8, 2017
@brwilkinson
Copy link

brwilkinson commented Jun 13, 2017

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:

  • Endpoint
    An optional String, The Default EndPoint should be: core.windows.net

  • Cluster
    An optional String, The default should leave this off, it will find the cluster on the local machine

  • StorageAccountAccessKey
    A Mandatory Credential (or String) StorageAccountAccessKey (only the password from the credential is used as the Key)

  • AccountName
    A Key String


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
Copy link
Member

johlju commented Jun 14, 2017

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

To all: Any takers making this resource? 😄

@flouwers
Copy link
Contributor

flouwers commented Oct 4, 2017

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

@johlju
Copy link
Member

johlju commented Oct 26, 2017

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

johlju pushed a commit that referenced this issue Jan 8, 2018
- Changes to xClusterQuorum
  - Cleaned up tests which was using over complicated evaluation code.
  - Added cloud witness (Azure storage) functionality on Windows 2016 (issue #37).
@johlju johlju removed the help wanted The issue is up for grabs for anyone in the community. label Jun 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request. resource proposal The issue is proposing a new resource in the resource module.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants