| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: I5878de658d4a3b2187e2fc91e4906d637bc9642e
|
| |
|
|
|
|
|
|
| |
Implements Trove client APIs to implement scheduled backups
via Mistral workflow.
Change-Id: I012eb88359e063adbb86979a8fbd2e2a1e83f816
Implements: blueprint scheduled-backups
|
| |
|
|
|
|
|
|
|
|
|
|
| |
There exists a method in the management API to change the quota
for a given resource. This change exposes that API via a new
"trove quota-update" command. Also, adds v1.Quotas to the python
client.
Note that this command requires admin privileges.
Partial implements: blueprint bp/quota-management
Change-Id: I6ca1a87fbc46781f83bc9b7bd33745783b8aaab1
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Added --incremental flag to backup-create and set the default
value to False. When the flag is passed it will create a
backup based on the last good known full/incremental backup.
If there is no previous backup a full backup will be created.
Change-Id: I96498180890b8b1692b1bac3b19988532f6eb077
Partial-Bug: #1607429
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Client side of being able to specify 'priority' modules plus a
way to rank the order in which modules are applied. Two new
attributes 'priority_apply' and 'apply_order' have been added
to the python API and are supported in the CLI by means of the
module-create and module-update commands.
Partially Implements: blueprint module-management-ordering
Change-Id: I2b871c7d1eab634174396bd0905329f3a66755f6
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In writing the scenario tests for the fix for
https://launchpad.net/bugs/1611525 (see
https://review.openstack.org/#/c/353118/ ) it became evident that the
--all_datastores and --all_datastore_versions options weren't
functioning correctly. These options are now handled in the right way.
Change-Id: I0f226f09db08f635c542b27d8d2f898050d327fa
Partial-Bug: #1612430
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Sometimes an instance/cluster can be stuck in BUILD state forever.
Attempting to delete the instance in this state is currently not
allowed. Add force-delete and reset-status command. Reset-status
will reset the status to ERROR, letting the instance/cluster be
deleted. Force-delete will combine functionality of reset-status
and delete.
Change-Id: I957b4be5030e493e0eb8c6b6855d41b942b2823c
Partial-Bug: #1579141
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | |
| | | |
This commit adds disk_space colmn to flavor-list
Change-Id: Iffd24d3527af7ba34da233833eb1a9831b84f8a6
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change includes a new "trove upgrade" CLI command and
a new "Instances.upgrade" python API method to implement
the new Instance Upgrade feature.
Change-Id: I6ec2ebb78019c014f87ba5d8cbfd284686c64f30
Implements: blueprint image-upgrade
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Due to recent changes (not sure what) the trove module-list command
now fails while trying to determine if the client is being run as
an admin user.
The error looks like the following:
DEBUG (shell:752) 'AccessInfoV2' object has no attribute '__getitem__'
Traceback (most recent call last):
File "/opt/python-troveclient/python-troveclient/troveclient/shell.py",
line 747, in main sys.argv[1:]))
File "/opt/python-troveclient/python-troveclient/troveclient/shell.py",
line 562, in main args.func(self.cs, args)
File "/opt/python-troveclient/python-troveclient/troveclient/v1/shell.py",
line 1552, in do_module_list
roles = cs.client.auth.auth_ref['user']['roles']
TypeError: 'AccessInfoV2' object has no attribute '__getitem__'
ERROR: 'AccessInfoV2' object has no attribute '__getitem__'
The code was changed so that it doesn't fail even if the structure
of the access object changes.
Change-Id: Ib0a7de0b8df359c9ad5a582bbe7afcff56d332f8
Closes-Bug: #1607428
|
| |\ \ \
| |_|/
|/| | |
|
| | |/
| |
| |
| |
| |
| | |
It's only needed for python < 2.7 which is not supported
Change-Id: Idfc1677ca01853993e21f4c8aa50a9be66c32203
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Here,assertDictEqual is test that two dictionaries are equal.This method
will be used by default to compare dictionaries in calls to assertEqual.
So,I replace assertDictEqual.
refer to [1] for more information
[1]:https://docs.python.org/2.7/library/unittest.html#unittest.TestCase.assertDictEqual
Change-Id: Idb30eeab13e9cad44e7c78c7903280f5e3bf66d6
|
| | |
| |
| |
| |
| |
| |
| | |
This commit adds vCPU colmn to flavor-list
Closes-Bug: #1261876
Change-Id: Id0ab43cdaa20918af278c44ea9bff7d23260e438
|
| | |
| |
| |
| | |
Change-Id: I98f43b58f73b0f372f204017ae7e7194cc53d3b0
|
| |\ \ |
|
| | |/
| |
| |
| |
| | |
Change-Id: I108bd63dce28be059ce1bbbcc7b1a5c4488f028e
Closes-Bug: #1214176
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When Trove moved to support alphanumeric flavor ids, the case of having
a numeric string id with leading zeros was not taken into account. The
behavior on the client side is to see if the id is all digits, and if so
it is converted to an int. That means that a flavor of '01' will be
incorrectly interpreted as '1'.
This behavior has been fixed and unit tests created.
Change-Id: I5acdec576a2e7da6cbfbb1cfc61c49fbbf7379af
Partial-Bug: #1603187
|
| |/
|
|
| |
Change-Id: Ib7aba3285ef2334dabce62cc890367b8499b8c0d
|
| |
|
|
| |
Change-Id: I9a5a828f9bd84bcbc1a06013b1f7e748a4bd74e2
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the module support was added, cluster-grow was missed on the
client side. This has been added.
The parsing of the --instance options was also consolidated
so that cluster-create and cluster-grow receive the same
options.
Partial Bug: #1578917
Co-Authored-By: Matt Van Dijk <mvandijk@tesora.com>
Change-Id: I9a73a8c81f31d80e13ce7030d35cd2b087defbf3
|
| |/
|
|
| |
Change-Id: I519af1cbb731902beccd111632252002a820ba41
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to allow clusters to be all on the same hypervisor
(affinity) or all on different hypervisors (anti-affinity) a new
argument (locality) needed to be added to the Trove cluster-create API.
This changeset addresses the Trove client part of this feature.
A --locality flag is now available on the 'cluster-create' command and
is passed to the server for processing.
Partially implements: blueprint replication-cluster-locality
Change-Id: Ie46cfa69ffe6a64760aca38c495563f5724bd0d0
|
| |\ \
| |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to allow replication sets to be all on the same hypervisor
(affinity) or all on different hypervisors (anti-affinity) a new
argument (locality) needed to be added to the Trove create API.
This changeset addresses the Trove client part of this feature.
A --locality flag is now available on the 'create' command and
is passed to the server for processing.
The --replica_count argument was also cleaned up in that it's not
passed on unless it is set. If --replica_of is specified, the
default is set to '1.'
DocImpact: New functionality
Partially implements: blueprint replication-cluster-locality
Change-Id: I18f242983775526a7f1e2644302ebdc0dac025cf
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The dict.keys()[0] will raise a TypeError in PY3,
as dict.keys() doesn't return a list any more in PY3
but a view of list.
Change-Id: Id9c7d3725c01bd0a193d8fc6705443efe9c25c34
Partially implements: blueprint trove-python3
Closes-Bug: #1583419
|
| |/ /
| |
| |
| | |
Change-Id: I92f339efd6b77a229c5e9219c53dc609f7887fee
|
| | |
| |
| |
| | |
Change-Id: I22be8ec609b752ac0bf8c6c59c09342b84b9fa68
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The output of the CLI command datastore-show was unreadable. The
output has been modified so that it now looks like:
$ trove datastore-show mysql
+-----------------+--------------------------------------------+
| Property | Value |
+-----------------+--------------------------------------------+
| default_version | 5.7 |
| id | 175a5187-df46-4d48-9c89-6fed421af03b |
| name | mysql |
| versions (id) | 5.6 (9162ed72-687d-4617-8e71-8ba1ed7f1dc4) |
| | 5.7 (edcd8008-a1be-4e17-9182-ea2b6a5e2229) |
+-----------------+--------------------------------------------+
Change-Id: Icba9cac0d0923ac5177d4ff3d248902fc64a5f04
Closes-Bug: #1585669
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Format the fault nicely on the Trove 'show' command.
Change-Id: I92777ea410e8df21169fddcfdc0de1f5ca00e7bd
Implements: blueprint persist-error-message
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: I6a398b588bd902206d1a21c218141f4a0eb4ac6b
|
| |\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Mistral gets confused by Trove's (aguably wrong) inclusion
of a member called 'items' in the Pagenated object that
Trove returns as the result of 'list' client methods.
This change changes Pagenated to inherit from the 'list'
class so that the items method is not required (and has
the additional benefit of just generally being a better
implementation of a list type result).
Change-Id: I683120451f69f07f131e6fa422c082f85735b196
Closes-bug: 1585705
Depends-On: Id674ae57bfcdc5e09bde1e323a614b3a03a7cad3
|
| |\ \ \ \ |
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
The example usage was really out of date and doesn't work on modern
clients. This updates it to a functional state.
Change-Id: I96bf56e3cd3943f8c0e210dd873bc4cae02a1ea8
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: If5b8ab83da3e197a5eefeb331cf6117efba07615
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: I89d5fe849ac47d59eb0c117280b7b78a9ef31519
|