Wiki Migration

From Lustre Wiki
Revision as of 17:46, 29 January 2016 by ChrisMorrone (talk | contribs)
Jump to navigation Jump to search


New wiki pages should not have "Lustre" in the title.

The entire wiki is about Lustre. The page titles double as the URL, and we want to keep both clean and concise. Instead of:

we would want the less redundant and more concise:

The exception to this rule is when the word "Lustre" is part of a larger formal name, such as in "Lustre User Group" or "".


Status Description
to-move can be moved to the new wiki (merged if there is an existing new page) without update
to-update-and-move needs updating before move, but no domain-specific knowledge necessary
to-review reviewer with domain-specific knowledge needed
to-delete page will not be moved and will no longer be available when the old wiki is shut down
moved moved to the new wiki
updated-and-moved updated and moved to new wiki Pages

Page Status Category Notes
Acceptance Small (acc-sm) Testing on Lustre
Accessing Lustre Code to-delete out of date
Applying Lustre Patches to a Kernel
Architecture - Adaptive Timeouts - Use Cases
Architecture - Backup
Architecture - CROW
Architecture - CTDB with Lustre
Architecture - Caching OSS
Architecture - Changelogs
Architecture - Changelogs 1.6
Architecture - Client Cleanup
Architecture - Clustered Metadata
Architecture - Commit on Share
Architecture - Cuts
Architecture - DMU OSD
Architecture - DMU Zerocopy
Architecture - End-to-end Checksumming
Architecture - Epochs
Architecture - External File Locking
Architecture - FIDs on OST
Architecture - Feature FS Replication
Architecture - Fileset
Architecture - Flash Cache
Architecture - Free Space Management
Architecture - GNS
Architecture - HSM
Architecture - HSM Migration
Architecture - HSM and Cache
Architecture - IO system
Architecture - Interoperability 1.6 1.8 2.0
Architecture - Interoperability fids zfs
Architecture - LRE Images
Architecture - Libcfs
Architecture - Llog over OSD
Architecture - Lustre DLDs
Architecture - Lustre HLDs
Architecture - Lustre Logging API
Architecture - MDS-on-DMU
Architecture - MDS striping format
Architecture - MPI IO and NetCDF
Architecture - MPI LND
Architecture - Metadata API
Architecture - Migration (1)
Architecture - Migration (2)
Architecture - Multiple Interfaces For LNET
Architecture - Network Request Scheduler
Architecture - New Metadata API
Architecture - OSS-on-DMU
Architecture - Open by fid
Architecture - PAG
Architecture - Pools of targets
Architecture - Profiling Tools for IO
Architecture - Proxy Cache
Architecture - Punch and Extent Migration
Architecture - Punch and Extent Migration Requirements
Architecture - Recovery Failures
Architecture - Request Redirection
Architecture - Scalable Pinger
Architecture - Security
Architecture - Server Network Striping
Architecture - Simple Space Balance Migration
Architecture - Simplified Interoperation
Architecture - Space Manager
Architecture - Sub Tree Locks
Architecture - User Level Access
Architecture - User Level OSS
Architecture - Userspace Servers
Architecture - Version Based Recovery
Architecture - Wide Striping
Architecture - Wire Level Protocol
Architecture - Write Back Cache
Architecture - Writing Architecture Documents
Architecture - ZFS TinyZAP
Architecture - ZFS for Lustre
Architecture - ZFS large dnodes
Architecture Descriptions
Backing Up a Lustre File System
Building Lustre Code
Building and Installing Lustre from Source Code
Change Log 1.6
Change Log 1.8
Change Log 2.0
Clustered Metadata previous failed DNE attempt. to-delete or keep for posterity?
Coding Guidelines to-delete We already have Lustre_Coding_Guidelines
Completing Basic Administrative Tasks to-delete odd random chapter index for old manual
Configuring InfiniBand Connectivity to-delete to out of date and too specific
Configuring Lustre File Striping
Configuring Lustre for Failover
Configuring RAID for Disk Arrays
Configuring the Lustre File System
Contribute redirect-page
Contribution Policy
Creating and Managing OST Pools
DRBD and Lustre
Debian Install
Debugging Lustre
Developers Guide to Bugzilla for Lustre to-delete
Diagnostic and Debugging Tools
Documenting Code
Download redirect-page
E1000 Driver Tuning to-delete
FAQ - Fundamentals
FAQ - Glossary
FAQ - Installation
FAQ - Licensing and Support
FAQ - Metadata Servers
FAQ - Networking
FAQ - OS Support
FAQ - Object Servers and I/O Throughput
FAQ - Recovery
FAQ - Release Testing and Upgrading
FAQ - Sizing
Finding a Project needs overhaul if kept
Fsck Support redirect-page
GSS / Kerberos
GetInvolved:Get Involved
Get Involved redirect-page
Git Transition Notice to-delete ancient history
Guidelines for Setting Up a Cluster to-delete Not lustre specific. There are better guides out there.
HPC Software Workshop and Seminars - Regensburg Germany 2009
Handling File System Errors
Handling Full OSTs
Installing Lustre from Downloaded RPMs
Large-Scale Tuning for Cray XT
Learn redirect-page
LibLustre How-To Guide to-delete liblustre is dead
Load Balancing with Infiniband
Logging API
Lustre 1.8
Lustre 2.0
Lustre 2.0 Features
Lustre 2.0 Release Milestone Status
Lustre All-Hands Meeting 12/08
Lustre All-Hands Meeting 3/08
Lustre Center of Excellence at Oak Ridge National Laboratory
Lustre Community Events, Conferences and Meetings
Lustre Configuration Example
Lustre Customers
Lustre DDN Tuning
Lustre Debugging Procedures
Lustre Debugging for Developers
Lustre Design Document Archive
Lustre Design Documents
Lustre Documentation
Lustre FAQ to-delete Incorporate still-relevant info from the old FAQ's sub-pages into the new one-page Frequently Asked Questions
Lustre FUSE to-delete liblustre is dead
Lustre Fall Workshop 10/2010
Lustre Features to-delete redirect-page
Lustre HPCS Activities
Lustre Internals
Lustre Interoperability - Upgrading From 1.8 to 2.0
Lustre Mailing Lists to-delete we already have this
Lustre Packages to-delete out of date, easy to make a better guide in the future without this
Lustre Project List to-delete ancient, we have Projects instead
Lustre Projects to-delete summary page no longer relevant
Lustre Publications
Lustre Release Information
Lustre Support to-delete mostly an Ad for Xyratex, mailing list references already available elsewhere
Lustre Support Matrix redirect-page
Lustre System Configuration Utilities
Lustre Test Plans
Lustre Tuning
Lustre User Group 2006
Lustre User Group 2007
Lustre User Group 2008
Lustre User Group 2009
Lustre User Group 2010
Lustre User Group 2011 to-delete
Lustre User Group 2012 to-delete
Lustre User Group 2014 to-delete
Main Page to-delete
Managing Free Space
Managing Lustre Failover
Managing OSTs
Metadata Performance Project
Migrating to Git to-delete
NFS vs. Lustre
Netconsole to-delete out of date, not lustre specific so unlikely to ever be kept up to date
POSIX Compliance Testing
Patchless Client
Preparing to Install Lustre
RAID5 Patches
Recovering from a Node or Network Failure
Reporting Bugs
Running Hadoop with Lustre
SC'09 and Lustre Senior Technical Meeting 11/09
Sample Style
Setting up Lustre Security
Simul Parallel File System Test Tool
Submitting Patches
Subsystem Map
Testing Lustre Code
Tuning Lustre for Performance
Upgrading to a New Version of Lustre
Use redirect-page
Use:Change Log 1.8 redirect-page
Using Pacemaker with Lustre
Using Quotas
Using Red Hat Cluster Manager with Lustre
Using Xen with Lustre
Windows Native Client
Working with File System Labels
ZFS Resources
ZFS and Lustre Pages

Intel's Confluence wiki contains information that is more up to date than what is found in the old mediawiki pages. We should be sure to mine for necesary information. Andreas has already translated and copied some pages from their, but no doubt there are many more pages remaining.


We should remember to make a copy of the LID (Lustre Internals Document) sources for posterity. We don't necessarily need to keep it on a web page, but we could at least put the sources in a git repo on github.