On Tue, May 7, 2019 at 1:38 PM Jeffrey Altman <jalt...@auristor.com> wrote:
> Gary, > > As far as I am aware there is no final decision either way with regards to > inclusion of kafs in rhel8. There are several components that were not > merged into Linux mainline until after the 4.18 kernel on which rhel8.0 is > based. These include not only AuriStorFS feature and openafs compatibility > enhancements to kafs but the new Linux mount API which provides namespace > support that kafs leverages and namespacing for keyrings which is needed > for filesystem credential management on behalf of containers. > > There is no business case for Red Hat to commit a ten year investment > simply to support legacy AFS deployments. The justification for including > kafs is to support functionality that will result in new deployments. That > functionality requires the new mount API, keyring namespacing, and even > some features that have yet to be implemented in AuriStorFS. > > The door is not closed. David Howells and the AuriStor team continue to > fill in the gaps. This week a request was filed to add /afs to the File > Hierarchy System (FHS). Inclusion in the FHS is required by some Linux > Distributions before a new roof directory can be added to the distribution. > Cool. Hopefully they might consider it for a "point" release then. Cheers,
