Replace all post_url with Hugo ref blocks
This commit is contained in:
@ -7,11 +7,11 @@ title: 'Review: Compulab Fitlet2'
|
||||
|
||||
A while ago, in June 2021, we were discussing home routers that can keep up with 1G+ internet
|
||||
connections in the [CommunityRack](https://www.communityrack.org) telegram channel. Of course
|
||||
at IPng Networks we are fond of the Supermicro Xeon D1518 [[ref]({% post_url 2021-09-21-vpp-7 %})],
|
||||
at IPng Networks we are fond of the Supermicro Xeon D1518 [[ref]({{< ref "2021-09-21-vpp-7" >}})],
|
||||
which has a bunch of 10Gbit X522 and 1Gbit i350 and i210 intel NICs, but it does come at a certain
|
||||
price.
|
||||
|
||||
For smaller applications, PC Engines APU6 [[ref]({%post_url 2021-07-19-pcengines-apu6 %})] is
|
||||
For smaller applications, PC Engines APU6 [[ref]({{< ref "2021-07-19-pcengines-apu6" >}})] is
|
||||
kind of cool and definitely more affordable. But, in this chat, Patrick offered an alternative,
|
||||
the [[Fitlet2](https://fit-iot.com/web/products/fitlet2/)] which is a small, passively cooled,
|
||||
and expandable IoT-esque machine.
|
||||
@ -82,7 +82,7 @@ For the curious, here's a list of interesting details: [[lspci](/assets/fitlet2/
|
||||
## Preparing the Fitlet2
|
||||
|
||||
First, I grab a USB key and install Debian _Bullseye_ (11.5) on it, using the UEFI installer. After
|
||||
booting, I carry through the instructions on my [[VPP Production]({% post_url 2021-09-21-vpp-7 %})]
|
||||
booting, I carry through the instructions on my [[VPP Production]({{< ref "2021-09-21-vpp-7" >}})]
|
||||
post. Notably, I create the `dataplane` namespace, run an SSH and SNMP agent there, run
|
||||
`isolcpus=1-3` so that I can give three worker threads to VPP, but I start off giving it only one (1)
|
||||
worker thread, because this way I can take a look at what the performance is of a single CPU, before
|
||||
@ -171,8 +171,8 @@ After this exploratory exercise, I have learned enough about the hardware to be
|
||||
Fitlet2 out for a spin. To configure the VPP instance, I turn to
|
||||
[[vppcfg](https://github.com/pimvanpelt/vppcfg)], which can take a YAML configuration file
|
||||
describing the desired VPP configuration, and apply it safely to the running dataplane using the VPP
|
||||
API. I've written a few more posts on how it does that, notably on its [[syntax]({% post_url
|
||||
2022-03-27-vppcfg-1 %})] and its [[planner]({% post_url 2022-04-02-vppcfg-2 %})]. A complete
|
||||
API. I've written a few more posts on how it does that, notably on its [[syntax]({{< ref "2022-03-27-vppcfg-1" >}})]
|
||||
and its [[planner]({{< ref "2022-04-02-vppcfg-2" >}})]. A complete
|
||||
configuration guide on vppcfg can be found
|
||||
[[here](https://github.com/pimvanpelt/vppcfg/blob/main/docs/config-guide.md)].
|
||||
|
||||
|
Reference in New Issue
Block a user