“If you’re going to use NFS for your enterprise apps, any generic NFS server will do…“
– Said no one. Ever.
So it’s well known that Red Hat is a huge contributor to the Open Source community, especially Linux. But it should also come as no surprise that Red Hat also depends on others for certain core components. A great example is the Linux NFS Client stack, which handles everything I/O related from the OS (and kernel) perspective.
Here’s a fun fact: A number of NetApp engineers currently maintain the Linux NFS Client stack. As code and patches are created, they are tested (relentlessly!) against the NetApp NFS server. Once the code/patches/features/fixes are successfully tested, they are submitted to the upstream Linux kernel maintainers.
(I promise I’ll get back to the beer & pretzels.)
To develop each version of Red Hat Enterprise Linux, Red Hat engineering consumes the Linux NFS Client stack as part of the Linux kernel. Red Hat adds their own code and patches, that are also submitted upstream, and then redistributes it in Red Hat Enterprise Linux.
More importantly, Red Hat & NetApp also collaborate on NFS-related activities. A lot. So while other Linux distributions could technically claim that they pull from the same upstream Linux kernel, they can’t claim the same level of collaboration with NetApp on NFS.
They go together like Beer & Pretzels – imagine NetApp Beer paired with Red Hat Pretzels, with a big bowl of Red Hat Pretzel Cheese Dip made with real NetApp Beer!
The Linux NFS Client stack works with any standards compliant NFS server, but the Linux NFS client stack as distributed with RHEL was created in conjunction with NetApp NFS. In other words, they were made for each other. Like Beer & Pretzels.
And if you’re ever in Raleigh, NC, check out the Boylan Bridge Brew Pub, they’ve got GREAT beer & pretzels.
var _gaq = _gaq || ; _gaq.push(['_setAccount', 'UA-36272553-1']); _gaq.push(['_trackPageview']);