This patch contains several changes to the documentation which were brought about by, initially, removing the webapi/v1 page and replacing it with a link to the /api-ref/ page. As I did that, I saw that our front page (index.html) needed to be updated as well, and decided that the front page needed to actually be completely rerwitten -- while preserving all the links. Some of the TOC links from the front page were malformed because subpages included more than one H1 heading, so I had to make small changes in the api-audit-support and code-contribution-guide and dev-quickstart pages, in order for the front page to render properly. As I corrected the headings on dev-quickstart, I realized the page was not comprehensively organized, and so decided to reorganize the sections and make it easier to navigate. Here is a bullet-point summary of this change: * Major changes to content and organization of index page * Moved the version history from webapi/v1 to dev/webapi-version-history * Added API conceptual guide at dev/webapi * Replaced webapi/v1 with a link to dev/webapi, in case anyone bookmarked it * Removed doc references to webapi/v1 * Merged the pages dev/contributing and dev/code-contribution-guide * Removed duplicate H1 headers in deploy/api-audit-support * Reorganized and renamed section headers in dev/dev-quickstart, and made some substantive corrections and changes as well * Updated wording at the top of the index and deploy/user-guide pages. Change-Id: Ib418e1d4fdfab4f0e15560270f39922e33df3f12
4.1 KiB
REST API Version History
1.22
Added endpoints for deployment ramdisks.
1.21
Add node
resource_class
field.
1.20
Add node
network_interface
field.
1.19
Add
local_link_connection
andpxe_enabled
fields to the port object.
1.18
Add
internal_info
readonly field to the port object, that will be used by ironic to store internal port-related information.
1.17
Addition of provision_state verb
adopt
which allows an operator to move a node frommanageable
state toactive
state without performing a deployment operation on the node. This is intended for nodes that have already been deployed by external means.
1.16
Add ability to filter nodes by driver.
1.15
Add ability to do manual cleaning when a node is in the manageable provision state via PUT v1/nodes/<identifier>/states/provision, target:clean, clean_steps:[...].
1.14
Make the following endpoints discoverable via Ironic API:
- '/v1/nodes/<UUID or logical name>/states'
- '/v1/drivers/<driver name>/properties'
1.13
Add a new verb
abort
to the API used to abort nodes inCLEANWAIT
state.
1.12
This API version adds the following abilities:
- Get/set
node.target_raid_config
and to getnode.raid_config
.- Retrieve the logical disk properties for the driver.
1.11 (breaking change)
Newly registered nodes begin in the
enroll
provision state by default, instead ofavailable
. To get them to theavailable
state, themanage
action must first be run to verify basic hardware control. On success the node moves tomanageable
provision state. Then theprovide
action must be run. Automated cleaning of the node is done and the node is madeavailable
.
1.10
Logical node names support all RFC 3986 unreserved characters. Previously only valid fully qualified domain names could be used.
1.9
Add ability to filter nodes by provision state.
1.8
Add ability to return a subset of resource fields.
1.7
Add node
clean_step
field.
1.6
Add
inspection
process: introduceinspecting
andinspectfail
provision states, andinspect
action that can be used when a node is inmanageable
provision state.
1.5
Add logical node names that can be used to address a node in addition to the node UUID. Name is expected to be a valid fully qualified domain name in this version of API.
1.4
Add
manageable
state andmanage
transition, which can be used to move a node tomanageable
state fromavailable
. The node cannot be deployed inmanageable
state. This change is mostly a preparation for future inspection work and introduction ofenroll
provision state.
1.3
Add node
driver_internal_info
field.
1.2 (breaking change)
Renamed NOSTATE (
None
in Python,null
in JSON) node state toavailable
. This is needed to reduce confusion aroundNone
state, especially when future additions to the state machine land.
1.1
This was the initial version when API versioning was introduced. Includes the following changes from Kilo release cycle:
- Add node
maintenance_reason
field and an API endpoint to set/unset the node maintenance mode.- Add sync and async support for vendor passthru methods.
- Vendor passthru endpoints support different HTTP methods, not only
POST
.- Make vendor methods discoverable via the Ironic API.
- Add logic to store the config drive passed by Nova.
This has been the minimum supported version since versioning was introduced.
1.0
This version denotes Juno API and was never explicitly supported, as API versioning was not implemented in Juno, and 1.1 became the minimum supported version in Kilo.