Changes between Version 1 and Version 2 of InstMeasTopic_4.7LookupService

Timestamp:

02/16/12 13:37:44 (13 years ago)

Author:

hmussman@bbn.com

Comment:

--

InstMeasTopic_4.7LookupService

@@ -1 @@
-== 4.7)  Lookup Service ==
+== 4.7)  Measurement Information Service ==
 Lookup Service  [[BR]]
 
@@ -6 +6 @@
 == 1)  Goals ==
 
- Assume that Lookup Service will be implemented by GEMINI project using UNIS service.  [[BR]]
+ 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.
 
- The Lookup Service will 
+ 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.  [[BR]]
+
+ 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 ==
 
- For a detailed list, see the Spiral 4 SOW of the GEMINI project; these include:  [[BR]]
-c)      Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances:
-1.      Update topology model to Rspec version 3 and AM API (February 2012)
+ 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:  [[BR]]
+
+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)
 2.      Modifications to allow local UNIS to register with global UNIS (March 2012)
 3.      Initial deployment of persistent GENI Global I&M Registry (GGR) service, based on UNIS. (May 2012)
@@ -20 +33 @@
 5.      Unify Perl and Python implementations (September 2012)
 
- Define, prototype, demonstrate and operate a GENI Lookup service, starting at GEC12. [[BR]]
+ Define, prototype, demonstrate and operate a MI service, starting at GEC12. [[BR]]
 
  Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
 
- Define operations plan for Lookup Service.  [[BR]]
+ Define operations plan for MI service.  [[BR]]
 
 
@@ -47 +60 @@
 
 
-== 6)  Definition of Lookup Service ==
+== 6)  Definition of MI Service ==
 
- a)  Global Lookup Service, as defined by perfSONAR  [[BR]]
- b)  Also global Topology Service?
- c)  Follow UNIS design?  
- d)  Include Global UNIS, loaded from Local UNIS in slice? [[BR]]
- e)  Map MDOD into metadata that is registered  [[BR]]
- f)  Can Lookup Service be used for finding web interfaces, and other types of portals?  [[BR]]
+ a)  Global UNIS
+ b)  Can be loaded from Local UNIS in slice [[BR]]
+ c)  Can map MDOD into metadata that is registered  [[BR]]
+ 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?  
 
+