2016-04-12 09:03:46 -04:00
|
|
|
.. -*- rst -*-
|
2016-04-20 16:10:51 -04:00
|
|
|
.. needs:parameter_verification
|
|
|
|
.. needs:example_verification
|
|
|
|
.. needs:body_verification
|
2016-04-12 09:03:46 -04:00
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
|
2016-04-12 09:03:46 -04:00
|
|
|
==============================
|
|
|
|
Cells (os-cells, capacities)
|
|
|
|
==============================
|
|
|
|
|
|
|
|
Adds neighbor cells, lists neighbor cells, and shows the capabilities of
|
2017-04-04 22:14:13 -04:00
|
|
|
the local cell. By default, only administrators can manage cells.
|
|
|
|
|
|
|
|
.. note:: These APIs refer to a Cells v1 deployment which is optional and not
|
|
|
|
recommended for new deployments of Nova. These are not used with Cells v2
|
|
|
|
which is required beginning with the 15.0.0 Ocata release where all Nova
|
|
|
|
deployments consist of at least one Cells v2 cell.
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
List Cells
|
|
|
|
==========
|
|
|
|
|
2016-06-02 08:50:03 -04:00
|
|
|
.. rest_method:: GET /os-cells
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
Lists cells.
|
|
|
|
|
2016-04-19 20:47:03 +08:00
|
|
|
Normal response codes: 200
|
2016-04-12 09:03:46 -04:00
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
NotImplemented(501)
|
|
|
|
|
|
|
|
Request
|
|
|
|
-------
|
|
|
|
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
|
|
|
|
- tenant_id: tenant_id
|
2016-12-15 13:20:32 -05:00
|
|
|
- limit: limit_simple
|
|
|
|
- offset: offset_simple
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
|
|
|
|
.. TODO(cdent): How do we indicate optionality of a URI parameter?
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
Response
|
2016-04-14 13:10:59 -04:00
|
|
|
--------
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 17:52:18 +09:00
|
|
|
**Example List Cells: JSON response**
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
.. literalinclude:: ../../doc/api_samples/os-cells/cells-list-resp.json
|
|
|
|
:language: javascript
|
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Create Cell
|
|
|
|
===========
|
|
|
|
|
|
|
|
.. rest_method:: POST /os-cells
|
|
|
|
|
|
|
|
Create a new cell.
|
|
|
|
|
|
|
|
Normal response code: 200
|
|
|
|
|
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
NotImplemented(501)
|
|
|
|
|
|
|
|
.. TODO(cdent): need to figure out body stuff for request and response
|
|
|
|
|
|
|
|
.. TODO(cdent): need a sample
|
|
|
|
|
|
|
|
Capacities
|
|
|
|
==========
|
|
|
|
|
|
|
|
.. rest_method:: GET /os-cells/capacities
|
|
|
|
|
|
|
|
Retrieve capacities.
|
|
|
|
|
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
NotImplemented(501)
|
|
|
|
|
|
|
|
.. TODO(cdent): Need to do more digging, no idea.
|
|
|
|
|
2016-04-12 09:03:46 -04:00
|
|
|
List Cells With Details
|
|
|
|
=======================
|
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
.. rest_method:: GET /os-cells/detail
|
2016-04-12 09:03:46 -04:00
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Lists cells with details of capabilities.
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 20:47:03 +08:00
|
|
|
Normal response codes: 200
|
2016-04-12 09:03:46 -04:00
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
NotImplemented(501)
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-12-15 13:20:32 -05:00
|
|
|
Request
|
|
|
|
-------
|
|
|
|
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
|
|
|
|
- limit: limit_simple
|
|
|
|
- offset: offset_simple
|
|
|
|
|
2016-04-12 09:03:46 -04:00
|
|
|
Response
|
2016-04-14 13:10:59 -04:00
|
|
|
--------
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 17:52:18 +09:00
|
|
|
**Example List Cells With Details: JSON response**
|
2016-04-12 09:03:46 -04:00
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
.. TODO(cdent): This sample was initially list with an empty list of cells.
|
|
|
|
The newly listed sample does not yet exist.
|
|
|
|
|
|
|
|
.. TODO(cdent): literal-include: ../../doc/api_samples/os-cells/cells-list-details-resp.json
|
2016-04-12 09:03:46 -04:00
|
|
|
:language: javascript
|
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Info For This Cell
|
|
|
|
==================
|
|
|
|
|
|
|
|
.. rest_method:: GET /os-cells/info
|
|
|
|
|
|
|
|
Retrieve info about the current cell.
|
|
|
|
|
|
|
|
Normal response code: 200
|
|
|
|
|
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
NotImplemented(501)
|
|
|
|
|
2016-06-13 13:44:53 +08:00
|
|
|
.. TODO(cdent): this is weird, data is structured entirely differently.
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
|
2016-04-12 09:03:46 -04:00
|
|
|
Show Cell Data
|
|
|
|
==============
|
|
|
|
|
2016-06-02 08:50:03 -04:00
|
|
|
.. rest_method:: GET /os-cells/{cell_id}
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
Shows data for a cell.
|
|
|
|
|
2016-04-19 20:47:03 +08:00
|
|
|
Normal response codes: 200
|
2016-04-12 09:03:46 -04:00
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
itemNotFound(404), NotImplemented(501)
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
Request
|
2016-04-14 13:10:59 -04:00
|
|
|
-------
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
|
|
|
|
- cell_id: cell_id
|
|
|
|
|
|
|
|
Response
|
2016-04-14 13:10:59 -04:00
|
|
|
--------
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 17:52:18 +09:00
|
|
|
**Example Show Cell Data: JSON response**
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 20:47:03 +08:00
|
|
|
.. literalinclude:: ../../doc/api_samples/os-cells/cells-get-resp.json
|
2016-04-12 09:03:46 -04:00
|
|
|
:language: javascript
|
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Update a Cell
|
|
|
|
=============
|
|
|
|
|
|
|
|
.. rest_method:: PUT /os-cells/{cell_od}
|
|
|
|
|
|
|
|
|
|
|
|
Update an existing cell.
|
|
|
|
|
|
|
|
Normal response code: 200
|
|
|
|
|
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
itemNotFound(404), NotImplemented(501)
|
|
|
|
|
|
|
|
.. TODO(cdent): Figure out what's going on here.
|
|
|
|
|
|
|
|
Delete a Cell
|
|
|
|
=============
|
|
|
|
|
|
|
|
.. rest_method:: DELETE /os-cells/{cell_id}
|
|
|
|
|
|
|
|
Remove a cell.
|
|
|
|
|
|
|
|
Normal response code: 200
|
|
|
|
|
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
itemNotFound(404), NotImplemented(501)
|
|
|
|
|
2016-04-12 09:03:46 -04:00
|
|
|
Show Cell Capacities
|
|
|
|
====================
|
|
|
|
|
2016-06-02 08:50:03 -04:00
|
|
|
.. rest_method:: GET /os-cells/{cell_id}/capacities
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
Shows capacities for a cell.
|
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
.. TODO(cdent): What's a capacities.
|
|
|
|
|
2016-04-12 09:03:46 -04:00
|
|
|
Normal response codes: 200,501
|
|
|
|
|
api-ref method verification for os-cells
Confirm and correct list methods and response codes in os-cells.
This is mostly just checking, correcting and adding methods, but
in the process of doing that it became clear that there was quite
a bit missing so several TODO notes have been left in place so that
the next stages of work are a bit more obvious.
* 405 has been removed everywhere as we don't send that response
* 400 badRequest is required anywhere, as that's what you'll get if
tenant_id does not match the context's project_id
* 503 does not happen as there's no application controlled proxying
in this api
* the URL for listing cells with details was incorrect
* the example response for cells with details was an empty list,
this is now a todo suggesting an as yet non-existent file
* capacities was not listed, now is
* not clear what capacities really are, so a TODO
* creating a new cell (via POST) was not there, so that is now added
as a method
* for that POST, request and response bodies, parameters currently a
TODO
* Update (PUT) and DELETE of a cell has been added, but details are TODO
Part of bp:api-ref-in-rst
Change-Id: I3f123f821820e5a5a4deff61fb716d43dc486142
2016-05-26 18:41:06 +01:00
|
|
|
Error response codes: badRequest(400), unauthorized(401), forbidden(403),
|
|
|
|
itemNotFound(404), NotImplemented(501)
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
Request
|
2016-04-14 13:10:59 -04:00
|
|
|
-------
|
2016-04-12 09:03:46 -04:00
|
|
|
|
|
|
|
.. rest_parameters:: parameters.yaml
|
|
|
|
|
|
|
|
- cell_id: cell_id
|
|
|
|
|
|
|
|
Response
|
2016-04-14 13:10:59 -04:00
|
|
|
--------
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 17:52:18 +09:00
|
|
|
**Example Show Cell Capacities: JSON response**
|
2016-04-12 09:03:46 -04:00
|
|
|
|
2016-04-19 20:47:03 +08:00
|
|
|
.. literalinclude:: ../../doc/api_samples/os-cells/cells-capacities-resp.json
|
2016-04-12 09:03:46 -04:00
|
|
|
:language: javascript
|