Because pNFS shifts most of the NFS work to the client, most vendors will wait for an OS vendor to incorporate pNFS. All of the vendors that contributed to the NFSv4.1 protocol and pNFS specification -- including EMC Corp., NetApp Inc. and Panasas Inc. -- are working with Linux kernel developers to finish a client that's stable and meets performance needs.
So what's next? According to NetApp chief technology officer (CTO) and senior vice president (VP) Brian Pawlowski -- and a co-chair of the Network File System Version 4 Working Group -- the NFSv4.0 and NFSv4.1 codes have the foundation to become a multivendor, heterogeneous and federated global namespace technology.
When a client makes a request for a particular portion of the namespace, and the data the client is seeking isn't in that namespace, the NFSv4.0 and NFSv4.1 Server will direct the client to the optimal namespace to retrieve the data, even if the namespace is part of another vendor's system. Pawlowski said this will allow customers to assemble and deploy a namespace from different vendor systems and deploy it globally.
Larry Jones, VP of marketing at Panasas, sees another benefit from pNFS — file server management. "[pNFS] provides a great platform for server consolidation," Jones said. "Another way to think about it is as scale-out NAS. Instead of having a single NAS Server, what parallel NFS lets you do is consolidate a whole bunch of [NAS] servers. You don't have to go hunting all over the place to find your data. Just one mount point and you get to that data."
Jones believes IT administrators expect a performance boost from pNFS, but the manageability and ease of administration "will surprise them."
This was first published in June 2010