summaryrefslogtreecommitdiff
path: root/troveclient/v1/shell.py
Commit message (Collapse)AuthorAgeFilesLines
* Uses the "network_id" param creating a clusterHirotaka Wakabayashi2022-04-091-0/+8
| | | | | | | | | | | | | | | | | | | | This PR replaces a request parameter name "net-id" with "network_id" creating a cluster. When creating a cluster, Clusters API internally calls Instaces API to create a instance. A request parameter name to create instances has changed[1] but python-troveclient still uses old parameter name when creating a cluster. The original problem is instance creation error when creating a instance that belongs to a cluster. Troves's Instances API has changed a parameter name from "net-id" to "network_id", but Clusters API and python-troveclient still uses the "net-id" parameter name. We need to fix it. [1]: https://opendev.org/openstack/trove/commit/535417240709694080255c064c9d84a5ab1d5372 Task: 44925 Story: 2009958 Change-Id: Ia3d1d6f451296eba34f2389da184c41a7ee9e84e
* Revert "Remove flavor API"Lingxian Kong2020-11-131-5/+51
| | | | | | | | | Story: 2008341 Task: 41242 This reverts commit 27cf71299ec51976fed8b18dbf5c0e4f9f4fd6f5. Change-Id: I036a0423263b1a0332415c6403647ae82c9e34c4
* Stop to use the __future__ module.Hervé Beraud2020-06-021-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Remove flavor APILingxian Kong2020-05-081-51/+5
| | | | Change-Id: I5a35911b5658fdf6bc08844b31cc1325b749526a
* Support log tail/save for instanceLingxian Kong2019-12-161-6/+2
| | | | | | | | | 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
* Support log actions in osc pluginLingxian Kong2019-12-161-8/+10
| | | | | | | | - openstack database log show <instance_id> <log_name> - openstack database log set <instance_id> <log_name> [OPTIONS] Change-Id: I86f414a53e6f6416f96e0040635bb010aa49cf41
* Update hacking versionZhijunWei2019-01-021-11/+11
| | | | | | | 1. update hacking version to latest 2. fix pep8 failed Change-Id: I49a6d46466b06bd56bed1f15632c9c80ef539b38
* Sync two parameters of cluster-create to OSCzhanggang2018-08-211-3/+7
| | | | | | | | | | | | | 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>
* Support configuration groups for clustersMarcin Piwowarczyk2018-08-071-1/+7
| | | | | | | | | | | | | | | | | 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>
* Add extended properties support for mongo cluster.zhanggang2018-07-311-1/+22
| | | | | | | | | | | 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>
* Clean imports in codeNguyen Hung Phuong2018-02-211-3/+3
| | | | | | | | | 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
* Merge "Fix error with configuration-parameter-show"Zuul2017-12-251-0/+5
|\
| * Fix error with configuration-parameter-showwangyao2017-12-211-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge "Use ID instead of Name in secgroup_delete_rule"Zuul2017-12-211-1/+1
|\ \ | |/ |/|
| * Use ID instead of Name in secgroup_delete_rulezhanggang2017-12-201-1/+1
| | | | | | | | | | | | | | | | | | | | 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
* | Merge "Support delete and cluster_delete with many resources"Zuul2017-12-211-14/+16
|\ \ | |/ |/|
| * Support delete and cluster_delete with many resourceswangyao2017-12-211-14/+16
| | | | | | | | | | | | | | | | | | 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
* | Merge "Fix datastore abnormal display with trove list"Zuul2017-12-201-2/+2
|\ \
| * | Fix datastore abnormal display with trove listwangyao2017-11-281-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | According bug description, the datastore display abnormal when use trove list. Change-Id: Ia1dda1c2fb6822ea991afbdf3a67819c262e49a8 Closes-Bug: #1734846
* | | Fix datastore abnormal display with trove backup-showwangyao2017-11-291-0/+6
|/ / | | | | | | | | | | | | | | | | | | | | 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
* | Merge "Fix networks abnormal display with trove show"Zuul2017-11-271-0/+3
|\ \ | |/ |/|
| * Fix networks abnormal display with trove showwangyao2017-11-271-0/+3
| | | | | | | | | | | | | | | | | | 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
* | Merge "Add proper message when delete instance or cluster"Zuul2017-11-171-4/+12
|\ \ | |/ |/|
| * Add proper message when delete instance or clusterwangyao2017-11-101-4/+12
| | | | | | | | | | | | | | | | | | 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
* | Merge "Remove extra parameter 'backup' in backup-create"Zuul2017-11-111-24/+0
|\ \
| * | Remove extra parameter 'backup' in backup-createint32bit2017-08-221-24/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge "ESFIX:Fix troveclient error with Chinese character"Zuul2017-11-081-1/+2
|\ \ \ | |_|/ |/| |
| * | ESFIX:Fix troveclient error with Chinese characterjiansong2017-11-031-1/+2
| |/ | | | | | | | | | | | | | | | | 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
* | Fix "trove module-instances" command which don't work.wlhc2017-11-061-0/+2
|/ | | | | | | | | | | | | | | | | | | 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
* Merge "Add related_to help message for instance help"Jenkins2017-06-151-1/+2
|\
| * Add related_to help message for instance helpjiansong2017-06-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | We have been change the mongodb cluster scaling related changes in the Liberty version[1], as mongodb cluster grow the necessary variables,we should displayed in the help message to expose it, rather than hide it. So made this change. [1]:https://specs.openstack.org/openstack/trove-specs/specs/liberty/cluster-scaling.html#cluster-grow Change-Id: I45f5702f7645aa7855f8140bcd5ec83e2c76eeae
* | Merge "Update reset-status docstring"Jenkins2017-06-111-1/+4
|\ \
| * | Update reset-status docstringAli Adil2017-01-161-1/+4
| | | | | | | | | | | | | | | | | | Added more information for reset-status docstring. Change-Id: I4ab194029e5bfbca990984be707f727081bf5907
* | | Enable user/db operations on clustersPetr Malik2017-04-181-11/+11
| |/ |/| | | | | | | | | | | | | Accept cluster ids in user and database API and route the requests on the single instance interface. Implements blueprint: datastore-specific-api-extensions Change-Id: I9cfa048cdee7c9eb18787957fb69e14e05dd4128
* | Merge "Client changes for datastore-version volume-types"Jenkins2017-04-111-0/+37
|\ \ | |/ |/|
| * Client changes for datastore-version volume-typesMatt Van Dijk2016-11-291-0/+37
| | | | | | | | | | | | | | | | | | Add trove client support for new volume-types listing and datastore version association listing. Co-Authored-By: amrith <amrith@tesora.com> Change-Id: Iafcd8d068b85c1993fac0471c04e57478c122bfe Depends-on: I790751ade042e271ba1cc902a8ef4d3c3a8dc557
* | Merge "Add support for module-reapply command"Jenkins2017-01-091-5/+29
|\ \
| * | Add support for module-reapply commandPeter Stachowski2017-01-051-5/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To facilitate the concept of live-update, a new command 'reapply' has been added to reapply a given module to all instances that it had previously been applied to. Originally, a module designated live-update would automatically be re-applied whenever it was updated. Adding a specific command however, allows operators/users more control over how the new payload would be distributed. Old 'modules' could be left if desired, or updated with the new command. Change-Id: Ic4cc9e9085cb40f1afbec05caeb04886137027a4 Partial-Bug: #1554903 Depends-On: I4caf4a57226dd711575cde766076fa25d16792e2
* | | Merge "Allow type to be specified on cluster-create"Jenkins2017-01-051-6/+6
|\ \ \ | |/ / |/| |
| * | Allow type to be specified on cluster-createPeter Stachowski2016-12-091-6/+6
| |/ | | | | | | | | Authored-By: Peter Stachowski <peter@tesora.com> Change-Id: I209a1883943e143b0ea66f6a08bb7e308aa516f3
* | Add module-instance-count commandPeter Stachowski2017-01-051-5/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added a --count_only flag to the call for module instances to return a summary of the applied instances based on the MD5 of the module (this is most useful for live_update modules, to see which ones haven't been updated). Added a new module-instance-count command. This was done to facilitate getting the summary, since it returns a different result set. It basically calls the same python interface as module-instances, but adds the --count_only flag. Also added some missing tests. Change-Id: Iea661166bf3a4f3520a590da5954aedcd0036243 Partial-Bug: #1554900 Depends-On: I4caf4a57226dd711575cde766076fa25d16792e2
* | Merge "Fix module-list"Jenkins2017-01-041-13/+1
|\ \
| * | Fix module-listPeter Stachowski2016-12-221-13/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Under a keystone V3 scenario, the CLI command for module-list will fail as it tried to determine whether to display the 'visible' and 'tenant' fields (which only make sense to show to an admin). Keystone V3 stores the role information (used to find out if the user has admin access) in a different place than V2. This fix uses a keystoneauth1 property to have the value determined correctly internally, so trove doesn't have to worry about it. The logic was also moved to the utils module to faciliate reuse. Closes-Bug: #1622019 Change-Id: I6dbc3660b507017f85d06bde2903f4d2334fea35
* | Merge "Cluster Upgrade"2.7.0Jenkins2016-12-101-0/+12
|\ \ | |/ |/|
| * Cluster UpgradeMorgan Jones2016-11-091-0/+12
| | | | | | | | | | | | | | | | | | Implements the Clusters.upgrade python API and corresponding shell command. Implements blueprint: bp/cluster-upgrade Change-Id: Iedb08c99bf8eb2a0b0d09e3c1ebd11965fdfff90
* | Merge "Added limit/marker support for config group lists"Jenkins2016-11-211-2/+16
|\ \
| * | Added limit/marker support for config group listsDuk Loi2016-11-021-2/+16
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Added support in the CLI for limit and marker to the configuration-list and configuration-instances command. Changed the python API to use the _pagination function instead of _list. Modified the unit tests to test this change. Change-Id: I46d8258eab81d1510707244547e31cd5707a22ce Closes-Bug: bug/1638352
* | Multi-Region SupportMorgan Jones2016-11-171-5/+20
|/ | | | | | | | | | | This is an initial attempt at supporting multiple regions. It should handle the mechanics of deploying an instance/volume to a remote region. Additional changes may be required to allow the guest agent on the instance to connect back to the originating region. Co-Authored-By: Doug Shelley <doug@tesora.com> Depends-On: I386efb2d5c147417af7ea25704405977c9b6bbcd Change-Id: Ib0b35100c0780dc07c60d20622554ba77c4bc850
* Add i18n to v1/shell.pyTrevor McCasland2016-10-181-383/+421
| | | | | | | | | | | | | | Help, print, and exception messages will now all be translated. I did not find any logging messages. Motivation for this change: 1. A patch for shell.py recently added i18n, we should be consistent with the additions from v1. 2. I noticed a patch on v1/shell.py that had reviewers suggesting to use i18n, instead of applying it to one message lets do it for the whole file. Change-Id: Ifd1bf25020c5f180a074165e2634a105bcbd4ed8
* Throw correct error on creation of size 0Trevor McCasland2016-09-301-1/+5
| | | | | | | | | | | | When trying to create an instance of size 0 an error is thrown stating that the size was not specified, this is not correct because I did specify it. The problem is that args.size evaluates to False because size is 0. This patch checks for size being zero instead and throws the correct error message. Change-Id: If00e83ccd919429dcfac7621dbbd9daa49f8b416