[edit] WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Accessing Lustre Code

From Obsolete Lustre Wiki
Revision as of 23:12, 18 September 2009 by Docadmin (Talk | contribs)
Jump to: navigation, search

We welcome and encourage contributions to the development and testing of a more robust, feature-rich Lustre. Three options are available for accessing Lustre code:

For all these options, the Concurrent Versions System (CVS) must be installed on your local system. For more information about CVS, see CVS - Concurrent Versions System.

Note: If you have questions or experience problems with using any of these options, send email to the CVS Administrator.

Contents

Naming conventions

Stable development branches are named b{major}_{minor} (for example, b1_6 and b1_8). Even-numbered minor releases are considered stable releases. Odd-numbered minor releases correspond to alpha and beta releases and will sometimes be given v{major}_{minor}_{patch} tags to provide a point of reference for internal and external testing.

A release branch is created an official release to isolate it from further development and named b_release_{major}_{minor}_{patch} (for example, b_release_1_8_0). A final release gets a tag in the form v{major}_{minor}_{patch} (for example, v1_8_0 or v1_6_7_1).

Long-range development is done on the HEAD branch.

Lustre Modules

These Lustre modules are needed to build Lustre. They are automatically checked out when the lustrecvs script is run for a specified Lustre branch or tag, such as HEAD, b1_8, or v1_8_1:

  • lustre (top-level directory)
  • ldiskfs (at lustre/ldiskfs)
  • libsysio (at lustre/libsysio)
  • lnet (at lustre/lnet)
  • libcfs (at lustre/libcfs)
  • lustre-build (at lustre/build)
  • lustre-core (at lustre/lustre)
  • lustre-snmp (at lustre/snmp)

See the following sections for details.

Lustre Subsystem Map describes each of the subsystems in the Lustre code.

Accessing the Open CVS repository

The Open CVS repository allows anonymous, read-only access to the Lustre code. See Contribute for more information about submitting a patch to the Lustre code.

Checking out code from Open CVS

To check out Lustre source code from the Open CVS repository, complete these steps. The Open CVS repository is used for public access to Lustre and is synced from the internal CVS repository several times a day.

1. Set CVSROOT in your environment by entering one of these commands:

export CVSROOT=":pserver:anonymous@cvs.lustre.org:/lustre"
or
cvs -d :pserver:anonymous@cvs.lustre.org:/lustre login
No password is needed.

2. Check out the lustre source.

cvs co lustre

3. Check out lustre modules.

cd lustre
./lustrecvs b1_8
In this example, modules for Release 1.8 are checked out.

Example

In this example, Lustre sources are checked out into ~/src/lustre-1_8. This directory can be called anything. The directory name will default to "lustre" if nothing is specified.

user@host:~$ cd src
user@host:~src$ cvs -d :pserver:anonymous@cvs.lustre.org:/lustre login
Logging in to :pserver:anonymous@cvs.lustre.org:2401/lustre
CVS password:      (Leave blank, hit <Enter>)

user@host:~/src$ cvs -d :pserver:anonymous@cvs.lustre.org:/lustre co -d lustre-1_8 lustre
cvs checkout: Updating lustre
U lustre/.cvsignore
U lustre/COPYING
U lustre/ChangeLog
U lustre/Makefile.in
U lustre/README
U lustre/README.lustrecvs
U lustre/autoMakefile.am
U lustre/autogen.sh
U lustre/configure.ac
U lustre/lustre.spec.in
U lustre/lustrecvs

user@host:~/src$ cd lustre-1_8
user@host:~/src/lustre-1_8$ ./lustrecvs b1_8
lustrecvs: updating lustrecvs
cvs update: Updating .
lustrecvs: Checking out build from b1_8
cvs checkout: Updating build
U build/.cvsignore
U build/Makefile
U build/README.kernel-source
U build/Rules.in
U build/autoMakefile.am
U build/autoMakefile.am.toplevel
:
:

To check out the most recent code for the release currently in development, replace b1_8 with HEAD.

Checking out code from Internal Lustre CVS

The Internal Lustre CVS repository gives access by authorized users to the internal Lustre repository.

Legal Notice

All software obtained from this CVS repository is considered pre-release proprietary software and is therefore confidential information. You may not redistribute any software obtained from this CVS repository and must destroy all copies upon request.
Unless otherwise authorized, you have a limited license to read, modify, compile, and use software obtained from this CVS repository in a non-production test environment.
If you do not agree with these restrictions, do not use this CVS repository. Please email us to have your account disabled.

To check out Lustre source code from the Internal Lustre CVS repository, complete these steps.

3. Set the CVS_RSH environment variable.

For bash users, enter:
export CVS_RSH=ssh
For csh users, enter:
setenv CVS_RSH ssh
Consider setting CVS_RSH permanently in your .bashrc or .cshrc.

4. Check out the Lustre code by running the following (change youraccountname to your cvs account name):

$ cvs -d :ext:youraccountname@cvs.lustre.org:/cvsroot/cfs co lustre
$ cd lustre
$ ./lustrecvs b1_8


Note: To update the tree or to change branches, run the "lustrecvs <tag>" command again. Using "cvs update" is not always reliable if there have been layout changes in the repository.

Personal tools
Navigation