| Commit message (Collapse) | Author | Age | Files | Lines |
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Log messages are no longer being translated. This removes all use
of the _LE, _LI, and _LW translation markers to simplify logging
and to avoid confusion with new contributions
Change-Id: I848087a85fdc056c0b6ed6f9d597400c257afc8f
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
pycrypto is unmaintained for a while and requirements team advises using
pycryptodome or cryptography libraries instead (see openstack-dev thread
[0]).
troveclient uses pycrypto to generate random data/content in its tests
which does not require any specific cryptographic need. This commit
replaces it by os.urandom from Python standard library.
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-March/113568.html
Change-Id: Ia43c5883a51e8412c4a238d127c13db39e863da1
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The unit tests mock tokens from keystoneauth. One of the responses
being returned from a mocked keystoneauth method was returning a v2.0
token that didn't have the right expiration attribute of a v2.0
token. This was caught by keystoneauth 3.0.1, which underwent a
significant refactor and added a bunch of new functionality for
version discovery. Keystoneauth was expecting `expires` to be
in the token but instead the mock was using `expires_at`, which isn't
a valid v2.0 token attribute.
Closes-Bug: 1706538
Change-Id: Iea77ef54585d0b3480369e9f5df629e3f46f7e3b
|
| |\ \ \
| |/ /
|/| | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
Fix a bunch of formatting issues with docstrings to allow us to turn on
the flag that treats warnings as errors to avoid mal-formed
documentation in the future.
Change-Id: Ic6fb73031e37314c49c41e4621dfd92b9c3f59d5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
|
| |/
|
|
|
|
|
| |
HMAC key of OSprofiler can be configure in config files of Trove
not in api-paste.ini (configs in paste are deprecated).
Change-Id: I4904e5d0104e1cac12cc1f3e6dc38b6ef8372982
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the datastore-list command.
The trove command datastore-list is now:
openstack datastore list
Change-Id: I4804e6deae350f05abdb66a6d8813e5581f2b22c
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the database-list command.
The trove command database-list is now:
openstack database list
To confirm the databases list command I had to create an instance
and specify a database name like how it shows in the user-guide[1]
on step 2.
[1] http://docs.openstack.org/user-guide/create-db.html
Change-Id: I4f4682eff1addc3fc837f5468939ddd96572e238
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the list command.
The trove command list is now:
openstack database instance list
Partially-Implements: blueprint trove-support-in-python-openstackclient
Change-Id: Ic5328827dbf6d1f47db62f0bb2e65e164a0b2b6b
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the user-list command.
The trove command user-list is now:
openstack database user list
Note: Only looking up an instance by ID works. I think it has
something to do with not using osc-lib.find_resource because we
use our own find_resource in the client manager's list call.
Change-Id: If8a4b97b91c661e400dfcac0fa4922ed359ce32a
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the limit-list command.
The trove command limit-list is now:
openstack database limit list
Change-Id: I534d30022cbfef4ae596077f604e2a305dbe3146
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the configuraiton-list command.
The trove command configuration-list is now:
openstack database configuration list
Change-Id: I3a85260c15b8d1b4a37a806db2cb5ff3c433537b
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ \
| |/ / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change adds database support to the python-openstackclient
project for the cluster-list command.
The trove command cluster-list is now:
openstack database cluster list
Change-Id: I06b398190930db459ef8739685548263499f0d3c
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added more information for reset-status docstring.
Change-Id: I4ab194029e5bfbca990984be707f727081bf5907
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
According to OpenStack Guideline[1], logged string message should be
interpolated by the logger.
Also, upgraded hacking requirement, to enable H904 check.
[1]: http://docs.openstack.org/developer/oslo.i18n/guidelines.html#adding-variables-to-log-messages
Co-Authored-By: jiansong <jian.song@easystack.cn>
Change-Id: I3f020b6bcb1b9bf6d18a3b4f738c13cccd1bbff8
Closes-Bug: #1596829
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change adds database support to the python-openstackclient
project for the backup-list command.
The trove command backup-list is now:
openstack database backup list
Change-Id: I9aafb76c5a0d4a49b92a356e8465abf5919ab0ac
Partially-Implements: trove-support-in-python-openstackclient
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change adds database support to the python-openstackclient
through a plugin and tests.
The support can be demonstrated through the implementation of
the trove command flavor-list which is now:
openstack database flavor list
Use the -v or --debug flag to see the calls being made to the correct
flavor list function.
ubuntu@ubuntu:~$ openstack database flavor list -v
START with options: [u'database', u'flavor', u'list', u'-v']
command: database flavor list -> troveclient.osc.v1.flavors.ListFlavors
Using auth plugin: password
+-----+-----------+-------+-------+------+-----------+
| id | name | RAM | vCPUs | Disk | ephemeral |
+-----+-----------+-------+-------+------+-----------+
| 1 | m1.tiny | 512 | 1 | 1 | 0 |
| 2 | m1.small | 2048 | 1 | 20 | 0 |
| 3 | m1.medium | 4096 | 2 | 40 | 0 |
| 4 | m1.large | 8192 | 4 | 80 | 0 |
| 42 | m1.nano | 64 | 1 | 0 | 0 |
| 451 | m1.heat | 512 | 1 | 0 | 0 |
| 5 | m1.xlarge | 16384 | 8 | 160 | 0 |
| 84 | m1.micro | 128 | 1 | 0 | 0 |
| c1 | cirros256 | 256 | 1 | 0 | 0 |
| d1 | ds512M | 512 | 1 | 5 | 0 |
| d2 | ds1G | 1024 | 1 | 10 | 0 |
| d3 | ds2G | 2048 | 2 | 10 | 0 |
| d4 | ds4G | 4096 | 4 | 20 | 0 |
+-----+-----------+-------+-------+------+-----------+
END return value: 0
Change-Id: I308a6c6f3f5ce7dbb814ec0fd8ecb1734a2f137f
Partially-Implements: trove-support-in-python-openstackclient
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |\ \ \
| |/ /
|/| | |
|
| | |/
| |
| |
| |
| | |
Authored-By: Peter Stachowski <peter@tesora.com>
Change-Id: I209a1883943e143b0ea66f6a08bb7e308aa516f3
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Updates the swift authentication handling in v1/instances:_get_swift_client
to set auth_version as appropriate.
Change-Id: I39a22eeb4a9c371f333f81a69d4d429805b935f9
Fixes-bug: 1651502
|
| |/ /
| |
| |
| |
| |
| | |
Now liberty is end of life,so we can get rid of slave_of
Change-Id: I429a95018a58a92576c52e0a9bc6b1b817c408ea
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Implements the Clusters.upgrade python API and corresponding
shell command.
Implements blueprint: bp/cluster-upgrade
Change-Id: Iedb08c99bf8eb2a0b0d09e3c1ebd11965fdfff90
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |\ \ |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|