(1) Refactor current Gluon code to fit into a Neutron Service Plugin
* Refactor API generator
* Refactor database to resue Neutron's database
(2) Two additional tasks that are also related to Neutron
* optional "network" in Neutron, i.e. when creating a port, it doesn't need to attach to a network
- https://bugs.launchpad.net/neutron/+bug/1664461
* new "network type" attribute
- https://bugs.launchpad.net/neutron/+bug/1664466
(3) Coding to experiment it
(4) Open questions:
* Do we keep current "gluon" repo or create a new repo e.g. "networking-gluon"
- Assume we go "networking-gluon" route for Gluon 2.x (Neutron Service Plugin), and keep "gluon" repo for Gluon 1.x (Extended ML2 Plugin).
* Implement it as "Service Plugin" generator, or just a "Service Plugin"?
- subject to initial experiment
(1) Refactor current Gluon code to fit into a Neutron Service Plugin /bugs.launchpad .net/neutron/ +bug/1664461 /bugs.launchpad .net/neutron/ +bug/1664466
* Refactor API generator
* Refactor database to resue Neutron's database
(2) Two additional tasks that are also related to Neutron
* optional "network" in Neutron, i.e. when creating a port, it doesn't need to attach to a network
- https:/
* new "network type" attribute
- https:/
(3) Coding to experiment it
(4) Open questions:
* Do we keep current "gluon" repo or create a new repo e.g. "networking-gluon"
- Assume we go "networking-gluon" route for Gluon 2.x (Neutron Service Plugin), and keep "gluon" repo for Gluon 1.x (Extended ML2 Plugin).
* Implement it as "Service Plugin" generator, or just a "Service Plugin"?
- subject to initial experiment