Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define the available data plane vlan range(s) in the manifest #159

Open
YufengXin opened this issue Jul 30, 2020 · 1 comment
Open

Define the available data plane vlan range(s) in the manifest #159

YufengXin opened this issue Jul 30, 2020 · 1 comment
Assignees

Comments

@YufengXin
Copy link
Contributor

Currently, they start from 1 and so on. We may not have that flexibility and need some VLAN ranges for dataplane connections.
That was one underimplemented function we noted in the audit report because the range [1,4089] is hard coded in two functions in sdxctrl/TopologyManager.py:

def find_vlan_on_tree(self, tree):

def find_vlan_on_path(self, path):

as part of finding the valid path and tree in the data plane.

Need to define the available range(s) in the manifest. But for the time being, probably just change the hard code.

@YufengXin
Copy link
Contributor Author

YufengXin commented Oct 29, 2020

Manifest allows to define individual clan ranges per link.

Added a new function to find disjoint vlan per link along a path: TopologyManager.py
def find_vlans_on_path(self, path):

Need more tests on vlan reservation per link along a path:
first, on the L2TunnelPolicy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants