I personally view OpenVZ as a technology to host application-centric VEs and not offer infrastructure VEs (NFS servers, etc). It's not that OpenVZ cannot do it but it doesn't seem to be it's core goal and there are outstanding issues with some of it (at least for me, no autofs in a VE, etc).Thanks for your feedback, I am really thinking in now take a look in these tools, but not now for two main reasons: 1) I really need to use the traditional nfs therefore must use pnfs in performance tests, and this all within an international collaboration (OSG - Sience Open Grid). I can not ask for that change to another tool for me to validate my this. pnfs and nfs4 are fairly new concepts to Linux. I *think* I understand the goals of this approach and it's benefits but I'd recommend to look at the goals of OpenVZ and how containers gets us this host abstraction. If you look at a shared kernel-based NFS design and how OpenVZ does it's thing, it seems to me that the two approaches are incompatible from at least a security point of view.2) I have not found any mention on the web about support of these tools to pnfs. For my environments, I think this would be good to have posted and see how it does. Maybe one of the OpenVZ developers is reading this and could tell us if such a patch really does exist. If it does, could it be posted (and ideally maintained)? --David |
_______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
