BGPQ3 argument string granularity

[jlixfeld]

Environment

• Python version: 3.5.3
• Peering Manager version: master

Proposed Functionality

Implement a mechanism that provides BGPQ3 argument strings that can be implemented on a per router, per-IX or per-peer basis.

Use Case

Requirements could be to specify prefix-list or route-filter-list on a per-peer basis. Other requirements could be to set a specific list of IRR server hosts or IRR source lists on a per-IX basis.

External Dependencies

[adamgent]

Right now the OS type shouldn't be relevant to bgpq3 config - peering-manager is using JSON response type from bgpq3 and parsing the response. You get served the prefix object itself when generating the configuration in the Jinja template, so can opt to generate any type of list in the correct format here.

You can globally specify other specifics (IRR source, max/min prefix lengths, other bgp3 command line flags), but to have this per IX would be an enhancement - it definitely makes sense I think with the new BGP Groups feature coming which covers more than just IX peers.

[jlixfeld]

Ah! I had a ; at the end of {{ p.prefix }} in my XR template. Thanks for the clue! I'll reformulate the text in the original issue.