[LUDOC-86] DNE Phase I Doc Changes

• Status: Closed
• Project: Lustre Documentation
• Type: Improvement
• Priority: Critical
• Reporter: Jodi Levi (Inactive)
• Assignee: Richard Henwood (Inactive)
• Resolution: Fixed
• Project: OpenSFS SFS-DEV-001

Description

A considerable amount of updates to the manual: description of feature, configuration, administration, troubleshooting and repair of MDT failures

Issue Links

• is duplicated by: LUDOC-108 add documentation for DNE
• is related to: LU-1187 DNE Phase 1: Remote Directories

Comments

[Andreas Dilger]

Update the user manual to describe changes to the user tools:

• formatting, mounting, usage, configuration, etc.
• potentially some of the example output (if relevant to the examples)
• /proc tunables, module parameters, etc.

Since we use a single manual for all of the Lustre releases, when changing any significant sections of text the content should include the version in which the change was made (i.e. 2.4) and leave the old comments in place (at least back to 2.1, older 1.x sections can be removed), for example:

Starting with Lustre 2.4, it is possible to add multiple MDTs to a single Lustre filesystem, by specifying a non-zero index for the later MDTs, like mkfs.lustre --mdt --index 1 ... /dev/mdt0001

[Richard Henwood (Inactive)]

This ticket is a duplicate of LUDOC-108. LUDOC-108 is closed as complete.

[Andreas Dilger]

There are a couple of gaps in the user manual related to DNE Phase 1:

• the glossary should define "DNE" since this is what users know the feature as
• it might make sense to use DNE in a few places where multiple MDTs are described, so that this is more easily found in the manual. As it stands, there is no one place to find out about DNE in the manual.
• add "lfs mkdir" to the UserUtilities section, per LU-4237

[Andreas Dilger]

It would also be useful to have a paragraph or six that provides an overview of the DNE Phase 1 functionality, in particular describing that it is mostly intended for administrator use (and by default limited only to administrators), only provides static directory distribution, that there is not yet a migration tool besides "copy all data", etc. This could easily be copy-pasted from the Project Scope, Solution Architecture, and/or HLD into the manual.

[Jessica A. Popp (Inactive)]

Richard -

Should this ticket be assigned to Di and tracked as part of DNE deliverables?

-Jessica

[Richard Henwood (Inactive)]

This got closed with LU-108