Difference between revisions of "Archived-Honeycomb"

From fd.io

Jump to: navigation, search

Revision as of 06:13, 17 August 2018

Honeycomb Facts
Project Lead: Marek Gradzki Committers: Dave Wallace Maros Marsalek Marek Gradzki Ed Warnicke Robert Varga Juraj Sloboda Repository: git clone https://gerrit.fd.io/r/honeycomb Mailing List: honeycomb-dev@lists.fd.io Jenkins: jenkins silo Gerrit Patches: code patches/reviews Bugs: HONEYCOMB bugs

Intro

Honeycomb is a generic NETCONF/RESTCONF java-based management agent and provides a framework for building specialized agents.

It uses many features and utilities from different Opendaylight (ODL) projects (e.g. yangtools, controller, mdsal and netconf). The biggest use case of honeycomb is VPP (fd.io’s Vector packet processor). Honeycomb delivers a management agent to enable integration of VPP with e.g. SDN controllers such as Opendaylight.

For VPP specific distribution of Honeycomb, please refer to hc2vpp project.

Overview

Slides

Honeycomb overview presentation from Paris FD.io 2016 event: File:Honeycomb overview.pptx

Honeycomb 1609 overview update from fd.io Seattle summit 2016: File:HC 1609 overview.pptx

Generic nature

Honeycomb provides a distribution to control VPP. However HC is developed as a generic agent that can be positioned on top of any other software/system etc. that can be controlled from Java(or some other JVM language) code. This is achieved thanks to the modularity of HC enabling any "translation plugin" such as V3PO (VPP core management translation code) to work in HC framework.

Minimal distribution

Honeycomb provides a minimal distribution that contains only:

HC framework jars + plugin jars + dependencies from Opendaylight
HC framework config files + plugin config files
Runnable shell scripts

Project Contact Name and Email

honeycomb-dev list,
Maros Marsalek, LF-ID: mmarsale,
Marek Gradzki, LF-ID: mgradzki,
Ed Warnicke, LF-ID: hagbard,
Dave Wallace, LF-ID: dwallacelf,

Meeting

Honeycomb meeting

Scope

This section is devided into 2 sections: in-scope and out-of-scope to clearly define what is developed as part of Honeycomb project and what will be just reused from other projects (or where Honeycomb relies on other projects).

Honeycomb project scope:

Northbound interfaces:
- Netconf northbound interface
- Restconf northbound interface
- BGP

Translation layer between device management and Yang based data structures

Honeycomb distribution
- Minimal distribution for Honeycomb management agent with all dependencies from ODL and their wiring

Out of scope:

Yang models and translation code for VPP management
- Moved to hc2vpp in 17.01

Vpp-japi
- Java APIs for VPP, allowing JVM to interact with VPP is out of scope of Honeycomb project and is part of the base VPP project

Yang parser
- Available from ODL's yangtools project

Base implementation of northbound interfaces
- Base implementation of generic northbound interfaces is out of scope and will be reused from ODL's netconf project

Yang based data structures and a dedicated DataTree(storage)
- Available from ODL's yangtools and mdsal projects, not necessarily the entire projects, only required parts in binary form.

Integration/performance testing
- Complex integration or performance tests are out of scope of Honeycomb project and are part of CSIT project

Any other application based on top of Honeycomb is out of scope of this project and needs to be hosted in a dedicated project inside or outside of fd.io