Re: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-flex-filesv2-00.txt

[David Noveck <[e-mail]>]

> And Ben, the other reason not to use a typed opaque auth blob
> is because the  ffds_user and ffds_group are strings, and do
> not fit into AUTH_UNIX.

I don''t see how the fact that ffds_user and ffds_group, being strings,
do not fit into AUTH_UNIX can be argument for retaining them.  If
the existence of AUTH_UNIX is relevant to the matter, it would argue
for deleting ffds_user and ffds_group and subsuming them both
within ffds_auth.

The situation is the same regarding the fact there might be arrays of these
things.  Clearly, if one of these items needs to be an array, they all do..
If that's the case, it would be better to have one potentially troublesome
array rather than three.

On Mon, Aug 7, 2017 at 8:25 PM, Thomas Haynes <[e-mail]>
wrote:

> So here is a first hack at Flex Files v2. I thought it would come in much
> smaller than 11 pages,
> so perhaps some pruning will be necessary.
>
> I’m aware Ben had some comments on:
>
>    Can I suggest putting in a typed opaque auth blob instead of explicit
>    synthetic uid/gid fields?
>
> I have purposely done:
>
>    /// struct ffv2_data_server4 {
>    ///     deviceid4               ffds_deviceid;
>    ///     uint32_t                ffds_efficiency;
>    ///     stateid4                ffds_stateid<>;
>    ///     nfs_fh4                 ffds_fh_vers<>;
>    ///     fattr4_owner            ffds_user;
>    ///     fattr4_owner_group      ffds_group;
>    ///     opaque_auth             ffds_auth;
>    /// };
>
> Because of AI1:
>
>    [[AI1: after the lesson learned from ffds_stateid, we either need to
> put an
>    array here or define all of the file handles to share the same
>    credentials.  And as Olga points out in her email, this gets big
>    fast.  Especially if we throw in many mirrored copies!  --TH]]
>
> I.e., the ffds_auth is inside an array of ffv2_data_server4 which is
> in itself inside an array of ffv2_mirror4 AND it could be argued that
> ffds_auth (and ffds_user/ffds_group) need to be an array.
>
> Even if we decide to make all FHs share the same credentials, we
> eventually can hit a limit of the number of mirrored copies.
>
> And Ben, the other reason not to use a typed opaque auth blob
> is because the  ffds_user and ffds_group are strings, and do
> not fit into AUTH_UNIX. We could define AUTH_SYNTHETIC. :-)
>
> Begin forwarded message:
>
> *From: *<[e-mail]>
> *Subject: **New Version Notification for
> draft-haynes-nfsv4-flex-filesv2-00.txt*
> *Date: *August 7, 2017 at 5:11:45 PM PDT
> *To: *Thomas Haynes <[e-mail]>
>
>
> A new version of I-D, draft-haynes-nfsv4-flex-filesv2-00.txt
> has been successfully submitted by Thomas Haynes and posted to the
> IETF repository.
>
> Name: draft-haynes-nfsv4-flex-filesv2
> Revision: 00
> Title: Parallel NFS (pNFS) Flexible File Layout v2
> Document date: 2017-08-07
> Group: Individual Submission
> Pages: 11
> URL:            https://www.ietf.org/internet-drafts/draft-
> haynes-nfsv4-flex-filesv2-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-haynes-
> nfsv4-flex-filesv2/
> Htmlized:       https://tools.ietf.org/html/draft-haynes-nfsv4-flex-
> filesv2-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-
> haynes-nfsv4-flex-filesv2-00
>
>
> Abstract:
>   The Parallel Network File System (pNFS) allows a separation between
>   the metadata (onto a metadata server) and data (onto a storage
>   device) for a file.  The flexible file layout type is an extension to
>   pNFS which allows the use of storage devices in a fashion such that
>   they require only a quite limited degree of interaction with the
>   metadata server, using already existing protocols.  This document
>   describes two extensions to the flexible file layout type to allow
>   for multiple stateids for tightly coupled NFSv4 models and an
>   additional security mechanism for loosely coupled models.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> nfsv4 mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/nfsv4
>
>