draft-ietf-nfsv4-federated-fs-reqts-02.txt | draft-ietf-nfsv4-federated-fs-reqts-03.txt | |||
---|---|---|---|---|
NFSv4 Working Group J. Lentini | NFSv4 Working Group J. Lentini | |||
Internet-Draft C. Everhart | Internet-Draft C. Everhart | |||
Intended status: Informational NetApp | Intended status: Informational NetApp | |||
Expires: October 22, 2009 D. Ellard | Expires: November 19, 2009 D. Ellard | |||
BBN Technologies | BBN Technologies | |||
R. Tewari | R. Tewari | |||
M. Naik | M. Naik | |||
IBM Almaden | IBM Almaden | |||
April 20, 2009 | May 18, 2009 | |||
Requirements for Federated File Systems | Requirements for Federated File Systems | |||
draft-ietf-nfsv4-federated-fs-reqts-02 | draft-ietf-nfsv4-federated-fs-reqts-03 | |||
Status of this Memo | Status of this Memo | |||
This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
Drafts. | Drafts. | |||
skipping to change at page 1, line 37 | skipping to change at page 1, line 37 | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on October 22, 2009. | This Internet-Draft will expire on November 19, 2009. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2009 IETF Trust and the persons identified as the | Copyright (c) 2009 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents in effect on the date of | Provisions Relating to IETF Documents in effect on the date of | |||
publication of this document (http://trustee.ietf.org/license-info). | publication of this document (http://trustee.ietf.org/license-info). | |||
Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
skipping to change at page 4, line 45 | skipping to change at page 4, line 45 | |||
that can be used to look up the location information. The service | that can be used to look up the location information. The service | |||
that can be used to map from FSN to FSL(s) is called a namespace | that can be used to map from FSN to FSL(s) is called a namespace | |||
database (NSDB) service. The NSDB provides a level of indirection | database (NSDB) service. The NSDB provides a level of indirection | |||
from the virtual paths in the uniform namespace to the actual | from the virtual paths in the uniform namespace to the actual | |||
locations of files. | locations of files. | |||
The servers direct clients to the proper locations by existing | The servers direct clients to the proper locations by existing | |||
mechanisms (e.g. the referrals mechanism within [RFC3530] and | mechanisms (e.g. the referrals mechanism within [RFC3530] and | |||
[NFSv4.1]). Updates to the locations make it possible to support | [NFSv4.1]). Updates to the locations make it possible to support | |||
migration and replication of physical filesystems that comprise the | migration and replication of physical filesystems that comprise the | |||
namespace, in a way that is transparent to filesystem clients. | namespace, in a way that is transparent to filesystem applications. | |||
Figure 1 shows an example of a federation. This federation has two | Figure 1 shows an example of a federation. This federation has two | |||
members, named ALPHA and BETA. Federation members may contain an | members, named ALPHA and BETA. Federation members may contain an | |||
arbitrary number of file servers and NSDB nodes; in this illustration | arbitrary number of file servers and NSDB nodes; in this illustration | |||
ALPHA and BETA each have three servers and one NSDB node. | ALPHA and BETA each have three servers and one NSDB node. | |||
+----------------------+ +----------------------+ | +----------------------+ +----------------------+ | |||
| Federation Member | | Federation Member | | | Federation Member | | Federation Member | | |||
| ALPHA | | BETA | | | ALPHA | | BETA | | |||
| | | | | | | | | | |||
skipping to change at page 10, line 41 | skipping to change at page 10, line 41 | |||
| | Server X | | | | Server Y | | | | | Server X | | | | Server Y | | | |||
| | | | | | | | | | | | | | | | | | |||
| +---------------+ | | +---------------+ | | | +---------------+ | | +---------------+ | | |||
| | | | | | | | | | |||
+-----------------------+ +-----------------------+ | +-----------------------+ +-----------------------+ | |||
Figure 2 | Figure 2 | |||
4.3. Junction Creation | 4.3. Junction Creation | |||
Given a local path, a remote export and a path relative to that | Given a local path and the FSN of a remote fileset, an administrator | |||
export, create a junction from the local path to the path within the | can create a junction from the local path to the remote fileset. | |||
remote export. | ||||
There are many possible variations to this procedure, depending on | There are many possible variations to this procedure, depending on | |||
how the junctions are represented and how the information necessary | how the junctions are represented and how the information necessary | |||
to perform resolution is represented by the server. | to perform resolution is represented by the server. | |||
Step 1 is the only step that uses the federation interfaces. The | Step 1 is the only step that uses the federation interfaces. The | |||
rest of the steps may use platform-specific interfaces. | remaining step may use platform-specific interfaces. | |||
1. Contact the server named by the export and ask for the FSN for | 1. The administrator requests the server create a junction to the | |||
the fileset, given its path relative to that export. | FSN of the remote fileset at the given path. | |||
2. Insert the junction to the FSN, at the given path, into the local | 2. The server inserts the junction to the FSN, at the given path, | |||
filesystem. | into the local filesystem. | |||
5. Glossary | 5. Glossary | |||
Administrator: user with the necessary authority to initiate | Administrator: user with the necessary authority to initiate | |||
administrative tasks on one or more servers. | administrative tasks on one or more servers. | |||
Admin entity: A server or agent that administers a collection of | Admin entity: A server or agent that administers a collection of | |||
fileservers and persistently stores the namespace information. | fileservers and persistently stores the namespace information. | |||
Client: Any client that accesses the fileserver data using a | Client: Any client that accesses the fileserver data using a | |||
End of changes. 9 change blocks. | ||||
13 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |