Follow up of fa0c3e75acd17b72d1e8e05712989ff1e55b232d. Ilo
doc is updated with clarification on swift url scheme.
Change-Id: Icf6603800d7d23bcd07c1cde0cadf3f742454e32
After IPA has completed a cleaning step such as upgrading firmware, it
may require a reboot. Ironic should be the one controlling the power
state and out of band reboots are preferable to in band reboots.
Change-Id: Iee3aeea198c556ab9adb9dcfd949d9cffb51418c
Co-Authored-By: Josh Gachnang <josh@servercobra.com>
Closes-bug: 1526918
Added the documentation to enable HTTPS endpoint in
glance for enabling secure communication between
Ironic and Glance.
Related-Bug: #1548086
Change-Id: I7e7f98e6d5281ef030a35f29a10eab753e8a8568
Removed note that indicated agent drivers do not support
deploying partition images.
Updated iLO documentation indicating support for partition
images for agent_ilo driver.
Change-Id: I2349604344328222db5b981fa9d75523d21a5186
The patch is adding a new property called "deploy_forces_oob_reboot"
for the Agent deployment methodology. If the property is specified in
the node's driver_info with the value of True, Ironic will call IPA to
flush the file system and then issue a out-of-band reboot at the end of
the deployment to the node to boot into the user's image.
Some hardware/firmware may have problems doing a power off in-band
(usually faulty hardware/bad firmware, see the bug this commit is fixing)
therefore we need Ironic to do it directly in the BMC.
This patch also closes one more consistency gap between the IPA deploy
model and the now deprecated bash ramdisk one which used the hard reboot
to finish the deployment by default.
Depends-On: I5cd1d1b821426e995dc584452494b93ab23917e0
Closes-Bug: #1512492
Change-Id: I5e389c5245826f86466aedfcb9730117e24b59db
Updated following under section "Understanding Bare Metal
Deployment"
changed "compute node" to "Bare Metal service node(s) where
ironic-conductor is running"
Change-Id: I434b7f71dd83ea544cca12a7de29f2ad2410b174
Closes-Bug: #1544419
Added the documentation for firmware update through iLO as a
manual clean step. It also serves as a user guidance on proper
usage of initiating firmware update as the manual clean step.
Related-Bug: #1526216
Change-Id: Ibcbbe1330df818705c4de33325878f5c816fe1d7
This patch updates OneView driver documentation with requirements
to run the driver with the DL Servers, minimun version of iLO and
Redfish that was not mentioned before.
Change-Id: I0f2a347c1fc94f1ed23e32a85f2175e960550a03
There was a typo in the command demonstrating how to change the IPMI
protocol version (an extra "t" in the parameter's name). This patch is
fixing that typo and making the command an one-liner to facilitate the
copy and paste.
Change-Id: I8a7bf5e51eb545944cdb7343c9263b75cc358dd1
This patch extending the current Install guide documentation to include
information about how one could request a specific disk label when
deploying a bare metal node.
Related-Bug: #1548788
Change-Id: Ib6d31a66db3e647abdb507f4741c64e99cd209e4
This patch is adding the documentation for the IPMITool driver. This
covers some general overview, basic setup (prerequisites, how to enable)
as well as some advanced topics such as single/double bridge and protocol
version.
The IPMITool driver is rich and allows a lot of configuration, therefore
not all topics are addressed by this commit. TODOs were left in the
documentation (as comments) so we don't forget to address them later.
Partial-Bug: #1468710
Change-Id: Ife99de75a42d7048fd1ad31e220b5606a8fe81f0
This patch removes 'grub2' option for disk-image-crate command
with 'whole disk images'. Current ironic can only support grub2
configuration when using partition image.
Change-Id: I748e10b76f6a31464590cf94bd28af20e35b6b04
This patch updates the document, "Administrator's Guide | Enabling
drivers | iRMC", by reflecting the changes made in "Add hardware
inspection module for iRMC driver" [1].
[1] commit 37590a86338e94845c74e1b1f7d8d6f61003d447
Change-Id: I38d16b4071a6661412ebaeff5eb0c0439ddc8ec0
Closes-Bug: #1525108
By default DEFAULT_INSTANCE_TYPE is not set. As result when tempest is
enabled default Nova flavors are used. To use 'baremetal' flavor
DEFAULT_INSTANCE_TYPE should be set to 'baremetal' as is done on gate job.
Otherwise running BaremetalBasicOps test locally will fail.
Change-Id: I1294b1dc7bf4fa32f9cdeb7a8c22667a76929ded
This updates the iLO documentation to indicate that clean step
'reset_ilo' is disabled by default.
Change-Id: I8dae0caaede45ff4dd8b5bf3a4c00737dab7a16b
Closes-Bug: 1542977
This patch updates the documentation with new supported Server Hardware class
(DL360 Gen9) and recommendations about installing python-oneviewclient to
enable the support.
This patch also corrects a misleading minimum version of python-oneviewclient on
L57.
Change-Id: I97460bfbd5467496ba3b21fbca55249b31d88d5c
ImcSdk is now available on PyPi, driver_requirements.txt was updated to
reflect this, but the Ironic driver doc was brought up to date, this
patch fixes that.
Change-Id: Ib9195d50f0a208a814e13d859cadd577d05aed54
Closes-Bug: #1552720
This commit updates the proliantutils version required in
Ironic to 2.1.7 for Mitaka release. This version of
proliantutils includes changes to NIC info and firmware
version retrieval logic.
Change-Id: Ieacfb2555bce0fc1f2542ddc837c6c67347fd891
While discovering the capabilities of the baremetal server using
iLO drivers, to support the capability "nic_capacity", it is
recommended to use ipmitool version >= 1.8.15
Closes-Bug: #1540842
Change-Id: I6d72a6e36672b8e164f779c5987457ff2e538958
This commit updates the proliantutils version required in Ironic
to 2.1.6 for Mitaka release. This version of proliantutils
includes defect fixes and feature enablement related to iLO based
firmware upgrade.
Change-Id: Ic895dcbf70fa0cc02d49e17bc8e9d2de40ab9ec8
This change switches the conductor to using Futurist library executor and
periodic tasks worker instead of oslo.service periodic tasks. This allows
running periodic tasks in parallel and relying on more standard interfaces
(futures, executors) when dealing with asynchronous execution.
A green thread executor is used instead of using an eventlet green pool
directly. The maximum number of workers is taken from the existing
workers_pool_size configuration option, and no tasks are allowed
to be enqueued to mimic the previous behaviour (might be lifted later).
The periodic tasks worker is using the same executor, and its main loop thread
is also running on it. For this reason minimum value for workers_pool_size
is now 3: periodic task main loop, keep alive thread and at least one thread for
other tasks. A special decorator for driver-periodic tasks is now deprecated,
as the generic decorator can be used there as well.
Closes-Bug: #1526277
Change-Id: I57bf7cebfb6db805b6c521bacfef2993b16ce1ee
