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.

Sign up for GitHub

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

Jump to bottom

DAOS-16276 doc: Address engine unavailability (#15456) #15496

Open
wants to merge 1 commit into
base: release/2.6
Choose a base branch
from
Open

DAOS-16276 doc: Address engine unavailability (#15456) #15496

wants to merge 1 commit into from

Conversation

liw
Copy link
Contributor

@liw liw commented Nov 13, 2024

Add a section on handling unavailable engines.

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate owners.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

@liw
DAOS-16276 doc: Address engine unavailability (#15456)
2c86a2e 
Add a section on handling unavailable engines.

Signed-off-by: Li Wei <[email protected]>
Required-githooks: true
@liw liw requested a review from a team as a code owner November 13, 2024 13:14
@liw liw added clean-cherry-pick Cherry-pick from another branch that did not require additional edits doc-only Changes only affect documentation, not code release-2.6.2 Targeted for release 2.6.2 labels Nov 13, 2024
@github-actions GitHub Actions
Copy link

Ticket title is 'Document how to bring DAOS cluster online after many servers failed'
Status is 'In Progress'
https://daosio.atlassian.net/browse/DAOS-16276

@liw liw requested a review from a team November 14, 2024 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Michael-Hennecke Michael-Hennecke Michael-Hennecke approved these changes

Assignees
No one assigned
Labels
clean-cherry-pick Cherry-pick from another branch that did not require additional edits doc-only Changes only affect documentation, not code release-2.6.2 Targeted for release 2.6.2
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@liw @Michael-Hennecke