|
The proper forum for discussing protocol changes is
[email protected]. OpenAFS cannot accept or deploy
any protocol changes that have not been approved by that group. Additional responses inline.... On 2/28/2012 11:22 AM, Troy Benjegerdes wrote: Concern does not equal resource availability and Dropbox is not an alternative to AFS. If you have the money to pay Dropbox, then you should start writing checks today to someone in the AFS community to move the things you want forward.If this is *not* a huge concern for the AFS community, then we might as well all start working on AFS to Dropbop migration plans. If someone is sitting on a pile of code, or even a contract to do some IPv6 work, it would be nice to make a public timeline of when it will be available. Your File System committed to implement IPv6 as part of the DoE grant but as with much of the work, the money didn't complete as much of the work as was hoped. The primary cause was that we found that somewhere between 35% and 50% of our time was spent fixing issues that were introduced into the OpenAFS code tree. It was impossible to develop substantial systems on a moving target with the limited resources available to us. Your File System still wants to implement IPv6 and give it to the OpenAFS community but there is at present no funding for that work and our internal priorities are elsewhere. It's not going to help the community any if three different implementations magically appear in December 2012 that haven't been tested outside of the site that's been developing them. That is unlikely to happen. RPCs need to be allocated by the registrars and OpenAFS will not accept code that is not standardized by afs3-standardization. Organizations could develop the work internally and not tell anyone about it but then they are not part of this community. If nothing else, can we at least get all the RPCs and APIs changes defined and documented? Doing so is 80% of the work. |
signature.asc
Description: OpenPGP digital signature
