Opened 12 years ago
Last modified 11 years ago
#72 assigned
RSpecs: preserve shared-vlan info in manifest
Reported by: | ahelsing@bbn.com | Owned by: | ibaldin@renci.org |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | AM | Version: | SPIRAL4 |
Keywords: | Cc: | ||
Dependencies: |
Description
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 12 years ago by
Owner: | changed from somebody to ibaldin@renci.org |
---|---|
Status: | new → assigned |
comment:2 Changed 11 years ago by
comment:3 Changed 11 years ago by
no, not yet. The manifest should include <link_shared_vlan name="1750"/>
comment:4 Changed 11 years ago by
Priority: | major → minor |
---|
comment:5 Changed 11 years ago by
Using 'ORCA Dungeness: v.4.0-SNAPSHOT.build-5495' 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.
Checking status for unresolved tickets. Requested the following RSpec shared-vlan element:
The manifest shows:
Aaron, does this address your request?