It is not needed in most cases, but was blindly cargo-culted everywhere.
It will be removed with the switch to hardware types.
Change-Id: I1de6be6ab8b0c210f457fa0c1cd685c42406b888
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I4b1ca0a1f067895640f0a71d6dd392d33e3def4e
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The PowerInterface methods set_power_state() and reboot() were enhanced
to take a 'timeout' parameter [1].
In the Queens release [2] , the conductor assumes that all PowerInterfaces
can support this timeout parameter. This patch changes the PowerInterfaces
so that they accept a 'timeout' parameter for reboot() and set_power_state().
The PowerInterfaces log a warning if the parameter is specified when it isn't
supported.
[1] f15d5b9a37260b3876f9dadeb030412e6e1053b2
[2] 9e87cebc12102cbb3ae47366836dcd7c3e439828
Change-Id: I0904958f1a7f981204ba41bfbdc0083182c5622e
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Iae39fc4feb54006ee1d10ba6afca105f84d6b042
Curly quotes usually input from Chinese input method.
When read from english context, it makes some confusion.
Change-Id: I3e99e14394469b1c16afe943dc69df5631f73186
it is now part of ironic itself, and version in ironic-staging-drivers
conflicts with version in ironic, blocking ironic-conductor from
starting when ironic-staging-drivers is installed.
Change-Id: I917b7399b3249143ba6cf75f61d96a1c64f94e7d
Remove Mitaka, it was published from master anyway. Add pike and ocata.
Remove references to versions, they're anyway outdated.
Change-Id: I7ea04a42b43030b7378ac9d06cb1325d98bca78b
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
Change-Id: I5148aaf965a36443d8ed03d2ac87b5c286b56261
This patch introduces new type of power and management drivers for ovirt vms.
Change-Id: Iebf31db70dfd800d47399c69d7b2255467a87a1d
Closes-Bug: #1564841
some places (apart from job names) were changed compared to what's
in openstack-zuul-jobs currently, mostly added/changed irrelevant-files,
and refactored to have a base dummy job to define common things.
Change-Id: Iff64438857e0947db1154645f6e2e964b38593c6
this is a followup to Id2bfd1ed552ed566b14f6ac5b222c011ff918bee
while adapting playbooks for Ansible 2.4 compatibility,
this place was missed, and playbooks tried to install grub
to a wrong device.
This patch re-uses the "ironic_root_device" fact set during discovery
as grub install target.
Change-Id: Ibfd885b4702ff86c802a8d184ebb406aae9262b5
some unit tests for ansible deploy interface were using
dumb monkeypatch instead of proper mocking.
Change-Id: I317e1b8e9f0ec4cb792ee09ce592cbd83f956b75
Apparently only checking that pyudev is importable is not enough,
as it can fail later if udev itself is not available on the system
Also bring the (empty) default between these two to be empty dict,
and fix logging invocations in WWN fact collecting module.
Change-Id: I137990280e90c9ca2687b38d98f6c5343e26e8d0
- fix callback plugin (add a new public methdod)
- ansible_devices fact now contains many more devices
(at least with tinyipa ramdisk and virtual HW),
so by default we now attempt to use only devices that
have non-empty 'host' attribute, and thus are
real block devices on some controller
(not memory-mapped files, loop devices etc)
+ during provisioning, the default target for image
when root device hints are absent will be the first such device
+ during cleaning, only such devices will be attempted to
be cleaned
Change-Id: Id2bfd1ed552ed566b14f6ac5b222c011ff918bee
Closes-Bug: #1718361
