From owner-freebsd-fs@freebsd.org Tue Jun 21 16:20:33 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4628AC5BD5 for ; Tue, 21 Jun 2016 16:20:33 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94CE3219C for ; Tue, 21 Jun 2016 16:20:33 +0000 (UTC) (envelope-from lkateley@kateley.com) Received: by mail-it0-x22c.google.com with SMTP id f6so18139247ith.0 for ; Tue, 21 Jun 2016 09:20:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kateley-com.20150623.gappssmtp.com; s=20150623; h=reply-to:subject:references:to:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=xUZbt6t5MHl8Y9Ex6+5wM7zbfuQ0jK4TD+HlOgqS9MQ=; b=rCl7umQ/p68PjmhsnLeV2m34xTCOQKVvPr1Jh3hRZTq7ihGzJO9zve/Q1nmVS62+J4 zQ0bMK+KV2QmVeeBiEqZpEsvlfmLNnm56bj3X7UY8Gs8897Pv5L3EtPuObLl8TFdfb4M SiySybo8kkaho41r6APirjaOdsII+8gfWgAA8RsLIoskIMUcM1zQoSyYkT09Ggxk6Ccm AfuxoC8MNMBSiIl/S88BUakcsa5GoZhNiY3X0FimYCM40Ia2IcaGaezNJU+T9bEJz/6s 1BLyTRMIcn5WagvXV7aJbKhVZDbSHmknsk+XwrJOEltds0fNnxSb8B+y23JToCTmA00Q PlFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=xUZbt6t5MHl8Y9Ex6+5wM7zbfuQ0jK4TD+HlOgqS9MQ=; b=STgar0GTqtMdOjv7SUiDw+tRyLIENB1Qtoji1Bh2l2sOM8HAVG/9oOCDDA7qrooV64 bdVBMis2jesBVAAs5fh1a1gUX7BhsGCK/mh9FzjNpc9psV+VusgbtWyikC475b6cHYFF exRiG6ELYJ3iNxvWFhEAtq+Dc1rcyjzfDW/m6GX7eiK/2OTud5gZpSdpQ+Rj8NEw06Kr qH7Zsv7LgMviitwIy3pZYSECTTUnzEDXa+/ujZNdfJ1mH0Gej1wKUJbNbKtRORpQ0G1F rYjlUS+H/s3ITy8ID8LqamvGlZwenZVK6kuErPqoh2yvGUscIRzXm2AdwDQE4bHADmCn M5TQ== X-Gm-Message-State: ALyK8tKo5I+GLAROiJGfrbaqtys9RBxbW2LqIv6LxrJjqc69dfkag1R+RWlicCu/n8Gz2Q== X-Received: by 10.36.192.9 with SMTP id u9mr7160157itf.90.1466526032478; Tue, 21 Jun 2016 09:20:32 -0700 (PDT) Received: from Kateleyco-iMac.local ([63.231.252.189]) by smtp.googlemail.com with ESMTPSA id s205sm1644167itd.16.2016.06.21.09.20.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jun 2016 09:20:31 -0700 (PDT) Reply-To: linda@kateley.com Subject: Re: pNFS server Plan B References: <1524639039.147096032.1465856925174.JavaMail.zimbra@uoguelph.ca> <74CD7EB1-1656-4511-8B63-5C4401D1BB8D@ixsystems.com> To: freebsd-fs@freebsd.org From: Linda Kateley Organization: Kateley Company Message-ID: <5ccbd619-88f2-8480-727a-4b70f11a35ba@kateley.com> Date: Tue, 21 Jun 2016 11:20:27 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <74CD7EB1-1656-4511-8B63-5C4401D1BB8D@ixsystems.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2016 16:20:33 -0000 I have really enjoyed this discussion. Just to echo this point further. I have spent most of my career with 1 foot in opensource and the other 3 feet in the enterprise(And yes I have 4 feet.). Enterprise always makes decisions based on reliability or someone telling them something is reliable. If you ask 100 vmware admins why they use nfs probably 100 will say because vmware recommends it. If you ask a CT at vmware why they recommend it, the couple I have asked have said because it is a reliable transport. Vmware now has interest in pnfs. Technology gets driven by business/enterprise. I talked to a CA at a large electronics chain and asked why they are using ceph and he said about 100 words, then said because red hat recommends it with openstack. Intel is driving lustre. RHEL driving ceph. Vmware driving pnfs. I don't see anyone driving gluster. Every once in awhile you see products grow on their merit(watching proxmox and zerto right now) but those usually get swooped up by a bigger one. To the point of setting up kerberized nfs, AD has made kerberos easy, it could be just as easy with nfs. Everything is easy once you know it. lk On 6/20/16 9:54 PM, Jordan Hubbard wrote: > OK, wow. This appears to have turned into something of a referendum on NFS and, just based on Rick and Doug’s defense of pNFS, I also think my commentary on that may have been misconstrued somewhat. > > So, let me just set the record straight by saying that I’m all in favor of pNFS. It addresses a very definite need in the Enterprise marketplace and gives FreeBSD yet another arrow in its quiver when it comes to being “a player” in that (ever-growing) arena. The only point I was trying to make before was that if we could ALSO address clustering in a more general way as part of providing a pNFS solution, that would be great. I am not, however, the one writing the code and if my comments were in any way discouraging to the folks that are, I apologize and want to express my enthusiasm for it. If iXsystems engineering resources can contribute in any way to moving this ball forward, let me know and we’ll start doing so. > > On the more general point of “NFS is hard, let’s go shopping” let me also say that it’s kind of important not to conflate end-user targeted solutions with enterprise solutions. Setting up a Kerberized NFSv4, for example, is not really designed to be trivial to set up and if anyone is waiting for that to happen, they may be waiting a very long time (like, forever). NFS and SMB are both fairly simple technologies to use if you restrict yourself to using, say, just 20% of their overall feature-sets. Once you add ACLs, Directory Services, user/group and permissions mappings, and any of the other more enterprise-centric features of these filesharing technologies, however, things rapidly get more complicated and the DevOps people who routinely play in these kinds of environments are quite happy to have all those options available because they’re not consumers operating in consumer environments. > > Sun didn’t design NFS to be particularly consumer-centric, for that matter, and if you think SMB is “simple” because you clicked Network on Windows Explorer one day and stuff just automagically appeared, you should try operating it in a serious Windows Enterprise environment (just flip through some of the SMB bugs in the FreeNAS bug tracker - https://bugs.freenas.org/projects/freenas/issues?utf8=✓&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=*&f%5B%5D=category_id&op%5Bcategory_id%5D=%3D&v%5Bcategory_id%5D%5B%5D=57&f%5B%5D=&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=fixed_version&group_by= - if you want to see the kinds of problems users wrestle with all the time). > > Anyway, I’ll get off the soapbox now, I just wanted to dispute the premise that “simple file sharing” that is also “secure file sharing” and “flexible file sharing” doesn’t really exist. The simplest end-user oriented file sharing system I’ve used to date is probably AFP, and Apple has been trying to kill it for years, probably because it doesn’t have all those extra knobs and Kerberos / Directory Services integration business users have been asking for (it’s also not particularly industry standard). > > - Jordan > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"