perfsonar-dev - nmwg: r327 - trunk/nmwg/doc/dLS

Subject: perfsonar development work

List archive

nmwg: r327 - trunk/nmwg/doc/dLS

From:
To: ,
Subject: nmwg: r327 - trunk/nmwg/doc/dLS
Date: Mon, 7 Jan 2008 12:30:29 -0500

Author: boote
Date: 2008-01-07 12:30:29 -0500 (Mon, 07 Jan 2008)
New Revision: 327

Modified:
trunk/nmwg/doc/dLS/dLS_spec.html
trunk/nmwg/doc/dLS/dLS_spec.xml
trunk/nmwg/doc/dLS/dLS_spec_1.html
Log:
Adding one more example into the scope description. Since this one
coincides with the 'default' scope selection later specified, it seemed
like a good idea.

Modified: trunk/nmwg/doc/dLS/dLS_spec.html
===================================================================
--- trunk/nmwg/doc/dLS/dLS_spec.html 2008-01-07 14:42:54 UTC (rev 326)
+++ trunk/nmwg/doc/dLS/dLS_spec.html 2008-01-07 17:30:29 UTC (rev 327)
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Distributed Lookup Service (dLS) in the perfSONAR
Framework</title><meta name="generator" content="DocBook XSL Stylesheets
V1.71.0" /></head><body><div class="article" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h1 class="title"><a
id="id2478927"></a>Distributed Lookup Service (dLS) in the perfSONAR
Framework</h1></div><div><div class="authorgroup"><div class="author"><h3
class="author">J. Boote</h3></div><div class="author"><h3
class="author">M. Glowiak</h3></div><div class="author"><h3
class="author">M. Swany</h3></div><div class="author"><h3
class="author">J. Zurawski</h3></div></div></div><div>Copyright © 2006, 2007, 2008 Internet2, Poznan
Supercomputing and Networking Center, University of
Delaware</div></div><hr /></div><div class="toc">Table of
Contents<dl><dt><a href="#changes">1. Document
Changes</a></dt><dt><a href="#introduction">2.
Introduction</a></dt><dt><a
href="#system_specific_operation">3. System Specific
Operation</a></dt><dd><dl><dt><a
href="#system_overview">3.1. Overview</a></dt><dt><a href="#system_scope">3.2. Scope
Formation</a></dt><dd><dl><dt><a
href="#scope_specification">3.2.1. Scope
Specification</a></dt><dt><a
href="#scope_hierarchy">3.2.2. Scope Hierarchy</a></dt><dt><a href="#scope_defaults">3.2.3. Scope
Defaults</a></dt><dt><a href="#scope_algorithms">
3.2.4. Scope Algorithms</a></dt><dd><dl><dt><a href="#join_procedure">3.2.4.1. Join
Procedure</a></dt><dd><dl><dt><a
href="#join_alg">3.2.4.1.1.
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#token_messages">3.2.5. Token Messages for Control and
Election</a></dt><dd><dl><dt><a
href="#leader_election">3.2.5.1. Leader Election</a></dt><dt><a href="#registration_control">3.2.5.2. Registration
Control</a></dt><dd><dl><dt><a
href="#passing_algorithm">3.2.5.2.1. Passing
Algorithm</a></dt><dt><a
href="#rotation_time_computation">3.2.5.2.2. Rotation Time
Computation</a></dt></dl></dd></dl></dd><dt><a
href="#summarization_messages">3.2.6. Summarization
Messages</a></dt></dl></dd><dt><a
href="#bootstrapping">3.3. Bootstrapping</a></dt><dt><a href="#system_summari
zation">3.4. Summarization</a></dt><dd><dl><dt><a href="#system_summarization_lower">3.4.1. Lower
Scope</a></dt><dt><a
href="#system_summarization_upper">3.4.2. Upper
Scope</a></dt><dd><dl><dt><a
href="#system_summarization_upper_alg">3.4.2.1. IP Address
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#system_search">3.5. Search</a></dt><dd><dl><dt><a href="#system_search_discovery_phase">3.5.1. Discovery
Phase</a></dt><dd><dl><dt><a
href="#system_search_discovery_algorithm">3.5.1.1.
Algorithm</a></dt></dl></dd><dt><a
href="#system_search_metadata_query_phase">3.5.2. Metadata Query
Phase</a></dt></dl></dd></dl></dd><dt><a
href="#structures_and_messages">4. Structures and
Messages</a></dt><dd><dl><dt><a href="#servic
e_metadata">4.1. Service Metadata Example</a></dt><dt!
><a href="#lookup_info">4.2. Lookup
Information</a></dt><dt><a href="#ls_ring">4.3.
LS Ring File Structure</a></dt><dd><dl><dt><a
href="#ls_ring_lower">4.3.1. Lower Level</a></dt><dt><a href="#ls_ring_upper">4.3.2. Upper
Level</a></dt></dl></dd><dt><a
href="#ls_join">4.4. LS Join</a></dt><dd><dl><dt><a href="#ls_join_request">4.4.1.
Request</a></dt><dt><a
href="#ls_join_response">4.4.2. Response</a></dt></dl></dd><dt><a href="#ls_token_message">4.5. LS Token
Message</a></dt><dd><dl><dt><a
href="#ls_token_message_request">4.5.1. Request</a></dt><dt><a href="#ls_token_message_response">4.5.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message">4.6. LS Summary Message</a>
</dt><dd><dl><dt><a
href="#ls_summary_message_upper">4.6.1.
Upper</a></dt><dd><dl><dt><a
href="#ls_summary_message_upper_request">4.6.1.1.
Request</a></dt><dt><a
href="#ls_summary_message_upper_response">4.6.1.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message_lower">4.6.2.
Lower</a></dt><dd><dl><dt><a
href="#ls_summary_message_lower_request">4.6.2.1.
Request</a></dt><dt><a
href="#ls_summary_message_lower_response">4.6.2.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#ls_leader_message">4.7. LS Leader
Message</a></dt><dd><dl><dt><a
href="#ls_leader_message_request">4.7.1. Request</a></dt><dt><a href="#ls_leader_message_response">4.7.2.
Response</a></dt></dl></dd><dt><a hre
f="#ls_discovery_message">4.8. LS Discovery Message</a></spa!
n></dt><
dd><dl><dt><a
href="#ls_discovery_message_request">4.8.1. Request</a></dt><dt><a href="#ls_discovery_message_response">4.8.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#glossary">Terms</a></dt><dt><a
href="#bibliography">References</a></dt></dl></div><div
class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a id="changes"></a>1. Document
Changes</h2></div></div></div><div class="table"><a id="table.1"></a>Table 1. Change Log<div
class="table-contents"><table summary="Change Log" border="1"><colgroup><col
align="left" /></colgroup><thead><tr><th align="left">Version</th><th
align="left">Date</th><th align="left">Description</th><th
align="left">Author(s)</th></tr></thead><tbody><tr><td
align="left">1.0</td><td align="left">12/17/2007</td><td align="left">Initia
l Preparation</td><td align="left">J. Zurawski</td></tr><tr><td
align="left">1.1</td><td align="left">1/1/2008</td><td align="left">Update of
Scope Formation and boot-strapping</td><td align="left">J.
Boote</td></tr><tr><td align="left">1.0</td><td align="left">1/7/2008</td><td
align="left">Addition/Correction of scope diagrams</td><td align="left">J.
Zurawski</td></tr></tbody></table></div></div> </div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
id="introduction"></a>2. Introduction</h2></div></div></div>
+<html xmlns="http://www.w3.org/1999/xhtml";><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Distributed Lookup Service (dLS) in the perfSONAR
Framework</title><meta name="generator" content="DocBook XSL Stylesheets
V1.71.1" /></head><body><div class="article" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h1 class="title"><a
id="id824766"></a>Distributed Lookup Service (dLS) in the perfSONAR
Framework</h1></div><div><div class="authorgroup"><div class="author"><h3
class="author">J. Boote</h3></div><div class="author"><h3
class="author">M. Glowiak</h3></div><div class="author"><h3
class="author">M. Swany</h3></div><div class="author"><h3
class="author">J. Zurawski</h3></div></div></div><div>Copyright © 2006, 2007, 2008 Internet2, Poznan Supercomputing
and Networking Center, University of Delaware</div></div><hr /></div><div
class="toc">Table of Contents<dl><dt><a
href="#changes">1. Document Changes</a></dt><dt><a href="#introduction">2.
Introduction</a></dt><dt><a
href="#system_specific_operation">3. System Specific
Operation</a></dt><dd><dl><dt><a
href="#system_overview">3.1. Overview</a></dt><dt><a href="#system_scope">3.2. Scope
Formation</a></dt><dd><dl><dt><a
href="#scope_specification">3.2.1. Scope
Specification</a></dt><dt><a
href="#scope_hierarchy">3.2.2. Scope Hierarchy</a></dt><dt><a href="#scope_defaults">3.2.3. Scope
Defaults</a></dt><dt><a
href="#scope_algorithms">3
.2.4. Scope Algorithms</a></dt><dd><dl><dt><a href="#join_procedure">3.2.4.1. Join
Procedure</a></dt><dd><dl><dt><a
href="#join_alg">3.2.4.1.1.
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#token_messages">3.2.5. Token Messages for Control and
Election</a></dt><dd><dl><dt><a
href="#leader_election">3.2.5.1. Leader Election</a></dt><dt><a href="#registration_control">3.2.5.2. Registration
Control</a></dt><dd><dl><dt><a
href="#passing_algorithm">3.2.5.2.1. Passing
Algorithm</a></dt><dt><a
href="#rotation_time_computation">3.2.5.2.2. Rotation Time
Computation</a></dt></dl></dd></dl></dd><dt><a
href="#summarization_messages">3.2.6. Summarization
Messages</a></dt></dl></dd><dt><a
href="#bootstrapping">3.3. Bootstrapping</a></dt><dt><a href="#system_summariz
ation">3.4. Summarization</a></dt><dd><dl><dt><a href="#system_summarization_lower">3.4.1. Lower
Scope</a></dt><dt><a
href="#system_summarization_upper">3.4.2. Upper
Scope</a></dt><dd><dl><dt><a
href="#system_summarization_upper_alg">3.4.2.1. IP Address
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#system_search">3.5. Search</a></dt><dd><dl><dt><a href="#system_search_discovery_phase">3.5.1. Discovery
Phase</a></dt><dd><dl><dt><a
href="#system_search_discovery_algorithm">3.5.1.1.
Algorithm</a></dt></dl></dd><dt><a
href="#system_search_metadata_query_phase">3.5.2. Metadata Query
Phase</a></dt></dl></dd></dl></dd><dt><a
href="#structures_and_messages">4. Structures and
Messages</a></dt><dd><dl><dt><a href="#service
_metadata">4.1. Service Metadata Example</a></dt><dt>!
<a href="#lookup_info">4.2. Lookup
Information</a></dt><dt><a href="#ls_ring">4.3.
LS Ring File Structure</a></dt><dd><dl><dt><a
href="#ls_ring_lower">4.3.1. Lower Level</a></dt><dt><a href="#ls_ring_upper">4.3.2. Upper
Level</a></dt></dl></dd><dt><a
href="#ls_join">4.4. LS Join</a></dt><dd><dl><dt><a href="#ls_join_request">4.4.1.
Request</a></dt><dt><a
href="#ls_join_response">4.4.2. Response</a></dt></dl></dd><dt><a href="#ls_token_message">4.5. LS Token
Message</a></dt><dd><dl><dt><a
href="#ls_token_message_request">4.5.1. Request</a></dt><dt><a href="#ls_token_message_response">4.5.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message">4.6. LS Summary Message</a></dt><dd><dl><dt><a
href="#ls_summary_message_upper">4.6.1.
Upper</a></dt><dd><dl><dt><a
href="#ls_summary_message_upper_request">4.6.1.1.
Request</a></dt><dt><a
href="#ls_summary_message_upper_response">4.6.1.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message_lower">4.6.2.
Lower</a></dt><dd><dl><dt><a
href="#ls_summary_message_lower_request">4.6.2.1.
Request</a></dt><dt><a
href="#ls_summary_message_lower_response">4.6.2.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#ls_leader_message">4.7. LS Leader
Message</a></dt><dd><dl><dt><a
href="#ls_leader_message_request">4.7.1. Request</a></dt><dt><a href="#ls_leader_message_response">4.7.2.
Response</a></dt></dl></dd><dt><a href
="#ls_discovery_message">4.8. LS Discovery Message</a></span!
></dt><d
d><dl><dt><a
href="#ls_discovery_message_request">4.8.1. Request</a></dt><dt><a href="#ls_discovery_message_response">4.8.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#glossary">Terms</a></dt><dt><a
href="#bibliography">References</a></dt></dl></div><div
class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a id="changes"></a>1. Document
Changes</h2></div></div></div><div class="table"><a id="table.1"></a>Table 1. Change Log<div
class="table-contents"><table summary="Change Log" border="1"><colgroup><col
align="left" /></colgroup><thead><tr><th align="left">Version</th><th
align="left">Date</th><th align="left">Description</th><th
align="left">Author(s)</th></tr></thead><tbody><tr><td
align="left">1.0</td><td align="left">12/17/2007</td><td align="left">Initial
Preparation</td><td align="left">J. Zurawski</td></tr><tr><td
align="left">1.1</td><td align="left">1/1/2008</td><td align="left">Update of
Scope Formation and boot-strapping</td><td align="left">J.
Boote</td></tr><tr><td align="left">1.0</td><td align="left">1/7/2008</td><td
align="left">Addition/Correction of scope diagrams</td><td align="left">J.
Zurawski</td></tr></tbody></table></div></div> </div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
id="introduction"></a>2. Introduction</h2></div></div></div>
This document describes the
Distributed Lookup Service
(dLS)
- in the <a href="#id2532917">perfSONAR</a> system. This modification
extends
+ in the <a href="#id905683">perfSONAR</a> system. This modification
extends
the basic Lookup Service
(LS)
functionality that has been present in the system for some time. The
basic LS supports the storage and querying of
@@ -66,7 +66,7 @@
<a href="#lookup_info">Lookup Information</a>).

The idea is to move the metadata from a service-local
- <a href="#id2532935">XML</a> data store to a specialized
+ <a href="#id905701">XML</a> data store to a specialized
LS with additional
searching capabilities. The
LS consists of an
XML database, (i.e.
<a href="#Berkeley DB XML">Berkeley DB XML</a> or <a
href="#eXist XML DB">eXist XML DB</a>)
@@ -219,8 +219,7 @@
example of this would be
psls://perfsonar.net/!psls://internet2.edu.
The next level up from this would be
- psls://perfsonar.net, where this
- LS
would be a member.
+ psls://perfsonar.net.
</li></ol></div>

When configuring a new LS instance the
@@ -290,7 +289,7 @@
</li><li>
C and D have a similar arrangement as A and B
above, but are part of a sub-domain (the
- ls.
subclass of
+ ls.
subscope of
geant.net). This sub-domain
will be summarized and one of (C or D) will
represent the sub-domain information in the
@@ -325,8 +324,22 @@
G and H will elect a leader of the domain
level scope and summarize the domain for
participation in the global ring.
+ </li><li>
+ I is specified similar to H above for
+ the ls.
subdomain
+ of rnp.br, but there
+ are no current instances defined at the
+ domain level.
+ 
+ This is a perfectly valid configuration, and
+ useful if a domain is planning for future
+ extensibility. The I instance will end up
+ initially being the leader of both the
+ ls.rnp.br
subdomain and the
+ rnp.br
domain as the
+ defacto winner of both leader elections.
</li><li>
- Finally, in this example there would be three
+ Finally, in this example there would be four
LS
instances participating
in the global ring representing the registed
content of all eight LS
@@ -1773,8 +1786,8 @@
A query language (with some programming language
features) that is designed to query collections of XML data. It
is semantically similar to SQL.
- </dd></dl></div><div class="glossdiv"><dl></dl></div><div
class="glossdiv"><dl></dl></div></div><div class="bibliography"><div
class="titlepage"><div><div><h2 class="title"><a
id="bibliography"></a>References</h2></div></div></div><div
class="biblioentry"><a id="id2532917"></a>[<abbr
class="abbrev">perfSONAR</abbr>] 
+ </dd></dl></div><div class="glossdiv"><dl></dl></div><div
class="glossdiv"><dl></dl></div></div><div class="bibliography"><div
class="titlepage"><div><div><h2 class="title"><a
id="bibliography"></a>References</h2></div></div></div><div
class="biblioentry"><a id="id905683"></a>[<abbr
class="abbrev">perfSONAR</abbr>] 
<a href="http://www.perfsonar.net"; target="_top">perfSONAR</a>
- . </div><div class="biblioentry"><a
id="id2532935"></a>[<abbr class="abbrev">XML</abbr>] 
+ . </div><div class="biblioentry"><a
id="id905701"></a>[<abbr class="abbrev">XML</abbr>] 
<a href="http://www.w3.org/XML"; target="_top">Extensible Markup
Language (XML)</a>
. </div></div></div></body></html>

Modified: trunk/nmwg/doc/dLS/dLS_spec.xml
===================================================================
--- trunk/nmwg/doc/dLS/dLS_spec.xml 2008-01-07 14:42:54 UTC (rev 326)
+++ trunk/nmwg/doc/dLS/dLS_spec.xml 2008-01-07 17:30:29 UTC (rev 327)
@@ -367,8 +367,7 @@
example of this would be

<emphasis>psls://perfsonar.net/!psls://internet2.edu</emphasis>.
The next level up from this would be
- <emphasis>psls://perfsonar.net</emphasis>, where
this
- <command>LS</command> would be a member.
+ <emphasis>psls://perfsonar.net</emphasis>.
</listitem>
</orderedlist>
</para>
@@ -465,7 +464,7 @@
<para>
C and D have a similar arrangement as A and B
above, but are part of a sub-domain (the
- <emphasis>ls.</emphasis> subclass of
+ <emphasis>ls.</emphasis> subscope of
<emphasis>geant.net</emphasis>). This sub-domain
will be summarized and one of (C or D) will
represent the sub-domain information in the
@@ -509,7 +508,25 @@
</para>
</listitem>
<listitem>
- Finally, in this example there would be three
+ <para>
+ I is specified similar to H above for
+ the <emphasis>ls.</emphasis> subdomain
+ of <emphasis>rnp.br</emphasis>, but there
+ are no current instances defined at the
+ domain level.
+ </para>
+ <para>
+ This is a perfectly valid configuration, and
+ useful if a domain is planning for future
+ extensibility. The I instance will end up
+ initially being the leader of both the
+ <emphasis>ls.rnp.br</emphasis> subdomain and the
+ <emphasis>rnp.br</emphasis> domain as the
+ defacto winner of both leader elections.
+ </para>
+ </listitem>
+ <listitem>
+ Finally, in this example there would be four
<command>LS</command> instances participating
in the global ring representing the registed
content of all eight <command>LS</command>
@@ -542,7 +559,8 @@
The default <emphasis>Scope</emphasis>
<command>SHOULD</command> be determined by appending a URI
with the fully qualified hostname of the host running the
- <command>LS</command> to the global ls.perfsonar.net domain
+ <command>LS</command> to the global
+ <emphasis>perfsonar.net</emphasis> domain
that will be supported by the perfSONAR consortium.
For example,
a new <command>LS</command> started on rnp.br would

Modified: trunk/nmwg/doc/dLS/dLS_spec_1.html
===================================================================
--- trunk/nmwg/doc/dLS/dLS_spec_1.html 2008-01-07 14:42:54 UTC (rev 326)
+++ trunk/nmwg/doc/dLS/dLS_spec_1.html 2008-01-07 17:30:29 UTC (rev 327)
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Distributed Lookup Service (dLS) in the perfSONAR
Framework</title><meta name="generator" content="DocBook XSL Stylesheets
V1.71.0" /></head><body><div class="article" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h1 class="title"><a
id="id2478927"></a>Distributed Lookup Service (dLS) in the perfSONAR
Framework</h1></div><div><div class="authorgroup"><div class="author"><h3
class="author">J. Boote</h3></div><div class="author"><h3
class="author">M. Glowiak</h3></div><div class="author"><h3
class="author">M. Swany</h3></div><div class="author"><h3
class="author">J. Zurawski</h3></div></div></div><div>Copyright © 2006, 2007, 2008 Internet2, Poznan
Supercomputing and Networking Center, University of
Delaware</div></div><hr /></div><div class="toc">Table of
Contents<dl><dt><a href="#changes">1. Document
Changes</a></dt><dt><a href="#introduction">2.
Introduction</a></dt><dt><a
href="#system_specific_operation">3. System Specific
Operation</a></dt><dd><dl><dt><a
href="#system_overview">3.1. Overview</a></dt><dt><a href="#system_scope">3.2. Scope
Formation</a></dt><dd><dl><dt><a
href="#scope_specification">3.2.1. Scope
Specification</a></dt><dt><a
href="#scope_hierarchy">3.2.2. Scope Hierarchy</a></dt><dt><a href="#scope_defaults">3.2.3. Scope
Defaults</a></dt><dt><a href="#scope_algorithms">
3.2.4. Scope Algorithms</a></dt><dd><dl><dt><a href="#join_procedure">3.2.4.1. Join
Procedure</a></dt><dd><dl><dt><a
href="#join_alg">3.2.4.1.1.
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#token_messages">3.2.5. Token Messages for Control and
Election</a></dt><dd><dl><dt><a
href="#leader_election">3.2.5.1. Leader Election</a></dt><dt><a href="#registration_control">3.2.5.2. Registration
Control</a></dt><dd><dl><dt><a
href="#passing_algorithm">3.2.5.2.1. Passing
Algorithm</a></dt><dt><a
href="#rotation_time_computation">3.2.5.2.2. Rotation Time
Computation</a></dt></dl></dd></dl></dd><dt><a
href="#summarization_messages">3.2.6. Summarization
Messages</a></dt></dl></dd><dt><a
href="#bootstrapping">3.3. Bootstrapping</a></dt><dt><a href="#system_summari
zation">3.4. Summarization</a></dt><dd><dl><dt><a href="#system_summarization_lower">3.4.1. Lower
Scope</a></dt><dt><a
href="#system_summarization_upper">3.4.2. Upper
Scope</a></dt><dd><dl><dt><a
href="#system_summarization_upper_alg">3.4.2.1. IP Address
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#system_search">3.5. Search</a></dt><dd><dl><dt><a href="#system_search_discovery_phase">3.5.1. Discovery
Phase</a></dt><dd><dl><dt><a
href="#system_search_discovery_algorithm">3.5.1.1.
Algorithm</a></dt></dl></dd><dt><a
href="#system_search_metadata_query_phase">3.5.2. Metadata Query
Phase</a></dt></dl></dd></dl></dd><dt><a
href="#structures_and_messages">4. Structures and
Messages</a></dt><dd><dl><dt><a href="#servic
e_metadata">4.1. Service Metadata Example</a></dt><dt!
><a href="#lookup_info">4.2. Lookup
Information</a></dt><dt><a href="#ls_ring">4.3.
LS Ring File Structure</a></dt><dd><dl><dt><a
href="#ls_ring_lower">4.3.1. Lower Level</a></dt><dt><a href="#ls_ring_upper">4.3.2. Upper
Level</a></dt></dl></dd><dt><a
href="#ls_join">4.4. LS Join</a></dt><dd><dl><dt><a href="#ls_join_request">4.4.1.
Request</a></dt><dt><a
href="#ls_join_response">4.4.2. Response</a></dt></dl></dd><dt><a href="#ls_token_message">4.5. LS Token
Message</a></dt><dd><dl><dt><a
href="#ls_token_message_request">4.5.1. Request</a></dt><dt><a href="#ls_token_message_response">4.5.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message">4.6. LS Summary Message</a>
</dt><dd><dl><dt><a
href="#ls_summary_message_upper">4.6.1.
Upper</a></dt><dd><dl><dt><a
href="#ls_summary_message_upper_request">4.6.1.1.
Request</a></dt><dt><a
href="#ls_summary_message_upper_response">4.6.1.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message_lower">4.6.2.
Lower</a></dt><dd><dl><dt><a
href="#ls_summary_message_lower_request">4.6.2.1.
Request</a></dt><dt><a
href="#ls_summary_message_lower_response">4.6.2.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#ls_leader_message">4.7. LS Leader
Message</a></dt><dd><dl><dt><a
href="#ls_leader_message_request">4.7.1. Request</a></dt><dt><a href="#ls_leader_message_response">4.7.2.
Response</a></dt></dl></dd><dt><a hre
f="#ls_discovery_message">4.8. LS Discovery Message</a></spa!
n></dt><
dd><dl><dt><a
href="#ls_discovery_message_request">4.8.1. Request</a></dt><dt><a href="#ls_discovery_message_response">4.8.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#glossary">Terms</a></dt><dt><a
href="#bibliography">References</a></dt></dl></div><div
class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a id="changes"></a>1. Document
Changes</h2></div></div></div><div class="table"><a id="table.1"></a>Table 1. Change Log<div
class="table-contents"><table summary="Change Log" border="1"><colgroup><col
align="left" /></colgroup><thead><tr><th align="left">Version</th><th
align="left">Date</th><th align="left">Description</th><th
align="left">Author(s)</th></tr></thead><tbody><tr><td
align="left">1.0</td><td align="left">12/17/2007</td><td align="left">Initia
l Preparation</td><td align="left">J. Zurawski</td></tr><tr><td
align="left">1.1</td><td align="left">1/1/2008</td><td align="left">Update of
Scope Formation and boot-strapping</td><td align="left">J.
Boote</td></tr><tr><td align="left">1.0</td><td align="left">1/7/2008</td><td
align="left">Addition/Correction of scope diagrams</td><td align="left">J.
Zurawski</td></tr></tbody></table></div></div> </div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
id="introduction"></a>2. Introduction</h2></div></div></div>
+<html xmlns="http://www.w3.org/1999/xhtml";><head><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"
/><title>Distributed Lookup Service (dLS) in the perfSONAR
Framework</title><meta name="generator" content="DocBook XSL Stylesheets
V1.71.1" /></head><body><div class="article" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h1 class="title"><a
id="id824766"></a>Distributed Lookup Service (dLS) in the perfSONAR
Framework</h1></div><div><div class="authorgroup"><div class="author"><h3
class="author">J. Boote</h3></div><div class="author"><h3
class="author">M. Glowiak</h3></div><div class="author"><h3
class="author">M. Swany</h3></div><div class="author"><h3
class="author">J. Zurawski</h3></div></div></div><div>Copyright © 2006, 2007, 2008 Internet2, Poznan Supercomputing
and Networking Center, University of Delaware</div></div><hr /></div><div
class="toc">Table of Contents<dl><dt><a
href="#changes">1. Document Changes</a></dt><dt><a href="#introduction">2.
Introduction</a></dt><dt><a
href="#system_specific_operation">3. System Specific
Operation</a></dt><dd><dl><dt><a
href="#system_overview">3.1. Overview</a></dt><dt><a href="#system_scope">3.2. Scope
Formation</a></dt><dd><dl><dt><a
href="#scope_specification">3.2.1. Scope
Specification</a></dt><dt><a
href="#scope_hierarchy">3.2.2. Scope Hierarchy</a></dt><dt><a href="#scope_defaults">3.2.3. Scope
Defaults</a></dt><dt><a
href="#scope_algorithms">3
.2.4. Scope Algorithms</a></dt><dd><dl><dt><a href="#join_procedure">3.2.4.1. Join
Procedure</a></dt><dd><dl><dt><a
href="#join_alg">3.2.4.1.1.
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#token_messages">3.2.5. Token Messages for Control and
Election</a></dt><dd><dl><dt><a
href="#leader_election">3.2.5.1. Leader Election</a></dt><dt><a href="#registration_control">3.2.5.2. Registration
Control</a></dt><dd><dl><dt><a
href="#passing_algorithm">3.2.5.2.1. Passing
Algorithm</a></dt><dt><a
href="#rotation_time_computation">3.2.5.2.2. Rotation Time
Computation</a></dt></dl></dd></dl></dd><dt><a
href="#summarization_messages">3.2.6. Summarization
Messages</a></dt></dl></dd><dt><a
href="#bootstrapping">3.3. Bootstrapping</a></dt><dt><a href="#system_summariz
ation">3.4. Summarization</a></dt><dd><dl><dt><a href="#system_summarization_lower">3.4.1. Lower
Scope</a></dt><dt><a
href="#system_summarization_upper">3.4.2. Upper
Scope</a></dt><dd><dl><dt><a
href="#system_summarization_upper_alg">3.4.2.1. IP Address
Algorithm</a></dt></dl></dd></dl></dd><dt><a
href="#system_search">3.5. Search</a></dt><dd><dl><dt><a href="#system_search_discovery_phase">3.5.1. Discovery
Phase</a></dt><dd><dl><dt><a
href="#system_search_discovery_algorithm">3.5.1.1.
Algorithm</a></dt></dl></dd><dt><a
href="#system_search_metadata_query_phase">3.5.2. Metadata Query
Phase</a></dt></dl></dd></dl></dd><dt><a
href="#structures_and_messages">4. Structures and
Messages</a></dt><dd><dl><dt><a href="#service
_metadata">4.1. Service Metadata Example</a></dt><dt>!
<a href="#lookup_info">4.2. Lookup
Information</a></dt><dt><a href="#ls_ring">4.3.
LS Ring File Structure</a></dt><dd><dl><dt><a
href="#ls_ring_lower">4.3.1. Lower Level</a></dt><dt><a href="#ls_ring_upper">4.3.2. Upper
Level</a></dt></dl></dd><dt><a
href="#ls_join">4.4. LS Join</a></dt><dd><dl><dt><a href="#ls_join_request">4.4.1.
Request</a></dt><dt><a
href="#ls_join_response">4.4.2. Response</a></dt></dl></dd><dt><a href="#ls_token_message">4.5. LS Token
Message</a></dt><dd><dl><dt><a
href="#ls_token_message_request">4.5.1. Request</a></dt><dt><a href="#ls_token_message_response">4.5.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message">4.6. LS Summary Message</a></dt><dd><dl><dt><a
href="#ls_summary_message_upper">4.6.1.
Upper</a></dt><dd><dl><dt><a
href="#ls_summary_message_upper_request">4.6.1.1.
Request</a></dt><dt><a
href="#ls_summary_message_upper_response">4.6.1.2.
Response</a></dt></dl></dd><dt><a
href="#ls_summary_message_lower">4.6.2.
Lower</a></dt><dd><dl><dt><a
href="#ls_summary_message_lower_request">4.6.2.1.
Request</a></dt><dt><a
href="#ls_summary_message_lower_response">4.6.2.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#ls_leader_message">4.7. LS Leader
Message</a></dt><dd><dl><dt><a
href="#ls_leader_message_request">4.7.1. Request</a></dt><dt><a href="#ls_leader_message_response">4.7.2.
Response</a></dt></dl></dd><dt><a href
="#ls_discovery_message">4.8. LS Discovery Message</a></span!
></dt><d
d><dl><dt><a
href="#ls_discovery_message_request">4.8.1. Request</a></dt><dt><a href="#ls_discovery_message_response">4.8.2.
Response</a></dt></dl></dd></dl></dd><dt><a
href="#glossary">Terms</a></dt><dt><a
href="#bibliography">References</a></dt></dl></div><div
class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a id="changes"></a>1. Document
Changes</h2></div></div></div><div class="table"><a id="table.1"></a>Table 1. Change Log<div
class="table-contents"><table summary="Change Log" border="1"><colgroup><col
align="left" /></colgroup><thead><tr><th align="left">Version</th><th
align="left">Date</th><th align="left">Description</th><th
align="left">Author(s)</th></tr></thead><tbody><tr><td
align="left">1.0</td><td align="left">12/17/2007</td><td align="left">Initial
Preparation</td><td align="left">J. Zurawski</td></tr><tr><td
align="left">1.1</td><td align="left">1/1/2008</td><td align="left">Update of
Scope Formation and boot-strapping</td><td align="left">J.
Boote</td></tr><tr><td align="left">1.0</td><td align="left">1/7/2008</td><td
align="left">Addition/Correction of scope diagrams</td><td align="left">J.
Zurawski</td></tr></tbody></table></div></div> </div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
id="introduction"></a>2. Introduction</h2></div></div></div>
This document describes the
Distributed Lookup Service
(dLS)
- in the <a href="#id2532917">perfSONAR</a> system. This modification
extends
+ in the <a href="#id905683">perfSONAR</a> system. This modification
extends
the basic Lookup Service
(LS)
functionality that has been present in the system for some time. The
basic LS supports the storage and querying of
@@ -66,7 +66,7 @@
<a href="#lookup_info">Lookup Information</a>).

The idea is to move the metadata from a service-local
- <a href="#id2532935">XML</a> data store to a specialized
+ <a href="#id905701">XML</a> data store to a specialized
LS with additional
searching capabilities. The
LS consists of an
XML database, (i.e.
<a href="#Berkeley DB XML">Berkeley DB XML</a> or <a
href="#eXist XML DB">eXist XML DB</a>)
@@ -219,8 +219,7 @@
example of this would be
psls://perfsonar.net/!psls://internet2.edu.
The next level up from this would be
- psls://perfsonar.net, where this
- LS
would be a member.
+ psls://perfsonar.net.
</li></ol></div>

When configuring a new LS instance the
@@ -290,7 +289,7 @@
</li><li>
C and D have a similar arrangement as A and B
above, but are part of a sub-domain (the
- ls.
subclass of
+ ls.
subscope of
geant.net). This sub-domain
will be summarized and one of (C or D) will
represent the sub-domain information in the
@@ -325,8 +324,22 @@
G and H will elect a leader of the domain
level scope and summarize the domain for
participation in the global ring.
+ </li><li>
+ I is specified similar to H above for
+ the ls.
subdomain
+ of rnp.br, but there
+ are no current instances defined at the
+ domain level.
+ 
+ This is a perfectly valid configuration, and
+ useful if a domain is planning for future
+ extensibility. The I instance will end up
+ initially being the leader of both the
+ ls.rnp.br
subdomain and the
+ rnp.br
domain as the
+ defacto winner of both leader elections.
</li><li>
- Finally, in this example there would be three
+ Finally, in this example there would be four
LS
instances participating
in the global ring representing the registed
content of all eight LS
@@ -1074,32 +1087,32 @@
Layer 3.
<pre class="programlisting">

- <nmwg:metadata
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; id="m_ale-netutil-1">
- <netutil:subject
xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";
id="s_ale-netutil-1">
- <nmwgt:interface xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";>
- <nmwgt:ifAddress type="ipv4">128.4.133.165</nmwgt:ifAddress>
- <nmwgt:hostName>ale.pc.cis.udel.edu</nmwgt:hostName>
- <nmwgt:ifName>eth0</nmwgt:ifName>
- <nmwgt:ifIndex>2</nmwgt:ifIndex>
- <nmwgt:direction>in</nmwgt:direction>
- <nmwgt:capacity>1000000000</nmwgt:capacity>
- </nmwgt:interface>
- </netutil:subject>
- <nmwg:eventType>
+ <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
id="m_ale-netutil-1">
+ <netutil:subject
xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";
id="s_ale-netutil-1">
+ <nmwgt:interface
xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/">
+ <nmwgt:ifAddress
type="ipv4">128.4.133.165</nmwgt:ifAddress>
+
<nmwgt:hostName>ale.pc.cis.udel.edu</nmwgt:hostName>
+ <nmwgt:ifName>eth0</nmwgt:ifName>
+ <nmwgt:ifIndex>2</nmwgt:ifIndex>
+ <nmwgt:direction>in</nmwgt:direction>
+ <nmwgt:capacity>1000000000</nmwgt:capacity>
+ </nmwgt:interface>
+ </netutil:subject>
+ <nmwg:eventType>
http://ggf.org/ns/nmwg/tools/snmp/2.0
- </nmwg:eventType>
- <nmwg:eventType>
+ </nmwg:eventType>
+ <nmwg:eventType>
http://ggf.org/ns/nmwg/characteristic/utilization/2.0
- </nmwg:eventType>
- <nmwg:parameters id="p_ale-netutil-1">
- <nmwg:parameter name="supportedEventType">
+ </nmwg:eventType>
+ <nmwg:parameters id="p_ale-netutil-1">
+ <nmwg:parameter name="supportedEventType">
http://ggf.org/ns/nmwg/tools/snmp/2.0
- </nmwg:parameter>
- <nmwg:parameter name="supportedEventType">
+ </nmwg:parameter>
+ <nmwg:parameter name="supportedEventType">
http://ggf.org/ns/nmwg/characteristic/utilization/2.0
- </nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ </nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h3 class="title"><a
id="lookup_info"></a>4.2. Lookup Information</h3></div></div></div>
Example Lookup Information from a Measurement Archive
@@ -1108,51 +1121,51 @@
metadata from the MA.
<pre class="programlisting">

- <nmwg:metadata
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
id="http://newcastle.pc.cis.udel.edu:6767/perfSONAR_PS/services/snmpMA";>
- <perfsonar:subject id="subject.15977808">
- <psservice:service id="service.16283379">
- <psservice:serviceName>UDel perfSONAR-PS SNMP
MA</psservice:serviceName>
- <psservice:accessPoint>
+ <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
id="http://newcastle.pc.cis.udel.edu:6767/perfSONAR_PS/services/snmpMA">
+ <perfsonar:subject id="subject.15977808">
+ <psservice:service id="service.16283379">
+ <psservice:serviceName>UDel perfSONAR-PS SNMP
MA</psservice:serviceName>
+ <psservice:accessPoint>

http://newcastle.pc.cis.udel.edu:6767/perfSONAR_PS/services/snmpMA
- </psservice:accessPoint>
- <psservice:serviceType>MA</psservice:serviceType>
- <psservice:serviceDescription>
+ </psservice:accessPoint>
+ <psservice:serviceType>MA</psservice:serviceType>
+ <psservice:serviceDescription>
perfSPNAR-PS SNMP MA deployed at UDel, Newark DE, USA
- </psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- </nmwg:metadata>
+ </psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ </nmwg:metadata>

<nmwg:data xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";

id="http://newcastle.pc.cis.udel.edu:6666/perfSONAR_PS/services/LS/1177595435/1";

metadataIdRef="http://newcastle.pc.cis.udel.edu:6767/perfSONAR_PS/services/snmpMA">
- <nmwg:metadata id="m_ale-netutil-1">
- <netutil:subject
xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";
id="s_ale-netutil-1">
- <nmwgt:interface xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";>
- <nmwgt:ifAddress type="ipv4">128.4.133.165</nmwgt:ifAddress>
- <nmwgt:hostName>ale.pc.cis.udel.edu</nmwgt:hostName>
- <nmwgt:ifName>eth0</nmwgt:ifName>
- <nmwgt:ifIndex>2</nmwgt:ifIndex>
- <nmwgt:direction>in</nmwgt:direction>
- <nmwgt:capacity>1000000000</nmwgt:capacity>
- </nmwgt:interface>
- </netutil:subject>
- <nmwg:eventType>
+ <nmwg:metadata id="m_ale-netutil-1">
+ <netutil:subject
xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";
id="s_ale-netutil-1">
+ <nmwgt:interface
xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/">
+ <nmwgt:ifAddress
type="ipv4">128.4.133.165</nmwgt:ifAddress>
+
<nmwgt:hostName>ale.pc.cis.udel.edu</nmwgt:hostName>
+ <nmwgt:ifName>eth0</nmwgt:ifName>
+ <nmwgt:ifIndex>2</nmwgt:ifIndex>
+ <nmwgt:direction>in</nmwgt:direction>
+ <nmwgt:capacity>1000000000</nmwgt:capacity>
+ </nmwgt:interface>
+ </netutil:subject>
+ <nmwg:eventType>
http://ggf.org/ns/nmwg/tools/snmp/2.0
- </nmwg:eventType>
- <nmwg:eventType>
+ </nmwg:eventType>
+ <nmwg:eventType>
http://ggf.org/ns/nmwg/characteristic/utilization/2.0
- </nmwg:eventType>
- <nmwg:parameters id="p_ale-netutil-1">
- <nmwg:parameter name="supportedEventType">
+ </nmwg:eventType>
+ <nmwg:parameters id="p_ale-netutil-1">
+ <nmwg:parameter name="supportedEventType">
http://ggf.org/ns/nmwg/tools/snmp/2.0
- </nmwg:parameter>
- <nmwg:parameter name="supportedEventType">
+ </nmwg:parameter>
+ <nmwg:parameter name="supportedEventType">
http://ggf.org/ns/nmwg/characteristic/utilization/2.0
- </nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
- </nmwg:data>
+ </nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>
+ </nmwg:data>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h3 class="title"><a id="ls_ring"></a>4.3. LS
Ring File Structure</h3></div></div></div>
The LSRing file
represents the
@@ -1167,71 +1180,71 @@
our scope (for example, a domain).
<pre class="programlisting">

- <nmwg:store
type="LSRing-lower">
+ <nmwg:store type="LSRing-lower">

- 
+ 

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>Internet2 LS #2</psservice:serviceName>
- <psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">0</nmwg:parameter>
- <nmwg:parameter name="leader">0</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>Internet2 LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">0</nmwg:parameter>
+ <nmwg:parameter
name="leader">0</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">0</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">0</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.1">
- <perfsonar:subject id="subject.1">
- <psservice:service id="service.1">
- <psservice:serviceName>Internet2 LS #1</psservice:serviceName>
- <psservice:accessPoint>http://patdev0.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">1</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.1">
+ <perfsonar:subject id="subject.1">
+ <psservice:service id="service.1">
+ <psservice:serviceName>Internet2 LS
#1</psservice:serviceName>
+
<psservice:accessPoint>http://patdev0.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">1</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.9">
- <perfsonar:subject id="subject.9">
- <psservice:service id="service.9">
- <psservice:serviceName>Internet2 LS #9</psservice:serviceName>
- <psservice:accessPoint>http://thunderbird.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">0</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.9">
+ <perfsonar:subject id="subject.9">
+ <psservice:service id="service.9">
+ <psservice:serviceName>Internet2 LS
#9</psservice:serviceName>
+
<psservice:accessPoint>http://thunderbird.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">0</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- </nmwg:store>
+ </nmwg:store>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
id="ls_ring_upper"></a>4.3.2. Upper Level</h4></div></div></div>
The upper level represents
the interaction
@@ -1239,41 +1252,41 @@
split).
<pre class="programlisting">

- <nmwg:store
type="LSRing-upper">
+ <nmwg:store type="LSRing-upper">

- 
+ 

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>ESnet LS #2</psservice:serviceName>
- <psservice:accessPoint>http://mea1.es.net:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">0</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>ESnet LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://mea1.es.net:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">0</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.1">
- <perfsonar:subject id="subject.1">
- <psservice:service id="service.1">
- <psservice:serviceName>Geant LS #1</psservice:serviceName>
- <psservice:accessPoint>http://ls.perfsonar.pionier.net.pl:8080/XML-LS-1.1.1/services/LookupService</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">1</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.1">
+ <perfsonar:subject id="subject.1">
+ <psservice:service id="service.1">
+ <psservice:serviceName>Geant LS
#1</psservice:serviceName>
+
<psservice:accessPoint>http://ls.perfsonar.pionier.net.pl:8080/XML-LS-1.1.1/services/LookupService</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">1</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- </nmwg:store>
+ </nmwg:store>

</pre></div></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h3 class="title"><a id="ls_join"></a>4.4. LS
Join</h3></div></div></div>
The LSJoin messages
are used by a service to
@@ -1287,23 +1300,23 @@
contain service information.
<pre class="programlisting">

- <nmwg:message type="LSControlRequest">
+ <nmwg:message type="LSControlRequest">

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>Internet2 LS #2</psservice:serviceName>
- <psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/join</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>Internet2 LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/join</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data
id="data.2" metadataIdRef="metadata.2" />
+ <nmwg:data id="data.2" metadataIdRef="metadata.2" />

- </nmwg:message>
+ </nmwg:message>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
id="ls_join_response"></a>4.4.2. Response</h4></div></div></div>
The response message should indicate success or failure via the
@@ -1315,45 +1328,45 @@
snapshot of the group.
<pre class="programlisting">

- <nmwg:message type="LSControlResponse">
+ <nmwg:message type="LSControlResponse">

- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/join/success</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/join/success</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data
id="data.6" metadataIdRef="metadata.6">
- <nmwg:metadata id="metadata.1">
- <perfsonar:subject id="subject.1">
- <psservice:service id="service.1">
- <psservice:serviceName>Internet2 LS #1</psservice:serviceName>
- <psservice:accessPoint>http://patdev0.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- </nmwg:metadata>
+ <nmwg:data id="data.6" metadataIdRef="metadata.6">
+ <nmwg:metadata id="metadata.1">
+ <perfsonar:subject id="subject.1">
+ <psservice:service id="service.1">
+ <psservice:serviceName>Internet2 LS
#1</psservice:serviceName>
+
<psservice:accessPoint>http://patdev0.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.9">
- <perfsonar:subject id="subject.9">
- <psservice:service id="service.9">
- <psservice:serviceName>Internet2 LS #9</psservice:serviceName>
- <psservice:accessPoint>http://thunderbird.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- </nmwg:metadata>
- </nmwg:data>
+ <nmwg:metadata id="metadata.9">
+ <perfsonar:subject id="subject.9">
+ <psservice:service id="service.9">
+ <psservice:serviceName>Internet2 LS
#9</psservice:serviceName>
+
<psservice:accessPoint>http://thunderbird.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ </nmwg:metadata>
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h3 class="title"><a
id="ls_token_message"></a>4.5. LS Token Message</h3></div></div></div>
This message exchange represents the token that is passed between
@@ -1366,77 +1379,77 @@
upper depending on the
token we are exchanging).
<pre class="programlisting">

- <nmwg:message
type="LSControlRequest">
+ <nmwg:message type="LSControlRequest">

- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/token/lower</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/token/lower</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data
id="data.6" metadataIdRef="metadata.6">
+ <nmwg:data id="data.6" metadataIdRef="metadata.6">

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>Internet2 LS #2</psservice:serviceName>
- <psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">0</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>Internet2 LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">0</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.1">
- 
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.1">
+ 
+ </nmwg:metadata>

- <nmwg:metadata id="metadata.9">
- 
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.9">
+ 
+ </nmwg:metadata>

- </nmwg:data>
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
id="ls_token_message_response"></a>4.5.2. Response</h4></div></div></div>
The response to this message should indicate success or failure.
Failure and timeouts should trigger a resend.
<pre class="programlisting">

- <nmwg:message type="LSControlResponse">
+ <nmwg:message type="LSControlResponse">

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>Internet2 LS #2</psservice:serviceName>
- <psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/token/lower/success</nmwg:eventType>
- <nmwg:parameters>
- <nmwg:parameter name="active">1</nmwg:parameter>
- <nmwg:parameter name="leader">0</nmwg:parameter>
- </nmwg:parameters>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>Internet2 LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/token/lower/success</nmwg:eventType>
+ <nmwg:parameters>
+ <nmwg:parameter
name="active">1</nmwg:parameter>
+ <nmwg:parameter
name="leader">0</nmwg:parameter>
+ </nmwg:parameters>
+ </nmwg:metadata>

- <nmwg:data
id="data.2" metadataIdRef="metadata.2">
- <nmwgr:datum value="some sort of message?">
- </nmwg:data>
+ <nmwg:data id="data.2" metadataIdRef="metadata.2">
+ <nmwgr:datum value="some sort of message?">
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h3 class="title"><a
id="ls_summary_message"></a>4.6. LS Summary Message</h3></div></div></div>
The summary message
represents one
@@ -1454,35 +1467,35 @@
is the summary info.
<pre class="programlisting">

- <nmwg:message type="LSControlRequest">
+ <nmwg:message type="LSControlRequest">

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>Internet2 LS #2</psservice:serviceName>
- <psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/summary/upper</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>Internet2 LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/summary/upper</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data id="data.2" metadataIdRef="metadata.2">
- <nmwg:metadata>
- <summary:subject
xmlns:summary="http://ggf.org/ns/nmwg/summary/2.0/";>
- <nmtl3:network>
- <nmtl3:ipAddress>128.4.10.0/16</nmtl3:ipAddress>
- </nmtl3:network>
- </summary:subject>
- <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType>
- <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
- <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:data id="data.2" metadataIdRef="metadata.2">
+ <nmwg:metadata>
+ <summary:subject
xmlns:summary="http://ggf.org/ns/nmwg/summary/2.0/">
+ <nmtl3:network>
+
<nmtl3:ipAddress>128.4.10.0/16</nmtl3:ipAddress>
+ </nmtl3:network>
+ </summary:subject>
+
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType>
+
<nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
+
<nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType>
+ </nmwg:metadata>

- </nmwg:data>
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h5 class="title"><a
id="ls_summary_message_upper_response"></a>4.6.1.2. Response</h5></div></div></div>
The response message should indicate success or failure via
@@ -1504,26 +1517,26 @@
</li></ul></div>
<pre class="programlisting">

- <nmwg:message type="LSControlResponse">
+ <nmwg:message type="LSControlResponse">

- 
- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/summary/upper/success</nmwg:eventType>
- </nmwg:metadata>
+ 
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/summary/upper/success</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data id="data.6" metadataIdRef="metadata.6">
- <nmwgr:datum value="some sort of message?">
- </nmwg:data>
+ <nmwg:data id="data.6" metadataIdRef="metadata.6">
+ <nmwgr:datum value="some sort of message?">
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div></div><div class="section" lang="en"
xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a
id="ls_summary_message_lower"></a>4.6.2. Lower</h4></div></div></div>
This message exchange represents when an LS instance is holding
@@ -1536,33 +1549,33 @@
parameters) summary.
<pre class="programlisting">

- <nmwg:message type="LSControlRequest">
+ <nmwg:message type="LSControlRequest">

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>Internet2 LS #2</psservice:serviceName>
- <psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/summary/lower</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>Internet2 LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://packrat.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/summary/lower</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data id="data.2" metadataIdRef="metadata.2">
+ <nmwg:data id="data.2" metadataIdRef="metadata.2">

- <nmwg:metadata>
- 
- </nmwg:metadata>
+ <nmwg:metadata>
+ 
+ </nmwg:metadata>

- <nmwg:metadata>
- 
- </nmwg:metadata>
+ <nmwg:metadata>
+ 
+ </nmwg:metadata>

- </nmwg:data>
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h5 class="title"><a
id="ls_summary_message_lower_response"></a>4.6.2.2. Response</h5></div></div></div>
The response message should indicate success or failure via
@@ -1584,26 +1597,26 @@
</li></ul></div>
<pre class="programlisting">

- <nmwg:message type="LSControlResponse">
+ <nmwg:message type="LSControlResponse">

- 
- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/summary/lower/success</nmwg:eventType>
- </nmwg:metadata>
+ 
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/summary/lower/success</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data id="data.6" metadataIdRef="metadata.6">
- <nmwgr:datum value="some sort of message?">
- </nmwg:data>
+ <nmwg:data id="data.6" metadataIdRef="metadata.6">
+ <nmwgr:datum value="some sort of message?">
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div></div></div><div class="section" lang="en"
xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a
id="ls_leader_message"></a>4.7. LS Leader Message</h3></div></div></div>
This message exchange will be conducted between the Leader and
@@ -1622,67 +1635,67 @@
well as the summary data.
<pre class="programlisting">

- <nmwg:message type="LSControlRequest">
+ <nmwg:message type="LSControlRequest">

- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/leader</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/leader</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data
id="data.6" metadataIdRef="metadata.6">
+ <nmwg:data id="data.6" metadataIdRef="metadata.6">

- 
+ 

- <nmwg:metadata id="metadata.2">
- <perfsonar:subject id="subject.2">
- <psservice:service id="service.2">
- <psservice:serviceName>ESnet LS #2</psservice:serviceName>
- <psservice:accessPoint>http://mea1.es.net:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- <nmwg:eventType>http://perfsonar.net/services/LS/summary</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:metadata id="metadata.2">
+ <perfsonar:subject id="subject.2">
+ <psservice:service id="service.2">
+ <psservice:serviceName>ESnet LS
#2</psservice:serviceName>
+
<psservice:accessPoint>http://mea1.es.net:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+
<nmwg:eventType>http://perfsonar.net/services/LS/summary</nmwg:eventType>
+ </nmwg:metadata>

- 
+ 

- <nmwg:data id="data.2" metadataIdRef="metadata.2">
- <nmwg:metadata>
- <summary:subject
xmlns:summary="http://ggf.org/ns/nmwg/summary/2.0/";>
- <nmtl3:network>
- <nmtl3:ipAddress>128.4.10.0/16</nmtl3:ipAddress>
- </nmtl3:network>
- </summary:subject>
- <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType>
- <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
- <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:data id="data.2" metadataIdRef="metadata.2">
+ <nmwg:metadata>
+ <summary:subject
xmlns:summary="http://ggf.org/ns/nmwg/summary/2.0/">
+ <nmtl3:network>
+
<nmtl3:ipAddress>128.4.10.0/16</nmtl3:ipAddress>
+ </nmtl3:network>
+ </summary:subject>
+
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType>
+
<nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
+
<nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType>
+ </nmwg:metadata>

- </nmwg:data>
+ </nmwg:data>

- 
+ 

- </nmwg:data>
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
id="ls_leader_message_response"></a>4.7.2. Response</h4></div></div></div>
The response message will contain the results (success or
failure).
<pre class="programlisting">

- <nmwg:message type="LSControlRequest">
+ <nmwg:message type="LSControlRequest">

- 
+ 

- </nmwg:message>
+ </nmwg:message>

</pre></div></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h3 class="title"><a
id="ls_discovery_message"></a>4.8. LS Discovery
Message</h3></div></div></div>
The discovery message represents the step used to find the
@@ -1693,54 +1706,54 @@
section with some identifying features.
<pre class="programlisting">

- <nmwg:message type="LSDiscoveryRequest">
+ <nmwg:message type="LSDiscoveryRequest">

- <nmwg:metadata id="metadata.1">
+ <nmwg:metadata id="metadata.1">

- 
+ 

- </nmwg:metadata>
+ </nmwg:metadata>

- <nmwg:data
id="data.1" metadataIdRef="metadata.1" />
+ <nmwg:data id="data.1" metadataIdRef="metadata.1" />

- </nmwg:message>
+ </nmwg:message>

</pre></div><div class="section" lang="en" xml:lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
id="ls_discovery_message_response"></a>4.8.2. Response</h4></div></div></div>
The response message will feature a status message, as described
in <a href="#system_search_discovery_algorithm">Algorithm</a>.
<pre class="programlisting">

- <nmwg:message type="LSDiscoveryResponse">
+ <nmwg:message type="LSDiscoveryResponse">

- <nmwg:metadata id="metadata.1.r">
- 
- <nmwg:eventType>success</nmwg:eventType>
+ <nmwg:metadata id="metadata.1.r">
+ 
+ <nmwg:eventType>success</nmwg:eventType>

- <nmwg:eventType>failure</nmwg:eventType>
+ <nmwg:eventType>failure</nmwg:eventType>

- <nmwg:eventType>referral</nmwg:eventType>
- </nmwg:metadata>
+ <nmwg:eventType>referral</nmwg:eventType>
+ </nmwg:metadata>

- <nmwg:data
id="data.1.r" metadataIdRef="metadata.1.r">
+ <nmwg:data id="data.1.r" metadataIdRef="metadata.1.r">

- 
- <nmwgr:datum value="some message" />
+ 
+ <nmwgr:datum value="some message" />

- 
- <nmwg:metadata id="metadata.6">
- <perfsonar:subject id="subject.6">
- <psservice:service id="service.6">
- <psservice:serviceName>Internet2 LS #6</psservice:serviceName>
- <psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
- <psservice:serviceType>LS</psservice:serviceType>
- <psservice:serviceDescription>...</psservice:serviceDescription>
- </psservice:service>
- </perfsonar:subject>
- </nmwg:metadata>
+ 
+ <nmwg:metadata id="metadata.6">
+ <perfsonar:subject id="subject.6">
+ <psservice:service id="service.6">
+ <psservice:serviceName>Internet2 LS
#6</psservice:serviceName>
+
<psservice:accessPoint>http://mead.internet2.edu:8080/perfSONAR_PS/services/LS</psservice:accessPoint>
+
<psservice:serviceType>LS</psservice:serviceType>
+
<psservice:serviceDescription>...</psservice:serviceDescription>
+ </psservice:service>
+ </perfsonar:subject>
+ </nmwg:metadata>

- </nmwg:data>
+ </nmwg:data>

- </nmwg:message>
+ </nmwg:message>

</pre></div></div></div><div class="glossary"><div
class="titlepage"><div><div><h2 class="title"><a
id="glossary"></a>Terms</h2></div></div></div><div class="glossdiv"><h3
class="title">A</h3><dl><dt><a id=""></a></dt><dd>
</dd></dl></div><div class="glossdiv"><h3
class="title">B</h3><dl><dt><a id="Berkeley DB XML"></a>Berkeley DB
XML</dt><dd>
@@ -1773,8 +1786,8 @@
A query language (with some programming language
features) that is designed to query collections of XML data. It
is semantically similar to SQL.
- </dd></dl></div><div class="glossdiv"><dl></dl></div><div
class="glossdiv"><dl></dl></div></div><div class="bibliography"><div
class="titlepage"><div><div><h2 class="title"><a
id="bibliography"></a>References</h2></div></div></div><div
class="biblioentry"><a id="id2532917"></a>[<abbr
class="abbrev">perfSONAR</abbr>] 
+ </dd></dl></div><div class="glossdiv"><dl></dl></div><div
class="glossdiv"><dl></dl></div></div><div class="bibliography"><div
class="titlepage"><div><div><h2 class="title"><a
id="bibliography"></a>References</h2></div></div></div><div
class="biblioentry"><a id="id905683"></a>[<abbr
class="abbrev">perfSONAR</abbr>] 
<a href="http://www.perfsonar.net"; target="_top">perfSONAR</a>
- . </div><div class="biblioentry"><a
id="id2532935"></a>[<abbr class="abbrev">XML</abbr>] 
+ . </div><div class="biblioentry"><a
id="id905701"></a>[<abbr class="abbrev">XML</abbr>] 
<a href="http://www.w3.org/XML"; target="_top">Extensible Markup
Language (XML)</a>
. </div></div></div></body></html>

nmwg: r327 - trunk/nmwg/doc/dLS, svnlog, 01/07/2008

List archive

nmwg: r327 - trunk/nmwg/doc/dLS