Open Stack

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.

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.