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

fix: add support for vsan file services #94

Conversation

burnsjared0415
Copy link
Contributor

@burnsjared0415 burnsjared0415 commented Feb 15, 2024

Summary

Added support to PowerManagement-ManagmentDomain.ps1 and PowerManagement-WorkloadDomain.ps1 for vSAN File Services to be excluded from customer virtual machines.

Type

  • Bugfix
  • Enhancement or Feature
  • Code Style or Formatting
  • Documentation
  • Refactoring
  • Chore
  • Other
    Please describe:

Breaking Changes?

  • Yes, there are breaking changes.
  • No, there are no breaking changes.

Test and Documentation

  • Tests have been completed.
  • Documentation has been added or updated.

Issue References

Closes #48

Additional Information

@github-actions github-actions bot added documentation Documentation needs-review Needs Review labels Feb 15, 2024
@burnsjared0415 burnsjared0415 force-pushed the Bug-Added-support-for-vSAN-File- branch from 2a76eca to 51621e3 Compare February 15, 2024 14:24
@burnsjared0415 burnsjared0415 changed the title Bug added support for vSAN File Servides Bug added support for vSAN File Services Feb 15, 2024
@tenthirtyam tenthirtyam changed the title Bug added support for vSAN File Services fix: add support for vsan file services Feb 15, 2024
@tenthirtyam tenthirtyam added this to the v1.4.1 milestone Feb 15, 2024
@tenthirtyam tenthirtyam self-requested a review February 15, 2024 16:06
@tenthirtyam tenthirtyam force-pushed the Bug-Added-support-for-vSAN-File- branch from 51621e3 to 4fc1436 Compare February 15, 2024 19:22
Comment on lines 191 to 192
$vcfVersion = Get-VCFManager | Select-Object version | Select-String -Pattern '\d+\.\d+' -AllMatches | ForEach-Object { $_.matches.groups[0].value }

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
$vcfVersion = Get-VCFManager | Select-Object version | Select-String -Pattern '\d+\.\d+' -AllMatches | ForEach-Object { $_.matches.groups[0].value }
$vcfVersion = Get-VCFManager | Select-Object version | Select-String -Pattern '\d+\.\d+' -AllMatches | ForEach-Object { $_.matches.groups[0].value }

Comment on lines 594 to 595
if ( $answer -eq 'N') {
Write-PowerManagementLogMessage -Type WARNING "Please shutdown the workload domain vCenter Server instance $vm and retry."
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if ( $answer -eq 'N') {
Write-PowerManagementLogMessage -Type WARNING "Please shutdown the workload domain vCenter Server instance $vm and retry."
if ($answer -Match 'N') {
Write-PowerManagementLogMessage -Type ERROR "Please shutdown the workload domain vCenter Server instance $vm and retry. Exiting..."

@@ -612,6 +614,12 @@ if ($PsBoundParameters.ContainsKey("shutdown") -or $PsBoundParameters.ContainsKe
foreach ($vm in $vclsvms) {
[Array]$vcfvms += $vm
}
Write-PowerManagementLogMessage -Type INFO -Message "Trying to fetch all powered-on vSAN File Services virtual machines from server $($vcenter)..."
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Write-PowerManagementLogMessage -Type INFO -Message "Trying to fetch all powered-on vSAN File Services virtual machines from server $($vcenter)..."
Write-PowerManagementLogMessage -Type INFO -Message "Fetching all powered on vSAN File Services virtual machines from vCenter Server instance $($vcenter)..."

…mentDomain.ps1

Replaced code in `PowerManagement-ManagmentDomain.ps1` updated `$vcfvms` to allow for ip address or FQDN.

Signed-off-by: Jared Burns <[email protected]>
Updated `PowerManagement-ManagmentDomain.ps1` to allow for FQDN or IP address of SDDC Manager.

Signed-off-by: Jared Burns <[email protected]>
Added support to `PowerManagement-ManagmentDomain.ps1` for more than one cluster in management domain for shut down and start up.

Signed-off-by: Jared Burns <[email protected]>
Added support to PowerManagement-ManagmentDomain.ps1 for more than one cluster in management domain for shut down and start up.

Signed-off-by: Jared Burns <[email protected]>
Added support to `PowerManagement-ManagmentDomain.ps1` and `PowerManagement-WorkloadDomain.ps1` for vSAN File Services to be excluded from customer virtual machines.

Signed-off-by: Jared Burns <[email protected]>
@tenthirtyam tenthirtyam force-pushed the Bug-Added-support-for-vSAN-File- branch from 4fc1436 to 50b95fa Compare February 15, 2024 19:31
@tenthirtyam tenthirtyam removed the needs-review Needs Review label Feb 15, 2024
Copy link

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 17, 2024
@tenthirtyam tenthirtyam modified the milestones: v1.4.1, v1.4.2 Jul 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When vSAN File Services is enabled the workload domain shutdown attempts to shutdown the service nodes
2 participants