Difference between revisions of "Archived-ONE"
Florin.coras (Talk | contribs) (Created page with "{{Project Facts |name=ONE |shortname=one |jiraName=ONE |committers= * Florin Coras * Lorand Jakab * Vina Ermagan * Alberto Rodriguez }} ==Description== ONE (Overlay Network E...") |
m (Valderrv moved page ONE to Archived-ONE: The project has been archived) |
||
| (33 intermediate revisions by 4 users not shown) | |||
| Line 3: | Line 3: | ||
|shortname=one | |shortname=one | ||
|jiraName=ONE | |jiraName=ONE | ||
| + | |projectLead=[mailto:fcoras@cisco.com Florin Coras] | ||
|committers= | |committers= | ||
| − | * Florin Coras | + | * [mailto:fcoras@cisco.com Florin Coras] |
| − | * Lorand Jakab | + | * [mailto:lojakab@cisco.com Lorand Jakab] |
| − | * Vina Ermagan | + | * [mailto:vermagan@cisco.com Vina Ermagan] |
| − | * Alberto Rodriguez | + | * [mailto:arnatal@ac.upc.edu Alberto Rodriguez Natal] |
| + | |||
}} | }} | ||
==Description== | ==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== | ==Get Involved== | ||
| + | <!-- | ||
* [[ONE/Meeting|Weekly ONE Meeting]]. | * [[ONE/Meeting|Weekly ONE Meeting]]. | ||
| − | * [https://lists.fd.io/mailman3/lists/one-dev.lists.fd.io/ Join the | + | --> |
| + | * [https://lists.fd.io/mailman3/lists/one-dev.lists.fd.io/ Join the ONE Mailing List]. | ||
* [[IRC | Join fdio-one IRC channel]]. | * [[IRC | Join fdio-one IRC channel]]. | ||
| − | == | + | == Start Here == |
| − | Project | + | [https://wiki.fd.io/view/Project_Proposals/Overlay_Network_Engine Project Proposal] |
| + | |||
| + | [[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 | ||
| + | |||
| + | == Documentation == | ||
| + | |||
| + | [[ONE/Termination Review | ONE/Termination Review]] | ||
| + | |||
| + | [https://drive.google.com/open?id=0B-8ck2oQS3ByTDNTdElNOEVZbzA ONE-LISP architecture] | ||
| + | |||
| + | [[ONE/Command-line_Interface_CLI_Guide| Command-line Interface (CLI) Guide]] | ||
| + | |||
| + | [[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 == |
| − | + | *[1] https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe | |
| − | * | + | *[2] https://tools.ietf.org/html/rfc6830 |
| − | + | *[3] https://tools.ietf.org/html/draft-ietf-sfc-nsh | |
| − | * | + | *[4] https://tools.ietf.org/html/draft-ermagan-lisp-nsh |
| − | * | + | |
Latest revision as of 20:29, 10 November 2020
| ONE Facts |
|
Project Lead: Florin Coras Repository: git clone https://gerrit.fd.io/r/one |
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
Set Up Dev Environment - Explains how to set up a VPP development environment and the requirements for using the build tools
Documentation
Command-line Interface (CLI) Guide
Binary Interface and VAT Guide
Tutorial
Simple overlay setup for testing
Re-encapsulating tunnel router setup
Video tutorial: arch walkthrough, code dive and demo
