- Juno release of OpenStack Trove added support for Neutron networks, asynchronous MySQL replication, MongoDB clustering, and new datastores like PostgreSQL and Couchbase. - In Kilo, Trove specifications were moved to Gerrit for improved tracking and reviews. Initial implementations of CouchDB and Vertica were added, along with improvements to replication and clustering. - Kilo also focused on paying off technical debt, simplifying operations, and building out the community.

2. Trove Juno to Kilo

3. 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.
Mission Statement

4. Juno Overview
• 322 Commits from 71 different contributors
• 31 BPs implemented, and 201 bugs fixed
• ~3500 code reviews with 66168 total Lines of Code changed.
• More details:
• https://launchpad.net/trove/juno
• http://stackalytics.com/?release=juno&module=trove-group

5. Juno

6. Neutron Support
• Add Neutron NICs on instance create
• Support default Neutron Networks
• Horizon (Trove dashboard) enhancements

7. Replication
• Asynchronous MySQL master-slave replication
• Support for new, and existing instances
• Ability to Promote / Detach Slave

8. Clustering
• New Clustering API
• Support for MongoDB Cluster
• HA through replica sets
• Ability to grow horizontally by adding shards

9. Configuration Groups Enhancements
• Default configuration templates per datastore and version
• Configuration Groups per datastore and version
• Schema-based validation for values

10. Datastore Improvements
• Initial Support for new datastores
• PostgreSQL
• Backup/restore for non-mysql datastores
• Couchbase

11. Kilo

12. Specs for Trove
• Specifying specs on the wiki was getting cumbersome
• Hard to do reviews
• Hard to get feedback from ops, and users
• Hard to track changes
• In Kilo Trove moved to doing specs using gerrit
• http://specs.openstack.org/openstack/trove-specs
• https://review.openstack.org/#/q/status:open+project:openstack/trove-specs,n,z
• More information at:
• https://wiki.openstack.org/wiki/Blueprints#Spec_.2B_Blueprints_life
cycle

13. More Datastore Improvements
• Initial implementations of new datastores
• CouchDB
• Vertica
• Incremental improvements for existing datastores
• API to be able to fetch datastore specific logs from instances.
• e.g. MySQL error log, slow query log, etc.

14. Building on Replication
• Horizon Support for Replication
• Create instance as replica
• Detach replica from replication source
• Support for GTID based replication for MySQL
• Support for failover

15. Building out Clusters
• Support for clusters of Datastores other than MongoDB
• Cassandra
• Vertica
• XtraDBCluster (Galera)

16. Paying off Technical Debt
• Removal of 3rd
Party external “Deprecated Trove CI”
• All testing and CI now run under OpenStack Infra
• Functional / int-tests run in devstack-vm-gate environment
• Cleaning out deprecated oslo-incubator code.
• Switch to oslo.messaging for RPC
• Initial support for upgrade testing using Grenade.

17. Simplifying Ops
• Easier way to build Trove Guest Images
• Based on feedback from users and operators
• Standalone way to do this – “redstack” not needed
• Documentation Improvements for
• Image building
• Deploying Trove
• Getting started with Trove development

18. Your Idea Here!
• Growing community of contributors
• 136 contributors from 30 companies
• 1792 commits – 519258 lines of code
• Open to new ideas, and code
• Lots of room for improvement
• Find us at #openstack-trove on FreeNode.

19. Questions?
Nikhil Manchanda
PTL – OpenStack Trove
IRC, Twitter, Gmail – SlickNik

20. Thank You!