Difference between revisions of "Gluon"
(→People) |
(→General Task List) |
||
(7 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
== Project Overview == | == Project Overview == | ||
+ | |||
+ | === Use Cases and Requirements === | ||
+ | |||
+ | # [[Gluon/User-Story|New Telco NFV Service and User Story]] | ||
=== Blue Prints === | === Blue Prints === | ||
Line 17: | Line 21: | ||
=== General Task List === | === General Task List === | ||
− | * [[Gluon/Tasks- | + | * [[Gluon/Tasks-Queens|Tasks for Queens and Beyond]] |
− | * Task | + | * Task Archives |
+ | ** [[Gluon/Tasks-Pike|Tasks for Pike and Beyond]] | ||
** [[Gluon/Tasks-Ocata|Tasks for Ocata and Beyond]] | ** [[Gluon/Tasks-Ocata|Tasks for Ocata and Beyond]] | ||
** Here is the [https://etherpad.openstack.org/p/ocata-gluon-work-plan Etherpad of Tasks] from Ocata Design Summit | ** Here is the [https://etherpad.openstack.org/p/ocata-gluon-work-plan Etherpad of Tasks] from Ocata Design Summit | ||
** [[Gluon/PoC-Ocata-Summit|Proof-of-Concept in Ocata Design Summit]], October 24-28, 2016, Barcelona | ** [[Gluon/PoC-Ocata-Summit|Proof-of-Concept in Ocata Design Summit]], October 24-28, 2016, Barcelona | ||
* Historical Task Archive [[Gluon/Tasks| List of General Tasks]] of Gluon development | * Historical Task Archive [[Gluon/Tasks| List of General Tasks]] of Gluon development | ||
+ | |||
+ | == Gluon Releases == | ||
+ | |||
+ | # [https://github.com/openstack/gluon/tree/stable/pike Gluon Pike Release (1.1.0)] | ||
+ | # [https://github.com/openstack/gluon/tree/stable/ocata Gluon Ocata Release (1.0.3)] | ||
== Proof of Concepts == | == Proof of Concepts == | ||
+ | |||
+ | * [[Gluon/PoC-Boston|PoC for OpenStack Summit Boston, May 8-12, 2017]] | ||
== People == | == People == |
Latest revision as of 00:39, 30 August 2017
Gluon is a Model-Driven, Extensible Framework for NFV Networking Service. This framework enables Telecom Service Providers to provide its customers with NFV networking services on-demand. Gluon uses model-driven approach to generate APIs (including objects, database schema, and RESTful API endpoints) from a YAML file which models the NFV Networking Service. When a Telecom Service Provider needs to launch a new service, it only needs to model the new service in a YAML file. Gluon framework generates the APIs accordingly. And then applications can use those APIs to provide the new service. Thus Gluon helps Telecom Service Provide accelerate the time-to-market and achieve business agility through its extensibility and scalability in generating API for new use cases and services.
Contents
Project Overview
Use Cases and Requirements
Blue Prints
- Gluon Nova Plugin
- Gluon API Specification
- Authentication for Proton server endpoints and Role-base Access Control
- Port Service Binding Model
- Integrating Contrail's Mechanism Driver with Gluon's Extended ML2 Plugin
- Supporting Multiple API/Protons (completed)
- Gluon Neutron ML2 Plugin (completed)
- Synchronizing Port Binding in Shim Layer with Proton (completed)
- Gluon Repo Structure (completed)
General Task List
- Tasks for Queens and Beyond
- Task Archives
- Tasks for Pike and Beyond
- Tasks for Ocata and Beyond
- Here is the Etherpad of Tasks from Ocata Design Summit
- Proof-of-Concept in Ocata Design Summit, October 24-28, 2016, Barcelona
- Historical Task Archive List of General Tasks of Gluon development
Gluon Releases
Proof of Concepts
People
- PTL
- Bin Hu (bh526r)
- Feature Drivers
- Contributors
General Resources
- Weekly Team Meeting
- Face-to-Face Meetings
- Team IRC Channel: #openstack-gluon