- A new project proposal vpp
Re: A new project proposal vpp
toggle quoted messageShow quoted text
One thought that occurs to me is that VBD is actually honeycomb/vbd. We may want to consider doing something under the honeycomb/* tree at ODL, especially since we are really talking about mounting and managing Honeycomb Agents. Those agents can certainly manage VPP, but they could also manage other things as well.
In the case of honeycomb/vdb the naming was around virtual bridge domain (VBD)... basically naming it after the global cross node model being translated to the particular per-node models being mounted by netconf. It might be useful to start thinking in that direction. What is the global cross node model we are wanting to map to the models provided by Honeycomb?
On Sun, Jun 18, 2017 at 6:32 PM, Yang, Yi Y <yi.y.yang@...>
Ed, no problem, can you propose a better name?
From: firstname.lastname@example.org [mailto:project-proposals-bounces@...]
On Behalf Of Ed Warnicke
Sent: Saturday, June 17, 2017 1:34 AM
Subject: Re: [Project-proposals] A new project proposal vpp
With my fd.io TSC chair hat on, I would like to formally request that this project *not* be named 'vpp' due to potential for confusion with the
fd.io vpp project.
>On 16/06/17 03:56, Yang, Yi Y wrote:
>> I’d like to propose a new project vpp
>> avoid duplicate efforts for GBP, NetVirt and SFC vpp integration as well
>> as fix multiple applications coexistence for VPP, I send this out per
>> in order that we can incubate it as a formal project in Nitrogen release
>> cycle or Oxygen, please schedule review process in next TSC meeting,
> I would suggest a different name, as it can end up being very confusing
> to talk about components when multiple projects have the same name...
Join email@example.com to automatically receive all group messages.