| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ia0580a599fc2385d54def4e18e0780209b82eff7
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/ussuri branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I0b60250038ae2e8eb9dc12f1c4f2f23e64309690
|
|
|
|
| |
Change-Id: I559ae88bf9be2059904b319f309bed7f56a8d53e
|
|
|
|
|
|
|
|
|
| |
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Change-Id: I5da442bb2f1e634e6b3fe37a6ea3820cea1db96f
|
|
|
|
|
|
| |
Change-Id: I9192857a690585cb3f365b15707dfa98e521e788
Story: #2007188
Task: #38315
|
|
|
|
| |
Change-Id: Id0fe73eef95bb57ecee706b9eb9b7aae53236e3b
|
|
|
|
|
|
| |
usage: openstack datastore version delete <datastore_version_id>
Change-Id: I4b781e68b81a3888d15d002fcf488a1f765c9f6a
|
|
|
|
|
|
| |
openstack database instance reboot <instance>
Change-Id: Id5ac985399797356165eaac68dd05bc46ee0124d
|
|
|
|
| |
Change-Id: I20802f199ef943244f27a842743434e1c84c79e5
|
|
|
|
| |
Change-Id: I469fe301f438577ee7c897dcddb28cb672e50c6b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Support to show log content and save instance log files:
openstack database log tail [--lines LINES] <instance> <log_name>
openstack database log save [--file FILE] <instance> <log_name>
Change-Id: I2a4eecca663f9126f770fae4c4be28b3667f91c4
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I1ce51ea180be57b40faf084b25e0e214b0ce487a
Sem-Ver: feature
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
OpenStack is dropping the py2.7 support in ussuri cycle.
python-troveclient is ready with python 3 and ok to drop the
python 2.7 support.
Complete discussion & schedule can be found in
- http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html
- https://etherpad.openstack.org/p/drop-python2-support
Ussuri Communtiy-wide goal - https://review.opendev.org/#/c/691178/
Change-Id: I425cb0d2f1487819fde9ebae46fe3570b72cbe88
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
- openstack database log show <instance_id> <log_name>
- openstack database log set <instance_id> <log_name>
[OPTIONS]
Change-Id: I86f414a53e6f6416f96e0040635bb010aa49cf41
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some plugin command option help strings were using invalid syntax to
refer to another option. This looked odd in CLI output
--marker <ID> Begin displaying the results for IDs greater than
thespecified marker. When used with :option:`--limit,`
setthis to the last ID displayed in the previous run.
and also caused building autoprogram-cliff from python-openstackclient
to break with errors like:
<ListDatabaseInstances>:1:unknown option: --limit,
This commit reformats the help strings to use double backticks, which
render sanely in the CLI help and also build properly from
python-openstackclient.
Change-Id: Ia3fd6d5ec76e0e6d6aee87d8a8790a1ed2d38a26
|
|
|
|
|
|
| |
Change-Id: Ib21e950650237f8df8f8ed7860b5ba43f60f8491
Story: 2006500
Task: 36470
|
|
|
|
|
|
|
|
|
| |
Add two params for creating instance:
'--is-public' and '--allowed-cidr'
Change-Id: I3bc69e3d56d250b562543f0de2c78c05fcaefead
Story: 2006500
Task: 36469
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ie08aa9a11f1703073efdb1b5dd23c46fd0cf354a
|
|/
|
|
| |
Change-Id: Ib69c3524c0afa8c7f7827e4feb70c7aed2e06c9a
|
|
|
|
|
|
| |
Change-Id: I6d79bd4e668ba48114467859a7debc2e0eef1990
Story: #2006433
Task: #36347
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To get all the backups of an instance:
openstack database backup list --instance-id <instance-id>
Admin user gets backups of all the projects:
openstack database backup list --all-projects
Story: #2006433
Task: #36346
Change-Id: I871d1ffa27805158024e8ecbe1dceae725c4deac
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Also fix the CI failure due to:
https://docs.python.org/3/whatsnew/3.5.html#pep-479-change-stopiteration-handling-inside-generators
Change-Id: Ica582f99730c5019a1212d4f58d7d854ad2996fd
Story: #2005924
Task: #34254
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Iba671c617cec6172f6709c73cd8b5a61c3db4e13
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All the integration testing has been moved to
Bionic now[1] and py3.5 is not tested runtime for
Train or stable/stein[2].
As per below ML thread, we are good to drop the py35
testing now:
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005097.html
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004647.html
[2]
https://governance.openstack.org/tc/reference/runtimes/stein.html
https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: Ib2b1297f75a245dbd2209f958a89a510bc62965c
|
| |
| |
| |
| | |
Change-Id: If48449acf7037ffb04e1b5b9d1c4b059ea629055
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Id9c9e6352742c672ae3f2764c42dd984c8202544
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Allow users to delete database instances in batch, usage:
usage: openstack database instance delete [-h] instance [instance ...]
Change-Id: I88a15ba1910f7b3294067b54ae4a7a9b4c4a17a5
|
|/ /
| |
| |
| | |
Change-Id: I3a1fd52759f22502fa9617f3dae017a0e132ec6a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, there is no way for the admin user to get databases of all
the projects, which is very important for auditing or billing purpose.
With this change, admin user can get all the database instances by
running:
$ openstack database instances list --all-projects
Change-Id: I318907b1d4a63017f4a6f7967312770f8784c1f4
Story: #2005735
Task: #33393
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Why we need to run Trove functional jobs for python-troveclient?
Especialy, the python-troveclient-tempest-neutron-src is running all
the core tempest jobs which are definitely unrelated to either Trove or
python-troveclient.
Disable those jobs until we have good reasons.
Change-Id: I91b41e19d40bc09cb883ef18d26949613196c439
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Iaeef060105d102a4ae96ca9776e4025b53991d7b
|
|
|
|
|
|
|
| |
1. update hacking version to latest
2. fix pep8 failed
Change-Id: I49a6d46466b06bd56bed1f15632c9c80ef539b38
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a mechanically generated patch to add a unit test job running
under Python 3.6 as part of the python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I72d4101d9edb049b58f5ce662160f9629dbf1665
Story: #2002586
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: Id9bd181ef7d76f228484e0f610e31904eca52b8a
|
|/
|
|
|
|
| |
Mailinglists have been updated. Openstack-discuss replaces openstack-dev.
Change-Id: Ic6ce8f7fad2375b37c0fae477ca43803ff907280
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During working with python3-first goals, I have notticed the
log_generator and log_save methods was non compliance with python3.
This is what doesn't appears in integration tests because we execute
only trove-functional-mysql job which doesn't covers guest-log tests.
In separate change I will extend zull definition by scenario tests to
avoid similar issues in future.
Change-Id: If85dff57afe110991553d510c6af4468a6781f64
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Current functional tests executed via trovestack doesn't cover all
integration tests scenarios.
This change extends gate and check pipelines by
trove-scenario-mysql-single job.
Change-Id: I04c53c47b078f4006397f503a58b85ba868ecaac
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
|
|
|
|
|
|
|
|
| |
The commands used by constraints need at least tox 2.0. Update to
reflect reality, which should help with local running of constraints
targets.
Change-Id: I8a8766706f60a75c546fa338943630a28f3670f2
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, listing instances only allows to get basic information about
entities. To get the details, one need to query instance "show" endpoint
for each instance separately. This is inefficient and exposes API to a
heavier load.
There are use cases in which we want to obtain detailed information
about all instances. In particular, in services integrating with Trove.
For example, Vitrage project requires this information to build vertices
and edges in the resource graph for RCA analysis.
This change extends Trove client by optional parameter allowing user to
specify whether API should include more instance details in the
response.
Change-Id: Iecea2f711a3e23fd63167beb6cab4cecc63bcabe
Signed-off-by: Bartosz Zurkowski <b.zurkowski@samsung.com>
|