The Trove vision: Trove is an OpenStack Service which provides simple, intelligent, reliable, and scalable provisioning, monitoring, and management of both single and multi-node datastores. Find out what comes next.

1. Amrith Kumar
OpenStack Trove Core Team Member
Founder and CTO, Tesora
The Future of Trove

2. “To provide scalable and reliable
Cloud Database as a Service
provisioning functionality for both
relational and non-relational
database engines, and to continue to
improve its fully-featured and
extensible open source framework.”
https://wiki.openstack.org /wiki/Trove
Future of Trove
What is Trove? - The Trove Mission
August 25, 2015

3.  Incubated through Havana
 Integrated in Icehouse
 MySQL, MongoDB, Cassandra, Couchbase, …
 Included framework for Backup & Restore
 CLI, API, and Horizon Dashboard
 More recently (in Juno and Kilo)
 Frameworks for replication and clustering
 More databases (DB2, Vertica, CouchDB, …)
Trove History
Future of TroveAugust 25, 2015

4. “Trove is an OpenStack Service which
provides simple, intelligent, reliable,
and scalable provisioning, monitoring,
and management of both single and
multi-node datastores.”
https://wiki.openstack.org/wiki/TroveVi
sion
Future of Trove
What is Trove? – The Trove Vision
August 25, 2015

5. Trove: Simple
 A REST API
 CLI and Horizon Dashboard use this API
 Same API, different datastores
 Provides database independent abstraction
 Trove handles database specific details
 Does not interfere with application data access
 Trove is Management layer (+ some data layer)
Future of TroveAugust 25, 2015

6. Trove: Intelligent
 Leverages hardware capabilities
 Nova scheduler options
 Cinder back ends and volume types
 Network topologies
 Uses this to Schedule instances and cluster nodes
 Schedule cluster nodes in different AZs
 Can use local storage instead of block
 Rack affinity to schedule chatty cluster nodes to
minimize latency
Future of TroveAugust 25, 2015

7. Trove: Reliable and Scalable
Provisioning
 Users of the API shouldn’t be able to shoot
themselves in the foot
 Block restores to flavors with invalid profile
 Only allow flavors that make sense for certain datastores
 Prevent nonsensical cluster configuration
 Makes it easy to scale-up and scale-down based on
usage.
 Provide ways to resize compute, memory, and disk space
for
 Provide ways to resize the number of nodes in a cluster.
Future of TroveAugust 25, 2015

8. Trove: Monitoring
 Provides APIs to monitor and report state of
datastores
 Actively take actions based on the outcome
 Promote a slave to a master if it detects a failed
master
 Provision a new slave if it detects a failed slave
 Self healing for clusters on failed nodes
Future of TroveAugust 25, 2015

9. Trove: Management
 Provides APIs to perform routine and scheduled
maintenance tasks
 Taking backups
 Tuning datastore configuration parameters
 Does not require remote log-in to the datastore
 Provides APIs to seamlessly migrate from one
version to another
 Data Security
Future of TroveAugust 25, 2015

10. Trove: Looking ahead
 Support for more datastores
 Both SQL and NoSQL datastores
 Additional capabilities for datastores
 Replication, Clustering, Backup and Restore,
Configuration Groups, …
 Integration with other systems
 Billing, Event Notification, Security and Key
Management, …
Future of TroveAugust 25, 2015