Add a Stevedore entrypoint for Dragonflow applications
Bug #1702462 reported by
Omer Anson
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DragonFlow |
Fix Released
|
Undecided
|
Dima Kuznetsov | ||
Bug Description
In order to facilitate writing 3rd party Dragonflow applications, a stevedore[1] entrypoint should be used. This will allow out-of-tree applications to be loaded and used.
Existing Dragonflow applications should also be loaded using this new mechanism.
| Changed in dragonflow: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to dragonflow (master) | #1 |
| Changed in dragonflow: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7367754398eef00
Author: Dima Kuznetsov <email address hidden>
Date: Wed Jul 5 21:12:04 2017 +0300
Use stevedore to load apps
We used to load apps by listing module and class names in a
configuration entry. This patch defines entry points for all present
apps, so we don't have to import them by module path, additionally,
other packages can register new apps, allowing further extensibility.
Closes-Bug: #1702462
Change-Id: Iffa0fea3db36df