gluon/doc/source/devref/task_list.rst

Gluon Task List

For Infrastructure and Repository

1. Set up cloud infrastructure with 5 blade servers in Ericsson's new data center
2. Create repos based on new architecture
   1. For now, we need to consolidate everything back int one repo
3. The requirements.txt files needs to be updated and aligned with the Global Requirements

For Proof-of-Concept in Barcelona

1. Setup system with base linux bridge networking
2. Use separate SDN-C for each host to support gluon networking
3. Implement Gluon Neutron ML2 Plugin

For Neutron Gluon ML2 Plugin

1. Investigate using subclass of Neutron Core plugin to direct bind/unbind operations to Gluon/Proton

For Enhancements of Gluon Implementation

1. Investigate how different VIF drivers can be used for different port types on the same hypervisor
   1. Need to understand VIF plugging and how it affects Gluon
   2. Generic VIF driver may be okay for most use cases
2. Investigate and resolve synchronization issues in the gluon/proton architecture
   1. Need to re-sync proton with gluon upon restart
      1. This is partially done
   2. Synchronization of mysql and etcd databases needs to be investigated
      1. Are we covered if Proton restarts or etcd is unavailable for a period of time?
3. Synchronize bind operation with SDN controller
   1. There is no feedback if the SDN bind fails
   2. Need to make sure bind is done before VM is spawned. Synchronize bind with port_update response
   3. Binding information needs to be pushed back to Proton
      1. Should Proton just read this from etcd?
4. Rebuild Gluon to not use particle generator

For Enhancements of Proton API Model

1. Fix VPNAFConfig in L3VPN Model (only one reference currently)
2. The API modeling approach needs to be cleaned up
   1. Need a baseport that is common to all APIs
      1. Right now each new API should need to copy/paste baseport object
   2. Binding information needs be be modeled consistently
      1. Separate table or part of baseport?
      2. Or, just resides in etcd?
   3. IP Addressing information should be modeled with a separate table
      1. IPAM is broken with current model.
      2. It is possible to assign IP address that cannot be supported because of SDN-C/Host mapping
3. Proton needs to be reworked to support multiple APIs
4. Create a cookiecutter (or script) to create a new API within the Proton source tree
5. Sync thread needs to be updated to use log table to support Proton HA
6. The Particle Generator only supports flat APIs at this time.
   1. Support for hierarchical APIs was started but not completed.
7. Need consistent way of handling empty/unset fields in the API

For Proton Database Migration

1. Modify Proton code to use MySQL (currently only using sqlite)
2. Need a strategy to handle database migrations if the API model is changed

For Testing

1. We need to add unit, functional, and tempest testing

For Installer Support (Devstack and Fuel)

1. Need to update devstack code to install Gluon
   1. Install etcd.
   2. Setup database
2. Create Fuel plugin to install Gluon

For Keystone Integration

1. Need to hook in keystone authorization to access API (wide open now)