Marcel Fest
In my free-time I am working for Selfnet e.V. as a volunteer and we bring Internet to students in Stuttgart.
Additionally I try to keep up with my garden.
During working-hours I bring proper networking concepts into the cloud-native world to fullfill the basic needs for Deutsche Telekoms Kubernetes platform called "Das SCHIFF".
For the past years I was also involved in monitoring of network devices with prometheus.
Projects:
* https://github.com/telekom/das-schiff
* https://github.com/telekom/netplanner
* https://github.com/Cellebyte/wichtelit
* https://github.com/Selfnet/prometheus-network-exporter
Contributions:
* https://github.com/STORDIS/monsoon
* https://github.com/telekom/das-schiff-network-operator
Sessions
As anyone else who works with network devices, you always stumble over errors during the planning phase which then cause outages during the execution phase.
Most of the time the errors are not syntax related but semantic errors or environmental impacts because of the configuration change.
Containerlab is versatile and can help you to replicate a testing environment for your needs.
It can integrate also with hypervisors if the network vendor only has virtual images of his network OS.
- containerlab
- podman
- git
Please bring with you a VM with Ubuntu 22.04
Laptops with Proxies and no direct internet access will be problematic.
Some guidance about the lab is available here .
Lab information
When you want to provide telecommunication services to customers you need to provide a good set of functions/services to them. Most commonly those services are IP-based, I mean of cource IP6-based.
These functions are commonly provided by vendors which are pre-selected by long negotiations.
In these, all requirements are marked as fulfilled at the end.
After signing the contracts, the vendors + internal operations teams onboard those functions onto our platform. And this is what we find.
- Kubernetes?
- cloud-native?
- 12-factors?
- do you have arp?
- redundancy?