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

DAOS-9355 doc: first draft of DAOS 2.4 support matrix #12494

Merged
merged 7 commits into from
Jul 12, 2023

Conversation

Michael-Hennecke
Copy link
Collaborator

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 watchers.
  • 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.

first draft of 2.4 release infos

Doc-only: true
Signed-off-by: Michael Hennecke <michael.hennecke@intel.com>
first draft of DAOS Version 2.4 support matrix document

Doc-only: true
Signed-off-by: Michael Hennecke <michael.hennecke@intel.com>
remove inadvertently added release_notes_v24.md draft

Doc-only: true
Signed-off-by: Michael Hennecke <michael.hennecke@intel.com>
@github-actions
Copy link

Bug-tracker data:
Ticket title is 'DAOS Version 2 documentation improvements'
Status is 'In Progress'
Labels: 'documentation'
https://daosio.atlassian.net/browse/DAOS-9355

codespell fixes

Doc-only: true
Signed-off-by: Michael Hennecke <michael.hennecke@intel.com>

### Enterprise Linux 8 (EL8): RHEL 8, Rocky Linux 8, AlmaLinux 8

DAOS Version 2.4 is supported on EL 8.8, and on EL 8.6 with Extended Update Support (EUS).
Copy link
Contributor

Choose a reason for hiding this comment

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

We have not actually validated 8.8. We still run on 8.6 in CI. I tried bumping to 8.7 but ran into failures that were unreproducible. This has gone through 2 iterations but I have yet to find time to validate the second iteration.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

as 8.8 is the current EL8 level, we have to support it (in the sense that we accept tickets against it).
it's highlighted elsewhere in the doc that most validation was done on 8.6.
And 8.7 is not relevant anymore as it's EOL.

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see any tickets in SRS for support of EL 8.7 or 8.8. Given past experience we do not move distro versions until there is a ticket requesting it as we are not aware of what our customer support requirement/constraints are.

I.e. if we move to 8.8 without a request for it -- without understanding the customer support requirements, we risk building on a point release that will not support customer environments that are still running older versions, such as 8.6 for example.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

good point, we'll add 2.4 SRS tickets to track EL8 OS validation beyond 8.6

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

reworded doc as "Validation of DAOS Version 2.4 on EL 8.8 is in progress."

docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Show resolved Hide resolved
docs/release/support_matrix.md Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Show resolved Hide resolved
docs/release/support_matrix.md Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Show resolved Hide resolved
docs/release/support_matrix.md Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
docs/release/support_matrix.md Outdated Show resolved Hide resolved
address reviewer comments

Doc-only: true
Signed-off-by: Michael Hennecke <michael.hennecke@intel.com>
@Michael-Hennecke Michael-Hennecke requested a review from a team July 12, 2023 09:56
@Michael-Hennecke
Copy link
Collaborator Author

please land - doc-only, test failures are unrelated

and in the DAOS Administration Guide.

For maximum performance, it is strongly recommended that all memory channels
of a DAOS server are populated.
Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure about this TBH, but does not hurt.

DAOS Version 2.4 includes a Technology Preview of the
_Metadata-on-SSD_ feature. This code path uses DRAM memory to hold the
DAOS metadata, and persists the DAOS metadata on NVMe SSDs through
a write-ahead log (WAL) and asynchronous metadata checkpointing.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe clarify somewhere that upgrade to 2.6 md-on-ssd GA is not guaranteed?


DAOS Version 2.4 supports Intel Volume Management Devices (VMD) to manage the
NVMe disks on the DAOS servers. Enabling VMD is platform-dependent;
details are provided in the Administration Guide.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe mentions that it is needed only for LED management.

@johannlombardi johannlombardi merged commit 2f614c2 into release/2.4 Jul 12, 2023
@johannlombardi johannlombardi deleted the michael-hennecke/2.3/daos-9355-relnotes23 branch July 12, 2023 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants