Peeringdb: Clean up info_type if name contains "Route Servers" or "Route Collector"

Created on 13 Jun 2020  Â·  8Comments  Â·  Source: peeringdb/peeringdb

[ has to wait for #745 being implemented ]

Generally, the field info_type is self-declared by the networks. However, if the name suggest a certain function (here RS or RC) name and info_type should match.

curl -sG https://peeringdb.com/api/net --data-urlencode name__contains="Route Server" --data-urlencode fields=info_type | jq -r '.data[].info_type' | sort | uniq -c
      2
      9 Non-Profit
     22 Not Disclosed
      7 NSP
    226 Route Server

curl -sG https://peeringdb.com/api/net --data-urlencode name__contains="Route Collector" --data-urlencode fields=info_type | jq -r '.data[].info_type' | sort | uniq -c
      1 Non-Profit
      3 Not Disclosed
      4 Route Server

Having info_type set properly is needed to automagically set the BGP session parameters properly as well.

@peeringdb/pc please vote. And @peeringdb/ac please keep an eye on it.

AC No code change

All 8 comments

+1

+1

+1

Sent from my iPhone

On 13 Jun 2020, at 19:42, Matt Griswold notifications@github.com wrote:


+1

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

What action should we do though? Fix it? Create a task for AC to ping the owner org?

What action should we do though? Fix it? Create a task for AC to ping the owner org?

Yes, this is something we want @peeringdb/ac to do. They have their own queue, but this is only used for on- and de-boarding.

On 17 Jun 2020, at 21:31, Arnold Nipper notifications@github.com wrote:


What action should we do though? Fix it? Create a task for AC to ping the owner org?

I’m ok with both suggestions, but I would suggest to: Create a task for AC to ping org owners.
Yes, this is something we want @peeringdb/ac to do. They have their own queue, but this is only used for on- and de-boarding.

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

  • [ ] @peeringdb/ac to ping the owner org

+1

On Thu, 18 Jun 2020, 00:12 Arnold Nipper notifications@github.com wrote:

>

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peeringdb/peeringdb/issues/747#issuecomment-645653259,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOZM2AICEKKK4U2JD4TVF4DRXE5VJANCNFSM4N5EMYKA
.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gordon-shumway-net picture gordon-shumway-net  Â·  14Comments

netravnen picture netravnen  Â·  14Comments

mcmanuss8 picture mcmanuss8  Â·  11Comments

stillwaxin picture stillwaxin  Â·  10Comments

mwtr picture mwtr  Â·  8Comments