| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Support "--datastore-version-number" for creating configuration
- Support "--datastore-version-number" for creating instance
- Support "--version-number" for creating datastore version
- Support "--version-name" for updating datastore version
- Support showing version number for datastore version, instance and
configuration
Story: 2008358
Task: 41264
Change-Id: Ie84b4506736a82a214b0416f7e451d565552f651
|
|
|
|
|
|
|
|
|
| |
Story: 2008341
Task: 41242
This reverts commit 27cf71299ec51976fed8b18dbf5c0e4f9f4fd6f5.
Change-Id: I036a0423263b1a0332415c6403647ae82c9e34c4
|
|
|
|
|
|
| |
Remove all usages of six.
Change-Id: I6ea8d1cdc3060d5c2a4311c7454b66ba75109b0c
|
|
|
|
| |
Change-Id: Ic4efe1fec9b26b90d1412ab13b94939961bb4be3
|
|
|
|
| |
Change-Id: Ie6f22493d1722f41db5aa1a601a652e7eefa29c4
|
|
|
|
| |
Change-Id: Ia590fa6aae23b7323963181d79c9b0097fd2e4d1
|
|
|
|
|
|
|
| |
* Added "public" and "allowed_cidrs" fields for getting instance.
* Added '--is-public/--is-private' and '--allowed-cidr' for updating.
Change-Id: Ifc919667e83573bd6c3b7aff205fe08e82667457
|
|
|
|
| |
Change-Id: Ieae9216033d1c9ce0078554c7519bc891f50dc35
|
|
|
|
|
|
|
| |
When creating replicas, flavor is not needed. Replica has the same
server settings as the primary.
Change-Id: Ia9b43a464763234b84ba163d8c773b21f53f4ee7
|
|
|
|
| |
Change-Id: Ic8c20109b287f2f9220379cb249669d18b52893d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The __future__ module [1] was used in this context to ensure compatibility
between python 2 and python 3.
We previously dropped the support of python 2.7 [2] and now we only support
python 3 so we don't need to continue to use this module and the imports
listed below.
Imports commonly used and their related PEPs:
- `division` is related to PEP 238 [3]
- `print_function` is related to PEP 3105 [4]
- `unicode_literals` is related to PEP 3112 [5]
- `with_statement` is related to PEP 343 [6]
- `absolute_import` is related to PEP 328 [7]
[1] https://docs.python.org/3/library/__future__.html
[2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[3] https://www.python.org/dev/peps/pep-0238
[4] https://www.python.org/dev/peps/pep-3105
[5] https://www.python.org/dev/peps/pep-3112
[6] https://www.python.org/dev/peps/pep-0343
[7] https://www.python.org/dev/peps/pep-0328
Change-Id: I73b532283079d346b75a925e2aee707c4de8fa9e
|
|
|
|
| |
Change-Id: I5a35911b5658fdf6bc08844b31cc1325b749526a
|
|
|
|
|
|
|
|
|
| |
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: Id0fe73eef95bb57ecee706b9eb9b7aae53236e3b
|
|
|
|
|
|
| |
usage: openstack datastore version delete <datastore_version_id>
Change-Id: I4b781e68b81a3888d15d002fcf488a1f765c9f6a
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
- openstack database log show <instance_id> <log_name>
- openstack database log set <instance_id> <log_name>
[OPTIONS]
Change-Id: I86f414a53e6f6416f96e0040635bb010aa49cf41
|
|
|
|
|
|
|
|
|
| |
Add two params for creating instance:
'--is-public' and '--allowed-cidr'
Change-Id: I3bc69e3d56d250b562543f0de2c78c05fcaefead
Story: 2006500
Task: 36469
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: If48449acf7037ffb04e1b5b9d1c4b059ea629055
|
|
|
|
| |
Change-Id: Id9c9e6352742c672ae3f2764c42dd984c8202544
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
1. update hacking version to latest
2. fix pep8 failed
Change-Id: I49a6d46466b06bd56bed1f15632c9c80ef539b38
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous patches have add configuration and extended_properties
to "trove cluster-create"[1][2], this commit add the two paramenters
to OSC, user can pass configuration and extended_properties during
"openstack database cluster create".
[1] https://review.openstack.org/#/c/583125/
[2] https://review.openstack.org/#/c/589047/
Change-Id: Ic8e3ba4e92d3b65fa65875675f58eead5827976a
Signed-off-by: zhanggang <zhanggang@cmss.chinamobile.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Handles API part implemented in change:
I7c0a22c6a0287128d0c37e100589c78173fd9c1a
So far passing configuration group was possible only for single instance
deployment.
As the trove api now already supports configuration attach and detach
for clusters, we are able to handle it in client.
Configuration will be applied to each cluster instance.
Partially implements: blueprint cluster-configuration-groups
Change-Id: Ic0840c995cbc34203c76494d7ba522f3e17141a7
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
User can specify the number and volume of mongos/configserver with
extended_properties argument when creating mongodb. Currently,
the supported parameters are, num_configsvr, num_mongos,
configsvr_volume_size, configsvr_volume_type, mongos_volume_size
and mongos_volume_type.
Change-Id: I35406f9967ce00a51b320eda37572e96228b209d
Signed-off-by: zhanggang <zhanggang@cmss.chinamobile.com>
|
|/
|
|
|
|
|
|
|
|
| |
With PEP 479, the behaviour of StopIteration is changing. Raising it to
stop a generator is considered incorrect and from Python 3.7 this will
cause a RuntimeError. The PEP recommends using the return statement.
More details: https://www.python.org/dev/peps/pep-0479/#examples-of-breakage
Change-Id: If53f0f4c313a699a4036838ab6035fffa931931b
|
|
|
|
|
|
|
|
|
| |
In some part in the code we import objects. In the Openstack style guidelines
they recommend to import only modules. [1]: "Do not import objects, only modules".
[1] https://docs.openstack.org/hacking/0.10.3/
Change-Id: I8dd5396ab604013639a0b626ce3ecd3e3fad12e8
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According bug description, there will be an error when
use configuration-parameter-show without version_id
and datastore. To fix this problem, I add an judgement
for use the cmd without parameter datstore and
datastore_version not like an uuid.
Now in such a case, the cmd will has an exception info.
Change-Id: I01fd56bad80f389da369be90dff5c89b05e6a8dc
Closes-Bug: #1363065
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In trove secgroup_delete_rule help message, the parameters
<security_group_rule> is described "Name of security group rule".
In fact, security group rule has not attribute 'name', it only has
'id'.
Users could use trove secgroup-list-rules to get all ID of rules.
Change-Id: If5b97f744b24838e6aa61f4c96608da569886dd2
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not like nova-delete when use trove-delete there is only support
delete an instance everytime. With this patch, we can delete
many instances or clusters in the same call, like
trove delete instance1 instance2.
Change-Id: I6bb0c406ba7f4c0e43cddfdff1d156b7e82ffa7a
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
According bug description, the datastore display abnormal
when use trove list.
Change-Id: Ia1dda1c2fb6822ea991afbdf3a67819c262e49a8
Closes-Bug: #1734846
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According bug description, the datastore display abnormal
when use trove backup-show. The cause of the problem
is method _print_object unformatted datastore from result.
Fix by formatted datastore where necessary.
Change-Id: Ifbcc8312e52eb3d052f5d24645d4d243ec50aed7
Closes-Bug: #1735157
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According bug description, the networks display abnormal
when use trove show. The cause of the problem is method
_print_instance unformatted networks from result.
Change-Id: I30e27b731f67ab7c31e30af8ab9bb3e499e27dfa
Closes-Bug: #1734710
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According bug description, not like nova-delete when use trove-delete
there is no message or alert is generated. To solve this problem, I
added some message when normally execute deleting instance or cluster.
Change-Id: I572a24116fd1abec220f49a3f9705a5c071155bf
Closes-Bug: #1569669
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The parameter 'backup' in backup-create is never read by our Trove API[1], so
I guess it's a extra key argument for history reason. In addition, the
'backup-copy' subcommand should be removed as well because it does not
support in current Trove API.
[1] https://github.com/openstack/trove/blob/master/trove/backup/service.py#L61-L77
Change-Id: I33d439e0037efd4573eeae186758fd778ba5c514
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Now troveclient does not support returning Chinese characters, so
to make changes.This should also avoid other unicode output
problems
Change-Id: Ie948cff4e81806f17c697f50271992cc492c48f4
Closes-Bug: #1720490
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "trove module-instances" command don't work.
cat <<EOF>> myping.data
message=Module.V1
EOF
trove module-create myping ping myping.data
trove module-apply \
7d95769f-1912-4e77-8b86-d9a4eb48cd2e myping
trove module-instances myping
ERROR: Module with ID 7d95769f-1912-4e77-8b86-d9a4eb48cd2e \
could not be found.
Change-Id: I30c2e698bd1ea90cc8fdf0dc5e3a5b087ca2bec2
Closes-Bug: #1664472
|