Subject: RARE user and assistance email list
List archive
- From: mc36 <>
- To: "Moises R. N. Ribeiro" <>
- Cc: Everson Borges <>, edgardcunha <>, "" <>
- Subject: Re: [RARE-users] RENaaS Architecture
- Date: Fri, 5 Aug 2022 06:36:41 +0200
hi,
On 8/5/22 02:36, Moises R. N. Ribeiro wrote:
I hope you're doing fine enjoying your holidays...I have two points that youabsolutely yess, sounds like you're having a plan... just one thing, put the
can return us at your convenience
1) sketches for the RENaaS architecture
We've been trying out ideas on how to organize freeRtr instances. Please find attached two simple diagrams. In principle, I'll try to mimic PoP and backbones. At PoPs (purple instances), the SASE should be play most of security roles whereas backbone instances will do IXP and route diversity.
Note also that part of local the traffic might be diverted at CPE (black) to the regular internet (with basic security being done at the CPE). Traffic headed for the academic/administrative services/applications will follow on the tunnels to reach corresponding cloud or external services, always bearing the IP from the NREN. Evidently, SD-WAN is a candidate for the CPE to PoP interconnection (now shown in the diagram).
For Control&Management (C&M), our plan is to have a separate instance (grey) on each host infrastructure (and perhaps with tunnels mirroring the one in charge of transporting traffic). In principle, that network will transport only C&M traffic. Uh, We've being thinking of enslaving the backbone instances (through the recent backplane functionality you recently made available) to the C&M instances. Does it make sense?
things together before start deploying anything...
just a small hint here, the p4dpdk dataplane recently got a new variance
where it uses the same packet in udp as freerouter does toward the external
world...
it means that you can have a whole topology, including all the external
forwarding properties running fully virtually, with as low overhead as a
single process...
(the first half of the above sentence was already there for a long, but the
second half, _with dataplane_, is quite new...)
to see it in action to have some inspiration, try the following:
wget www.freertr.org/rtr.zip
unzip rtr.zip
cd src
./c.sh
cd ../misc/native
./c.sh
cd ../../src
./tw.sh p4lang-rout001 other p4lang9.ini
Well, this way we could (from the NOC/SOC sitting on our private cloud at UFES) gather monitoring info (through Prometheus) and act on the physical hosting sites as if they were single instances (backbone and C&M) of freeRtr.yeahhh, that one is a real benefit, especially when you use routing protocols:
only a single instance need to be configured....
Yes, we want to find reasons/excuses to show off all features of freeRtr. :-):) tbh i suffer from this too... :)
Any vague suggestion/idea from you, will be music to our ears. And I am surenot that much, it's good as is as a hld for me :)
that hard criticism/correction to our concepts/views will save us a lot of
time. So, please don't hesitate to hit us with your views.
2) Here it is the final version of our paper for the Workshop on testbedswell done! congratulations for the pptx, very lovely slides :)
https://sol.sbc.org.br/index.php/wtestbeds/article/view/20752
<https://sol.sbc.org.br/index.php/wtestbeds/article/view/20752>
Everson has (physically) presented it at the conference in Rio...and he has
used this set of slides:
https://docs.google.com/presentation/d/1IigjhbTjRdT50pVvdlo-BhJJ7pY9Wks7XKMMCFxU0io/edit?usp=sharing <https://docs.google.com/presentation/d/1IigjhbTjRdT50pVvdlo-BhJJ7pY9Wks7XKMMCFxU0io/edit?usp=sharing>
br,
cs
- Re: [RARE-users] RENaaS Architecture, mc36, 08/05/2022
Archive powered by MHonArc 2.6.19.