Replace all post_url with Hugo ref blocks
This commit is contained in:
content
articles
2021-02-27-network.md2021-03-27-coloclue-vpp.md2021-05-26-amsterdam.md2021-05-28-lille.md2021-06-01-paris.md2021-07-03-geneva.md2021-07-26-bucketlist.md2021-08-07-fs-switch.md2021-08-13-vpp-2.md2021-08-15-vpp-3.md2021-08-25-vpp-4.md2021-08-26-fiber7-x.md2021-09-02-vpp-5.md2021-09-21-vpp-7.md2021-10-24-as8298.md2021-11-26-netgate-6100.md2021-12-23-vpp-playground.md2022-02-14-vpp-vlan-gym.md2022-02-21-asr9006.md2022-03-03-syslog-telegram.md2022-03-27-vppcfg-1.md2022-04-02-vppcfg-2.md2022-10-14-lab-1.md2022-11-20-mastodon-1.md2022-11-24-mastodon-2.md2022-11-27-mastodon-3.md2022-12-05-oem-switch-1.md2022-12-09-oem-switch-2.md2023-02-12-fitlet2.md2023-02-24-coloclue-vpp-2.md2023-03-11-mpls-core.md2023-03-17-ipng-frontends.md2023-03-24-lego-dns01.md2023-04-09-vpp-stats.md2023-05-07-vpp-mpls-1.md2023-05-17-vpp-mpls-2.md2023-05-21-vpp-mpls-3.md2023-05-28-vpp-mpls-4.md2023-08-06-pixelfed-1.md2023-08-27-ansible-nginx.md2023-10-21-vpp-ixp-gateway-1.md2023-11-11-mellanox-sn2700.md2023-12-17-defra0-debian.md2024-01-27-vpp-papi.md2024-02-10-vpp-freebsd-1.md2024-02-17-vpp-freebsd-2.md2024-03-06-vpp-babel-1.md2024-04-06-vpp-ospf.md2024-04-27-freeix-1.md2024-05-17-smtp.md2024-05-25-nat64-1.md2024-06-22-vpp-ospf-2.md2024-06-29-coloclue-ipng.md2024-07-05-r86s.md2024-08-03-gowin.md
services.md@ -12,10 +12,10 @@ title: 'Case Study: VPP at Coloclue, part 2'
|
||||
Almost precisely two years ago, in February of 2021, I created a loadtesting environment at
|
||||
[[Coloclue](https://coloclue.net)] to prove that a provider of L2 connectivity between two
|
||||
datacenters in Amsterdam was not incurring jitter or loss on its services -- I wrote up my findings
|
||||
in [[an article]({% post_url 2021-02-27-coloclue-loadtest %})], which demonstrated that the service
|
||||
in [[an article]({{< ref "2021-02-27-coloclue-loadtest" >}})], which demonstrated that the service
|
||||
provider indeed provides a perfect service. One month later, in March 2021, I briefly ran
|
||||
[[VPP](https://fd.io)] on one of the routers at Coloclue, but due to lack of time and a few
|
||||
technical hurdles along the way, I had to roll back [[ref]({% post_url 2021-03-27-coloclue-vpp %})].
|
||||
technical hurdles along the way, I had to roll back [[ref]({{< ref "2021-03-27-coloclue-vpp" >}})].
|
||||
|
||||
## The Problem
|
||||
|
||||
@ -169,7 +169,7 @@ I've now ensured that traffic to and from 185.52.227.1 will always traverse thro
|
||||
I've written about this before, the general _spiel_ is just following my previous article (I'm
|
||||
often very glad to read back my own articles as they serve as pretty good documentation to my
|
||||
forgetful chipmunk-sized brain!), so here, I'll only recap what's already written in
|
||||
[[vpp-7]({% post_url 2021-09-21-vpp-7 %})]:
|
||||
[[vpp-7]({{< ref "2021-09-21-vpp-7" >}})]:
|
||||
|
||||
1. Build VPP with Linux Control Plane
|
||||
1. Bring `eunetworks-2` into maintenance mode, so we can safely tinker with it
|
||||
@ -656,7 +656,7 @@ The performance of the one router we upgraded definitely improved, no question a
|
||||
there's a couple of things that I think we still need to do, so Rogier and I rolled back the change
|
||||
to the previous situation and kernel based routing.
|
||||
|
||||
* We didn't migrate keepalived, although IPng runs this in our DDLN [[colocation]({% post_url 2022-02-24-colo %})]
|
||||
* We didn't migrate keepalived, although IPng runs this in our DDLN [[colocation]({{< ref "2022-02-24-colo" >}})]
|
||||
site, so I'm pretty confident that it will work.
|
||||
* Kees and Ansible at Coloclue will need a few careful changes, to facilitate ongoing automation,
|
||||
think of dataplane and controlplane firewalls, sysctls (uRPF et al), fastnetmon, and so on will
|
||||
|
Reference in New Issue
Block a user