Naming CSCI 6900/4900. Names & Naming System Names have unique importance –Resource sharing –Identifying entities –Location reference Name can be resolved.

Slides:



Advertisements
Similar presentations
EECS122 - UCB 1 CS 194: Distributed Systems: Naming Computer Science Division Department of Electrical Engineering and Computer Sciences University of.
Advertisements

Chapter 4 : File Systems What is a file system?
File System Interface CSCI 444/544 Operating Systems Fall 2008.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Naming (2) DISTRIBUTED.
Naming Computer Engineering Department Distributed Systems Course Asst. Prof. Dr. Ahmet Sayar Kocaeli University - Fall 2014.
Distributed Systems Principles and Paradigms Chapter 04 Naming.
1 Networking through Linux Partha Sarathi Dasgupta MIS Group Indian Institute of Management Calcutta.
Naming in Distributed System Presented by Faraz Rasheed & Uzair Ahmed RealTime & Multimedia Lab Kyung Hee University, Korea.
The implementation of a name space
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
CS 582 / CMPE 481 Distributed Systems Naming Class Overview Why naming? Terminology Naming Fundamentals Name Services Case Studies –DNS –GNS.
File System Implementation: beyond the user’s view A possible file system layout on a disk.
Silberschatz, Galvin and Gagne ©2009 Operating System Concepts – 8 th Edition File-System Interface.
Computer Science Lecture 9, page 1 CS677: Distributed OS Today: Naming Names are used to share resources, uniquely identify entities and refer to locations.
Naming Names in computer systems are used to share resources, to uniquely identify entities, to refer to locations and so on. An important issue with naming.
NamingCS-4513, D-Term Naming CS-4513 Distributed Computing Systems (Slides include materials from Operating System Concepts, 7 th ed., by Silbershatz,
Processes After today’s lecture, you are asked to know
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
NamingCS-4513, D-Term Naming CS-4513 Distributed Computing Systems (Slides include materials from Operating System Concepts, 7 th ed., by Silbershatz,
Naming Names in computer systems are used to share resources, to uniquely identify entities, to refer to locations and so on. An important issue with naming.
NFS. The Sun Network File System (NFS) An implementation and a specification of a software system for accessing remote files across LANs. The implementation.
Rensselaer Polytechnic Institute CSCI-4210 – Operating Systems David Goldschmidt, Ph.D.
ICS362 Distributed Systems Dr Ken Cosh Week 5. Review Communication – Fundamentals – Remote Procedure Calls (RPC) – Message Oriented Communication – Stream.
Computer Science Lecture 9, page 1 CS677: Distributed OS Today: Naming Names are used to share resources, uniquely identify entities and refer to locations.
Lesson 7-Creating and Changing Directories. Overview Using directories to create order. Managing files in directories. Using pathnames to manage files.
Network Layer (3). Node lookup in p2p networks Section in the textbook. In a p2p network, each node may provide some kind of service for other.
CSC 322 Operating Systems Concepts Lecture - 4: by Ahmed Mumtaz Mustehsan Special Thanks To: Tanenbaum, Modern Operating Systems 3 e, (c) 2008 Prentice-Hall,
5.1 Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED.
Naming Chapter 4.
Naming CSCI 4780/6780.
COMP 655: Distributed/Operating Systems Summer 2011 Dr. Chunbo Chu Week 5: Naming 10/12/20151Distributed Systems - COMP 655.
Naming CSCI 4780/6780. Names & Naming System Names have unique importance –Resource sharing –Identifying entities –Location reference Name can be resolved.
Introduction to DFS. Distributed File Systems A file system whose clients, servers and storage devices are dispersed among the machines of a distributed.
Chapter 16 - File Systems –Persistent storage: storage that will continue to exist after a program that uses or creates it completes. –Sometimes called.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Some basic concepts and information on file systems Portions taken and modified from books by ANDREW S. TANENBAUM.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Computer Science Lecture 19, page 1 CS677: Distributed OS Last Class: Fault tolerance Reliable communication –One-one communication –One-many communication.
CS 346 – Chapter 11 File system –Files –Access –Directories –Mounting –Sharing –Protection.
Why Do We Need Files? Must store large amounts of data. Information stored must survive the termination of the process using it - that is, be persistent.
ADVANCED OPERATING SYSTEMS STRUCTURED NAMING BY KANNA KARRI.
THE FILE SYSTEM Files long-term storage RAM short-term storage Programs, data, and text are all stored in files, which is stored on.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Lecture Topics: 11/29 File System Interface –Files and Directories –Access Methods –Protection –Consistency.
Naming CSCI 6900/4900. Mounting Mounting – Merging different namespaces transparently File system example –Directory node of one namespace stores identifier.
Lecture 14 Page 1 CS 111 Online File Systems: Naming, Reliability, and Advanced Issues CS 111 On-Line MS Program Operating Systems Peter Reiher.
Naming CSCI 4780/6780. Name Space Implementation Naming service – A service that lets users to add/delete and lookup names In large distributed systems.
W4118 Operating Systems Instructor: Junfeng Yang.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Computer Science Lecture 19, page 1 CS677: Distributed OS Last Class: Fault tolerance Reliable communication –One-one communication –One-many communication.
Slide 1 Structured Naming. Slide 2 Given Credit Where It Is Due The following slides are borrowed from Dr. Katerina Goseva-Popstojanova at West Virginia.
Operating Systems Chapter 5 – File Systems
File System Implementation
Naming Chapter 4.
Naming A name in a distributed system is a string of bits or characters used to refer to an entity. To resolve name a naming system is needed.
5.3. Structured Naming Advanced Operating Systems Fall 2017
File Systems Kanwar Gill July 7, 2015.
File Structure 2018, Spring Pusan National University Joon-Seok Kim
File System B. Ramamurthy B.Ramamurthy 11/27/2018.
Naming Chapter - 5 Presenter: Venkatesh Javvaji
Directory Structure A collection of nodes containing information about all files Directory Files F 1 F 2 F 3 F 4 F n Both the directory structure and the.
Names, Identifiers and Addresses
Distributed Systems CS
Distributed Systems CS
Distributed Systems CS
Distributed Systems CS
Distributed Systems CS
Outline Review of Quiz #1 Distributed File Systems 4/20/2019 COP5611.
CORBA Programming B.Ramamurthy Chapter 3 5/2/2019.
Presentation transcript:

Naming CSCI 6900/4900

Names & Naming System Names have unique importance –Resource sharing –Identifying entities –Location reference Name can be resolved to the entity it refers to Naming system resolves names Naming system in distributed systems can itself be distributed

Names, Entities & Addresses Name is a string of bits/characters used to refer to an entity Entity can resources/users/data/processes –Web pages, files, hosts, printers, network connections –Entities permit certain operations (reading/writing files) To operate we need to access the entity Access Point – A special kind of entity –Host of a server Name of access point is called its Address –Hosts IP address and port Address of access point is the address of the entity at that access point

More on Entities and Addresses Entities can have multiple access points –Multiple telephone numbers/ addresses –Replicated services Entities might change access points –Laptops get different IP addresses based on their location –New phone number/ when switching jobs Can we use the address as the name of an entity? –Difficulties in relocation/replication transparency Name that is independent of address – Location Independent Names

Identifiers An name with following properties –Identifier refers to at most one entity –Entity is referred to by at most one identifier –Identifier always refers to same entity (persistence) Facilitates unambiguous reference –Testing equality of identifiers suffices if entities being referred to are the same Addresses cannot be identifiers if they can be re- assigned –Example: Telephone numbers

Name Spaces Names are organized into name spaces Name space is represented as a directed graph with two types of nodes Leaf Node – Represents named entity –No outgoing edges –Stores information on the entity it is referring (address or state of the entity) Directory node – Can have multiple outgoing edges each with a name –Directory table – Contains for each outgoing edge

Name Spaces - Example A general naming graph with a single root node.

More on Name Spaces Path name: Sequence of edge labels leading from one node to another –N: Absolute path name –First node is the root Relative path name –First node can be arbitrary node Global name –Denotes same entity where ever it is used Local name –Interpretation is dependent upon where it is used

Organizing Name Spaces Tree-based approach –Strict hierarchical approach Directed acyclic graph –Most commonly used General graphs –Rarely used Single root Multiple root

Name Spaces in Unix File System The general organization of the UNIX file system implementation on a logical disk of contiguous disk blocks.

Name Resolution Process of looking-up an entity given its path name –Find the corresponding node Example: N: –Start at N –Proceed along the edges A crucial question: Where should the resolution begin? –Which node represents the root? –Unix example: Which i-node corresponds to the root?

Closure Mechanism Knowing how and where to start resolution mechanism – Closure Have a universally agreed upon root In Unix root directory is the first i-node –Actual byte offset is calculated by other values in superblock HOME variable is Unix – always refers to the user’s home directory

Linking and Mounting Aliases – Another name for same entity Two approaches –Multiple absolute path names Hard links in Unix –Represent entity by a leaf node, but the leaf node stores absolute path name Return the absolute path name instead of address Symbolic links in Unix