From ellard at netapp.com Thu Apr 5 16:02:13 2007 From: ellard at netapp.com (Daniel Ellard) Date: Thu, 05 Apr 2007 19:02:13 -0400 Subject: [Federated-fs] New draft of requirements for federated file systems Message-ID: Many thanks to the folks who sent in their comments on the first draft. We haven't addressed all the issues raised, but we're getting a lot closer and it's time for another round... Attached are the latest version of the requirements draft for federated file systems and the diffs between this version and the previous. Please let me know if you have any problems viewing it. The next conference call to discuss the draft will be Monday, April 9, 4:00-5:00pm EDT. The conference call number will be the same as last time. Please let me know if you want to dial in and do not already have the phone info. Thanks, -Dan -------------- next part -------------- A non-text attachment was scrubbed... Name: DistFSReqts2.txt Type: application/octet-stream Size: 33891 bytes Desc: not available Url : https://lists.sdsc.edu/pipermail/federated-fs/attachments/20070405/5b5e4d3e/DistFSReqts2.txt -------------- next part -------------- A non-text attachment was scrubbed... Name: diffs1-2.txt Type: application/octet-stream Size: 9415 bytes Desc: not available Url : https://lists.sdsc.edu/pipermail/federated-fs/attachments/20070405/5b5e4d3e/diffs1-2.txt From ellard at netapp.com Tue Apr 10 08:55:04 2007 From: ellard at netapp.com (Ellard, Daniel) Date: Tue, 10 Apr 2007 11:55:04 -0400 Subject: [Federated-fs] Draft 3 of the requirements doc Message-ID: Attached are revision 3 of the federated fs requirements draft, and a context diff of the first revision and the third. One of the major changes to the document was re-ordering the sections (to move the examples and discussion to the front of the document rather than at the end) which resulted in a large number of the diffs, which I have elided from the attached diffs. Please note that if you are still reviewing the second revision, the diffs I sent in an earlier email are incorrect -- they were supposed to be the diffs between revision 1 and revision 2, but instead are the diffs between an intermediate draft (between revision 1 and 2) and revision 2. I apologize for any inconvenience or confusion this may have caused. If you'd like the correct diffs, let me know. The next conference call is tentatively scheduled for Friday, April 20, at 4pm EDT. I'd like to get wide participation in this call, so if this time does not work for you, please let me know and/or propose a better time. (Please keep in mind that some of the people on this list will be at Storage Networking World next week.) -Dan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: diffs1-3.txt Url: https://lists.sdsc.edu/pipermail/federated-fs/attachments/20070410/d6b6daca/diffs1-3.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: DistFSReqts3.txt Url: https://lists.sdsc.edu/pipermail/federated-fs/attachments/20070410/d6b6daca/DistFSReqts3.txt From ellard at netapp.com Fri Apr 20 13:59:07 2007 From: ellard at netapp.com (Ellard, Daniel) Date: Fri, 20 Apr 2007 16:59:07 -0400 Subject: [Federated-fs] Apologies for the lack of conf call Message-ID: My apologies if you tried to join the conference call today and couldn't. Nobody could. I didn't enter the correct date on my calendar and scheduled myself for something else this afternoon, and unfortunately I'm the only person with the PIN for that conference call number, so nobody else could host it. I will reschedule for next week. Again, I apologize. -Dan From ellard at netapp.com Wed Apr 25 07:44:57 2007 From: ellard at netapp.com (Ellard, Daniel) Date: Wed, 25 Apr 2007 10:44:57 -0400 Subject: [Federated-fs] Next conf call: Friday 4pm EDT Message-ID: The next federated-fs conference call to discuss the current requirements draft is tentatively scheduled for Friday April 27 at 4:00pm EDT. Please let me know if you need the dial-in info. Also let me know if you want to join the call, but cannot make that time. We may be able to reschedule. Thanks, -Dan