Resolves D000 and D001 checks in sahara docs. Change-Id: If6d577859170ae55d578d70885a9ed5a6b0db651 Closes-Bug: #1514887
3.0 KiB
Sahara REST API v1.1
1 General API information
This section contains base info about the sahara REST API design.
1.1 Authentication and Authorization
The sahara API uses the OpenStack Identity service as the default
authentication service. When the Identity service is enabled, users who
submit requests to the sahara service must provide an authentication
token in the X-Auth-Token
request header. A user can obtain
the token by authenticating to the Identity service endpoint. For more
information about the Identity service, please see the keystone project
developer documentation
With each request, a user must specify the OpenStack tenant(now known as project) in the url path, for example: '/v1.1/{tenant_id}/clusters'. Sahara will perform the requested operation in the specified tenant using the provided credentials. Therefore, clusters may be created and managed only within tenants to which the user has access.
1.2 Request / Response Types
The sahara API supports the JSON data serialization format. This
means that for requests that contain a body, the
Content-Type
header must be set to the MIME type value
application/json
. Also, clients should accept JSON
serialized responses by specifying the Accept
header with
the MIME type value application/json
or adding the
.json
extension to the resource name. The default response
format is application/json
if the client does not specify
an Accept
header or append the .json
extension
in the URL path.
Example:
GET /v1.1/{tenant_id}/clusters.json
or
GET /v1.1/{tenant_id}/clusters
Accept: application/json
1.3 Faults
The sahara API returns an error response if a failure occurs while processing a request. Sahara uses only standard HTTP error codes. 4xx errors indicate problems in the particular request being sent from the client and 5xx errors indicate server-side problems.
The response body will contain richer information about the cause of the error. An error response follows the format illustrated by the following example:
HTTP/1.1 400 BAD REQUEST
Content-type: application/json
Content-length: 126
{
"error_name": "CLUSTER_NAME_ALREADY_EXISTS",
"error_message": "Cluster with name 'test-cluster' already exists",
"error_code": 400
}
The error_code
attribute is an HTTP response code. The
error_name
attribute indicates the generic error type
without any concrete ids or names, etc. The last attribute,
error_message
, contains a human readable error
description.
2 API
- Sahara REST API Reference (OpenStack API Complete Reference - DataProcessing) .. _`Sahara REST API Reference (OpenStack API Complete Reference - DataProcessing)`: http://api.openstack.org/api-ref-data-processing-v1.1.html