diff options
| author | boden <boden@linux.vnet.ibm.com> | 2014-08-04 08:57:42 -0400 |
|---|---|---|
| committer | boden <boden@linux.vnet.ibm.com> | 2014-08-13 14:04:48 -0400 |
| commit | c9fd5a6a0bd28ac785e0a19770fbeb6d57280009 (patch) | |
| tree | e7b22257e6bb21fb35fa78609a8cb12c0232902f /etc | |
| parent | 1fd4c4508dd53ae5bea22ce2380d917921aa09cd (diff) | |
| download | trove-c9fd5a6a0bd28ac785e0a19770fbeb6d57280009.tar.gz | |
Load trove API extensions using stevedore
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
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/trove/trove-guestagent.conf.sample | 3 | ||||
| -rw-r--r-- | etc/trove/trove.conf.sample | 4 | ||||
| -rw-r--r-- | etc/trove/trove.conf.test | 3 |
3 files changed, 0 insertions, 10 deletions
diff --git a/etc/trove/trove-guestagent.conf.sample b/etc/trove/trove-guestagent.conf.sample index a8777064..d4984012 100644 --- a/etc/trove/trove-guestagent.conf.sample +++ b/etc/trove/trove-guestagent.conf.sample @@ -37,9 +37,6 @@ rabbit_password=f7999d1955c5014aa32c # RabbitMQ topic used for OpenStack notifications. (list value) #rabbit_notification_topic = ['notifications'] -# Path to the extensions -api_extensions_path = trove/extensions/routes - # Configuration options for talking to nova via the novaclient. # These options are for an admin user in your keystone config. # It proxies the token received from the user to send to nova via this admin users creds, diff --git a/etc/trove/trove.conf.sample b/etc/trove/trove.conf.sample index db9cee5a..6b8dedf4 100644 --- a/etc/trove/trove.conf.sample +++ b/etc/trove/trove.conf.sample @@ -68,10 +68,6 @@ sql_idle_timeout = 3600 #DB Api Implementation db_api_implementation = "trove.db.sqlalchemy.api" -# Path to the extensions. -# $pybasedir is the path to the installed trove package -api_extensions_path = $pybasedir/extensions/routes - # Configuration options for talking to nova via the novaclient. trove_auth_url = http://0.0.0.0:5000/v2.0 #nova_compute_url = http://localhost:8774/v2 diff --git a/etc/trove/trove.conf.test b/etc/trove/trove.conf.test index 2dd1bf5e..793ec5df 100644 --- a/etc/trove/trove.conf.test +++ b/etc/trove/trove.conf.test @@ -60,9 +60,6 @@ sql_idle_timeout = 3600 #DB Api Implementation db_api_implementation = trove.db.sqlalchemy.api -# Path to the extensions -api_extensions_path = trove/extensions/routes - # Configuration options for talking to nova via the novaclient. # These options are for an admin user in your keystone config. # It proxy's the token received from the user to send to nova via this admin users creds, |