OpenSolaris

1. Project: NFS version 4.1 pNFS
   1. Announcements
   2. Events
   3. News
   4. Blogs
   5. Discussions
   6. Leaders
   7. Observers
   8. Downloads
      1. How to Setup and Use pNFS
      2. June 2007 Release Notes
      3. August 2007 Release Notes
      4. October 2007 Release Notes
      5. March 2008 Release Notes
   9. NFSv4.1 Bakeathon
   10. NFS version 4.1 pNFS: Project Logistics
       1. NFS version 4.1 pNFS: FAQ
   11. Demos
       1. pNFS Basics
       2. pNFS Basics (Japanese Version)
       3. pNFS Basics (Chinese Version)
       4. pNFS Basics (German Version)
       5. pNFS Basics (Spanish Version)
       6. pNFS Basics (French Version)
       7. pNFS Basics (Russian Version)
       8. pNFS Basics (Brazilian Portuguese Version)
   12. Project Documentation
       1. NFSv4.1 MDS and DS Design
       2. speadm(1M)

What am I about to read?

The following is an outline of the NFS version 4.1 pNFS project and the proposal for how to run it. Feel free to send questions, comments or concerns to nfsv41 dash discuss at opensolaris dot org.

Outline of Project Deliverables:

The following is a description of the different deliverables that the pNFS project will produce. The items are divided up into four different classes of deliverables. Those classes are: Code/Binaries, Documents, Communication and Process Steps.

1. Code / Binaries:

We are currently releasing Code and Binaries at irregular intervals and would like to get to the point where we can release Code and Binaries in conjunction with the Solaris Express, Community Edition releases which occur approximately every two weeks. For those who don't know, the Solaris Express, Community Edition release is built from the Nevada source tree. To download the pNFS Code and Binaries, check out the pNFS download page.

Binaries

Binaries are released in the form of BFU archives. Each release of pNFS BFU Archives are combined with release notes which describe the functionality (or lack of functionality) and any known issues that exist in that particular release.

Code

The code drops are currently delivered via a tarball which includes the collection of all of the modified files. The Nevada build that these files are based on will always be documented in the release notes.

Currently we are exploring how to make the code available via an externally accessible Mercurial repository. Stay tuned for more information on this.

2.) Documents:

The following is a list of project documentation and a brief summary of the purpose of the documents. Each document will be posted to the NFS version 4.1 pNFS project website and an announcement will be sent to the nfsv41 dash discuss at opensolaris dot org email alias describing the newly posted document. All reviews of the documents will take place on nfsv41 dash discuss at opensolaris dot org.

a.) Architectural Overview Document

Documents the high level architectural components making up the pNFS project.

b.) Project Requirements Specifications

Lists the functional information for the project (i.e. what are the different pieces supposed to do). This is considered pNFS project documentation and its primary audience will be the test team in order for them to be effective in writing the test plan.

c.) Design Documents

Document the design choices made by the team.

d.) Project Plan

Document how we will run the project.

e.) Test Plan

Document how the project will be verified for quality.

f.) man pages

Document the command line interfaces delivered in order to administer pNFS.

3.) Communication:

Meetings

Currently, there are no plans to hold open meetings.

Website

Our web-home is at: http://www.opensolaris.org/os/project/nfsv41

Email

We will use the nfsv41 dash discuss at opensolaris dot org alias to announce the the availability of the project deliverables outlined here and as a place to hold discussions and gather feedback on the project.

Blogs

The following is a list (in alphabetical order) of bloggers in the OpenSolaris NFS community.

• Alok Aggarwal
• Bill Baker
• Sam Falkner
• Robert Gordon
• Tom Haynes
• Doug McCallum
• Rick Mesta
• Spencer Shepler
• Jim Wahlig
• Lisa Week

(We apologize if we have forgotten anyone. Please send a quick email to nfsv41 at opensolaris dot org to be added to our blog roll.)

4.) Process Steps:

The NFS version 4.1 pNFS project will follow the ARC review process. The ARC case will be ran as an external case meaning that the materials will be posted and reviewed externally.

As a requirement to putback into the onnv-gate the NFS version 4.1 pNFS project will be following the ON C-team review process. Materials for the review will be posted on nfsv41 dash discuss at opensolaris dot org.

How do you fit in?

Use it, give feedback and discuss, report bugs, fix bugs…

• Note: The following information can also be found in the FAQ.

Bug Reporting

What should you do if you find a bug?

Capture as much information as possible and send email to the nfsv41 dash discuss at opensolaris dot org alias.

Information that is useful for us to determine the root cause of a problem is:

1. ) A summary of the problem and what you were doing when you saw the problem. Note: It is good to give as much information as possible here. This will allow us to recreate the problem.
2. ) A summary of your configuration (i.e. I have x data servers running on x machines…).
3. ) What bits do you have installed (i.e. %cat /etc/motd on all machines)?
4. ) If the problem is a panic, provide us the stack trace and access to the core file.

Code Contributions

What should you do if you want to contribute code?

Contact us at nfsv41 dash discuss at opensolaris dot org

Code will be accepted or rejected from community members following the existing OpenSolaris process. The idea is that external contributors will have an internal pNFS project sponsor who is responsible for taking the changes from the external contributor and integrating them into the pNFS project gate. The pNFS project sponsor is also responsible for determining if a set of changes should not be taken.