#ident "@(#)issues	1.4 07/07/11 SAC"

PSARC 2007/249:	pNFS/basic
Submitter:	Brian Wong
Owner:		Mark Carlson
Intern:		Garrett.Damore@Sun.COM	

jdc-1	Should this work with Sun Cluster as well?  If so, what needed
	functionality does SC already provide?

jdc-2	The control protocol doesn't look "project private" to me, but
	rather "committed private."  Otherwise, individual node
	upgrade may be impossible and require a server-wide flag day.

jdc-3	What's the difference between a "rejected" and a "removed"
	group member in npool?  What's the intended usage model for
	"waiting" and "approved" pools and members?

jdc-4	How does "dpool add interface" actually control anything by
	interface?  Is it actually controlling by way of address
	binding or something more?

jdc-5	Can data pools be delegated to non-global zones, or are they
	restricted in the same way as general NFS servers?

jdc-6	How is data consistency guaranteed with writes to ordinary
	striped and multi-pathed files?  (It seems like this would
	require some sort of private data pool to data pool
	communications path.)

jdc-7	We approved integration of ethereal/wireshark in PSARC
	2007/334.  Should that be updated as well as (or in preference
	to) snoop?

jdc-8	Suggest roping off group names with some known form (such as
	"SUNW*") for future use, in addition to special "default"
	group.

gcs-1	Please describe the dpool life cycle.  The mentions of
	"approve" and "reject" in the dpool man page give some hints,
	but no more than that.

gcs-2	(Expanding jdc-6):  Please describe failure semantics.  E.g.,
	what happens if the mds or a ds crashes in the middle of
	handling a client request?

gcs-3	[nit] Please use the current interface taxonomy (e.g.,
	"evolving" and "standard" are no longer used).

seb-1	Include user interfaces and their stability levels in your
	exported interfaces table.

seb-2	The draft man pages referenced in the functional specs are missing
	from the case directory.  Please place copies there.