Adds API for retrieving node history events
via a node. Includes pagination and limitation
of the response set.
Story: 2002980
Tas: 42961
Change-Id: I22a92fa6c30d721f6a5dd0670b2e0a9cf76ad7b1
Currently we default to assuming the cache is up-to-date. This is likely
wrong. Normal web servers provide Last Modified for files they serve.
If it is absent, chances are high the image is served by some sort
of a dynamic service, which may modify the URL on fly.
In any case, always updating the image is a safer choice.
Change-Id: I0548db14a97638d26ebb687e8f47f1b295d1f774
Implements clean step "clear_ca_certificates" to remove any 3rd party
expired/revoked CA certificates from iLO.
Change-Id: I0a3c1da9b94e4037a53ade100354ac51ca08db35
Story: #2008784
Task: #42175
This commit fix a typo in the destination parameter
in tests and in doc, also including documentation
abou the subscription methods available via
vendor passthru.
Change-Id: Ifa82562d2ce8f34bd90dc5897a3b83fe9e8eb88b
Update the documentation of IRMC according to the changes of python-scciclient v0.10.0
Signed-off-by: Zhou Hao <zhouhao@fujitsu.com>
Change-Id: Ic4c359a1b489fb1e6f37759013b66f7eadaf0765
This commit add support for the fields query parameter to the GET /v1/drivers?fields=... and GET /v1/drivers/<driver_name>?fields=....
Story: 1674775
Task: 10581
Change-Id: I2ca4eb490e320e736a93851eed526ec862be901e
Add some notes on potential UDP packet loss during conductor/BMC
power sync with IPMI, the corresponding increase in retries and
how to mitigate.
Change-Id: I4bc9a8f6f7f4da7f719a65f76ae97b1244701ee9
The database schema upgrade check had support for an
explicit list of known versions to handle the upgrade.
who knew!
Anyhow, we haven't used it in three years since the addition,
and it seems to make more sense to just be able to indicate
"we know initial field versions may not be able to be retrieved
and act accordingly". As such, when no table is found, the
pre-upgrade version check execution will continue onward fearlessly!
Call it a spiritual successor to Ibcf0728bc5d1b0cbdd78796526f9c93fc99e8c08
Change-Id: Icae5162c2501b0d1217ad0e6ee34ebef40e95204
Explaing which cipher suites must be used and how to pre-configure the
BMC. Also explain the privilege levels.
Change-Id: I93845ac9dd068b0ddb52693afe4993804857e5ea
The devstack default limit enforcement for glance defaults
to 1GB, and unfortunately this is too small for many to use
larger images such as centos which includes hardware firmware
images for execution on baremetal where drivers need the vendor
blobs in order to load/run.
Sets ironic-base to 5GB, and updates examples accordingly.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/801309
Change-Id: I41294eb571d07a270a69e5b816cdbad530749a94
Add documentation for the CPU, memory, disk, and network burn-in
cleaning steps to the admin guide.
Change-Id: Ide8061f96eeb303490f06ebf31d2f2e6be93d0d1
Move the descriptions of the BIOS registry fields in the API to
a new section in the Redfish documentation.
Change-Id: Ifedb4526113bb84ccc598e13f5767b71a60f5532
Re-uses the force_persistent_boot_device driver_info option
which can be set to ``Never`` in order to set the virtual
media to one time boot.
Story: 2009042
Task: 42805
Change-Id: Ida7adb3c02db6279ef934797614eaa7be1f35daa
* add fields to Node object
* expose them at endpoint `/v1/nodes/{node_ident}/states`
* update states on powersync / entering managed state.
* tests
* update api endpoint info in api-ref
Story: 2008567
Task: 41709
Change-Id: Iddd1421a6fa37d69da56658a2fefa5bc8cfd15e4
Configuraiton drives get stored in the instance_info field which
is of a text type, which in theory is not a big deal, however large
configuration drives are returned over the database client
and when entire node objects are generated by the client, which
has an obvious bandwidth and record transfer latency overhead.
Change-Id: I7f2b6ab9c3adf88202f213a42af7553cf9e8276d
Add a section to the docs how to handle grub reinstallations
with Ironic software RAID on BIOS nodes, e.g. during disk
replacements.
Change-Id: I2c1d1a61a3340f6785ab6f63cb96f2c045f8eabe
Because of the way validation works, the ramdisk deploy interface
currently requires an image_source in addition to kernel/ramdisk.
After 1d6441cc347cfe984721f34ebb0cd64fd9e4d876 it is no longer
necessary, and this change removes this requirement.
Change-Id: I59996fac059dade0ef186598be1e8971e073eb04