[api-ref] Refactor share export location API documentation

This patch make share export location documentation be readable
and maintainable.

Change-Id: I9a43ef525b8c16941df99fe54c0d5483dcb2ed4b
This commit is contained in:
Ha Van Tu 2016-12-27 12:57:00 +07:00
parent f427dfe00b
commit a42c08e797
2 changed files with 114 additions and 33 deletions

View File

@ -44,7 +44,7 @@ consistency_group_id_7:
in: path in: path
required: true required: true
type: string type: string
export_location_id: export_location_id_path:
description: | description: |
The UUID of the export location. The UUID of the export location.
in: path in: path
@ -476,12 +476,12 @@ access_list:
type: string type: string
access_rules_status: access_rules_status:
description: | description: |
(Since API v2.10) The share instance access rules The share instance access rules status. Valid value are ``active``,
status. Valid value are ``active``, ``error``, and ``error``, and ``out_of_sync``.
``out_of_sync``.
in: body in: body
required: true required: true
type: string type: string
min_version: 2.10
access_rules_status_1: access_rules_status_1:
description: | description: |
(Since API v2.10) The share access rules status. (Since API v2.10) The share access rules status.
@ -1330,26 +1330,101 @@ driver_version:
type: string type: string
export_location: export_location:
description: | description: |
(Only for API v1.0-2.8) The export location. For The export location. For newer API versions it is available in
newer API versions it is available in separate APIs. See separate APIs. See sections `Share export locations
sections `Share export locations <#share-share-export-locations>`_ <#share-share-export-locations>`_ and `Share instance export
and `Share instance export locations <#share-share-instance- locations <#share-share-instance-export- locations>`_.
export- locations>`_.
in: body in: body
required: false required: false
type: string type: string
max_version: 2.8
export_location_created_at:
description: |
The date and time stamp when the share export location was
created.
The date and time stamp format is `ISO 8601
<https://en.wikipedia.org/wiki/ISO_8601>`_:
::
CCYY-MM-DDThh:mm:ss±hh:mm
The ``±hh:mm`` value, if included, returns the time zone as an
offset from UTC.
For example, ``2016-12-31T13:14:15-05:00``.
in: body
required: true
type: string
export_location_id:
description: |
The share export location UUID.
in: body
required: true
type: string
export_location_is_admin_only:
description: |
Defines purpose of an export location. If set to
``true``, then it is expected to be used for service needs and by
administrators only. If it is set to ``false``, then this export
location can be used by end users.
in: body
required: true
type: boolean
export_location_path:
description: |
The export location path that should be used for mout operation.
in: body
required: true
type: string
export_location_preferred:
description: |
Drivers may use this field to identify which export locations
are most efficient and should be used preferentially by clients.
By default it is set to ``false`` value.
in: body
required: true
type: boolean
min_version: 2.14
export_location_share_instance_id:
description: |
The UUID of the share instance that this
export location belongs to.
in: body
required: true
type: string
export_location_updated_at:
description: |
The date and time stamp when the share export location was
updated.
The date and time stamp format is `ISO 8601
<https://en.wikipedia.org/wiki/ISO_8601>`_:
::
CCYY-MM-DDThh:mm:ss±hh:mm
The ``±hh:mm`` value, if included, returns the time zone as an
offset from UTC.
For example, ``2016-12-31T13:14:15-05:00``.
in: body
required: true
type: string
export_locations: export_locations:
description: | description: |
(Only for API v1.0-2.8) A list of export A list of export locations. For example, when a share server
locations. For example, when a share server has more than one has more than one network interface, it can have multiple export
network interface, it can have multiple export locations. For locations. For newer API versions it is available in separate APIs.
newer API versions it is available in separate APIs. See See sections `Share export locations <#share-share-export-locations>`_
sections `Share export locations <#share-share-export-locations>`_
and `Share instance export locations <#share-share-instance- and `Share instance export locations <#share-share-instance-
export- locations>`_. export- locations>`_.
in: body in: body
required: false required: false
type: array type: array
max_version: 2.8
export_path: export_path:
description: | description: |
The share export path in the format appropriate The share export path in the format appropriate
@ -1983,13 +2058,19 @@ os-share-type-access:is_public:
in: body in: body
required: false required: false
type: boolean type: boolean
path: export_location_path:
description: | description: |
The export location path that should be used for The export location path that should be used for
mount operation. mount operation.
in: body in: body
required: true required: true
type: string type: string
path:
description: |
The export location path that should be used for mout operation.
in: body
required: true
type: string
pool: pool:
description: | description: |
The pool name for the back end. The pool name for the back end.
@ -2007,13 +2088,13 @@ pools:
type: string type: string
preferred: preferred:
description: | description: |
(Since API v2.14) Drivers may use this field to Drivers may use this field to identify which export locations
identify which export locations are most efficient and should be are most efficient and should be used preferentially by clients.
used preferentially by clients. By default it is set to ``false`` By default it is set to ``false`` value.
value.
in: body in: body
required: true required: true
type: boolean type: boolean
min_version: 2.14
project: project:
description: | description: |
The UUID of the project to which access to the The UUID of the project to which access to the

View File

@ -27,18 +27,18 @@ Request
.. rest_parameters:: parameters.yaml .. rest_parameters:: parameters.yaml
- share_id: share_id - share_id: share_id
- tenant_id: tenant_id_1 - tenant_id: tenant_id_path
Response parameters Response parameters
------------------- -------------------
.. rest_parameters:: parameters.yaml .. rest_parameters:: parameters.yaml
- id: id_5 - id: export_location_id
- share_instance_id: share_instance_id_1 - share_instance_id: export_location_share_instance_id
- path: path - path: export_location_path
- is_admin_only: is_admin_only - is_admin_only: export_location_is_admin_only
- preferred: preferred - preferred: export_location_preferred
Response example Response example
---------------- ----------------
@ -64,7 +64,7 @@ Request
.. rest_parameters:: parameters.yaml .. rest_parameters:: parameters.yaml
- share_id: share_id - share_id: share_id
- tenant_id: tenant_id_1 - tenant_id: tenant_id_path
- export_location_id: export_location_id - export_location_id: export_location_id
Response parameters Response parameters
@ -72,13 +72,13 @@ Response parameters
.. rest_parameters:: parameters.yaml .. rest_parameters:: parameters.yaml
- id: id_5 - id: export_location_id
- share_instance_id: share_instance_id_1 - share_instance_id: export_location_share_instance_id
- path: path - path: export_location_path
- is_admin_only: is_admin_only - is_admin_only: export_location_is_admin_only
- preferred: preferred - preferred: export_location_preferred
- created_at: created_at_5 - created_at: export_location_created_at
- updated_at: updated_at_2 - updated_at: export_location_updated_at
Response example Response example
---------------- ----------------