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: Difference between revisions

From Obsolete Lustre Wiki
Jump to navigationJump to search
(Created page with 'Content from Open CVS, Lustre CVS and Lustre External CVS')
 
No edit summary
Line 1: Line 1:
Content from Open CVS, Lustre CVS and Lustre External CVS
Content from Open CVS, Lustre CVS and Lustre External CVS
As an open-source product, we encourage contributions to develop and test a more robust, feature-rich Lustre by trying out the software while it is under development. To obtain Lustre code from the source repository, you must have CVS (Concurrent Versioning System) installed.
== Using the CVS repository ==
Check out Lustre source code as follows:
1. Set CVSROOT in your environment by entering of of these commands:
:pserver:anonymous@cvs.lustre.org:/lustre
or
cvs -d :pserver:anonymous@cvs.lustre.org:/lustre login
2. Run
cvs login
If a password is requested, hit enter to continue.
3. Check out the lustre source by entering: ''cvs co lustre''
#Check out the various modules of lustre ''cd lustre ; ./lustrecvs b1_6''
Stable development branches are named b''{major}''_''{minor}'', for example b1_6 and b1_8.  Release branches are cut for making an official release to isolate it from further development, named b_release_''{major}''_''{minor}''_''{patch}'', for example b_release_1_8_0.  A final release gets a tag of the form v''{major}''_''{minor}''_''{patch}'', for example v1_8_0 or v1_6_7_1.
Even-numbered minor releases are considered stable releases.  Odd-numbered minor releases are for alpha and beta releases, and will sometimes get v''{major}''_''{minor}''_''{patch}'' tags to allow a point of reference for internal and external testing.  The long-range development is done on the HEAD branch.
=== Example ===
This example will checkout all sources into ~/tmp
<code>
cfaber@atitude:~$ '''cd tmp'''
cfaber@atitude:~/tmp$ '''cvs -d :pserver:anonymous@cvs.lustre.org:/lustre login'''
Logging in to :pserver:anonymous@cvs.lustre.org:2401/lustre
CVS password:      <font color="red">''(Leave blank, Hit Enter)''</font>
</code>
<code>
cfaber@atitude:~/tmp$ '''cvs -d :pserver:anonymous@cvs.lustre.org:/lustre co 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
</code>
<code>
cfaber@atitude:~/tmp$ '''cd lustre'''
cfaber@atitude:~/tmp/lustre$ '''./lustrecvs b1_6'''
<font color=red> ''(You may also use '''lustrecvs HEAD''' for the HEAD release)''</font><br>
lustrecvs: updating lustrecvs
cvs update: Updating .
lustrecvs: Checking out build from b1_6
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
.........
</code>
=== CVS Modules ===
The following modules are provided via the anonymous pserver:
*lustre
*ldiskfs
*libsysio
*lnet
*lustre-build (as .../build)
*lustre-core (as .../lustre)
*lustre-snmp (as .../snmp)
=== Note ===

Revision as of 11:39, 29 August 2009

Content from Open CVS, Lustre CVS and Lustre External CVS

As an open-source product, we encourage contributions to develop and test a more robust, feature-rich Lustre by trying out the software while it is under development. To obtain Lustre code from the source repository, you must have CVS (Concurrent Versioning System) installed.

Using the CVS repository

Check out Lustre source code as follows:

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

:pserver:anonymous@cvs.lustre.org:/lustre

or

cvs -d :pserver:anonymous@cvs.lustre.org:/lustre login

2. Run

cvs login 

If a password is requested, hit enter to continue.

3. Check out the lustre source by entering: cvs co lustre

  1. Check out the various modules of lustre cd lustre ; ./lustrecvs b1_6

Stable development branches are named b{major}_{minor}, for example b1_6 and b1_8. Release branches are cut for making an official release to isolate it from further development, named b_release_{major}_{minor}_{patch}, for example b_release_1_8_0. A final release gets a tag of the form v{major}_{minor}_{patch}, for example v1_8_0 or v1_6_7_1.

Even-numbered minor releases are considered stable releases. Odd-numbered minor releases are for alpha and beta releases, and will sometimes get v{major}_{minor}_{patch} tags to allow a point of reference for internal and external testing. The long-range development is done on the HEAD branch.

Example

This example will checkout all sources into ~/tmp

cfaber@atitude:~$ cd tmp
cfaber@atitude:~/tmp$ 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)

cfaber@atitude:~/tmp$ cvs -d :pserver:anonymous@cvs.lustre.org:/lustre co 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

cfaber@atitude:~/tmp$ cd lustre
cfaber@atitude:~/tmp/lustre$ ./lustrecvs b1_6

(You may also use lustrecvs HEAD for the HEAD release)

lustrecvs: updating lustrecvs
cvs update: Updating .
lustrecvs: Checking out build from b1_6
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
.........

CVS Modules

The following modules are provided via the anonymous pserver:

  • lustre
  • ldiskfs
  • libsysio
  • lnet
  • lustre-build (as .../build)
  • lustre-core (as .../lustre)
  • lustre-snmp (as .../snmp)

Note