8 Commits

Author SHA1 Message Date
Lingxian Kong
94dd0bd2b7 API doc: 'access' support for creating trove instance
Story: 2006500
Task: 36471
Change-Id: Ie0c4ead89316001107c02450627eb5491ff8b521
2019-09-11 20:45:20 +12:00
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
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
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
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
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