Difference between revisions of "Project Proposals/honeycomb-vpp"
From fd.io
(→Administrata) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Name == | == Name == | ||
| − | honeycomb-vpp | + | hc2vpp (changed from initial honeycomb-vpp) |
== Project Contact Name and Email == | == Project Contact Name and Email == | ||
| Line 12: | Line 12: | ||
== Repository Name == | == Repository Name == | ||
| − | honeycomb-vpp | + | hc2vpp (changed from initial honeycomb-vpp) |
== Description == | == Description == | ||
| − | + | Hc2vpp is building on top of existing, generic Honeycomb infrastructure to build a set of plugins to provide a standalone management agent for VPP. | |
Originally part of Honeycomb codebase, now seeking a dedicated project in order to: | Originally part of Honeycomb codebase, now seeking a dedicated project in order to: | ||
* Separate the VPP specific and Generic parts of Honeycomb | * Separate the VPP specific and Generic parts of Honeycomb | ||
| Line 40: | Line 40: | ||
== Scope == | == Scope == | ||
* Translation code for Honeycomb agent that targets: | * Translation code for Honeycomb agent that targets: | ||
| + | ** VPP core APIs | ||
| + | ** VPP core plugins' APIs | ||
| + | ** any other VPP plugins' APIs | ||
| + | * YANG models for: | ||
** VPP core APIs | ** VPP core APIs | ||
** VPP core plugins' APIs | ** VPP core plugins' APIs | ||
Latest revision as of 09:09, 10 November 2016
Contents
Name
hc2vpp (changed from initial honeycomb-vpp)
Project Contact Name and Email
- Marek Gradzki, mgradzki@cisco.com
- Maros Marsalek, mmarsale@cisco.com
- Hongjun Ni, hongjun.ni@intel.com
- Jan Srnicek, jsrnicek@cisco.com
Repository Name
hc2vpp (changed from initial honeycomb-vpp)
Description
Hc2vpp is building on top of existing, generic Honeycomb infrastructure to build a set of plugins to provide a standalone management agent for VPP. Originally part of Honeycomb codebase, now seeking a dedicated project in order to:
- Separate the VPP specific and Generic parts of Honeycomb
- Leaving Honeycomb project as a generic platform for building management agents
- Enabling the 2 projects to grow and reach maturity at different pace
- Enable easier community involvement
- The honeycomb-vpp project is of bigger value and interest to fd.io community, requiring more participants and possibly different committers with different skills compared to honeycomb project itself
These parts of honeycomb codebase would be extracted:
- https://git.fd.io/cgit/honeycomb/tree/v3po
- https://git.fd.io/cgit/honeycomb/tree/lisp
- https://git.fd.io/cgit/honeycomb/tree/nsh
- https://git.fd.io/cgit/honeycomb/tree/nat
- https://git.fd.io/cgit/honeycomb/tree/packaging
- https://git.fd.io/cgit/honeycomb/tree/vpp-common
- https://git.fd.io/cgit/honeycomb/tree/vpp-integration
These parts would be split:
Approving this project will require scope redefinition for honeycomb project in order to remove VPP related items from it.
Scope
- Translation code for Honeycomb agent that targets:
- VPP core APIs
- VPP core plugins' APIs
- any other VPP plugins' APIs
- YANG models for:
- VPP core APIs
- VPP core plugins' APIs
- any other VPP plugins' APIs
- Distribution
- Primary, honeycomb-vpp distribution extensible with any other translation code no necessarily part of honeycomb-vpp project
- Packaging
- Packaging of honeycomb-vpp for various packaging systems (deb, rpm required)
Initial Committers
- Maros Marsalek, mmarsale@cisco.com
- Marek Gradzki, mgradzki@cisco.com
- Hongjun Ni, hongjun.ni@intel.com
- Jan Srnicek, jsrnicek@cisco.com
- Stefan Kobza, skobza@cisco.com
- Ed Warnicke, hagbard@gmail.com
Vendor Neutral
Meets Board Policy (including IPR, being within Board defined Scope etc)
Meets board policy as expressed in Technical Community Charter and IP Policy
Administrata
- Request for Project proposal consideration
- Email: https://lists.fd.io/pipermail/tsc/2016-October/000290.html
- Date: 10/27/2016
