# Presentation: 210388

## DOE 2000 Architecture

**Information and Computing Sciences Division**

**DOE 2000 Architecture**

- Ernest Orlando Lawrence Berkeley National Laboratory

- 		        Deb Agarwal
- (Presenting material from some of the DOE 2000
- projects at LBNL, ANL, PNNL, and SNL.)

## DOE2000 - Architecture Components

**Collaboration management**
**coordination of collaboratory environment**
**Quality of Service**
**priority network bandwidth when needed**
**Security**
**integrated login**
**authentication using public key**
**Collaboratory interoperability framework**
**common communication**
**directory services**
**access to unicast and multicast messaging**

## Collaboratory Architecture

**Collaboratory Architecture**

**Collaboratory Interoperability Framework**
**Security Infrastructure**
**Network Quality of Service**

**Instrument**
**Control**

**Experiment**
**Notebook**

**Collaboration**
**Management**

**Telepresence**

**Analysis**

**Visualization**

**Database**

**Distributed**
**File System**

**Floor Control**

**Unifying User Interface**

## CIF - Collaboratory Interoperability Framework

**Joint project involving four laboratories**
**LBNL participants - Peter Schabert, Nitya Narasimhan, Karlo Berket, and Deb Agarwal**
**ANL participants - Ian Foster and Steve Tueke**
**PNNL participants - Jim Myers**
**SNL participants - Bruce Mah**
**More information available at**
**http://www.mcs.anl.gov/cif **

## Collaboratory Interoperability Framework

**Common communication API for unicast and multicast communication**
**Reliable multicast communication**
**CORBA evaluation and integration with the API**
**Directory services**

## CIF - Motivation

**People building essential components of the collaboratory are not computer scientists or are not expert in building communication protocols**
**Programming interfaces for the communication protocols are not consistent**
**Need access to multicast capabilities Reliable multicast is needed but not readily available in an easy to use form**
**Integration with the CORBA environment**
**Collaboratory tools need to be interoperable to allow provision of a plug-and-play environment**
**Need to be able to locate other collaboratory resources**

## Communication Protocols

**Unicast**
**unreliable unordered (UDP)**
**reliable source ordered (TCP)**
**Multicast**
**Unreliable unordered (IP Multicast, RTP)**
**Unreliable source ordered (filtered IP Multicast)**
**Reliable source ordered (XTP)**
**Reliable totally ordered delivery (Totem, InterGroup)**

## Communication API Design criteria

**Simple to use programming interface**
**Consistent interface across all protocols**
**Default settings for a connection type will normally suit the user’s needs **
**Message oriented (not streams)**
**Consistent exception and event handling**
**Integrated security**
**Integrated flow control mechanisms**

## Communication API

**Function calls**
**open_connection( destination, port, timeout)**
**send_msg( buffer )**
**receive_msg()**
**close_connection()**
**Connection setup parameters set prior to connection initiation **
**flow control**
**packetization**
**security**

## CIF - Consistent Information Provided

**Standard header provides information including**
**sender id**
**timestamp of message**
**Appropriate membership information provided for all protocols**
**Well defined exceptions thrown by API routines**
**All protocols use message-based communication**

## Reliable Multicast

**There are several protocols and  significant research into reliable multicast protocols**
**Variety of levels of reliability and ordering**
**CIF will provide**
**reliable source ordered message delivery**
**reliable ordered delivery for process groups**
**total order across an arbitrary set of connections possible in the future**

## CIF - Directory Service

**Provide a means of locating resources in the collaboratory environment**
**Nexus/Globus Metacomputing Directory Service**
**based on the LDAP API and data representation**
**efficient implementation of servers**
**uniform interface to diverse resources**
**security architecture integrated to provide access control**

## CIF - CORBA Integration

**Define the API as a new CORBA service so that it can be used from any CORBA implementation**
**Provide an efficient message oriented communication capability**
**Allow access to collaboratory components that do not run a CORBA ORB**
**Not intended as a replacement for the event service**

## CIF - Implementation

**Definition of the common API**
**Circulation of API definition to DOE 2000 pilots for feedback**
**Development of reliable multicast protocols**
**Implementations of the API**
**Nexus implementation**
**Java implementation **
**C++ implementation ????**
**CORBA implementation**
**Directory service**

## CIF - Milestones

**Generic API definition**
**Directory service definition of collaboratory components and implementation**
**Implementation of API integrating Nexus, XTP, and Totem**
**CORBA service implementation**
**Determination and development of scalable reliable ordered delivery protocols**

## Quality of Service

**Van Jacobson of LBNL**
**For more information contact Van Jacobson**

## QOS Design Criteria

**Scalable to a large network**
**Requests for small amounts of priority traffic incur minimal overhead**
**Minimal state for priority connections needs to be kept at routers**
**Negotiations for pre-allocated chunks of priority bandwidth require the agreement of only two parties**
**Limited number of bits available to represent priority in the message**

## QOS - Design

**Each site pre-negotiates a chunk of bandwidth to use for small quantities of priority traffic**
**Each site runs a bandwidth broker which then allocates the priority bandwidth**
**small requests are given immediate access to the pre-negotiated chunk**
**large requests require an end-to-end bandwidth allocation (these could be pre-negotiated also)**
**The leaf router is contacted by the bandwidth broker and assigned responsibility for setting the priority bit in the traffic**

## QOS - Design (continued)

**Routers use priority queueing and forward packets based on whether the priority bit is set**
**Routers can be configured to enforce additional constraints as needed regarding priority traffic**

- ESNet

- Host

## QOS - Testbed implementation

**LBNL <--> ANL implementation**
**SuperComputing ‘97 demonstration**
**Components critical to success**
**bandwidth broker implementation**
**local router priority setting capability**
**priority queueing enabled in ESNet routers**

## Collaboration Management

**Involves personnel from 2 national laboratories**
**PNNL participants - Debbie Payne**
**ANL participants - Bob Olson**
**For more information see**
**  ****http://www.emsl.pnl.gof:2080/docs/collab/CollabHome.html**

## Collaboration Management

**Develop a real-time collaboration framework to integrate existing, collaboration tools:**
**provide a real-time collaboration engine that handles membership, authentication, event distribution and invocation**
**provide a real-time collaboration interface specification, including APIs and components for tool integration**
**provide a space-based collaboration manager, based on a spatial metaphor such as LabSpace**
**provide a session-based collaboration manager, based on a conference metaphor**

## Collaboration Management - Progress

**Adaptation of the cross platform, Java based, Habanero architecture from NCSA as a baseline.**
**Integration of the Televiewer tool and video conferencing tools into Habanero framework.**
**Creation of a multi-platform white board tool.**
**ANL and PNNL have both signed development licenses with NCSA for Habanero.  PNNL has signed a further agreement to allow redistribution of a DOE 2000 version of Habanero with modification, additions, etc. **
**Development of some help documentation and a WWW Help Desk form that sends information to a monitored queue**

## Security Architecture

**LBNL participants - Bill Johnston, Case Larsen, and Srilekha Mudumbai**
**For more information see**
**   ****http://www-itg.lbl.gov/SecurityArch**

## Security Architecture

**Public key**
**Policy-based resource access**
**Easy to use **
**Access administered by stakeholders**
**Mechanisms for distributing and verifying digitally signed documents**
**Distributed management of access control**
**Role-based authentication**

## How This All Fits Together

**How This All Fits Together**

**QOS implementation provides basic services accessible through CIF communication API**
**Security architecture provides authentication capabilities to the CIF directory service, CIF communication API, Collaboration management, and QOS**
**CIF architecture provides the communication, membership and directory service infrastructure needed by the collaboration management**
**All components provide basic services needed by the collaboratory application**
**By working together we can provide a unified application view of the DOE 2000 architecture**

## Some Bumps on the Road of Progress

**Integration of architecture components into pre-existing tools**
**May need an upgrade of some ESNet CISCO routers to allow QOS test**
**Mbone routing is still not “stable”**
**Current reliable ordered multicast is not scalable to Internet size collaborations**
**Videoconferencing over the Mbone still isn’t easy**
**Tool development is concurrent with pilot development**
**Determination of application needs**

## Links to information

**DOE 2000 - http://www.mcs.anl.gov/DOE2000**
**CIF Project - http://www.mcs.anl.gov/cif**
**Collaboration Management Project - http://www.emsl.pnl.gov:2080/docs/collab/CollabHome.html**
**Security Project -**
**     ****http://www-itg.lbl.gov/SecurityArch**
**This talk**
**    ****http://www-itg.lbl.gov/~deba/doe2000/ESSC9-11-97/index.htm**