From a0a10f0b947c63ac06787b490afd0ebecef1477e Mon Sep 17 00:00:00 2001 From: Lingxian Kong Date: Thu, 12 Dec 2019 00:26:09 +1300 Subject: Support HEALTHY status for db instance - '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 --- api-ref/source/database-instances.inc | 14 ++------------ .../source/samples/db-instance-status-detail-response.json | 2 +- api-ref/source/samples/db-instances-index-response.json | 2 +- 3 files changed, 4 insertions(+), 14 deletions(-) (limited to 'api-ref') diff --git a/api-ref/source/database-instances.inc b/api-ref/source/database-instances.inc index 58a40088..fa48ecb6 100644 --- a/api-ref/source/database-instances.inc +++ b/api-ref/source/database-instances.inc @@ -53,22 +53,12 @@ Shows database instance details. Lists the status and details of the database instance. Lists the volume size in gigabytes (GB) and the approximate GB -used. - -After instance creation, the ``used`` value is greater than 0, which +used. After instance creation, the ``used`` value is greater than 0, which is expected as databases may create some basic (non empty) files to represent an empty schema. The response does not include the ``used`` attribute when the instance status is ``BUILD``, ``REBOOT``, ``RESIZE``, or ``ERROR``. -The list operations return a DNS-resolvable host name for the -database instance rather than an IP address. Because the host name -always resolves to the correct IP address for the database -instance, you do not need to maintain the mapping. Although the IP -address might change when you resize, migrate, or perform other -operations, the host name always resolves to the correct database -instance. - Normal response codes: 200 Error response codes: badRequest(400), unauthorized(401), forbidden(403), @@ -380,7 +370,7 @@ Upgrade datastore version Upgrade datastore version. During datastore version upgrading, the instance status change to ``UPGRADE``, -and changes back to ``ACTIVE`` after upgrading finishes, otherwize changes to +and changes back to ``HEALTHY`` after upgrading finishes, otherwize changes to ``ERROR`` if the upgrading fails. Normal response codes: 202 diff --git a/api-ref/source/samples/db-instance-status-detail-response.json b/api-ref/source/samples/db-instance-status-detail-response.json index eacb3fc4..d69ed5df 100644 --- a/api-ref/source/samples/db-instance-status-detail-response.json +++ b/api-ref/source/samples/db-instance-status-detail-response.json @@ -32,7 +32,7 @@ ], "name": "json_rack_instance", "region": "RegionOne", - "status": "ACTIVE", + "status": "HEALTHY", "updated": "2014-10-30T12:30:00", "volume": { "size": 2, diff --git a/api-ref/source/samples/db-instances-index-response.json b/api-ref/source/samples/db-instances-index-response.json index 341308ea..ed401281 100644 --- a/api-ref/source/samples/db-instances-index-response.json +++ b/api-ref/source/samples/db-instances-index-response.json @@ -32,7 +32,7 @@ ], "name": "json_rack_instance", "region": "RegionOne", - "status": "ACTIVE", + "status": "HEALTHY", "volume": { "size": 2 } -- cgit v1.2.1