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

Maintenance Email #240

Open
jjavierweb opened this issue Apr 23, 2020 · 2 comments
Open

Maintenance Email #240

jjavierweb opened this issue Apr 23, 2020 · 2 comments
Assignees
Labels
status: accepted type: feature request Issue is an accepted feature request

Comments

@jjavierweb
Copy link
Contributor

Environment

  • Python version: 3.6
  • Peering Manager version: 1.1.1-dev

Proposed Functionality

Create a new template for sending emails to peers connected to a specific router when maintenance is going to be performed to send an email update to peers
This should be a simple template that goes over each peering session on a router, and gets the AS number, from there it uses the contact email information and based on a form that has the date and time of the maintenance and the time of outage expected
Then an email is sent to each peer

Use Case

If router x will be reloaded for an upgrade, we want to notify peers x,x,x,x via email with the information of date and time and duration

External Dependencies

@gmazoyer gmazoyer self-assigned this Apr 23, 2020
@gmazoyer gmazoyer added the type: feature request Issue is an accepted feature request label Apr 23, 2020
@XioNoX
Copy link

XioNoX commented May 11, 2020

FYI, there is a draft standard for maintenance emails: https://github.com/jda/maintnote-std/blob/master/standard.md
And some tools like https://github.com/wasabi222/janitor use it.

@mngan
Copy link
Contributor

mngan commented May 29, 2020

I think a more general bulk email mechanism would be good. There is also the use case of reaching out peers that you don't have sessions with for an IX. So I guess you would want to do different criteria.

  • Contact all peers on a router (both Direct and IX sessions)
  • Contact all peers for an IX (ideally regardless of router)
  • Contact all peers that are missing for an IX

@jamesditrapani jamesditrapani added this to To do in Templating/Notification via automation Apr 30, 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepted type: feature request Issue is an accepted feature request
Development

No branches or pull requests

4 participants