Difference between revisions of "Gluon/Tasks-Queens"
< Gluon
(→Gluon Framework) |
(→Gluon Neutron Service Plugin) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 9: | Line 9: | ||
| Refactor Gluon Extended ML2 Plugin into Neutron Service Plugin | | Refactor Gluon Extended ML2 Plugin into Neutron Service Plugin | ||
|| TBD | || TBD | ||
− | || TBD || See "Gluon Neutron Service Plugin" section || || | + | || TBD || See "Gluon Neutron Service Plugin" section || || https://bugs.launchpad.net/neutron/+bug/1716489 |
|- | |- | ||
| Fix hard-coded way of creating default interface when creating a port in gluon/managers/manager_base.py. See Line 113 TO-DO. It should be fixed to support all YAML models | | Fix hard-coded way of creating default interface when creating a port in gluon/managers/manager_base.py. See Line 113 TO-DO. It should be fixed to support all YAML models | ||
Line 73: | Line 73: | ||
|| TBD || || || https://bugs.launchpad.net/neutron/+bug/1664466 | || TBD || || || https://bugs.launchpad.net/neutron/+bug/1664466 | ||
|- | |- | ||
− | | Database Migration (from SQLLite to Neutron's Database) | + | | Study exemplary code of existing service plugin, e.g. networking-bgpvpn, to understand all necessary steps and tasks for implementing a service plugin |
+ | || TBD | ||
+ | || TBD || || || | ||
+ | |- | ||
+ | | Address open question - how to get a service plugin to require an API file and minimal extra code when implemented on the gluon framework? Preference is to make 'gluon' a library for implementing service plugins. | ||
+ | || TBD | ||
+ | || TBD || || || | ||
+ | |- | ||
+ | | Refactor API Generator | ||
+ | || TBD | ||
+ | || TBD || || || | ||
+ | |- | ||
+ | | Database Migration (from SQLLite to Neutron's Database) - this means that the tables are added to the Neutron DB space as service plugins would do, potentially with relationship to Neutron's own objects, but would still come from our API description | ||
|| TBD | || TBD | ||
|| TBD || || || https://jira.opnfv.org/browse/NETREADY-26 and https://jira.opnfv.org/browse/NETREADY-51 | || TBD || || || https://jira.opnfv.org/browse/NETREADY-26 and https://jira.opnfv.org/browse/NETREADY-51 | ||
Line 80: | Line 92: | ||
|| TBD | || TBD | ||
|| TBD || || || | || TBD || || || | ||
+ | |} |
Latest revision as of 14:48, 12 September 2017
Contents
Tasks for Queens and Beyond
Gluon Framework
Task | Resources | Release | Status | Blueprint | JIRA |
---|---|---|---|---|---|
Refactor Gluon Extended ML2 Plugin into Neutron Service Plugin | TBD | TBD | See "Gluon Neutron Service Plugin" section | https://bugs.launchpad.net/neutron/+bug/1716489 | |
Fix hard-coded way of creating default interface when creating a port in gluon/managers/manager_base.py. See Line 113 TO-DO. It should be fixed to support all YAML models | Jin L | Queens | |||
Fix hard-coded way in gluon/backends/backend_base.py, and perhaps other files so that it can parse and support all YAML models at backend, like API generator. | Jin L | Queens | |||
Investigate and fix the missing "version-id" in "process_message", Line 64 of gluon/shim/main.py, for processing in Shim Layer. | TBD | Queens | |||
Fix the CLI "protonclient" known bug as documented in doc/source/usage.rst. | TBD | Queens | |||
Use of “etcd” approved by infrastructure team, including (1) upgrade from etcd-v2.3.6 to etcd3 (2) reuse etcd3 that is started when starting devstack (3) alignment with global requirements of infrastructure packages (i.e. python-etcd>=0.4.3, click>=6.6) | TBD | Queens | https://jira.opnfv.org/browse/NETREADY-49 | ||
Documentation Update: Developer Guide, Installation Guide and User Guide for Queens Release | Bin H | Queens | https://jira.opnfv.org/browse/NETREADY- | ||
Investigate and resolve synchronization issues sync between MySQL and etcd | TBD | TBD | On hold | https://jira.opnfv.org/browse/NETREADY-45 | |
Synchronize bind operation with SDN controllers (e.g. (1) when SDNC “bind” fails; (2) ensure that “bind” succeeds before VM is spawned; (3) synchronize “bind” with “port_update” response; (4) push binding information to Proton) | TBD | TBD | On hold | https://jira.opnfv.org/browse/NETREADY-46 | |
DevStack Integration (e.g. install etcd, database integration etc.) | TBD | TBD | On hold | https://jira.opnfv.org/browse/NETREADY-52 |
Proton Model
Task | Resources | Release | Status | Blueprint | JIRA |
---|---|---|---|---|---|
Sync thread needs to be updated to use log table to support Proton HA | TBD | TBD | On Hold | https://jira.opnfv.org/browse/NETREADY-55 |
Gluon Neutron Service Plugin
Task | Resources | Release | Status | Blueprint | JIRA |
---|---|---|---|---|---|
Removal of “port” dependency on “network/subnet” in Neutron. Refer to RFE "Neutron API enhancement - make network and subnets as optional" (https://bugs.launchpad.net/neutron/+bug/1664461) | Ian W and Sukhdev K | TBD | https://bugs.launchpad.net/neutron/+bug/1664461 | ||
Network “type” attribute in Neutron. Refer to RFE "Neutron API enhancement - add optional attribute to network" (https://bugs.launchpad.net/neutron/+bug/1664466) | Ian W and Sukhdev K | TBD | https://bugs.launchpad.net/neutron/+bug/1664466 | ||
Study exemplary code of existing service plugin, e.g. networking-bgpvpn, to understand all necessary steps and tasks for implementing a service plugin | TBD | TBD | |||
Address open question - how to get a service plugin to require an API file and minimal extra code when implemented on the gluon framework? Preference is to make 'gluon' a library for implementing service plugins. | TBD | TBD | |||
Refactor API Generator | TBD | TBD | |||
Database Migration (from SQLLite to Neutron's Database) - this means that the tables are added to the Neutron DB space as service plugins would do, potentially with relationship to Neutron's own objects, but would still come from our API description | TBD | TBD | https://jira.opnfv.org/browse/NETREADY-26 and https://jira.opnfv.org/browse/NETREADY-51 | ||
Other tasks as identified when refactoring Gluon as Neutron Service Plugin | TBD | TBD |