Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Ibc047f8a603fd81b32e3e4dd29a9eab283cc1048
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Switch to using sphinx-build, fix problems found
- Use newer openstackdocstheme and Sphinx versions
- Cleanup */source/conf.py to remove now obsolete content.
- Remove install_command from tox.ini, the default is fine
Change-Id: I6c593dff382a7aac4d758f802173f5a9f1e66182
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Iabf25521d98521111d732eddf13f36a5c207d4ef
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I421f513f39922332f5b5899b476bd245321a86a3
Story: #2002586
Task: #24342
When I visit http://specs.openstack.org/openstack/trove-specs/, nothing
shows in `Ocata approved specs` section, but there are some *.rst files in
Github. So try to display ocata approved specs. And add 'Pike approved
specs' section and pike folder. Delete sample.rst in Ocata.
Change-Id: Ia828e648f23d263a45e076a4f2387126b4e7f753
Signed-off-by: Fan Zhang <zh.f@outlook.com>
This spec defines the new list of trove commands to be implemented in
the python-troveclient repository as python-openstackclient plugins.
Change-Id: Ie2fc47c920256cbef50adf33fa76546ce74cb379
Partially-Implements: trove-support-in-python-openstackclient
This blueprint defines the new feature to secure the oslo messaging
messages with symmetric keys.
Change-Id: If0146f08b3c5ad49a277963fcc685f5192d92edb
Partially-Implements: secure-oslo-messaging-messages
Outlines a proposal for supporting the creation of Trove
instances with multiple volumes attached.
Included in this spec is a new guest configuration file.
Change-Id: If14438396a2864428cf8e0b9a70368e889e41906
The Oslo Policy library provides support for RBAC policy enforcement
across all OpenStack services.
Change-Id: Ifee24ab34a897152e3a0d001628558f95269e80f
Implements: blueprint trove-policy
Improve user and database API extensions to handle datastore-specific
properties and allow them to work with clusters.
Implements blueprint: datastore-specific-api-extensions
Change-Id: I33fe68b0255c256a33ecf4d59e15450e72eb3416
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