Difference between revisions of "Honeycomb/Releases/1609/Developing Honeycomb Plugins"
From fd.io
< Honeycomb | Releases/1609
(→Developing generic plugins) |
(→Adding existing plugins) |
||
| Line 26: | Line 26: | ||
==== Creating custom agent distribution ==== | ==== Creating custom agent distribution ==== | ||
| − | ==== Adding existing plugins ==== | + | ===== Adding existing plugins to the mix ===== |
==== Verifying agent ==== | ==== Verifying agent ==== | ||
==== Full working example ==== | ==== Full working example ==== | ||
Revision as of 08:15, 2 September 2016
Contents
Honeycomb plugin development tutorial
Honeycomb plugin development guide for 16.09 Honeycomb release.
Developing generic plugins
Since Honeycomb is a generic agent. Any plugin (translation code) can be injected into the framework, creating a custom agent providing RESTCONF/NETCONF northbound interfaces out-of-box.
Developing plugin code
Bootstrapping Honeycomb plugin
Creating custom agent distribution
Adding existing plugins to the mix
Verifying agent
Full working example
Developing plugins for VPP
Honeycomb's primary use case is to provide an agent for VPP. There already are some plugins that provide the translation code for VPP, but there are still APIs that are not covered. In this section, a sample Honeycomb plugin will be created communicating with VPP.
