Opened 9 years ago

Last modified 9 years ago

#161 new

Shared VLANs should be reserved by labels instead of VLAN IDs

Reported by: tupty@bbn.com Owned by: somebody
Priority: major Milestone:
Component: AM Version: SPIRAL5
Keywords: Cc:
Dependencies:

Description

I think we all know about this issue, but I just want to make a ticket to track it. The particular thing that we want is in RSpecs, we'd like to reserve shared VLANs using some logical name rather than a VLAN ID, partially because sometimes different VLAN IDs at different sites end up being in the same broadcast domain due to VLAN translation along the way. One example is that many sites connect to the shared mesoscale VLAN on 1750, but FIU connects in on 1752 and UH connects in on 1751.

As an example, we would want to reserve something like:

 <sharedvlan:link_shared_vlan name="mesoscale-openflow" />

instead of:

 <sharedvlan:link_shared_vlan name="1750" />

We understand that this will require code changes and redeployment.

Change History (1)

comment:1 Changed 9 years ago by tupty@bbn.com

This is not something that we are looking for before GEC 16. It would be nice if these changes could fit in before the next redeployment, but please let us know if the changes are difficult enough that this needs to be pushed back further. If there are questions about priority of this in relation to other things, please let me know.

Note: See TracTickets for help on using tickets.