|
|
| (96 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| 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:
| | <small>''(Updated: Jan 2010)''</small> |
| * ''Anonymous access''. You can obtain Lustre source code by [[Accessing the Open CVS repository]]. When using this option, you will have read-only access to the code. See [[Contribution Landing Page]] for how to submit code.
| |
|
| |
|
| * ''Read/write access''. With a password-protected account, you can check out Lustre source code by [[Accessing the Lustre CVS repository]]. After signing a Contributor Agreement (see our Contribution Policy), you will be able to submit changes directly to the Lustre code.
| | '''''NOTICE:''''' The transition from CVS to Git took place on Monday, December 14. For more information about the transition, see the [[Git Transition Notice]]. For details about how to migrate to Git, see [[Migrating to Git]]. |
|
| |
|
| * ''Authorized access''. Obtaining Lustre source code by [[Accessing the External Lustre CVS repository]] requires a password-protected account and authorization from Sun Microsystems.
| | ---- |
|
| |
|
| For all these options, the Concurrent Versions System (CVS) must be installed on your local system. For more information about CVS, see [[http://www.nongnu.org/cvs/|CVS - Concurrent Versions System]].
| | We welcome and encourage contributions to the development and testing of a more robust, feature-rich Lustre™. You can obtain the latest bleeding-edge Lustre source code by anonymous Git access. |
|
| |
|
| === Naming conventions ===
| | git clone git://git.lustre.org/prime/lustre.git |
|
| |
|
| 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.
| | '''''Note:''''' For more information about using Git, including tutorials and guides to help you get started, see the [http://git-scm.com/documentation Git documentation] page. ''For descriptions of the commands you are most likely to need, see the Commands section at the bottom of this page.'' |
|
| |
|
| [[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 in the form v''{major}''_''{minor}''_''{patch}'' (for example, v1_8_0 or v1_6_7_1). | | See [[Contribute]] for more information about developing, testing, and submitting a patch to the Lustre code. |
|
| |
|
| Long-range development is done on the HEAD branch.
| | '''''Note:''''' If you have questions or experience problems, send email to the [mailto:lustre-wiki-feedback@sun.com Admins]. |
|
| |
|
| | For more information about Git, see the [http://git-scm.com/ Git home] |
|
| |
|
| == Accessing the Open CVS repository == | | === Naming conventions === |
| The Open CVS repository allows anonymous, read-only access to the Lustre code. See [[Contribution Landing Page]] for more information about submitting a patch to the Lustre code.
| |
|
| |
|
| You can check out any of the following Lustre modules from the Open CVS repository:
| | 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. |
| *lustre
| |
| *ldiskfs
| |
| *libsysio
| |
| *lnet
| |
| *lustre-build (as .../build)
| |
| *lustre-core (as .../lustre)
| |
| *lustre-snmp (as .../snmp)
| |
| | |
| === Checking out Code from Open CVS ===
| |
| To check out Lustre source code from Open CVS:
| |
| | |
| 1. Set CVSROOT in your environment by entering one 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
| |
| 4. Check out the lustre modules by entering:
| |
| cd lustre
| |
| ./lustrecvs b1_6
| |
| :In this example, modules for Release 1.6 are checked out.
| |
| | |
| | |
| === Example ===
| |
| In this example, all sources are checked out 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>
| |
| | |
| == Accessing the Lustre CVS repository ==
| |
| | |
| The Lustre CVS repository allows read/write access to Lustre code.
| |
| | |
| [[This page contains instructions for obtaining CVS versions of Lustre, [[as well as migrating checkouts from sourceforge to the new CVS server.]]
| |
| | |
| | |
| | |
| === Checking out Code from Lustre CVS ===
| |
| | |
| * Test that your account is working by logging into [https://bugzilla.lustre.org/userprefs.cgi bugzilla]. CVS and bugzilla share the same account information.
| |
| | |
| * Upload a public ssh key
| |
| | |
| : You can use an ssh key so that you don't have to keep typing in your password. This is done in bugzilla's [http://bugzilla.lustre.org/userprefs.cgi user preferences]. If there is no "Change Public SSH key" field, please send mail to the address below.
| |
| | |
| : Currently, only SSH2 keys are supported.
| |
| | |
| * Set the CVS_RSH environment variable.
| |
| | |
| : For bash users, this is <pre>export CVS_RSH=ssh</pre>. For csh users, <pre>setenv CVS_RSH ssh</pre>.
| |
| | |
| : You should probably put this in your .bashrc or .cshrc.
| |
| | |
| * You can now check out lustre by running the following (changing <pre>youraccountname</pre> to your cvs account name, as specified on the [https://bugzilla.lustre.org/userprefs.cgi user preferences page]):
| |
| | |
| : <pre>
| |
| : $ cvs -d :ext:youraccountname@cvs.lustre.org:/cvsroot/cfs co lustre
| |
| : $ cd lustre
| |
| : $ ./lustrecvs b1_8
| |
| </pre>
| |
| | |
| === Problems ===
| |
| | |
| Not working as you expected? Do you think you should have CVS access, but don't? Send email to cvs-admin@cvs.lustre.org [[Ask Robert Read if email address is still valid - for all three?.]]
| |
| | |
| == Accessing the Lustre External CVS repository ==
| |
| | |
| This page contains instructions for obtaining Lustre source code from the external CVS repository. This read-only repository is synchronized with the CFS internal CVS every three hours.
| |
| | |
| === 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 in a non-production test environment.
| |
| | |
| If you do not agree with these restrictions, '''do not use the CVS repository'''; please email us to have your account disabled.
| |
| | |
| === Checking out Code from Lustre External CVS ===
| |
| | |
| 1. Check out the top-level lustre directory
| |
| | |
| : <pre>
| |
| : $ cvs -d {username}@cvs.clusterfs.com:/cvsroot/lustre-external co lustre
| |
| </pre>
| |
| | |
| : Where {username} is your Bugzilla account id.
| |
| | |
| : When prompted for a password, enter your Bugzilla password.
| |
| | |
| 2. Get the desired CVS tag
| |
| | |
| : Download the Lustre source tree from the desired CVS tag using the lustrecvs script
| |
|
| |
|
| : <pre>
| | 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). |
| : $ cd /your/cvs/checkout/lustre
| |
| : $ ./lustrecvs <tag or branch>
| |
| </pre>
| |
|
| |
|
| : Where <tag or branch> is a valid Lustre branch or tag name (e.g. b1_4, HEAD)
| | Work for the next upcoming version is done on the ''master'' branch. |
|
| |
|
| NOTE: To update the tree or to change branches, do NOT use "cvs update". Rather, run the "lustrecvs <tag>" command again.
| | The Lustre [[Subsystem Map]] describes each of the subsystems in the Lustre code. |
(Updated: Jan 2010)
NOTICE: The transition from CVS to Git took place on Monday, December 14. For more information about the transition, see the Git Transition Notice. For details about how to migrate to Git, see Migrating to Git.
We welcome and encourage contributions to the development and testing of a more robust, feature-rich Lustre™. You can obtain the latest bleeding-edge Lustre source code by anonymous Git access.
git clone git://git.lustre.org/prime/lustre.git
Note: For more information about using Git, including tutorials and guides to help you get started, see the Git documentation page. For descriptions of the commands you are most likely to need, see the Commands section at the bottom of this page.
See Contribute for more information about developing, testing, and submitting a patch to the Lustre code.
Note: If you have questions or experience problems, send email to the Admins.
For more information about Git, see the Git home
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).
Work for the next upcoming version is done on the master branch.
The Lustre Subsystem Map describes each of the subsystems in the Lustre code.
