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

Add Additional Settings/Options for ASNs #392

Open
Patchshifter opened this issue Apr 23, 2021 · 1 comment
Open

Add Additional Settings/Options for ASNs #392

Patchshifter opened this issue Apr 23, 2021 · 1 comment
Labels
Projects

Comments

@Patchshifter
Copy link

Environment

  • Python version: Python 3.6.9
  • Peering Manager version: v1.3.3-dev

Proposed Functionality

It would be nice to have additional options and logging for ASNs, for example:

  • Have a log of when an email was sent to the peer, so we can track who we've reached out to
  • Have a way to disable certain ASNs from showing up in the Available Peers Tab (for example if they decline peering)

Currently, we are using the tag feature to handle this, but it would be nice to have it natively

Use Case

We go to one of our IXes, and see an available peer. We send an email through PM to the peers. They could either respond positively and we set up the sessions. They could decline the peering request, and we could check a box that will remove the peer from the Available Peers tab so we know not to re-engage them (or engage them at a later time). The other option is that they don't respond, and it would be nice to see when the last email was sent so we don't bombard peers with requests.

@jamesditrapani jamesditrapani added priority: low type: feature request Issue is an accepted feature request labels Apr 29, 2021
@jamesditrapani jamesditrapani added this to To do in Core via automation Apr 29, 2021
@stale stale bot added the status: wontfix Not an issue, no fix to be done, no code to be changed label Jul 12, 2021
@peering-manager peering-manager deleted a comment from stale bot Jul 12, 2021
@stale stale bot removed the status: wontfix Not an issue, no fix to be done, no code to be changed label Jul 12, 2021
@maznu
Copy link
Contributor

maznu commented Mar 7, 2022

Sometimes peers that decline peering also suggest a traffic level — I guess that could go in the comments — but they also might specify a date to wait until before submitting another request. Would "hide from Available Peers tab" be a "yes/no" option, or "until [date]/forever"?

Or perhaps that shouldn't be part of Peering Manager's remit? I guess every NOC should have their own ticketing system, so there's nothing stopping the peering team creating a ticket with "delay response until" to review peering with the hidden AS.

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

No branches or pull requests

4 participants