as mitaka branch was finally EOLed, Ironic team is going to proceed with
removal of SSH-based power and management drivers for virtualized HW which
were deprecated back in newton release.
Since newton the virtualbmc-based simulation of IPMI-capable HW is
officially supported, and we plan to switch all gates away from using *_ssh
drivers and eventually remove those from the ironic code, most probably in
I've skimmed through the project-config/zuul/layout.yaml and found a number
of projects that use some gate jobs with 'ironic' in the job name which are
not defined in project-config/jenkins/jobs/ironic.yaml, those project are
tagged in the subject of this message.
While kolla, magnum, OSA and rally seem to have only non-voting jobs with
ironic and thus should not be completely broken by removal of SSH drivers
anyway, puppet-ironic seems to have a voting
This message especially concerns deployment-specific projects that do not
install ironic via DevStack in their gate jobs. To successfully install a
working ironic which is capable to actually deploy nodes, such projects
will have to incorporate some additional steps to setup virtualbmc-based HW
simulation for baremetal nodes and configure nodes enrolled in ironic
If your project is mentioned, please ensure that any ironic-including gate
jobs you use do not setup ironic with *_ssh drivers, and switch to other
supported drivers if needed. Examples of necessary steps can be found in
ironic's DevStack plugin and in the playbooks of openstack/bifrost project.
For any questions please do not hesitate to contact ironic team, we'll be
glad to help you.
Dr. Pavlo Shchelokovskyy
Senior Software Engineer
OpenStack Development Mailing List (not for usage questions)