Subject: [nfsv4] Scribe from May 3rd

From: "Reyes-Ortiz, Talia" <[email-masked]>
Date: Fri, 4 May 2012 21:38:40 +0000

On call: Audrey/Talia, Tom, Chuck, Trond, Bryan Schumaker, Marc, Andy , Bondi, Bruce, Dean

Note-well agreement - not private, first bi-weekly 4.1 main document no xdr, changed from 4.1 draft version 9. To get to line number run cat minus n to produce document, not all chapters are finished.

3 items to makes sure process is working, not sure on speed, just learning. Review order going to kept up to date in the repository - no tabs, no spaces at the end of lines, how to send patches. On linux know how to do it, commands from Bruce, attached copies to get clone from repository.

Questions - Tom: how do we do the readers? Switch off? Don't mind doing it today but once in server side copy, main author of draft to read. Format to follow, discuss section in order, take notes and AI, I produce notes sometime a week before the next meeting, then resolve issues in email. Unless important enough, continue going through the document.

START: 13.9 Changes to Operation 51: LAYOUTRETURN

Draft 9 Line 4177 - Tom: Layoutreturns- allow MDS to report back an error back to client 8 class of items in 4.2 that is a clarification to 4.1, not new operation, modification.

4195 - Tom: "to be persistent" is an error -> to be transient [ANDY agrees]

4206 - Andy:  NSFS error_stale_stateID -> error_bad_stateID

4207- 4210 Tond: change the mandatory to optional
MDS shouldn't be expecting to report an error, should be optional for the client.  Sounds mandatory, ANDY - knows it's bad trying to fence -client filehandle a better example. Trond - not required to, only client out there will forget the whole stateID, find a wording that exercise the fact that is optional not man

4225 - ANDY: Need to add a sequence number? - follow up in email: Any reason to provide any sequence number information? Know exactly what operation changed the error

4247 - TOM: Add, For both "filebased layout" and "Block-based layout"

4177 - Trond: concerned this violates the minor version rules to put in this operation.  Proceed to checking the rest of the section and respond in email.
Add new argument types, can't make incompatible change to existing arguments, adding a new structure that goes into opaque field, Trond - seems backward incompatible. Nothing here is mandatory to be implemented)
4265 - Andy: question why NFS4_OKAY to be returned? Proposals - should be removed (go back and figure it out.

4265 - Chuck: NFS4_OKAY to NFS4_OK and why have it at all?

4267 - Trond: No supporting text for this error in the introduction, Tom is going to go back and add text.  Lapse case in any of the preamble, emphasis on relaying error codes. Andy wants to clarify what happens in there was some communication and it stops.

4279 & 4280 - Andy: Both "should" too stringent

4279 - Entire paragraph - Trond is questioning if whether it belongs there at all, need to be reviewed

4291 -Trond: Add the word "device" in front of "access"

4229 - The MDS "May" should be capitalized

4299 - Trond - Add new sentence to describe why the client wants to return the layout for fencing, will return for edits (Recommended even for forgetful clients)

4324 - Andy: remove 4326-4328 and move up to previous paragraph. Trond: Take out entire paragraph, really necessary?

4320-28 - Action Items: rewrite telling the clients what they must be prepared to receive the device with a bad ID.

4330 - 4331- Trond: Remove half the sentence up to the "but"

4333 - Chuck: Whether there may be a mix match in expectation, how the long the data is cached

4337 - Andy: Would this be redundant to 4.1 Symantics
Dean: Order of chapters list, sections are off; chapter 4 is now chapter 3. Not as complete of a section, needs to be editing to have it flow better.
Goal is to have done by Vancouver meeting in August

END
Start next meeting: 13.10 Operation 65: READ_PLUS

Change requests - will be taken only up to a certain time after the reading period after which we will not allow additional comments or changes. Comments on sections reviewed can be sent in until the day before the meeting (1 week). And if meeting is missed comments can be sent in on the section being reviewed prior to the weekly meeting.
Cheers!
Talia Reyes-Ortiz
Program Manager
CTO Office
NetApp Inc.
408.822.1566 Direct Phone
[email-masked]
[Description: http://media.netapp.com/images/esigs-innovative-company-480x75.png]<http://www.forbes.com/special-features/innovative-companies.html>