naming
DESCRIPTION
Naming. CSCI 6900/4900. Mounting. Mounting – Merging different namespaces transparently File system example Directory node of one namespace stores identifier of directory node of another namespace Mount Point – Directory node storing the foreign ID - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/1.jpg)
Naming
CSCI 6900/4900
![Page 2: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/2.jpg)
Mounting• Mounting – Merging different namespaces
transparently• File system example
– Directory node of one namespace stores identifier of directory node of another namespace
– Mount Point – Directory node storing the foreign ID– Mounting Point – Directory node in foreign space– Resolution occurs by looking up mounting point and
then accessing its directory table• Can be generalized to other namespaces as well
![Page 3: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/3.jpg)
Mounting Foreign Namespaces• Namespaces on different servers possibly on different
machines– Mounting might require network communication
• Mounting requires at least three information– Name of access protocol– Name of server– Name of mounting point in foreign space
• Each name needs to be resolved– Mounting point needs to be resolved by the foreign server– Three names are represented as a URL– Example: nfs://flits.cs.vu.nl//home/steen
![Page 4: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/4.jpg)
Mounting - Example
Tracing the resolution of /remote/vu/mbox
Mounting remote name spaces through a specific process protocol.
![Page 5: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/5.jpg)
Mounting Alternative• Pioneered by Global Name Service• Add new root and make the existing root nodes the
children of new root• Problem – Existing path names need to be changed• Solution – The root id (from where the resolution
should normally start) is implicitly included in the path
![Page 6: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/6.jpg)
Global Name Service
![Page 7: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/7.jpg)
Name Space Implementation• Naming service – A service that lets users to
add/delete and lookup names• In large distributed systems naming service has to
be distributed• For convenience namespace is partitioned into
logical layers– Global layer – Highest level nodes (root and first level
children)– Administration layer – Directory nodes managed by
single organization (Ex: Departmental nodes in UGA)– Managerial layer – Nodes of local network, shared files,
etc.
![Page 8: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/8.jpg)
Name Space Distribution
An example partitioning of the DNS name space, including Internet-accessible files, into three layers.
![Page 9: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/9.jpg)
Layers and their Characteristics• Global layer
– Stability – Directory tables rarely change– High availability is critical– Permits high levels of caching, throughput is critical
• Administrative Layer– Availability is critical – Permits high levels of caching– Response time should be fast
• Managerial level– Client-side caching is in general less effective– Fast response time is crucial
![Page 10: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/10.jpg)
Comparison of Layers
Item Global Administrational Managerial
Geographical scale of network Worldwide Organization Department
Total number of nodes Few Many Vast numbers
Responsiveness to lookups Seconds Milliseconds Immediate
Update propagation Lazy Immediate Immediate
Number of replicas Many None or few None
Is client-side caching applied? Yes Yes Sometimes
![Page 11: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/11.jpg)
Name Resolution - Implementation• Distribution affects name resolution
implementation• Example: root:<nl, vu, cs, ftp, pub, globe, index.txt>
• Two types – Iterative process and Recursive Process
• Iterative Process– Each node resolves as much as it can and sends result
to client, which contacts the next level of node• Recursive Process
– Nodes do not return intermediate results to client– Contact next level of nodes obtain addresses and send
complete results to the client
![Page 12: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/12.jpg)
Iterative Name Resolution
![Page 13: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/13.jpg)
Recursive Name Resolution (2)
![Page 14: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/14.jpg)
Iterative Vs. Recursive Name Resolutions• Iterative
– Shorter connection durations -> Less load on servers– Caching can be done only at the server -> High
latency• Recursive
– Longer connection duration -> High loads on servers– Permits caching at higher levels of nodes
• High-level nodes can “learn” about lower level nodes • Permits shortcuts
– Cheaper with respect to communication latency
![Page 15: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/15.jpg)
Caching in Recursive Name Resolution
Recursive name resolution of <nl, vu, cs, ftp>. Name servers cache intermediate results for subsequent lookups.
Server for node
Should resolve Looks up Passes to
childReceives
and cachesReturns to requester
cs <ftp> #<ftp> -- -- #<ftp>
vu <cs,ftp> #<cs> <ftp> #<ftp> #<cs>#<cs, ftp>
ni <vu,cs,ftp> #<vu> <cs,ftp> #<cs>#<cs,ftp>
#<vu>#<vu,cs>#<vu,cs,ftp>
root <ni,vu,cs,ftp> #<nl> <vu,cs,ftp> #<vu>#<vu,cs>#<vu,cs,ftp>
#<nl>#<nl,vu>#<nl,vu,cs>#<nl,vu,cs,ftp>
![Page 16: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/16.jpg)
Implementation of Name Resolution (4)
The comparison between recursive and iterative name resolution with respect to communication costs.
![Page 17: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/17.jpg)
The Domain Name Service• Largest distributed naming service• Used for looking up host addresses and mail
servers• Hierarchically organized as a rooted tree
– Labels – 63 Characters; Pathnames – 256 characters– String representation – Listing labels from right to left
separated by dots• Domain – Subtree of nametree
– Domain name – Path to the root of the domain• Contents of node – Resource records
![Page 18: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/18.jpg)
The DNS Name Space
The most important types of resource records forming the contents of nodes in the DNS name space.
Type of record
Associated entity Description
SOA Zone Holds information on the represented zone
A Host Contains an IP address of the host this node represents
MX Domain Refers to a mail server to handle mail addressed to this node
SRV Domain Refers to a server handling a specific service
NS Zone Refers to a name server that implements the represented zone
CNAME Node Symbolic link with the primary name of the represented node
PTR Host Contains the canonical name of a host
HINFO Host Holds information on the host this node represents
TXT Any kind Contains any entity-specific information considered useful
![Page 19: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/19.jpg)
DNS Implementation• DNS namespace is divided into global layer and
administration layer– Managerial layer no part of DNS
• Each zone implemented by a name server– Replicated for availability– Updates happen only at primary name server– Lazy replication – Zone transfer
• Database is made up of collection of files
![Page 20: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/20.jpg)
DNS Implementation - Example
An excerpt from the
DNS database for the zone
cs.vu.nl.
![Page 21: Naming](https://reader035.vdocument.in/reader035/viewer/2022062521/568167df550346895ddd3ecb/html5/thumbnails/21.jpg)
Reference to Subdomains
Part of the description for the vu.nl domain which contains the cs.vu.nl domain.
Name Record type Record value
cs.vu.nl NIS solo.cs.vu.nl
solo.cs.vu.nl A 130.37.21.1