summaryrefslogtreecommitdiff
path: root/api-ref/source/samples
Commit message (Collapse)AuthorAgeFilesLines
* Show user network ID for getting instanceLingxian Kong2021-08-024-4/+8
| | | | Change-Id: Ia1e9112ae69e04f8c3e9e9d1b4a0189c743d7448
* Support instance operating_statusLingxian Kong2020-12-096-13/+35
| | | | | | | Added a new field ``operating_status`` for the instance to show the actual operational status of user's database. Change-Id: I7c52cff0ec48289fe1a260e99e02a506d4f8ddec
* Support datastore version number for configurationLingxian Kong2020-11-224-7/+11
| | | | | | | Story: 2008358 Task: 41263 Change-Id: I529a07d50c0659af0c9821a8570f7548e8521805
* [API Doc] Support datastore version numberLingxian Kong2020-11-196-7/+14
| | | | | | Change-Id: Ia38f313a87067f664e11b3f61fb60b6ce584e930 Story: 2008358 Task: 41263
* Update quota API descriptionLingxian Kong2020-10-221-1/+2
| | | | Change-Id: Ia8d36dca81e2dd028b36289cb4547c1a8b88a1b1
* [Doc] Refine the root enable API descriptionLingxian Kong2020-09-131-0/+3
| | | | Change-Id: Id144c0c73b10550a8b8d636beece37578c0af124
* Support to update instance accessLingxian Kong2020-08-111-0/+8
| | | | Change-Id: I640cd8b50fd0e0f80a1a45399b8bfdac437ae2b9
* Support to rebuild instance by adminLingxian Kong2020-08-061-0/+5
| | | | Change-Id: I48f8c6f997daeb6d82ff62b3325277d86fee2147
* Support backup strategy APILingxian Kong2020-07-173-0/+24
| | | | Change-Id: I0ddd7214dae6e29ddfaf045fdb282f4980a8afff
* Doc: Fix configuration APILingxian Kong2020-06-162-17/+20
| | | | Change-Id: Ieff5200c220376f5927835f46c1b0a5a4f34052e
* Datastore containerizationLingxian Kong2020-05-271-2/+1
| | | | | | | | | | | | | Significant changes: * Using docker image to install datastore. * Datastore image is common to different datastores. * Using backup docker image to do backup and restore. * Support MariaDB replication * Set most of the functional jobs as non-voting as nested virtualization is not supported in CI. Change-Id: Ia9c97a63a961eebc336b70d28dc77638144c1834
* Remove flavor APILingxian Kong2020-04-276-88/+8
| | | | | | Uses should get flavor from Nova. Change-Id: Id26d71811f94cdcf4ff188c021d4ed5613eeb8cd
* Support ip address type for instancesLingxian Kong2020-04-264-0/+40
| | | | | | | | | | | | | | Include address type in getting instance response. * Deprecate confip option network_label_regex as we don't reply on Nova to get addresses, network names don't make any sense. * Add 'addresses' in instance API response, keep 'ip' as is but mark it deprecated in API doc, python-troveclient shouldn't break. Story: 2007562 Task: 39445 Change-Id: Ia0458b5ddae8959ce29c17e444e1a51a026283cd
* Improve API docLingxian Kong2019-12-24288-2624/+969
| | | | Change-Id: If48ef016c6fb7a875ceabc9f106e4cd85858d147
* Show service_status_updated in instance APILingxian Kong2019-12-181-2/+3
| | | | | | | | A new field named ``service_status_updated`` is added to the instance API response which e.g. could be used to validate if the instance 'HEALTHY' status is stale or not. Change-Id: Iabcfad81343a71304b843b3a7778486253220d20
* Support HEALTHY status for db instanceLingxian Kong2019-12-142-2/+2
| | | | | | | | | | | - 'HEALTHY' means the db service is responsive, 'ACTIVE' means the db service is alive. - Remove the CI job fakemodetests, but will add similar testing task in the future. - Fix the periodic CI job - Remove MongoDB and related jobs Change-Id: I5abe9091ba203297dc87db5fba139179166321f7
* Add quotas resource operation in API docLingxian Kong2019-12-112-0/+27
| | | | Change-Id: I2108f2c6bf067ce228829de9c4e7e47005acf358
* API doc: 'access' support for creating trove instanceLingxian Kong2019-09-111-25/+32
| | | | | | Story: 2006500 Task: 36471 Change-Id: Ie0c4ead89316001107c02450627eb5491ff8b521
* Remove flavor operations from API docLingxian Kong2019-06-066-296/+0
| | | | | | Trove doesn't need to expose resources directly from Nova. Change-Id: If705470330f51be9b78914ac2d456c62348c4329
* Return 204 instead of 200 for root-disable APIZhao Chao2018-03-021-1/+1
| | | | | | | | | | | | | | | | 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>
* [api-ref] Add sections for instance logs.Zhao Chao2018-01-2911-0/+103
| | | | | Change-Id: I3b0eb2103c89610ec494ac33407e8a7969af1164 Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
* [api-ref] Update style and instances api.Zhao Chao2018-01-252-0/+10
| | | | | | | | | | | | | | | | | | | | 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>
* Add support for MySQL 5.7 on Ubuntu XenialLuke Browning2018-01-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Merge "Fix backup of mysql variants on Centos"Jenkins2017-01-191-1/+2
|\
| * Fix backup of mysql variants on CentosDoug Shelley2016-12-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | secure oslo_messaging.rpcAmrith Kumar2017-01-114-2/+6
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Add compute instance ID and volume ID to trove show outputSimon Chang2016-11-284-4/+8
| | | | | | | | | | | 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
* Multi-Region SupportMorgan Jones2016-11-0414-7/+15
| | | | | | | | | | 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
* Fixing trove config group requestKim Jensen2016-09-231-8/+4
| | | | | | | Corrects the documentation of the create configuration group request. Closes-Bug: #1627145 Change-Id: Id1624bcc1f0e79908d78fa62bfe76f00d68623da
* Display flavor-ephemeral in trove flavor-list commandjiansong2016-09-174-2/+16
| | | | | | | This commit adds ephemeral column to flavor-list Change-Id: I537bc2f3578e1e99b22f701f70ab8d96fec8908e Closes-Bug:1617980
* Merge "Display more flavor information in trove flavor-list command"Jenkins2016-09-074-15/+29
|\
| * Display more flavor information in trove flavor-list commandjiansong2016-08-294-15/+29
| | | | | | | | | | | | | | This commit adds disk_space colmn to flavor-list Change-Id: I71ca7ddbb6b835b5250bd2c4a0cb7ef4d72c9826 Closes-Bug:#1617987
* | Recent changes to api examplesAmrith Kumar2016-08-313-3/+5
|/ | | | | | | 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
* Adds the api-ref migrated RST + YAML filesAmrith Kumar2016-08-17245-0/+3170
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
View Lorry Controller Status