Difference between revisions of "Project Proposals/honeycomb-vpp"

From fd.io
Jump to: navigation, search
(Created page with "Category:Project Proposal <!-- Please note: fd.io code is to be licensed under the Apache 2.0 license unless an exception is approved by the board --> == Name == <!-- The...")
 
 
(7 intermediate revisions by the same user not shown)
Line 3: Line 3:
  
 
== Name ==
 
== Name ==
−
<!-- The name of your project, for example Honeycomb BridgeDomain or NSH Advanced Features etc. -->
+
hc2vpp (changed from initial honeycomb-vpp)
−
honeycomb-vpp
+
  
 
== Project Contact Name and Email ==
 
== Project Contact Name and Email ==
−
<!-- Name and email of the project contact -->
 
 
* Marek Gradzki, mgradzki@cisco.com
 
* Marek Gradzki, mgradzki@cisco.com
 
* Maros Marsalek, mmarsale@cisco.com
 
* Maros Marsalek, mmarsale@cisco.com
 +
* Hongjun Ni, hongjun.ni@intel.com
 +
* Jan Srnicek, jsrnicek@cisco.com
  
 
== Repository Name ==
 
== Repository Name ==
−
honeycomb-vpp
+
hc2vpp (changed from initial honeycomb-vpp)
  
 
== Description ==
 
== Description ==
−
Honeycomb-vpp is building on top of existing, generic Honeycomb infrastructure to build a set of plugins to provide a standalone management agent for VPP.
+
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 21: Line 21:
 
** Enabling the 2 projects to grow and reach maturity at different pace
 
** Enabling the 2 projects to grow and reach maturity at different pace
 
* Enable easier community involvement
 
* 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 than honeycomb project itself
+
** 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
  
−
Initially, these parts of honeycomb codebase would be contributed:
+
These parts of honeycomb codebase would be extracted:
 
* https://git.fd.io/cgit/honeycomb/tree/v3po
 
* https://git.fd.io/cgit/honeycomb/tree/v3po
 
* https://git.fd.io/cgit/honeycomb/tree/lisp
 
* https://git.fd.io/cgit/honeycomb/tree/lisp
Line 32: Line 32:
 
* https://git.fd.io/cgit/honeycomb/tree/vpp-integration
 
* https://git.fd.io/cgit/honeycomb/tree/vpp-integration
  
−
These parts will have to be split:
+
These parts would be split:
 
* https://git.fd.io/cgit/honeycomb/tree/samples
 
* https://git.fd.io/cgit/honeycomb/tree/samples
 
* https://git.fd.io/cgit/honeycomb/tree/release-notes
 
* https://git.fd.io/cgit/honeycomb/tree/release-notes
Line 39: Line 39:
  
 
== Scope ==
 
== Scope ==
−
<!-- Project scope.  The project scope should be well defined.  It should be possible from the scope to crisply answer whether something belongs or not within the scope of this particular project.  Scopes should not be overly broad.  A Project scope must also lie within the overall scope set by the board for projects in fd.io:
+
* Translation code for Honeycomb agent that targets:
−
    - IO
+
** VPP core APIs
−
        – Hardware/vHardware <-> threads/cores
+
** VPP core plugins' APIs
−
    - Processing
+
** any other VPP plugins' APIs
−
        - Classify
+
* YANG models for:
−
        - Transform
+
** VPP core APIs
−
        - Prioritize
+
** VPP core plugins' APIs
−
        - Forward
+
** any other VPP plugins' APIs
−
        - Terminate
+
−
    - Management Agents
+
−
        - Control/Manage IO/Processing
+
−
    - Supporting Projects
+
−
        - Testing/Tools/Infrastructure
+
−
        - Integration with other systems
+
−
-->
+
−
* Translation code for Honeycomb agent:
+
−
** To manage VPP core APIs
+
−
** To manage VPP core plugins
+
−
** To manage any other VPP plugins
+
 
* Distribution
 
* Distribution
−
** Primary, but extensible, honeycomb-vpp distribution
+
** Primary, honeycomb-vpp distribution extensible with any other translation code no necessarily part of honeycomb-vpp project
 
* Packaging
 
* Packaging
 
** Packaging of honeycomb-vpp for various packaging systems (deb, rpm required)
 
** Packaging of honeycomb-vpp for various packaging systems (deb, rpm required)
Line 95: Line 84:
 
== Administrata ==
 
== Administrata ==
 
* Request for Project proposal consideration
 
* Request for Project proposal consideration
−
** Email: (place link to email to TSC proposing project, this can be obtained from [https://lists.fd.io/pipermail/tsc/ TSC Archives]
+
** Email: https://lists.fd.io/pipermail/tsc/2016-October/000290.html
−
** Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)
+
** Date: 10/27/2016

Latest revision as of 09:09, 10 November 2016


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:

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

Retrieved from "https://wiki.fd.io/index.php?title=Project_Proposals/honeycomb-vpp&oldid=3739"