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

Flag IX Peering Sessions Without Corresponding PeeringDB Entry #720

Open
mngan opened this issue May 19, 2023 · 2 comments
Open

Flag IX Peering Sessions Without Corresponding PeeringDB Entry #720

mngan opened this issue May 19, 2023 · 2 comments
Assignees
Labels
priority: low status: accepted type: enhancement Issue is considered as an enhancement to the code, so it is not a regression nor a blocking issue

Comments

@mngan
Copy link
Contributor

mngan commented May 19, 2023

Peering Manager version

1.7.4

Feature type

New functionality

Proposed functionality

Help identify stale IX Peering Sessions by flagging Sessions don't have a corresponding NetIXLan entry.

Use case

This flag can be used to filter and possibly clean up sessions on an IX.

Database changes

Possibly none, unless you want to cache this state in the session.

External dependencies

None

@gmazoyer
Copy link
Member

This functionality is half there, see 1.

The proposed feature could be another version of this function, removing check related to session state, and exposed as a property.

@gmazoyer gmazoyer self-assigned this May 20, 2023
@gmazoyer gmazoyer added type: enhancement Issue is considered as an enhancement to the code, so it is not a regression nor a blocking issue priority: low status: accepted labels May 20, 2023
@mngan
Copy link
Contributor Author

mngan commented May 21, 2023

I agree that separating this out would allow the operators to define their own logic for what is abandoned/stale. In general though, the combination you have is reasonable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low status: accepted type: enhancement Issue is considered as an enhancement to the code, so it is not a regression nor a blocking issue
Projects
None yet
Development

No branches or pull requests

2 participants