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 fields valid_from and valid_until to object ixpfx #661

Open
arnoldnipper opened this issue Mar 7, 2020 · 6 comments
Open

Add fields valid_from and valid_until to object ixpfx #661

arnoldnipper opened this issue Mar 7, 2020 · 6 comments
Assignees

Comments

@arnoldnipper
Copy link
Contributor

@arnoldnipper arnoldnipper commented Mar 7, 2020

Migrations to new and larger IP ranges happen every now and then at ix. Supporting this in PeeringDB is crucial, as esp. the netixlan data is used to set up sessions. netixlan otoh needs information from the corresponding ixpfx resp. ixlan.

Adding fields valid_from and valid_until would support net and ix during migration.

On creation

  • value has to be a date as in created or updated
  • default for valid_ from is now()
  • default for valid_until is null
@arnoldnipper

This comment has been minimized.

Copy link
Contributor Author

@arnoldnipper arnoldnipper commented Mar 7, 2020

@peeringdb/pc this is a feature request. Please make up your mind.

@arnoldnipper

This comment has been minimized.

Copy link
Contributor Author

@arnoldnipper arnoldnipper commented Mar 7, 2020

+1

@shane-kerr

This comment has been minimized.

Copy link

@shane-kerr shane-kerr commented Mar 9, 2020

What - if any - automated processing based on this proposed value is expected here? Is this just for documenting migrations, so PeeringDB won't actually do anything with it?

@arnoldnipper

This comment has been minimized.

Copy link
Contributor Author

@arnoldnipper arnoldnipper commented Mar 9, 2020

@shane-kerr, use cases are

  • hint for networks, not to use any entries before valid_from. This keeps the ix clean from BC/ND
  • hint for PeeringDB, to automigrate leftovers to the new prefix after valid_until
  • hint for networks not to use any entries after valid_until
@grizz

This comment has been minimized.

Copy link
Member

@grizz grizz commented Mar 9, 2020

While I don't think it's a bad idea, I'm not sold on it and I'm not sure any networks would actually use it so I think it would be better to focus our efforts elsewhere.

@arnoldnipper

This comment has been minimized.

Copy link
Contributor Author

@arnoldnipper arnoldnipper commented Mar 9, 2020

Low hanging fruits IMHO. And of course it's not a a big feature, but improvement comes in small steps. I came across the idea because I've migrated eight ix the last days because of cleansing of the ixpfx/ixlan. Migration leftovers could be done automagically.

Improving data quality should be one of our top priorities.

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

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.