By default ironic-inspector listens on 0.0.0.0:5050
, port
can be changed in configuration. Protocol is JSON over HTTP.
POST /v1/introspection/<Node ID>
initiate hardware introspection for node
<Node ID>
. All power management configuration for this node needs to be
done prior to calling the endpoint.
Requires X-Auth-Token header with Keystone token for authentication.
Response:
GET /v1/introspection/<Node ID>
get hardware introspection status.
Requires X-Auth-Token header with Keystone token for authentication.
Response:
Response body: JSON dictionary with keys:
finished
(boolean) whether introspection is finished
(true
on introspection completion or if it ends because of an error)state
state of the introspectionerror
error string or null
; Canceled by operator
in
case introspection was aborteduuid
node UUIDstarted_at
a UTC ISO8601 timestampfinished_at
a UTC ISO8601 timestamp or null
links
containing a self URLGET /v1/introspection
get all hardware introspection statuses.
Requires X-Auth-Token header with Keystone token for authentication.
Returned status list is sorted by the started_at, uuid
attribute pair,
newer items first, and is paginated with these query string fields:
marker
the UUID of the last node returned previouslylimit
default, max: CONF.api_max_limit
Response:
Response body: a JSON object containing a list of status objects:
{
'introspection': [
{
'finished': false,
'state': 'waiting',
'error': null,
...
},
...
]
}
Each status object contains these keys:
finished
(boolean) whether introspection is finished
(true
on introspection completion or if it ends because of an error)state
state of the introspectionerror
error string or null
; Canceled by operator
in
case introspection was aborteduuid
node UUIDstarted_at
an UTC ISO8601 timestampfinished_at
an UTC ISO8601 timestamp or null
POST /v1/introspection/<Node ID>/abort
abort running introspection.
Requires X-Auth-Token header with Keystone token for authentication.
Response:
GET /v1/introspection/<Node ID>/data
get stored data from successful
introspection.
Requires X-Auth-Token header with Keystone token for authentication.
Response:
Response body: JSON dictionary with introspection data
Note
We do not provide any backward compatibility guarantees regarding the format and contents of the stored data. Notably, it depends on the ramdisk used and plugins enabled both in the ramdisk and in inspector itself.
POST /v1/introspection/<Node ID>/data/unprocessed
to trigger
introspection on stored unprocessed data. No data is allowed to be
sent along with the request.
Requires X-Auth-Token header with Keystone token for authentication. Requires enabling Swift store in processing section of the configuration file.
Response:
See rules for details.
All these API endpoints require X-Auth-Token header with Keystone token for authentication.
POST /v1/rules
create a new introspection rule.
Request body: JSON dictionary with keys:
conditions
rule conditions, see rulesactions
rule actions, see rulesdescription
(optional) human-readable descriptionuuid
(optional) rule UUID, autogenerated if missingResponse
Response body: JSON dictionary with introspection rule representation (the same as above with UUID filled in).
GET /v1/rules
list all introspection rules.
Response
Response body: JSON dictionary with key rules
- list of short rule
representations. Short rule representation is a JSON dictionary with keys:
uuid
rule UUIDdescription
human-readable descriptionlinks
list of HTTP links, use one with rel=self
to get the full
rule detailsDELETE /v1/rules
delete all introspection rules.
Response
GET /v1/rules/<UUID>
get one introspection rule by its <UUID>
.
Response
Response body: JSON dictionary with introspection rule representation
(see POST /v1/rules
above).
DELETE /v1/rules/<UUID>
delete one introspection rule by its <UUID>
.
Response
POST /v1/continue
internal endpoint for the ramdisk to post back
discovered data. Should not be used for anything other than implementing
the ramdisk. Request body: JSON dictionary with at least these keys:
inventory
full hardware inventory from the ironic-python-agent with at
least the following keys:
memory
memory information containing at least key physical_mb
-
physical memory size as reported by dmidecode,cpu
CPU information containing at least keys count
(CPU count) and
architecture
(CPU architecture, e.g. x86_64
),bmc_address
IP address of the node’s BMC,interfaces
list of dictionaries with the following keys:name
interface name,ipv4_address
IPv4 address of the interface,mac_address
MAC (physical) address of the interface.client_id
InfiniBand Client-ID, for Ethernet is None.disks
list of disk block devices containing at least name
and
size
(in bytes) keys. In case disks
are not provided
ironic-inspector assumes that this is a disk-less node.root_disk
default deployment root disk as calculated by the
ironic-python-agent algorithm.
Note
ironic-inspector default plugin root_disk_selection
may change
root_disk
based on root device hints if node specify hints via
properties root_device
key. See Specifying the disk for deployment
root device hints for more details.
boot_interface
MAC address of the NIC that the machine PXE booted from
either in standard format 11:22:33:44:55:66
or in PXELinux BOOTIF
format 01-11-22-33-44-55-66
. Strictly speaking, this key is optional,
but some features will now work as expected, if it is not provided.
Optionally the following keys might be provided:
error
error happened during ramdisk run, interpreted by
ramdisk_error
plugin.logs
base64-encoded logs from the ramdisk.Note
This list highly depends on enabled plugins, provided above are expected keys for the default set of plugins. See plugins for details.
Note
This endpoint is not expected to be versioned, though versioning will work on it.
Response:
Response body: JSON dictionary with uuid
key.
If an error happens during request processing, Ironic Inspector returns a response with an appropriate HTTP code set, e.g. 400 for bad request or 404 when something was not found (usually node in cache or node in ironic). The following JSON body is returned:
{
"error": {
"message": "Full error message"
}
}
This body may be extended in the future to include details that are more error specific.
The API supports optional API versioning. You can query for minimum and maximum API version supported by the server. You can also declare required API version in your requests, so that the server rejects request of unsupported version.
Note
Versioning was introduced in Ironic Inspector 2.1.0.
All versions must be supplied as string in form of X.Y
, where X
is a
major version and is always 1
for now, Y
is a minor version.
If X-OpenStack-Ironic-Inspector-API-Version
header is sent with request,
the server will check if it supports this version. HTTP error 406 will be
returned for unsupported API version.
All HTTP responses contain
X-OpenStack-Ironic-Inspector-API-Minimum-Version
and
X-OpenStack-Ironic-Inspector-API-Maximum-Version
headers with minimum
and maximum API versions supported by the server.
Note
Maximum is server API version used by default.
The API supports API discovery. You can query different parts of the API to discover what other endpoints are avaliable.
GET /
List API Versions
Response:
Response body: JSON dictionary containing a list of versions
, each
version contains:
status
Either CURRENT or SUPPORTEDid
The version identifierlinks
A list of links to this version endpoint containing:href
The URLrel
The relationship between the version and the hrefGET /v1
List API v1 resources
Response:
Response body: JSON dictionary containing a list of resources
, each
resource contains:
name
The name of this resourceslinks
A list of link to this resource containing:href
The URLrel
The relationship between the resource and the hrefExcept where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.