OVIL sounds somewhat EVIL :)

Just curious: is "OpenDaylight VPP Interface Layer" too different from "VPP Plugin" proposed by Yi earlier? As a suggestion - if you want to avoid the evil sounding OVIL acronym, yet want to hide the name VPP inside an acronym perhaps you could go with the name OVP (an acronym for "OpenDaylight VPP Plugin").

On Thu, Jul 13, 2017 at 5:56 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Yes, we have a new name OVIL (Opendaylight VPP Interface Layer) for it, Ed agreed with this name J So I think you can start formal creation review thread on the TSC mailing list.

 

Because of name change, I drafted a new page for this, https://wiki.opendaylight.org/view/Project_Proposals:OVIL, you can still use the old one https://wiki.opendaylight.org/view/Project_Proposals:Vpp for convenience.

 

From: Colin Dixon [mailto:colin@...]
Sent: Thursday, July 13, 2017 11:58 PM
To: Ed Warnicke <hagbard@...>

Cc: Yang, Yi Y <yi.y.yang@...>; Robert Varga <nite@...>; Tomas Cechvala -X (tcechval - PANTHEON TECHNOLOGIES at Cisco) <tcechval@...>; project-proposals@...ylight.org
Subject: Re: [Project-proposals] A new project proposal vpp

 

So, assuming the name is fixed, should we start a formal creation review thread on the TSC mailing list?

 

--Colin

 

 

On Mon, Jul 10, 2017 at 6:00 PM, Ed Warnicke <hagbard@...> wrote:

Yi,

 

honeycomb/vbd is named that way :)

 

Ed

 

On Mon, Jul 10, 2017 at 5:26 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Can a project name contain “/”? NetVirt is just one of its consumers, we can’t name it as “netvirt”. Logically honeycombplugin is better, but obviously peope can’t think of vpp from such name J

 

From: Ed Warnicke [mailto:hagbard@...]
Sent: Monday, July 10, 2017 10:50 PM
To: Yang, Yi Y <yi.y.yang@...>
Cc: Colin Dixon <colin@...>; Robert Varga <nite@...>; Tomas Cechvala -X (tcechval - PANTHEON TECHNOLOGIES at Cisco) <tcechval@...>; project-proposals@...ylight.org

Subject: Re: [Project-proposals] A new project proposal vpp

 

Yang,

 

The thing is, its talking to honeycomb, which is talking to vpp, but could also talk to other things as well.  My suggestion would be:

 

honeycomb/netvirt

 

Ed

 

On Fri, Jul 7, 2017 at 4:02 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Ed, can you propose a better name for it? How about vppplugin?

 

From: Ed Warnicke [mailto:hagbard@...]
Sent: Friday, July 7, 2017 11:24 PM
To: Colin Dixon <colin@...>
Cc: Yang, Yi Y <yi.y.yang@...>; Robert Varga <nite@...>; Tomas Cechvala -X (tcechval - PANTHEON TECHNOLOGIES at Cisco) <tcechval@...>; project-proposals@...ylight.org

Subject: Re: [Project-proposals] A new project proposal vpp

 

Has the proposed project name and repo been changed to something other than 'vpp' ?

 

Ed

 

 

On Fri, Jul 7, 2017 at 8:22 AM, Colin Dixon <colin@...> wrote:

The next APAC-friendly TSC call is scheduled for July 27th. If you're willing to wait until then, that call is at 11:30a Beijing time. Otherwise, we can have the creation review happen over e-mail if it needs to be sooner. Changing the TSC schedule is... more complicated.

 

--Colin

 

On Thu, Jun 29, 2017 at 8:35 PM Yang, Yi Y <yi.y.yang@...> wrote:

Thanks Colin, good summary, I discussed it with Tomas and Ed privately, I think they have well understood why we need this project. it seems weekly TSC meeting time is Beijing Time 1:00 AM, can you schedule next meeting to Beijing Time 7:00 AM or 10:00 PM in order that I can join?

 

From: Colin Dixon [mailto:colin@...]
Sent: Thursday, June 29, 2017 10:35 PM
To: Yang, Yi Y <yi.y.yang@...>
Cc: Robert Varga <nite@...>; Ed Warnicke <hagbard@...>; project-proposals@...ylight.org

Subject: Re: [Project-proposals] A new project proposal vpp

 

So, it sounds to me like the project proposal wanted to try to factor out the common elements of how SFC, NetVirt, and GBP would talk to VPP to do service chaining int one place so that (a) the code could be shared and (b) we could reuse some of the work that GBP has done. However, the tone of this thread makes it pretty clear that (i) GBP isn't really interested in the shared code and (ii) is pretty opposed to the idea of their code being used as the base even if it's a separate copy.

 

Give that, it seems like the right path forward is for SFC and NetVirt to decide if they still want to have a shared code bas for how they interact with VPP and if that should be a new project.

 

I'll let that discussion keep going here and tentative schedule a creation review for next week—July 6th:

https://wiki.opendaylight.org/view/TSC:Main#Intended_Topics_for_Coming_Weeks

 

Cheers,

--Colin

 

 

On Thu, Jun 22, 2017 at 8:02 PM, Yang, Yi Y <yi.y.yang@...> wrote:

Hi, Robert

vpp data store isn't mirror of data store in honeycomb/vpp node, they are some intermediate data, vpp renderer and classifier will renderer them to real vpp data in honeycomb/vpp node, I'll work out a PoC to show you what it looks like.

we hope GBP guys can agree this, if you check Srikanthi's PoC and RPCs GBP vpp renderer provided, you can assume the vpp data store is just to save those parameters for those RPCs, for classifier, NetVirt defined its own classifier, GBP defined its own classifier, SFC defined its own classifier, we hope they can have common classifier then augment it by itself, all the projects should use IETF ACLs and IETF interfaces, if so, the vpp data store can share these data in ODL.


-----Original Message-----
From: Robert Varga [mailto:nite@...]
Sent: Thursday, June 22, 2017 11:52 PM
To: Ed Warnicke <hagbard@...>; Yang, Yi Y <yi.y.yang@...>
Cc: project-proposals@...ylight.org
Subject: Re: [Project-proposals] A new project proposal vpp

On 20/06/17 15:39, Ed Warnicke wrote:
> On Tue, Jun 20, 2017 at 4:25 AM, Yang, Yi Y <yi.y.yang@...
> <mailto:yi.y.yang@...>> wrote:
>
>     For vpp renderer, it needs to render bridge domain information
>     (neutron network, including VNI) and interfaces to bridge domain,
>     vxlan, vxlan-gpe, vhostuser etc in vpp node, you know information
>     model on ODL side is different from information model on VPP node
>     side, especially for sfc, vpp renderer will also render RSP to
>     bridge domain, vxlan-gpe, NSH entry and NSH map in every vpp node
>     RSP spans. sfc vpp renderer is much more complicated than NetVirt
>     needs, so we can use the existing code in sfc vpp renderer to
>     achieve a vpp renderer NetVirt needs very easily.
>
>
>
> I'm still not clear on what models are being rendered to what models.
> The SFC renderer renders the SFC models to the models being mounted
> via netconf.  It sounds like the *to* side of rendering is the models
> mounted via netconf.  What precisely are the *from* models?  Are we
> writing new models in this project for bridge domains, vxlan,
> vxlan-gpe, etc.  It also sounds like you are taking a small fragment
> of the SFC model and creating a new model for a bunch of virtual
> bridging concepts (similar to what is done in VBD).  Are there
> existing models being rendered to the netconf mounted models?

I tend to agree with Ed's point. I am probably missing something, as I am not too fluent in SFC/GBP information models nor how they align with NetVirt's view of the world.

I think we have multiple input models (SFC, netvirt, GBP) being rendered onto a target device (which happens to be VPP, but it's really about models).

What would be the models for "VPP data store"? Is this a mirror of the SB device's model and are we talking about the proposed project performing the equivalent of FRM?

I am sorry, but it is extremely hard to distill scope from the proposal in its current form. I think it needs to be beefed up with details of interactions and needs to be vetted by all of GBP, SFC and NetVirt to make sure the proposal actually fits the use case.

Furthermore it would be very beneficial to understand how this plays with netconf topology -- as I mentioned "VPP node" is in reality any SB device implementing a specific set of models (either directly or through an adaptor).

Regards,
Robert

_______________________________________________
project-proposals mailing list
project-proposals@...ylight.org
https://lists.opendaylight.org/mailman/listinfo/project-proposals

 

 

 

 

 

_______________________________________________
project-proposals mailing list
project-proposals@...ylight.org
https://lists.opendaylight.org/mailman/listinfo/project-proposals

_______________________________________________
project-proposals mailing list
project-proposals@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/project-proposals