No need to make everyone install rabbitmq just to play with ironic.
Also make it clearer that MySQL is not required.
Change-Id: Ib286f30f16579815ca05c8477f7fd446cad6e453
Adds `instance_info/kernel_append_params` property support to
`redfish` hardware type. If given, this property overrides
`[redfish]/kernel_append_params` ironic option.
The rationale for adding this property is to allow passing
node-specific kernel parameters to instance kernel.
One of the use-cases for this is to pass node static network
configuration to the kernel.
Change-Id: Ib1617f5a7ab34968d8bfe06fe49f3ba68e56f99f
Story: 2006691
Task: 36988
configdrive can contain a vendor_data2.json file containing key/value
pairs injected by nova's vendordata mechanism[1].
This change lets Ironic accept a vendor_data key when configdrive is
provided as json, allowing parity with nova.
This change requires an openstacksdk release 0.37.0
[1] https://www.madebymikal.com/nova-vendordata-deployment-an-excessively-detailed-guide/
Change-Id: Id990b970619a113c5d5ead47fb550870d91b5e04
Task: 36756
Story: 2006597
Blueprint: nova-less-deploy
Adds additional details on how to use the iDrac driver with
Ironic.
Change-Id: I598181a8227179b8c587b31905e38aa7595eef87
Co-Authored-By: Pranjali Srivastava <srivastavapranjali@ymail.com>
The loop keyword is the current recommended way to handle loops,
and supports filters.
It's available since Ansible version 2.5 so changing ansible
requirement in driver-requirements.
Change-Id: Ibff1f07ca00b8f5a5274d73f9e53196f49c33a66
After a release we need to update the `templates` for zuul
in master to have the job for the new cycle.
Change-Id: Ic275ea9ec97f74732f4bafa99037c2d8a8229b91
- Ara report was removed and we have the Zuul web page
that shows the information about the job build.
Change-Id: I74f70ee21421746983cb3c8d290cc6a619819e34
This patch:
6df83e0bc5
changes the variables that must be exported to use ironic in standalone
mode. The old env. variables:
export OS_URL=http://localhost:6385/
export OS_TOKEN='fake-token'
must be replaced by:
export OS_ENDPOINT=http://localhost:6385/
export OS_AUTH_TYPE=none
Change-Id: Ia2ae95af66f701198d5e3174a7cb5564664ae038
Signed-off-by: Manuel Buil <mbuil@suse.com>
The cisco hardware types and interfaces were removed in
Ie12eaf7572ce4d66f6a68025b7fe2d294185ce28. This removes the
last few references to them, and adds a release note about
their removal.
Change-Id: I6d11dda0132d999b2dbf6bbd47cac55336e1d079
Story: 2005033
Task: 29522
The documentation currently has no information at all about what steps
are available *generally* for automated or manual cleaning. Users who
want to find this information must review the source code themselves,
except in one or two cases where driver-specific documentation has the
details spelled out.
This patch adds a series of tables to the general cleaning
documentation to provide details about the steps one could possibly
add to the instructions given to ironic, along with details about
required parameters and what the effect of each step will be.
Change-Id: I6b225cce38b815248c457814508531041c437e6d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
In order to create/delete RAID configuration via the Ansible driver
we should be able to retrieve the JSON target_raid_config data from
the node.
Change-Id: Ie1bbefbc438a6c7f4592ea96ff84d2d5eb2d412d
Story: 2006417
Task: 36307
Add power state change callbacks of an instance to nova by
performing API requests. Whenever there is a change in the
power state of a physical instance (example a "power on"
or "power off" IPMI command is issued or the periodic
``_sync_power_states`` task detects a change in power state)
ironic will create and send a ``power-update`` external event
to nova using which nova will update the power state of the
instance in its database. By conveying the power state changes
to nova, ironic becomes the source of truth thus preventing
nova from forcing wrong power states on the instance during
the nova-ironic periodic sync. It also adds the possibility of
bringing up/down a physical instance through the ironic API
even if it was put down/up through the nova API.
Note that ironic only sends requests to nova if the target
power state is either "power on" or "power off". Other error
states will be ignored. In cases where the power state change
is originally coming from nova, the event will still be
created and sent to nova and on the nova side it will be a
no-op with a debug log saying the node is already powering on/off.
NOTE: Although an exclusive lock (task_manager.upgrade_lock()
method) is used when calling the nova API to send events,
there can still be a race condition if the nova-ironic power sync
happens to happen a nano-second before the power state change
event is received from ironic in which case the nova state will
be forced on the node.
Credit for introducing ksa adapter: Eric Fried <openstack@fried.cc>
Depends-On: https://review.opendev.org/#/c/645611/
Part of blueprint nova-support-instance-power-update
Story: 2004969
Task: 29424
Change-Id: I6d105524e1645d9a40dfeae2850c33cf2d110826
* Use more copy-paste friendly indentation in the examples
* Use subheadings for properties
* Render JSON examples as JSON
* Remove explicit API version from CLI, we've been defaulting
to latest for several releases.
* Small fixes
Change-Id: I1cae6e9b4ff124e3404bd55638bc77bdf3465fe0
This provides a bunch of updates based on user testing of the feature.
Also the lines are wrapped and inter-document links are created.
Change-Id: Ia3408aee3ebcd4ad5deedaa48967f46134ad2cfc
