A proposal for implementing multiple region support by
simply allocating instances in different regions using
the existing --os-region-name support. Includes support
for allocating instances in multiple regions for replication
and clustering. Support for restoring backups to
different regions will also be included.
APIImpact
Implements Blueprint: bp/multi-region
Change-Id: I6270310716944272651d6ac62bdd3e41e056f975
The openstack directory was used to keep codes from oslo-incubator,
we have retired oslo-incubator,so don't use this directory any more.
Change-Id: Id3d23b4f130cf982e02a45d544805cc5d9c05813
This is a proposal for a project to get rid of trove-integration and
redstack in Ocata.
Change-Id: I2468db022e1560b84ede2448fd6d3b01a7a9603a
Implements-Blueprint: eliminate-trove-integration-and-redstack
The original url is wrong, or is outdated, after open is 404 not
found. This time should be updated this url address to the correct
documents
Change-Id: Ic765aba45f5081fa7ae47bb631ee28b44c28cc7b
Outlines a proposal to implement scheduled backups in Trove by
utilizing the triggers workflow features of Mistral.
DocImpact
Change-Id: Ia5d55d93f95c331177fe1bfaeeffaacf1a9c0673
Modules currently are applied in any order, however operators may wish
to control the order that modules are applied to ensure proper
functionality.
This spec addresses this issue.
References: blueprint module-management-ordering
Change-Id: I12afa490033f018a8feda874b59e1e219ec96d4a
Exposes the existing Quotas.update call in the management API to
the user API and implements a corresponding shell command. Admin
privileges will be required to execute the command.
Change-Id: I7cc19a9d2c034bb4b0695cacf7e1bc18a4fd999f
Currently Trove only supports full offline backups
for DB2. This spec details how to configure DB2
for full online backups & restore.
Implements blueprint: db2-online-backup
Change-Id: I260133431d12ea1f4aea63e49bfd408cf2454431
This week is the deadline for Newton specs so I'm creating the Ocata
directory.
To get around the chicken and egg problem of having a dummy spec in
the Ocata directory, I'm using the same technique that Nova adopted in
https://review.openstack.org/#/c/127047
Change-Id: Ie5ae1d732e34d2bdf7e187eb4194a1c006d0a17d
A proposal for upgrading running Trove instances to a new image.
This would support upgrading the Trove guestagent, the database,
and/or the underlying OS.
APIImpact
DOCImpact
Change-Id: If1ca9b9bf944c3ce3b0aaddd28f32f76a9a9500f
Cinder exposes volume types and a user can specify the volume type when
requesting a new instance (implementation for this is under way, see
https://blueprints.launchpad.net/trove/+spec/volume-type-on-create).
This BP proposes adding the capability to restrict the volume types that
can be used for each datastore just the same as the current ability to
restrict flavors to datastores.
Change-Id: I65773795e728e2d25c168eca8ad31effd2e39537
Implements: blueprint associate-volume-type-datastore
As we now have four releases of specs (starting with Kilo) when
reviewing the documentation it is more convenient if information were
sorted reverse chronologically. So I've put Newton at the top; when
you go to the website therefore you will see the most recent documents
at the top.
Change-Id: I202a1a33ef6e4f4eb2dbafd79bcd8be468d17440
This spec describes the work required to persist error
messages to the db and make them available to end users.
References: blueprint persist-error-message
Change-Id: I967b2c9f4f115a36e373eb83d0303601c3388cae
This spec describes the work required to add locality
to replication sets and clusters.
APIImpact
References: blueprint replication-cluster-locality
Change-Id: I061f086f90899c6287fcdac3c88523d62f4e4b30
This change dynamically picks the release directory
based on the fact that they are in alphabetical order.
This should avoid having to modify the current_release
variable at the beginning of each cycle.
Fixes errors in trove-image-build.rst since the
tests weren't being run in the right directory.
Change-Id: If8f84d25fbdde14103db56304eba92abc93dc4ee
This specification proposes to create a new Trove repository
that will contain source code artifacts for a Trove guest database
image generation tool.
Change-Id: I823d5d611cf951360e11c4564c7e4696a586916d
Implements: blueprint trove-image-build-repo
A proposal for adding support for configuration groups for CouchDB.
Implements: blueprint couchdb-configuration-groups
Change-Id: Icb6557a73b8de89aee64702486b88e2833cdc871
Since Trove now supports proprietary databases, a mechanism for
handling licensing for said databases is needed.
Other third-party 'modules' may also need configuration or
activation.
A proposal for allowing end users the ability to manage adding,
deleting, listing, viewing and updating the corresponding
module data file is included in this spec.
Methods to apply, remove, query and retrieve the actual module
data file on the Trove instance will also be provided.
Change-Id: I3e8cc4548fe5b48cc53f4da55e4f1f40573fa057
Even though the CouchDB datastore has been implemented in Trove,
there are lots of missing functionalities. This spec aims to
add the database and user functions for CouchDB.
Change-Id: I5aced70a0739ee1c52265ab445af048bf9fc0ed1
Implements: blueprint couchdb-database-user-functions
Implement cluster create/grow/shrink and delete operations
for the Cassandra datastore.
Change-Id: I97fc1026426a4c023950fd61bdf2c85b96b37768
Implements: blueprint cassandra-cluster
This spec outlines adding root enable to the PXC datastore.
Partially-Implements: blueprint pxc-root-enable
Change-Id: I2cf260e775160d1f157305449f8fe15e63f5c718
