> On Dec 4, 2014, at 11:04 AM, Clint Byrum <cl...@fewbar.com> wrote: > > Excerpts from Steve Kowalik's message of 2014-12-03 20:47:19 -0800: >> Hi all, >> >> I'm becoming increasingly concerned about all of the code paths >> in tripleo-incubator that check $USE_IRONIC -eq 0 -- that is, use >> nova-baremetal rather than Ironic. We do not check nova-bm support in >> CI, haven't for at least a month, and I'm concerned that parts of it >> may be slowly bit-rotting. >> >> I think our documentation is fairly clear that nova-baremetal is >> deprecated and Ironic is the way forward, and I know it flies in the >> face of backwards-compatibility, but do we want to bite the bullet and >> remove nova-bm support? > > Has Ironic settled on a migration path/tool from nova-bm? If yes, then > we should remove nova-bm support and point people at the migration > documentation. >
Clint, I believe this is the migration document: https://wiki.openstack.org/wiki/Ironic/NovaBaremetalIronicMigration. As it was required for graduation, as far as I’m aware this is all the work that’s going to be done by Ironic for nova-bm migration. FWIW, I’m +1 to removing this support from TripleO as other uses of nova-bm have been deprecated across the Juno release, and this, IMO, should follow the same pattern. Thanks, Jay > If Ironic decided not to provide one, then we should just remove support > as well. > > If Ironic just isn't done yet, then removing nova-bm in TripleO is > premature and we should wait for them to finish. > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
