Motivation: Each datastore type has its own hardware requirements (minimum and maximum). Currently, trove lacks the ability to enforce this requirement. This change enables trove with the ability to associate the virtual hardware templates (flavors) with datastore types.
Trove supports multiple datastore types. However, each datastore type has its own hardware requirements, which presently, cannot be enforced in trove.
For example: MySQL - Minimum System Requirements: - 2 or more CPU cores - 2 or more GB of RAM - Disk I/O subsystem applicable for a write-intensive database
Find more information about other datastore specific hardware requirements in the References section.
Trove uses virtual hardware templates called ‘flavors’ in OpenStack. In order for trove to be able to enforce the datastore specific hardware requirements, there needs to be a way in which datastore types can be associated with their minimum flavor (hardware) requirements. This way, the user/administrator can at least be notified while provisioning the datastore with the inappropriate flavor, that does not meet the minimum hardware requirements.
No impact on existing tables.
One new entity will be created in the trove database: datastore_version_metadata. This will store any additional metadata related to a datastore version including its relation with flavors: key=flavor and the value=flavor_id.
The blueprint specifies the table attributes in detail.
Does not impact any other API which the user has access to.