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

[Lou Berger]

On 8/15/2017 7:20 PM, Raymond Burkholder wrote:
> On 08/15/17 13:30, Lou Berger wrote:
>
>> 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.
> thanx for the info.  I have been looking for mechanisms to control 
> openflow based devices in a distributed manner.  Maybe this might offer 
> some ideas.

I've posted the FRR/VNC+OpenFlow demo code in
https://github.com/LabNConsulting/frr-rfp-ovs-of
note that the code is in a branch and not master.  (There's actually a
branch for each of 2.0, 3.0, and master).  The code implements a simple
learning bridge. One bgpd/NVO3 controller can support N openflow
NVEs/forwarders.  The code has been used with a bunch of different
switch (OS) vendors OpenFlow clients.  MiniNet is typically used for
development and test.

> When you post your code, will it have your current 'test rig', ie 
> configurations used for proving concepts?
not yet, but I'll put something together and add it to the repo.
> Are you using openvswitch for your openflow test engine?  What _do_ you 
> use as a protocol to talk openflow, if VNC does *not* include a protocol?
The code hijacks OVS' openflow implementation and binds it into VNC via
the RFAPI so bgpd can talk openflow.  Definitely a bit of a hack, but
this is *demo* code.

Lou

> Thanx.
>
>> 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.
>>