[LU-1655] System engineering review of DNE Created: 12/Jun/12 Updated: 29/May/17 Resolved: 29/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Richard Henwood (Inactive) | Assignee: | WC Triage |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 2215 |
| Description |
|
How does DNE change the way systems are designed? What is best practice? |
| Comments |
| Comment by Richard Henwood (Inactive) [ 12/Jun/12 ] |
|
This is a ticket to build up our body of knowledge about how DNE changes how Lustre file systems are designed. |
| Comment by Joshua Kugler (Inactive) [ 12/Jun/12 ] |
|
My first question about DNE: What's DNE? Dance New England? |
| Comment by Richard Henwood (Inactive) [ 25/Jun/12 ] |
|
That's an easy one for me: Distributed NamEspace http://wiki.whamcloud.com/display/PUB/Remote+Directories+Solution+Architecture |
| Comment by Andreas Dilger [ 25/Jun/12 ] |
|
Actually, I'd always thought it as being "Distributed NamespacE", and the wiki page confirms this. It's a bit of an internal play on words (letters, really), since the previous implementation of this functionality was called "Clustered MetaData" (CMD), and +1 for each letter gives "DNE". |
| Comment by Jodi Levi (Inactive) [ 24/Jul/12 ] |
|
This is a blocker for 2.4. |