Load opts and config from drivers and handlers
Right now, if a driver or a handler want to have options and configuration defined, they must put it in kuryr-kubernete
* 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_kubernete
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/
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:
- pike-3
- Started by
- Irena Berezovsky
- Completed by
- Antoni Segura Puimedon
Related branches
Related bugs
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://
http://
Notice the new class variables on the above pastes.
Gerrit topic: https:/
Addressed by: https:/
Split nested drivers config options out of generic config.