Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
/cephPublic

mgr/nfs: show whether the NFS cluster is deployed as active-active or active-passive#66664

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
Shubhaj1810 wants to merge1 commit intoceph:main
base:main
Choose a base branch
Loading
fromShubhaj1810:fix-issue-deployment-type

Conversation

@Shubhaj1810
Copy link

Summary

Theceph nfs cluster info <cluster> command does not display whether the
cluster is deployed in an active-active or active-passive configuration.
This change adds the deployment type to the cluster info output.

Tracker

Fixes:https://tracker.ceph.com/issues/74240

Testing

  • tox -e flake8 (passed)
  • tox -e mypy (fails in rook module due to missing stubs, unrelated to this change)

Contribution Guidelines

  • To sign and title your commits, please refer toSubmitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer toSubmitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding anx between the brackets:[x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • [ x ] References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • AffectsDashboard, opened tracker ticket
    • AffectsOrchestrator, opened tracker ticket
    • [ x ] No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • [ x ] No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands

You must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Shubhaj1810

[8]ページ先頭

©2009-2025 Movatter.jp