Difference between revisions of "Archived-ONE"

From fd.io
Jump to: navigation, search
m
m (Valderrv moved page ONE to Archived-ONE: The project has been archived)
 
(19 intermediate revisions by 3 users not shown)
Line 26: Line 26:
 
* [[IRC | Join fdio-one IRC channel]].
 
* [[IRC | Join fdio-one IRC channel]].
  
−
==Scope==
+
== Start Here ==
−
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.
+
[https://wiki.fd.io/view/Project_Proposals/Overlay_Network_Engine Project Proposal]
  
−
In more detail the scope will include:
+
[[VPP/Setting_Up_Your_Dev_Environment|Set Up Dev Environment]] - Explains how to set up a VPP development environment and the requirements for using the build tools
−
 
+
−
* 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
+
  
 
== Documentation ==
 
== Documentation ==
 +
 +
[[ONE/Termination Review | ONE/Termination Review]]
 +
 
[https://drive.google.com/open?id=0B-8ck2oQS3ByTDNTdElNOEVZbzA ONE-LISP architecture]
 
[https://drive.google.com/open?id=0B-8ck2oQS3ByTDNTdElNOEVZbzA ONE-LISP architecture]
  
−
== Documentation ==
+
[[ONE/Command-line_Interface_CLI_Guide| Command-line Interface (CLI) Guide]]
−
[https://www.youtube.com/watch?v=ULqWiOh1LYc&list=PLWHpG2-3ZXXteDBrVaDhaT9w-58Uu33sK&index=13 Video tutorial: arch walkthrough and demo]
+
 
 +
[[ONE/BI_and_VAT_Guide | Binary Interface and VAT Guide]]
 +
 
 +
[[ONE/Restconf_Lisp_Guide | RESTCONF Guide (WIP)]]
 +
 
 +
== Tutorial ==
 +
[[ONE/Functional_Tests_Guide | Run the ONE functional tests ]]
 +
 
 +
[[ONE/Simple_test_setup | Simple overlay setup for testing]]
 +
 
 +
[[ONE/RTR_setup | Re-encapsulating tunnel router setup]]
 +
 
 +
[https://www.youtube.com/watch?v=ULqWiOh1LYc&list=PLWHpG2-3ZXXteDBrVaDhaT9w-58Uu33sK&index=13 Video tutorial: arch walkthrough, code dive and demo]
 +
 
 
== References ==
 
== References ==
 
*[1] https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe
 
*[1] https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe

Latest revision as of 20:29, 10 November 2020

ONE Facts

Project Lead: Florin Coras
Committers:

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

Overlay Network Engine (ONE) is a VPP project that enables programmable dynamic Software Defined overlays. ONE uses an extended LISP-based map-assisted control plane to dynamically lookup overlay-to-underlay address mappings, as well as forwarding policies, on demand and as packets arrive. This includes policies such as connectivity, encryption, traffic engineering and virtual topologies, access control, and service chaining. The looked up mappings and forwarding policies are cached locally for a TTL period until they time out. The mapping and forwarding policy information is then used to encapsulate overlay packets towards their associated destinations or next hops.

ONE can use and operate a variety of encapsulation formats for the overlay including GRE, VXLAN-GPE (Generic Protocol Extension) [1], which is effectively merging VXLAN and LISP [2] encapsulations in a single format that supports multi-protocol payloads, etc. The control plane can be used to fetch the encapsulation capabilities of a destination as part of its mapping and forwarding policies.

An external open SDN controller will be used as the mapping system to store and provide the mapping and forwarding policies.

Get Involved

Start Here

Project Proposal

Set Up Dev Environment - Explains how to set up a VPP development environment and the requirements for using the build tools

Documentation

ONE/Termination Review

ONE-LISP architecture

Command-line Interface (CLI) Guide

Binary Interface and VAT Guide

RESTCONF Guide (WIP)

Tutorial

Run the ONE functional tests

Simple overlay setup for testing

Re-encapsulating tunnel router setup

Video tutorial: arch walkthrough, code dive and demo

References

Retrieved from "https://wiki.fd.io/index.php?title=Archived-ONE&oldid=10937"