Stop, Start or Restart a Compute Node
/paas/service/dbcs/api/v1.1/instances/{identityDomainId}/{serviceId}
Request
- application/vnd.com.oracle.oracloud.provisioning.Service+json
-
identityDomainId: string
The value depends on the type of Exadata Cloud Service account that is used to make the request:
For a Traditional Cloud Account, specify the
Identity Domain Name
that is associated with the service.For a Cloud Account with Identity Cloud Service, specify the
Identity Service Id
that is associated with the service, which has the formatidcs-letters-and-numbers
.
-
serviceId: string
Name of the Exadata Cloud Service database deployment, which uses the compute node you want to act on.
-
Authorization: string
Base64 encoding of the user name and password of the user making the request. For more information, see Security, Authentication and Authorization.
-
X-ID-TENANT-NAME: string
The value depends on the type of Exadata Cloud Service account that is used to make the request:
For a Traditional Cloud Account, specify the
Identity Domain Name
that is associated with the service.For a Cloud Account with Identity Cloud Service, specify the
Identity Service Id
that is associated with the service, which has the formatidcs-letters-and-numbers
.
For more information, see Security, Authentication and Authorization.
object
-
lifecycleState(optional):
string
The operation being performed:
stop
- Stop a running compute node.start
- Start a stopped compute node.restart
- Restart a running compute node.
-
lifecycleTimeout(optional):
string
The operation timeout for the request.
The range of valid values is
1
to300
minutes.The default is
60
minutes. -
vmName(optional):
string
Name of the compute node being acted on.
Response
202 Response
The Location header returns a REST URI that can be used to access the status of the operation, as described in View the Status of an Operation.
Examples
The following example shows how to stop a compute node associated with an Exadata Cloud Service instance by submitting a POST request on the REST endpoint using cURL.
In this example, the identity domain is usexample
and the Oracle Cloud user name and password are serviceadmin
and Pa55_word
. The name of the Exadata Cloud Service database instance being acted on is db12c
and the name of the compute node being stopped is node01.us2.oraclecloud.com
.
cURL Command
In the following cURL command, the request body is provided directly in the -d
option.
curl -i -X POST --cacert ~/cacert.pem -u serviceadmin:Pa55_word -H "X-ID-TENANT-NAME:usexample" -H "Content-Type:application/json" -d '{ "lifecycleState" : "stop", "vmName" : "node01.us2.oraclecloud.com" }' https://dbaas.oraclecloud.com/paas/service/dbcs/api/v1.1/instances/usexample/db12c
HTTP Status Code and Response Headers
HTTP/2.0 202 server: Oracle-Application-Server-11g strict-transport-security: max-age=31536000;includeSubDomains location: https://dbaas.oraclecloud.com:443/paas/service/dbcs/api/v1.1/instances/usexample/status/control/job/12209188 content-language: en access-control-allow-origin: * access-control-allow-headers: Content-Type, api_key, Authorization, X-ID-TENANT-NAME, X-USER-IDENTITY-DOMAIN-NAME retry-after: 30 access-control-allow-methods: GET, POST, DELETE, PUT, OPTIONS, HEAD x-oracle-dms-ecid: 005KA6x9wuw6uHFpR0H7id00067c00042A x-oracle-dms-ecid: 005KA6x9wuw6uHFpR0H7id00067c00042A service-uri: https://dbaas.oraclecloud.com:443/paas/service/dbcs/api/v1.1/instances/usexample/db12c x-frame-options: DENY content-type: application/json vary: user-agent date: Mon, 29 May 2017 04:01:17 GMT