Jump to: navigation, search

Trove/FlexibleDatastoreOpts

< Trove
Revision as of 22:45, 24 May 2014 by Denis M. (talk | contribs) (Intro)

Description

At this time all datastore specific options are defined inside codebase, so there's no valid way to add new option to datastore without modifying codebase. We need to define flexible way to load and register datastore options (in future - all Trove options).

Where Trove will look for required configurations?

   trove/templates/{datastore}/datastore.options


Justification/Benefits

Justification

Trove uses configuration file that describes what types of groups and options can be used. No valid way to add/modify options without changing actual Trove codebase. We need to define valid way to load configurations from external sources and render them into a oslo.config groups with specific options.

Benefits

The biggest benefit is adding support of commercial datastores into the Trove-API, Trove-Taskmanager, Trove-Conductor services. Proposed feature allows to load configuration files for each datastore from external sources.


Impacts

From user perspective nothing would change. From deployer perspective - will be provided more flexible way to prepare configuration files for each datastores.

Configuration

None

Database

None

Public API

None

Internal API

None

Guestagent changes

None