Difference between revisions of "Archived-ONE"

From fd.io
Jump to: navigation, search
(Documentation)
m (Valderrv moved page ONE to Archived-ONE: The project has been archived)
 
(4 intermediate revisions by 2 users not shown)
Line 32: Line 32:
  
 
== 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]
  
Line 38: Line 41:
 
[[ONE/BI_and_VAT_Guide | Binary Interface and VAT Guide]]
 
[[ONE/BI_and_VAT_Guide | Binary Interface and VAT Guide]]
  
[[ONE/Restconf_Lisp_Guide | RESTCONF LISP Guide]]
+
[[ONE/Restconf_Lisp_Guide | RESTCONF Guide (WIP)]]
  
 
== Tutorial ==
 
== Tutorial ==
 +
[[ONE/Functional_Tests_Guide | Run the ONE functional tests ]]
 +
 
[[ONE/Simple_test_setup | Simple overlay setup for testing]]
 
[[ONE/Simple_test_setup | Simple overlay setup for testing]]
  

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