34 Commits

Author SHA1 Message Date
Zhao Chao
d597bb4714 Return 204 instead of 200 for root-disable API
As no content will be returned to the client if a root-disable request
succeeds, a HTTP 204 (Not Content) response is more appropriate.

Redis root-disable scenario test fails because it's return HTTP 204, but
all API related tests are expecting a HTTP 200. Although changing Redis
root-disable API is a much simpler way to resolve the problem, migrating
from HTTP 200 to HTTP 204 should be a better solution. Related tests and
documents are also updated accordingly.

APIImpact

Change-Id: If732a578009fd35436e810fb7ceceefd1ada3778
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
2018-03-02 20:57:23 +08:00
Fan Zhang
3301a2a740 [api-ref] Add sections for backups.
Change-Id: If3a929e9de31dd901c4838e85f91f76941f33d05
Closes-bug: #1663096
Signed-off-by: Fan Zhang <zh.f@outlook.com>
2018-02-27 19:28:38 +08:00
Zhao Chao
51b73cf198 [api-ref]: update instance creating parameters.
Closes-Bug: #1643496
Change-Id: I8c9ca4ad690751d3c53cbe9469cf5864a528d631
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
2018-02-11 15:18:42 +08:00
Zhao Chao
e4f181e424 [api-ref] Add sections for instance logs.
Change-Id: I3b0eb2103c89610ec494ac33407e8a7969af1164
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
2018-01-29 11:01:34 +08:00
Zhao Chao
b0577ae97e [api-ref] Update style and instances api.
Doc style:
* use tildes for heading 2 (following the rst convention);
* break source lines exceeded 79 characters (rst convention);
* remove unneccessary blank lines:
  * 4 blank lines between sections;
  * 2 blank lines between sub-sections;
  * 1 blank line between paragraphs in a section/subsection;
  * no blank lines at the bottom of a source file.
* add a space after commas in the middle of a line;

Instances API:
* change the order to match the description at the begin;
* add "Update instance name";
* add "Upgrade datastore version".

Change-Id: I3520e42f6ad97cb30632cf05241cec316409c9be
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
2018-01-25 22:55:13 +08:00
shangxiaobj
e54c46e312 [api-ref] Add fault names for the error response codes
Error response codes with fault names will be easier for understanding.

Change-Id: I5970cb6d40cf5793f024fd5d46b0da8f24bee0d6
2018-01-25 00:25:55 +00:00
Luke Browning
36926f39e6 Add support for MySQL 5.7 on Ubuntu Xenial
Ubuntu Trusty continues to get MySQL 5.6.

The selection of the MySQL version is based on the version
of Ubuntu that is installed.  If the script trovestack is
invoked on Xenial, the version that is chosen is 5.7.  If
it is invoked on Trusty, then version 5.6 is chosen.

The only thing that is eliminated is the dubious combination
of MySQL 5.6 on Ubuntu Xenial.  This combination is probably
not supported by Ubuntu as it is down level from their
standard offering is probably not tested anywhere.

Note Xenial does not provide the 5.6 version of mysql.  This
was accomplished by initializing the Apt repo with the
Trusty software repository.

The size of the root file system is increased from 3 to 4 GBs
as the Mysql Xenial image does not fit in 3 GBs. This has an
impact on the flavors that are used by Trove for testing as the
name of the flavor includes the size of the root file system.

This is turn caused a change to each of the db specific test
config files as the trove falvors are referenced in them.

Change-Id: I4f4e497208b8f4728580e48239a8ae208e0a96dd
2018-01-08 14:57:56 -06:00
liuqing
0427f2ef00 Trove user-delete API can use periods in user names in fact
I can create and delete a user named "mytest.abc" correctly both
with mysql-5.6 and mongodb-3.0, not as the details describe that
"Do not use periods in user names".

In addition, in order to create a mongodb database user in trove,
its format must be as "DBName.UserName". And, I can delete the users correctly!

Closes-Bug: #1652889
Change-Id: I2316943475b0bcfdb498733e221d2021b8a827a0
2017-05-18 07:23:53 +00:00
Amrith Kumar
49a6f565c1 unwedge the gate
This commit is a composite of two commits [1] and [2] to help unwedge
the gate. Both of them are required for the gate to possibly pass.

It introduces an unsafe change to unblock the gate temporarily. It
still needs to be debugged and addressed. The change in question is in
_remove_incompatible_context_args() in
trove/common/context.py. Without this check, initial tests indicate
that the system works as expected and testing locally is
successful. Why this is the case, I don't know yet but will
investigate in parallel.

[1] https://review.openstack.org/#/c/425857/
[2] https://review.openstack.org/#/c/423086/
[3] https://review.openstack.org/#/c/412497

From [1]

Fix a ``tox -eapi-ref`` warning

Currently, generating api-ref results in a warning that is treated as
an error.

See [1]. Since api-ref is now a jenkins voting gate, this needs to be
fixed.

[1] http://logs.openstack.org/56/401456/9/check/gate-trove-api-ref/e2e0d9d/console.html#_2017-01-26_17_23_10_952073

From [2]

SessionClient' object has no attribute 'user' Now gate py27 and py34
are being error:'SessionClient' object has no attribute 'user'" I
observed that this is because novaclient from 6.0.0 into 7.0.0 caused,
In novaclient 7.0.0,password and username is merge to auth[1],[2], I
tried to make a change, get password and username from auth[3].

[1]:https://github.com/openstack/python-novaclient/blob/6.0.0/novaclient/client.py#L164
[2]:https://github.com/openstack/python-novaclient/blob/7.0.0/novaclient/client.py#L147
[3]:https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/identity/generic/password.py#L37

Change-Id: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
Closes-Bug: #1657968
Co-Authored-By: Andrey Kurilin <akurilin@mirantis.com>
Co-Authored-By: jiansong <jian.song@easystack.cn>
Co-Authored-By: Tin Lam <tinlam@gmail.com>
Related: I45a40d599b3a302726dc21e409a8da26c9f1f741
Related: I93c1942bb41bd77ea169f0e47d37132ce5d3637d
Related: I41f4144821e491da689c188e25bc2b916867bdca
2017-01-29 18:37:11 -05:00
Jenkins
c1fd3e3a4c Merge "Fix backup of mysql variants on Centos" 2017-01-19 16:07:48 +00:00
Amrith Kumar
a7115e22f7 secure oslo_messaging.rpc
This is an interim commit of the changes for secure
oslo-messaging.rpc. In this commit we introduce the code for
serializers that will encrypt all traffic being sent on
oslo_messaging.rpc.

Each guest communicates with the control plane with traffic encrypted
using a per-instance key. This includes both traffic from the
taskmanager to the guest as well as the guest and the conductor.

Per-instance keys are stored in the infrastructure database. These
keys are further encrypted in the database.

Tests that got annoyed have been placated.

Upgrade related changes have been proposed. If an instance has no key,
no encryption is performed. If the guest gets no key, it won't
encrypt, just pass through. When an instance is upgraded, keys are
added.

The output of the trove show command (and the show API) have been
augmented to show which instances are using secure RPC communication
** if the requestor is an administrator **.

A simple caching mechanism for encryption keys has been proposed; this
will avoid the frequent database access to get the encryption
keys. For Ocata, to handle the upgrade case, None as an encryption_key
is a valid one, and is therefore not cached. This is why we can't use
something like lrucache.

A brief writeup has been included in dev docs
(dev/secure_oslo_messaging.rst) which shows how the feature can be
used and would help the documentation team write up the documentation
for this capability.

Change-Id: Iad03f190c99039fd34cbfb0e6aade23de8654b28
DocImpact: see dev/secure_oslo_messaging.rst
Blueprint: secure-oslo-messaging-messages
Related: If0146f08b3c5ad49a277963fcc685f5192d92edb
Related: I04cb76793cbb8b7e404841e9bb864fda93d06504
2017-01-11 07:56:35 -05:00
Jenkins
40762e266a Merge "Delete description of the disk" 2017-01-06 06:22:45 +00:00
Doug Shelley
f5d1caea88 Fix backup of mysql variants on Centos
The switch to XtraBackup 2.3 was causing an issue on RHEL/Centos
related to is using the "mysql" user instead of "trove". The fix on
Ubuntu was to move the os_admin credentials to ~trove/.my.cnf. While
this is a better place to write the credentials anyway (i.e. they
shouldn't be stored in server my.cnf) this doesn't solve the whole
issue on Centos. This commit changes the XB backup strategy to pass
the user/password in on the innobackupex command line.

Also, it was noticed that the "socket" option wasn't being specified
in the config.template. This is causing some client connections,
such as XB to fail connect because it can't locate the socket.
Forcing the server/client to write/read the socket from a known
location fixes this.

Change-Id: Iea941ce60179ef4dc5c403c2fc374cc8eb7d1617
Closes-bug: 1649592
2016-12-13 16:29:41 +00:00
Simon Chang
17ba7bc92e Add compute instance ID and volume ID to trove show output
The Compute ID (server_id) and Volume ID (volume_id)
associated with a trove instance are useful information
for an administrator. This commit add these fields to the
trove show output. They will only be visible to users
with admin rights.

Change-Id: I4a39b59ae610803f5aaf849f2e20ebb6e4ea1565
Closes-Bug: 1633581
2016-11-28 16:54:58 -05:00
Jenkins
48dcbb6dcd Merge "Multi-Region Support" 2016-11-18 15:50:39 +00:00
jiansong
f89ecc90d9 Delete description of the disk
Now,flavor-list can return disk property.So I think can delete this
description of disk

Change-Id: Ia0f9c5ec38ce6dc5171adee857b2e4078685cb7c
2016-11-17 03:58:07 +00:00
Jenkins
f2607bdfc2 Merge "[api-ref] configure LogABug feature" 2016-11-15 23:57:02 +00:00
Jenkins
9cd3a99e6b Merge "Remove unused parameters" 2016-11-15 23:52:10 +00:00
Morgan Jones
3f93ff110b Multi-Region Support
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: Petr Malik <pmalik@tesora.com>
Change-Id: I780de59dae5f90955139ab8393cf7d59ff3a21f6
2016-11-04 15:36:16 +00:00
Jenkins
25d668450b Merge "Config logABug feature for Trove api-ref" 2016-10-04 16:25:00 +00:00
KATO Tomoyuki
c1d2f3de52 [api-ref] configure LogABug feature
To report a bug into the trove project, not default openstack-manuals.

Change-Id: I8e1c16ab070541b00b92dc019ed86bbf71e56bb7
2016-09-27 23:44:17 +09:00
Kim Jensen
931b993063 Fixing trove config group request
Corrects the documentation of the create configuration group request.

Closes-Bug: #1627145
Change-Id: Id1624bcc1f0e79908d78fa62bfe76f00d68623da
2016-09-23 18:37:27 +00:00
jiansong
469bf6a647 Display flavor-ephemeral in trove flavor-list command
This commit adds ephemeral column to flavor-list

Change-Id: I537bc2f3578e1e99b22f701f70ab8d96fec8908e
Closes-Bug:1617980
2016-09-17 16:00:02 +00:00
Jenkins
f1136f723a Merge "[api-ref] Remove temporary block" 2016-09-12 13:48:35 +00:00
Jenkins
4b56d80e63 Merge "Update api-ref documentation" 2016-09-12 03:04:07 +00:00
Amrith Kumar
d797074053 Update api-ref documentation
This change updates the api-ref documentation with some issues
identified in an earlier review.

Change-Id: Ic769a1ae376e8569f5a13af8feada88f4cf0ac32
Closes-Bug: 1614923
Related: I3315261aa18729fa7a6aa79d4a1d6c24de1e2c6b
2016-09-09 20:05:23 +00:00
Jenkins
e33556c519 Merge "Display more flavor information in trove flavor-list command" 2016-09-07 19:39:20 +00:00
Ha Van Tu
b0170c04d2 [api-ref] Remove temporary block
The os-api-ref 1.0.0 is out. We can remove the support to older
version now.
Reference: https://github.com/openstack/senlin/commit/
6d41feb58dd836d426c9b6f025846dbbf7295097
https://review.openstack.org/#/c/362170/

Change-Id: I4a3697f7f43fdce0620d4faa16166078fe984c25
2016-09-07 12:20:14 +07:00
Ha Van Tu
fab422136b Remove unused parameters
This patch removes some parameters which are in parameters.yaml
but are not used in other *.inc files.

Change-Id: I202c182188a0cb276d1523991500d3576011da29
2016-09-06 17:03:44 +07:00
Amrith Kumar
193bcc6b70 Recent changes to api examples
Recent changes to api need to be reflected in api examples. This has
come to light because client 2.5.0 is now released.

Change-Id: I924cfd1ca93bef7f3dc79149519df10305390779
2016-08-31 11:08:45 -04:00
Ha Van Tu
07e0330de6 Config logABug feature for Trove api-ref
Currently, Trove api-ref is not configured with logABug feature.
When users click "Report bug" button, it leads to
"bugs.launchpad.net/openstack-manuals" which is default.
We should change it to "bugs.launchpad.net/trove/".

Change-Id: I90b37c3ef6b73daf2e05f253b9778ce548a38a1c
2016-08-31 12:39:05 +07:00
jiansong
6f6293f90d Display more flavor information in trove flavor-list command
This commit adds disk_space colmn to flavor-list

Change-Id: I71ca7ddbb6b835b5250bd2c4a0cb7ef4d72c9826
Closes-Bug:#1617987
2016-08-29 04:43:06 -07:00
Graham Hayes
cbd0f0f080 Get ready for os-api-ref sphinx theme change
Change-Id: I0325c1c42b2ea0b208547e902ff558b9be325d39
2016-08-19 16:44:03 +01:00
Amrith Kumar
3b0d1ea25d Adds the api-ref migrated RST + YAML files
With this email[0], you must migrate API reference docs into RST. The
conf.py and the tox environment are also cribbed from nova.

Still need to retain the install_command in tox.ini, otherwise the
api-ref job fails.

[0] http://lists.openstack.org/pipermail/openstack-dev/2016-May/093765.html

Co-Authored-By: Anne Gentle <agentle@cisco.com>
Co-Authored-By: Amrith Kumar <amrith@tesora.com>

Change-Id: I3315261aa18729fa7a6aa79d4a1d6c24de1e2c6b
2016-08-17 17:46:41 -04:00