Upstream Ironic is switching from using pxe_ssh driver to using pxe_ipmitool + a proxy tool called virtualbmc: https://github.com/openstack/virtualbmc. This allows using the same driver for testing and for production. This affects both undercloud and overcloud
Rough work items:
1. Package virtualbmc
2. Create puppet manifests for deploying it
3. Install virtualbmc in undercloud
4. Install virtualbmc in overcloud
5. Switch instack-virt-setup and ooo-quickstart to using it
Will that break customers using pxe_ssh for managing their overcloud? If that's the case, then removing this driver will break the upgradability of some overclouds unless each nodes using pxe_ssh are migrated to pxe_ipmitool beforehand.
Hi! It probably will. So, for the upgrade we're planning to provide pxe_ssh drivers in another package (openstack-ironic-staging-drivers). Please keep in mind that upstream has never supported pxe_ssh driver in production, and that the deprecation period has begun in OSP 10.
Good progress here. Lucas, what is left?
This works for me now...
@Dmitry, the overcloud bits still needs some work. Right now we have virtualbmc setup for the undercloud and tripleo-quickstart should be using it to deploy the nodes.
Just to link it, introspection issues: https://bugs.launchpad.net/tripleo/+bug/1651719
So the current update of this BZ:
* VirtualBMC is already packaged in RDO: https://review.rdoproject.org/r/#/c/3756/
* The TripleO-Quickstart support for VirtualBMC has been merged:
* Instack-undercloud hasn't been updated to use VirtualBMC. It's unsure whether we need to put some effort on it or not since TripleO-Quickstart is going to replace it next cycle (Pike). Also, Ironic will keep the *_ssh drivers in tree for the Ocata release, which will TripleO the time needed for switching instack-undercloud.
We still need to test the Ironic in the overcloud with VirtualBMC, I don't foresee any code modification for that, only documentation. Because right now the VBMCs runs on the undercloud node, so we need to change the "pm_address" option in the instackenv.json for the overcloud Ironic to point to the external IP address of the undercloud. That should do the trick.
> Instack-undercloud hasn't been updated to use VirtualBMC
I think you mean instack-virt-setup, right? If so, we should not bother as it was officially deprecated in Ocata.
> We still need to test the Ironic in the overcloud with VirtualBMC
This can be done a part of moving this task to ON_QA. I suggest moving it to POST if you don't have other TODO items. WDYT?
We need upstream documentation on tripleo.org, but it can be don async as well.
(In reply to Dmitry Tantsur from comment #12)
> > Instack-undercloud hasn't been updated to use VirtualBMC
> I think you mean instack-virt-setup, right? If so, we should not bother as
> it was officially deprecated in Ocata.
> > We still need to test the Ironic in the overcloud with VirtualBMC
> This can be done a part of moving this task to ON_QA. I suggest moving it to
> POST if you don't have other TODO items. WDYT?
Seems fine for me, doing that now.
> We need upstream documentation on tripleo.org, but it can be don async as
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.