Our team is planning to provide CloudFoundry PaaS service and we have found two main use cases when FSS should be mounted at the arbitrary locations:
1. We believe that the target audience for FSS would be an existing applications (mainly written in PHP). It may happen that:
a) Application is written without usage of DRY principle and there may be cases when it will require a lot of work to rewrite filesystem access code so that it will use folders names provided by the CloudFoundry platform.
b) Application is written with usage of 3rd-party libraries. These libraries may write to the pre-defined locations and it might be hard/impossible to change these locations from the client code. For example this is the case with some PHP CMS.
2. If someone want to auto-migrate (I mean automatically prepare application for provisioning into cloudfoundry) many existing applications from another hosting to the CF cloud (or maybe provide auto-migration service to the cloudfoundry users), then it will require significantly more automation work (or sometimes will be impossible taking into account item 1.b).
Also, in my opinion, it looks more natural from the user perspective to set folder name for FSS service and then mount this folder to the application. What do you think?
Actually we were planning to create FSS from scratch until we found out that someone is already working on this feature. Also, we would like to provide FSS on top of GlusterFS instead of nfs, thus we need to write additional "FSS provisioning adapter". How can we join the development effort for this feature? Are there any public git branch and/or tasks list available?
Best regards,
Alex