Load opts and config from drivers and handlers

Registered by Antoni Segura Puimedon

Right now, if a driver or a handler want to have options and configuration defined, they must put it in kuryr-kubernetes/config. This is problematic because:

* It prevents or at least makes it awkward for out of tree drivers/handlers to have configuration in kuryr.conf (fuxi-kubernetes being one example of out of tree)
* It pollutes kuryr_kubernetes/config.py with non general options

This blueprint proposes to have the drivers/handlers:

* Have an OPTS class variable list with oslo_cfg StrOpt elements for the options that they need.
* Have a NAME class variable with the name their kuryr.conf subsection should be named after. The name should come as [TYPE/NAME]. For example, for the nested vlan pod_vif driver, it would be [pod_vif/nested_vlan]. Handlers would be [handler/port_pool]

Blueprint information

Status:
Complete
Approver:
Irena Berezovsky
Priority:
Medium
Drafter:
Antoni Segura Puimedon
Direction:
Needs approval
Assignee:
Irena Berezovsky
Definition:
Approved
Series goal:
Accepted for pike
Implementation:
Implemented
Milestone target:
milestone icon pike-3
Started by
Irena Berezovsky
Completed by
Antoni Segura Puimedon

Related branches

Sprints

Whiteboard

seems similar to what is done today for registering opts from kuryr-lib.

It is similar. Here you can see an example:

http://paste.openstack.org/show/602736/
http://paste.openstack.org/show/602737/

Notice the new class variables on the above pastes.

Gerrit topic: https://review.openstack.org/#q,topic:bp/driver-handler-opt-loading,n,z

Addressed by: https://review.openstack.org/450113
    Split nested drivers config options out of generic config.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.