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

Persistent vlan resource between SDX-controller restart #215

Open
Tracked by #214
YufengXin opened this issue Aug 16, 2024 · 4 comments
Open
Tracked by #214

Persistent vlan resource between SDX-controller restart #215

YufengXin opened this issue Aug 16, 2024 · 4 comments
Assignees

Comments

@YufengXin
Copy link
Collaborator

Doublecheck: this might be implemented in sdx-controller: needs save the vlan resource use in DB so that it is persistent after sdx-controller restart.

@sajith
Copy link
Member

sajith commented Aug 20, 2024

We will need to add a method (something like TEManager.restore_vlan_reservations(..)), and sdx-controller will need to call that after a restart, I think?

@YufengXin
Copy link
Collaborator Author

will you need a persistent storage for used vlan recovery? should be implemented in MondoDB in sdx-controller? or just local? I think?

@sajith
Copy link
Member

sajith commented Aug 20, 2024

If PCE is going to stay a library the way it is today, it should not use a database. It should be up to sdx-controller to restore the previous state. I have not thought much about what sdx-controller would need to store, but I suppose it should be straightforward. This probably is the sensible medium-term plan.

If PCE becomes a stand-alone service, its application logic could use a database.

@YufengXin
Copy link
Collaborator Author

Next step: make two methods for sdx-controller: get_available_vlans():-> {domain:available_vlans} and set_available_vlans({domain:available_vlans})

six-controller will call and save/pop the info to/from the DB.

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