c9fd5a6a0b
The current trove impl loads trove API extensions by searching on a single file path which is exposed as a conf property. This results in a less than optimal approach from a consumer extension POV. This change replaces the single extension path approach with dyanmic loading using stevedore. Consumers can now bind into the API extensions using the 'trove.api.extensions' entry point; a standard means to define extension points. Moreover this change refactors to the trove.openstack.common.extensions logic into trove.common.extensions. In addition this change includes base unit tests to ensure the existing trove proper extension points are loaded and that some basic checks are in place W/R/T validating trove extension points. Change-Id: Id3e712b536aef3bc9c9d1603367cdc0d4816b970 Implements: blueprint dynamic-extension-loading |
||
|---|---|---|
| .. | ||
| cloudinit | ||
| conf.d | ||
| api-paste.ini | ||
| api-paste.ini.test | ||
| trove-conductor.conf.sample | ||
| trove-guestagent.conf.sample | ||
| trove-taskmanager.conf.sample | ||
| trove.conf.sample | ||
| trove.conf.test | ||