Opened 10 years ago

Last modified 9 years ago

#72 assigned

RSpecs: preserve shared-vlan info in manifest

Reported by: Owned by:
Priority: minor Milestone:
Component: AM Version: SPIRAL4
Keywords: Cc:


manifest RSpecs should preserve the shared-vlan elements from the request, if any.

That is, the allocated links in the manifest should be marked as on the shared vlan. In particular, this allows the experimenter to see, in the manifest, the name of the shared VLAN that the link is on. This will also be useful for monitoring and GMOC data integration.

Note that this is a single instance of a larger rule: manifests should preserve elements from the request. But each such element requires (a) a model in NDL, and (b) explicit code to convert in both directions in the RSpec converter. So we will take these on a case by case basis.

Change History (5)

comment:1 Changed 10 years ago by

Owner: changed from somebody to
Status: newassigned

comment:2 Changed 10 years ago by

Checking status for unresolved tickets. Requested the following RSpec shared-vlan element:

  <link client_id="lan0">
    <interface_ref client_id="VM:if0"/>
    <s:link_shared_vlan name="1750"/>

The manifest shows:

  <link vlantag="1750" sliver_id="" 
   <interface_ref client_id="VM:if0"/>
   <ns4:geni_sliver_info start_time="2013-03-26T10:47:50.111-04:00" expiration_time="2013-04-09T09:47:50.111-04:00" 
    creation_time="2013-03-26T10:47:50.111-04:00" creator_urn=""/>

Aaron, does this address your request?

comment:3 Changed 10 years ago by

no, not yet. The manifest should include <link_shared_vlan name="1750"/>

comment:4 Changed 10 years ago by

Priority: majorminor

comment:5 Changed 9 years ago by

Using 'ORCA Dungeness:' on GPO SM verified that sliver manifest still does not include <link_shared_vlan name="1750"/> when a shared vlan element has been requested and allocated.

Note: See TracTickets for help on using tickets.