From sac-owner Fri Jul 17 14:39:25 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n6HLdPMH019536 for ; Fri, 17 Jul 2009 14:39:25 -0700 (PDT) Received: from newsunmail1brm.central.sun.com (localhost [127.0.0.1]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6HLdPTO014311 for ; Fri, 17 Jul 2009 15:39:25 -0600 (MDT) Received: (from noaccess@localhost) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/Submit) id n6HLdPNC014309 for one-pager-not-2b-used-directly; Fri, 17 Jul 2009 15:39:25 -0600 (MDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n6HLdN9x014265 for <@sunmail2sca.sfbay.sun.com:one-pager@sun.com>; Fri, 17 Jul 2009 15:39:24 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KMY0080345O5G00@brm-avmta-1.central.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 17 Jul 2009 15:39:24 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KMY00AL945NTJE0@brm-avmta-1.central.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 17 Jul 2009 15:39:23 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6HLdNUJ024189 for ; Fri, 17 Jul 2009 21:39:23 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KMY00B003WY1600@mail-amer.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 17 Jul 2009 15:39:23 -0600 (MDT) Received: from [10.1.106.211] ([unknown] [10.1.106.211]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KMY0046245L1L30@mail-amer.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Fri, 17 Jul 2009 15:39:21 -0600 (MDT) Date: Fri, 17 Jul 2009 14:39:21 -0700 From: Alan M Wright Subject: [2009/399]Reparse Points and Referrals Umbrella Case Sender: alan.m.wright@sun.com To: one-pager@sun.com Message-id: <4A60EF89.7070303@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 9906 Template Version: @(#)onepager.txt 1.35 07/11/08 SMI Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Reparse Points and Referrals Umbrella Case 1.2. Name of Document Author/Supplier: Alan Wright 1.3. Date of This Document: 07/16/2009 1.3.1. Date this project was conceived: 01/07/2009 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris PAC 1.4.2. The ARC(s) you expect to review your project: PSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Fred.Zlotnick@Sun.COM 1.4.4. The name of your business unit: Solaris File Systems 1.5. Email Aliases: 1.5.1. Responsible Manager: Fred.Zlotnick@Sun.COM 1.5.2. Responsible Engineer: Alan.M.Wright@Sun.COM 1.5.3. Marketing Manager: 1.5.4. Interest List: reparse-points@Sun.COM 2. Project Summary 2.1. Project Description: This project is the umbrella case to document the roadmap for reparse points and referrals. The roadmap will be delivered in phases and will be documented in subsequent PSARC cases. The intent of this case is to provide the overall context and motivation to add reparse points by describing an implementation (referrals) that will be built on the fundamental infrastructure provided by reparse points. 2.2. Risks and Assumptions: Support for referrals is predicated on the availability of a reparse point implementation. The infrastructure being proposed may introduce changes to existing file system objects and VFS interfaces. Significant efforts will be made to prevent incompatibilities and minimize the potential for any changes proposed in this or the follow-on cases to affect existing behavior. The intent is to avoid introducing changes that will affect the Single UNIX Specification or the IEEE and ISO POSIX standards. 3. Business Summary 3.1. Problem Area: This roadmap will improve both UNIX and Windows interoperability by adding support for features that are being delivered by other UNIX vendors and Microsoft (for Windows). Reparse points are a feature of NTFS, the main file system used with Microsoft Windows, and provide the underpinning for symbolic links, junctions, mount points and, of particular interest here, the Microsoft Distributed File System (MS-DFS). MS-DFS is a referral mechanism that is conceptually similar to NFS4.x referrals. The addition of reparse points will provide the enabling infra- structure to support both SMB referrals (MS-DFS) and NFS referrals, which may be used to provide powerful and flexible features, such as namespace aggregation. In essence, referrals extend the concept of a symbolic link to go beyond the local system and refer clients to locations within file system namespaces on other systems. The result would be the ability for customers to create a unified namespace from a collection of separate and/or disparate file systems on a collection of independent machines. 3.2. Market/Requester: Customers would include, but are not limited to, users of OpenSolaris and Amber Road. 3.3. Business Justification: Customers using both OpenSolaris and Amber Road have requested support for MS-DFS and NFS referrals. 3.4. Competitive Analysis: NFS is a key technology for Sun and support for NFS referrals will help Sun remain a market leader in NFS feature support. Microsoft and many NAS vendors, such as Network Appliance and EMC, support MS-DFS. Windows interoperability is a high priority for Sun, MS-DFS is heavily deployed in the marketplace and Sun is currently lagging in this area with respect to Windows interoperability. 3.5. Opportunity Window/Exposure: ASAP, with phased deliveries of the projects into OpenSolaris. 3.6. How will you know when you are done?: When customers can create NFS and SMB referrals on OpenSolaris and integrate OpenSolaris into existing MS-DFS environments. 4. Technical Description: 4.1. Details: An overview of identified projects follows below. The specifics of each sub-project will be detailed in the follow-on projects. Reparse points are file system objects that allow applications and services (consumers) to store tagged identifiers. Identifiers are typed such that consumers can identify their own identifiers and take consumer specific action when such an object is encountered in the file system. Referrals represent a specific use of reparse points to redirect a service, such as NFS or SMB, to another location. Referrals are similar to symlinks in that they redirect path processing to resume at a target location but they extend the model to include targets on different, disparate file systems, which may reside on other machines running different operating systems. Referrals provide a means to create aggregated namespaces from a collection of separate and/or disparate file systems on a collection of independent machines. File systems should treat reparse points and referrals as opaque objects and are not expected to interpret them. The follow-on projects will define the specific implementation details and syntax but, for the purpose of illustration only, the NFS service might create a reparse point represented by the tag NFS and a UUID. When the NFS service encounters this reparse point, it can take the appropriate action indicated by the UUID. A reparse point of the form NFS:550e8400-e29b-41d4-a716-446655440000 may resolve to path@host. The NFS server would refer an NFS client to connect to 'path' on 'host'. Other services, such as SMB, would not attempt to act on this reparse point. The follow-on projects are: 1. Reparse Points The reparse points project will define and implement the infra- structure to support these objects, which will include a library and service to parse reparse tags. 2. NFSv4 Referrals This project will provide support for NFSv4 referrals as defined in RFC 3530. 3. Standalone MS-DFS This project will provide support for SMB referrals in a standalone (single root) configuration as defined in [MS-DFSC]: Distributed File System (DFS): Referral Protocol Specification and [MS-DFSNM]: Distributed File System (DFS): Namespace Management Protocol Specification. A DFS root is the top of a DFS topology and the start of a shared folders hierarchy. A DFS root can be defined at the server level or at the domain level. A standalone DFS root is hosed and stored on a single machine, as opposed to being stored in Active Directory. 4. Domain based MS-DFS This project will extend the functionality from the standalone MS-DFS project to add support for domain based DFS. Domain based DFS is hosted on Active Directory member servers or domain controllers, with the topology stored in Active Directory. 4.2. Bug/RFE Number(s): 6232743 Server should support NFS4ERR_MOVED error and fs_locations attribute 6711751 SMB/CIFS Distributed File System (DFS) 4.3. In Scope: The framework and services to support reparse points and NFS and SMB referrals. 4.4. Out of Scope: Automounter enhancements. 4.5. Interfaces: Interfaces will be specified on a per-project basis. 4.6. Doc Impact: Manual pages and administration guides will be impacted by projects on this roadmap. 4.7. Admin/Config Impact: Configuration will be needed to define referrals with a goal to keep administration simple. Where possible, Windows MS-DFS tools will be supported. Configuration changes never require a reboot. 4.8. HA Impact: None 4.9. I18N/L10N Impact: None 4.10. Packaging & Delivery: None 4.11. Security Impact: None. Referrals depend on the security in place at the referral target. No security impact is envisaged with the addition of reparse points or referrals. 4.12. Dependencies: NFS and SMB referrals will depend on reparse points. 5. Reference Documents: RFC 3530 NFSv4 Protocol http://www.ietf.org/rfc/rfc3530.txt http://www.citi.umich.edu/projects/nfsv4/linux/using-referrals.html http://nfsv4.bullopensource.org/doc/migration-and-replication-0.2.pdf http://docs.hp.com/en/5900-0306/ch01s11.html?jumpid=reg_R1002_USEN http://docs.hp.com/en/13578/nfsv4_whitepaper.pdf http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/com.ibm.aix.commadmn/doc/commadmndita/nfs_referrals.htm Windows Server Protocols (WSPP) http://msdn.microsoft.com/en-us/library/cc197979(PROT.10).aspx) [MS-DFSC]: Distributed File System (DFS): Referral Protocol Specification [MS-DFSNM]: Distributed File System (DFS): Namespace Management Protocol Specification Overview of DFS in Windows 2000 http://support.microsoft.com/kb/812487 6. Resources and Schedule: 6.1. Projected Availability: Reparse Points Q3 CY2009 NFSv4 Referrals Q4 CY2009 Standalone MS-DFS Q4 CY2009 Domain MS-DFS Q1 CY2010 6.2. Cost of Effort: To be defined by the follow-on projects. 6.3. Cost of Capital Resources: Existing lab clients and servers will be used. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: To be defined by the follow-on projects. 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: Reparse Points snv_123 Standalone MS-DFS snv_125 NFSv4 Referrals snv_130 Domain MS-DFS snv_137 6.4.8. Target Code Design Review Date: To be defined by the follow-on projects. 6.4.9. Update approval addition: No 6.5. ARC review type: Standard 6.6. ARC Exposure: Open 7. Prototype Availability: 7.1. Prototype Availability: To be defined by the follow-on projects. 7.2. Prototype Cost: To be defined by the follow-on projects.