Archived-ONE

From fd.io
Revision as of 12:04, 31 March 2016 by Florin.coras (Talk | contribs)

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

Project Lead: {{{projectLead}}}
Committers:

  • Florin Coras
  • Lorand Jakab
  • Vina Ermagan
  • Alberto Rodriguez

Repository: git clone https://gerrit.fd.io/r/one
Mailing List: one-dev@lists.fd.io
Jenkins: jenkins silo
Gerrit Patches: code patches/reviews
Bugs: ONE bugs

Description

ONE (Overlay Network Engine) project is focusing on:

  1. first
  2. second

Get Involved

Scope

Project scope includes implementation of nodes that enable dynamic encapsulation and de-capsulation of data packets using different encapsulation formats, the map cache, and the LISP control plane for retrieval and update of the mapping and forwarding policies. The scope also includes integration with other components within VPP such as IPSec for encryption and NSH.

In more detail the scope will include:

  • Implementation of plugins/graph nodes to allow dynamic lookup and retrieval of mappings of network traffic to encapsulations for next hops (various encaps are supported and mapping system can determine the encap to use.) Various network traffic can be mapped, including L2, L3, NSH,...
  • Implementation of plugins/graph nodes to store/cache the retrieved mappings locally
  • Implementation of plugins/graph nodes to carry out/apply the mappings for existing flows (match and encap)
  • Implementation of plugins/graph nodes to allow integration with other components including IPSec for encryption and NSH for service chaining
  • Exporting APIs over NETCONF - using Honeycomb or other means defined by fd.io
  • Supporting tools, testing