Jump to: navigation, search

Difference between revisions of "Gluon/Tasks-Queens"

(Gluon Framework)
(Gluon Neutron Service Plugin)
 
(19 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
|| TBD
+
|| Jin L
 
|| Queens || ||  ||
 
|| Queens || ||  ||
 
|-
 
|-
| Investigate and resolve synchronization issues sync between MySQL and etcd
+
| 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.
|| Ian W and Sukhdev K
+
|| Jin L
|| Pike || On hold ||  || https://jira.opnfv.org/browse/NETREADY-45
+
|| Queens || ||  ||
 
|-
 
|-
| 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)
+
| Investigate and fix the missing "version-id" in "process_message", Line 64 of gluon/shim/main.py, for processing in Shim Layer.
|| Ian W and Sukhdev K
+
|| TBD
|| Pike || On hold ||  || https://jira.opnfv.org/browse/NETREADY-46
+
|| Queens || ||  ||
 
|-
 
|-
| DevStack Integration (e.g. install etcd, database integration etc.)
+
| Fix the CLI "protonclient" known bug as documented in doc/source/usage.rst.
|| Ian W
+
|| TBD
|| Pike || On hold ||  || https://jira.opnfv.org/browse/NETREADY-52
+
|| Queens || ||  ||
 
|-
 
|-
| Fuel Integration (e.g. create Fuel plugin to install Gluon)
+
| 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)
|| Szilard C
+
|| TBD
|| Pike || On hold ||  || https://jira.opnfv.org/browse/NETREADY-
+
|| Queens || ||  || https://jira.opnfv.org/browse/NETREADY-49
 
|-
 
|-
| Documentation Update: Developer Guide (API Specification, Version Management and RBAC), Installation Guide and User Guide for Queens Release
+
| Documentation Update: Developer Guide, Installation Guide and User Guide for Queens Release
 
|| Bin H
 
|| Bin H
 
|| Queens ||  ||  || https://jira.opnfv.org/browse/NETREADY-
 
|| Queens ||  ||  || https://jira.opnfv.org/browse/NETREADY-
 
|-
 
|-
| Use of “etcd” approved by infrastructure team (e.g. aligned with global requirements of infrastructure packages) (i.e. python-etcd>=0.4.3, click>=6.6)
+
| Investigate and resolve synchronization issues sync between MySQL and etcd
|| Ian W
+
|| TBD
|| TBD || On hold ||  || https://jira.opnfv.org/browse/NETREADY-49
+
|| 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
 
|-
 
|-
| Database Migration (from SQLLite to MySQL)
+
| DevStack Integration (e.g. install etcd, database integration etc.)
|| Niko H
+
|| TBD
|| TBD || On Hold ||  || https://jira.opnfv.org/browse/NETREADY-26 and https://jira.opnfv.org/browse/NETREADY-51
+
|| TBD || On hold ||  || https://jira.opnfv.org/browse/NETREADY-52
 
|}
 
|}
  
Line 49: Line 53:
 
|-
 
|-
 
! Task !! Resources !! Release !! Status !! Blueprint !! JIRA
 
! Task !! Resources !! Release !! Status !! Blueprint !! JIRA
|-
 
| Create a cookiecutter (or script) to create a new API within the Proton source tree
 
||
 
|| Pike || On Hold ||  || https://jira.opnfv.org/browse/NETREADY-54
 
 
|-
 
|-
 
| Sync thread needs to be updated to use log table to support Proton HA
 
| Sync thread needs to be updated to use log table to support Proton HA
||  
+
|| TBD
|| Pike || On Hold ||  || https://jira.opnfv.org/browse/NETREADY-55
+
|| TBD || On Hold ||  || https://jira.opnfv.org/browse/NETREADY-55
 
|}
 
|}
  
=== Nova and Neutron Related ===
+
=== Gluon Neutron Service Plugin ===
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 65: Line 65:
 
! Task !! Resources !! Release !! Status !! Blueprint !! JIRA
 
! Task !! Resources !! Release !! Status !! Blueprint !! JIRA
 
|-
 
|-
| Removal of “port” dependency on “network/subnet” '''Nova''' part (https://review.openstack.org/#/c/390513/)
+
| 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
+
|| Ian W and Sukhdev K
|| Pike/Queens || On Hold (Shift to Neutron) || [https://blueprints.launchpad.net/python-gluon/+spec/gluon-nova-plugin gluon-nova-plugin] || https://jira.opnfv.org/browse/NETREADY-
+
|| 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 || ||  ||
 
|-
 
|-
| IPAM (i.e. defer IP address assignment until “port-bind-to-VM” instead of port creation time after VM is landed on specific hypervisor) – '''Nova''' part (https://review.openstack.org/#/c/390511/) – to verify https://github.com/openstack/nova/commit/54b8d7770ac7ba0ab49417ceacf82ebc708a3b3b
+
| 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.  
|| Ian W
+
|| TBD
|| Pike/Queens || Completed || [https://blueprints.launchpad.net/python-gluon/+spec/gluon-nova-plugin gluon-nova-plugin] || https://jira.opnfv.org/browse/NETREADY-
+
|| TBD || || ||
 
|-
 
|-
| Removal of “port” dependency on “network/subnet” – '''Neutron''' part
+
| Refactor API Generator
|| Ian W and Sukhdev K
+
|| TBD
|| Pike/Queens || On hold (Shift to Neutron) ||  || https://jira.opnfv.org/browse/NETREADY-
+
|| TBD || ||  ||
 
|-
 
|-
| IPAM (i.e. defer IP address assignment until “port-bind-to-VM” instead of port creation time after VM is landed on specific hypervisor) – '''Neutron''' part
+
| 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
|| Ian W
+
|| TBD
|| Pike/Queens || Completed ||  || https://jira.opnfv.org/browse/NETREADY-
+
|| TBD || ||  || https://jira.opnfv.org/browse/NETREADY-26 and https://jira.opnfv.org/browse/NETREADY-51
 
|-
 
|-
| Network “type” attribute in '''Neutron'''
+
| Other tasks as identified when refactoring Gluon as Neutron Service Plugin
|| Ian W and Sukhdev K
+
|| TBD
|| Pike/Queens || On hold (Shift to Neutron) ||  || https://jira.opnfv.org/browse/NETREADY-
+
|| TBD || ||  ||
 
|}
 
|}

Latest revision as of 14:48, 12 September 2017

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