Website: ix.labitat.dk
We use Ansible to deploy changes, such as adding a new peer to the route server. Please check out ansible directory for further details
Presuming that you already have an ASN and prefixes, do the following:
- Read peering policy
- Join LabiColo, setup machine and prepare routing daemon
- Add your Autonomous System to the
ix_client.ymlfile, and create a pull request with changes. - Poke Hafnium to deploy Ansible playbook
The diagram below provides an overview of data dependencies in the automation tool-chain. Peering members must modify details in the blue boxes themselves, while administrator maintain fuchsia boxes to enrich data outputs. The boxes with white a background are automated outputs. Hugo website is handled in a separate repository.
We've not yet fully implemented the following features:
- Automatic population to website
- Exposing IX-F schema
- Automatic upload of RPSL schema
The route server architecture diagram below illustrates the various data sources used for generating the RS BIRD configuration. have configured ARouteServer to include bogon filters, check peering DB, use RPKI and use the peer config. ARouteServer then creates a Route Server config for BIRD to utilize.
The Grafana dashboard provides a view of the LabIX route server, showing established BGP peers and exported/imported routes. Data source is the Prometheus BIRD exporter. Dashboard will be published soon-ish.
