[dev] FRR, NVO3, VNC, .. what happens underneath?

[Lou Berger]

Hi,

FRR-VNC enables FRR to be used as a controller for remote forwarders
(e.g., whiteboxes, line cards, OVS, eitc), in NVO3 terms it can act as
an NVA - I think it's also called a Map Server in LISP terminology. 

The VNC code does *not* include a protocol to be used between the
controller (FRR) and the remote forwarding plane - this needs to be
developed/integrated into the code.  We do have a demo quality
integration with openflow.  I've wanted to get it to be a bit more
mature before making it available, but given that this is a low priority
task, I'll see about putting it up on the LabN github repo so others can
play with this.

Lou


On 8/15/2017 8:16 AM, Raymond Burkholder wrote:
> Hello,
>
> I have a network virtualisation scenario, and I think FRR might be a part of it, but I am not sure.
>
> I have taken a look at https://frrouting.org/user-guide/VNC-and-VNC_002dGW.html, and taken a quick skim of the NVO3 stuff.
>
> The NVO3 stuff references a bunch of possibilities.  The FRR site provides command descriptions and a few examples.
>
> The bit missing from the FRR site is what happens underneath?  What is actually used for encapsulation?  How does FRR interact with the encapsulation layer?   There was a one word reference to OpenFlow, but what is the glue that ties FRR, VNC, and the underpinnings together, particularly in a Linux environment?
>
> Are there any presentations, blog entries, black-magic or dark-art places describing example scenarios?  Or is it really just that simple?
>
> An additional search problem is that VNC refers to screen virtualisation, so search parameters become delicate.