Opened 5 years ago

#1295 new

AL2S OESS manifest does not include any slivers.

Reported by: lnevers@bbn.com Owned by: luke@grnoc.iu.edu
Priority: major Milestone:
Component: STITCHING Version: SPIRAL6
Keywords: GENI Network Stitching Cc:
Dependencies:

Description

The OESS manifest does not list any slivers.

According to Aaron, the problem is that Omni looks for slivers in the manifest RSpec so it can tell the clearinghouse that you have a reservation at this aggregate. But AL2S does not add any sliver_id attribute on the link where it has allocated VLAN tags.

For comparison, here is what MAX sends back in a manifest:

.....
  <link client_id="link-pg2-max3" sliver_id="urn:publicid:IDN+dragon.maxgigapop.net+sliver+dragon.maxgigapop.net-2510" vlantag="3030">
....
</link
<stitching ........

Without this fix, an experimenter will have to use the new unreleased Omni and call sliverstatus on the slice at AL2S (or all AMs known to stitcher) before Omni will tell the clearinghouse that AL2S has a reservation for this slice. Or else rely on stitcher to know there are resources at AL2S: The portal will not know.

Change History (0)

Note: See TracTickets for help on using tickets.