Version 7 (modified by 13 years ago) (diff) | ,
---|
T7) Measurement Information (MI) Service
Lookup Service
1) Goals
A Lookup Service is a type of registry defined in the perfSONAR toolset; the availability of MD at perfSONAR interfaces MC services is registered there, using metadata describing the data and its location.
In addition, a similar Topology Service is used to store the topology of the network being examined.
Together, these services are combined in the Unified Network Information Service (UNIS).
The GEMINI project includes perfSONAR tools, and requires UNIS functions. Some will be provided locally (within the slice), but a global service is required if available MD is to be registered, so that users can find it and get it.
For GENI, the Measurement Information service (MI) will be provided to serve the need for a global UNIS service.
Can the MI service be used for other registry functions?
Can the MI service be used for finding web interfaces, and other types of portals?
Can the MI service be used to provide topology information to assist resource assignment and stitching in GENI?
2) Tasks
The MI service will be built by the GEMINI project using UNIS technology; see the Spiral 4 SOW of the GEMINI project for the detailed steps, which include:
1) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances:
2) Update topology model to Rspec version 3 and AM API (February 2012)
3) Modifications to allow local UNIS to register with global UNIS (March 2012)
4) Initial deployment of persistent GENI Global I&M Registry (GGR) service, based on UNIS. (May 2012)
5) Complete noSQL (MongoDB) backend (September 2012)
6) Unify Perl and Python implementations (September 2012)
Define, prototype, demonstrate and operate a MI service, starting in May, 2012.
Support use in GENI by many tools, including GEMINI and GIMI I&M tools
Define operations plan for MI service.
3) Team
? (GEMINI)
Giridhar Manepalli (CNRI)
Harry Mussman (GPO)
4) Meetings
(organized calls or meetings before GEC13?)
Review conclusions in pre-meeting at GEC13
Review with working team at GEC13
5) Open Issues
6) Definition of MI Service
a) Global UNIS b) Can be loaded from Local UNIS in slice
c) Can map MDOD into metadata that is registered
d) Can the MI service be used for other registry functions? e) Can the MI service be used for finding web interfaces, and other types of portals? f) Can the MI service be used to provide topology information to assist resource assignment and stitching in GENI?