Project Proposals/honeycomb-vpp

From fd.io
< Project Proposals
Revision as of 10:04, 27 October 2016 by Mmarsale (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Name

honeycomb-vpp

Project Contact Name and Email

  • Marek Gradzki, mgradzki@cisco.com
  • Maros Marsalek, mmarsale@cisco.com

Repository Name

honeycomb-vpp

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. 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 than honeycomb project itself

Initially, these parts of honeycomb codebase would be contributed:

These parts will have to 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:
    • To manage VPP core APIs
    • To manage VPP core plugins
    • To manage any other VPP plugins
  • Distribution
    • Primary, but extensible, honeycomb-vpp distribution
  • 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: (place link to email to TSC proposing project, this can be obtained from TSC Archives
    • Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)