Make spinning up peeringdb-py fully automated

[leovegoda]

Is your feature request related to a problem? Please describe.
To improve the experience for heavy users and to better manage costs, we should make it as easy as possible to install, configure, and synchronize peeringdb-py.

Who is affected by the problem?

1. Users who make intensive queries are rate limited and should be helped to make those queries to a local machine.
2. Users whose queries travel a significant distance to be answered by www.peeringdb.com could have a better user experience with a local cache.
3. It is much cheaper for PeeringDB as an organization when heavy users keep their queries local.

What is the impact?
Happier users and more control over operational costs.

Are there security concerns?
There should not be.

Are there privacy concerns?
No.

Describe the solution you'd like
The user should be able to run a simple script that will install peeringdb-py and guide them through the configuration and synchronization.

Do you think this feature will require a formal design?
Probably.

Describe alternatives you've considered
We looked at deploying on a CDN but that would have meant extra cost and PeeringDB's data is not CDN cache friendly.

Could this feature request need support from the Admin Committee?
It should not.

What is the proposed priority?
Medium.

Provide a rationale for any/all of the above
This should make many heavy users happy. It should also help PeeringDB as an organization manage costs more effectively.

[mcmanuss8]

+1
We run a cache of peeringdb and periodically refresh the entire data set. It would be nice for other users who don't want to build their own to have this

[ccaputo]

Not automated, but in case useful to others, these are the install & upgrade steps we use at the SeattleIX for peeringdb-py: https://lists.peeringdb.com/pipermail/pdb-tech/2022-September/000444.html

[grizz]

+1

[grizz]

@peeringdb/pc Need another vote please.

[martinhannigan]

+1

…

On Fri, Oct 14, 2022 at 10:11 Matt Griswold ***@***.***> wrote: @peeringdb/pc <https://github.com/orgs/peeringdb/teams/pc> Need another vote please. — Reply to this email directly, view it on GitHub <#65 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQV3VQAP27TFVRMGPDTWDFSY7ANCNFSM5Z7V6EMQ> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[grizz]

This should be able to use the container from peeringdb/peeringdb#1274 with a few minor modifications and some documentation.