Difference between revisions of "Gluon/PoC-Boston"
< Gluon
(→PoC Scope and Scenario Description) |
(→PoC Scope and Scenario Description) |
||
| Line 8: | Line 8: | ||
The PoC Scenario includes: | The PoC Scenario includes: | ||
| − | * | + | * Four YAMLs and Protons/APIs: L3VPN, SFC, P2P and ELAN |
| − | ** Write | + | ** Write 4 YAMLs for L3VPN, SFC, P2P and ELAN service models respectively |
| − | ** Use Particle Generator to generate | + | ** Use Particle Generator to generate 4 Protons / 4 sets of APIs respectively |
** ''NO CODE'' is needed to implement those APIs on SDN Controllers, except those already supported. | ** ''NO CODE'' is needed to implement those APIs on SDN Controllers, except those already supported. | ||
* Showing: | * Showing: | ||
| − | ** | + | ** 4 YAMLs and generated 3 Protons |
** Related presentation/explanation | ** Related presentation/explanation | ||
* Then demonstrate a fun use case for interoperability of multiple SDN controllers using L3VPN Proton API | * Then demonstrate a fun use case for interoperability of multiple SDN controllers using L3VPN Proton API | ||
Revision as of 03:44, 29 March 2017
PoC for OpenStack Summit Boston, May 8-12, 2017
Contents
PoC Scope and Scenario Description
The goal of the PoC is to showcase Gluon and Proton, and demonstrate the unique value of Gluon to enable quick development and deployment of new networking service APIs. The business value proposition includes:
- Accelerated time-to-market
- Improved business agility
The PoC Scenario includes:
- Four YAMLs and Protons/APIs: L3VPN, SFC, P2P and ELAN
- Write 4 YAMLs for L3VPN, SFC, P2P and ELAN service models respectively
- Use Particle Generator to generate 4 Protons / 4 sets of APIs respectively
- NO CODE is needed to implement those APIs on SDN Controllers, except those already supported.
- Showing:
- 4 YAMLs and generated 3 Protons
- Related presentation/explanation
- Then demonstrate a fun use case for interoperability of multiple SDN controllers using L3VPN Proton API
- MINIMUM CODE is needed to automate passing RT and RD parameters via L3VPN Proton API
- BGP peering among those SDN controllers
- Contrail may need a separate setup because their BGPVPN support is via Monolithic Plugin instead of ML2 Mechanism Driver for Gluon.
The PoC is NOT interested in how the packets are flowed / data path (which is out of scope of Gluon)
Lab Status
- OPNFV Pharos Lab in Germany
- Huawei Lab in Santa Clara
OpenContrail Status
L3VPN YAML and API
- Parameter List for BGP Peering
