Community Forums
The
PVFS community
holds to the open source practice that fosters
community collaboration. We encourage PVFS users and administrators to
discuss their setup, ideas, or problems via the following channels.
PVFS2 Users List
The users mailing list
is provided for general purpose discussion, configuration, and
bug reporting. We encourage users to provide feedback on their own PVFS setups
and configurations that can be useful to the entire community.
When emailing the users list with questions, please include your hardware
setup (network, storage, etc.) and the output of the pvfs2-statfs utility.
Also, if your question is in regard to a failure, check for related
messages in the output of the client's system log, and the pvfs2-server.log
and pvfs2-client.log files, and send that output to us as well.
This will allow us to directly address your questions.
[subscribe here]
[view archives]
PVFS2 Developers List
The PVFS developer's mailing list is available for
those interested in contributing to the PVFS project.
The developers list
is the best way to get in touch with us if you wish to contribute to
PVFS. Patches to PVFS source for new features or bug fixes, should be
posted to this list.
[subscribe here]
[view archives]
Bug Reports
The PVFS project uses Trac to manage bug reports and feature requests.
Please review the list of submitted tickets before submitting a new ticket for your own bug report or feature request.
#pvfs2 IRC channel
An IRC channel for PVFS is hosted on
freenode.net, allowing users and developers
to ask questions, get to know the developers, or just provide feedback. The
freenode website
has info on how to access the freenode irc servers. Once you have connected
to the IRC server, join the #pvfs2 channel.
Developer and Contributor Information
We are always looking for help with the Parallel Virtual File System
project. If you have any ideas, suggestions, bug reports, bug fixes, or
want to help implement a new feature, please let us know. PVFS is
distributed under the LGPL license and the source code is readily
available. If you are interested in helping out or simply tracking
PVFS development process please read on.
Source Code Access
We manage the source code for all of the PVFS components using CVS. For more information on how to use CVS,
please check your local documentation or visit the CVS web site.
We provide anonymous read only access to all of the current PVFS code.
DO NOT USE CODE FROM CVS IN A PRODUCTION ENVIRONMENT!
Access to the CVS repository is provided for people interested in
experimenting with PVFS or developing new features. We do not guarantee
that the code in CVS works at all, or that your data is safe using it.
Support is only provided for the latest stable releases, which can be
downloaded from the
download section. That is the code that
you should choose for every day use.
- To check out the latest pvfs2 tree:
cvs -d :pserver:anonymous@cvs.parl.clemson.edu:/anoncvs login
(use any password)
cvs -d :pserver:anonymous@cvs.parl.clemson.edu:/anoncvs co pvfs2
cvs -d :pserver:anonymous@cvs.parl.clemson.edu:/anoncvs logout
Online Source Browsing
View the PVFS source code,
change logs, and create diffs via the
Fisheye web interface.
Regression Tests
PVFS tests are run on a daily basis both for code under
development as well as released versions. We include a number of
well known filesystem stress tests and benchmarks in our regular
testing. The PVFS Tinderbox
page has further information.
|
Quick Links
-
FAQ
- Frequently Asked Questions.
- Fisheye
- Browse the source code.
- Tinderbox
- Continuous Integration Testing. View the latest test runs and results.
|
|
