I don't think this is a valid bug anymore; Ironic is implementing support for more and more of these every day. We have a path forward (using service steps) for implementing snapshotting, if desired. Resize can make sense in some future-world with composable hardware and we support multiple kinds of reboot already (soft and hard).
I disagree with the basic premise that baremetal servers will simply never be able to support some of thse endpoints; over the last ten years we've enabled baremetal servers, through Nova, to do things -- like rescue -- which might have previously been seen as unreasonable to do on bare metal.
From an Ironic standpoint; I would say this bug is invalid. If this is a bug in Nova/Horizon, it should be around exposing hypervisor/instance capabilities, generally, via API -- not about special casing bare metal instances.
This showed up in Ironic's bug review dashboard.
I don't think this is a valid bug anymore; Ironic is implementing support for more and more of these every day. We have a path forward (using service steps) for implementing snapshotting, if desired. Resize can make sense in some future-world with composable hardware and we support multiple kinds of reboot already (soft and hard).
I disagree with the basic premise that baremetal servers will simply never be able to support some of thse endpoints; over the last ten years we've enabled baremetal servers, through Nova, to do things -- like rescue -- which might have previously been seen as unreasonable to do on bare metal.
From an Ironic standpoint; I would say this bug is invalid. If this is a bug in Nova/Horizon, it should be around exposing hypervisor/instance capabilities, generally, via API -- not about special casing bare metal instances.