[openstack-dev] [ironic][heat][mistral][magnum] Manage Ironic resource in Orchestration.

Rico Lin rico.lin.guanyu at gmail.com
Mon Dec 12 08:18:59 UTC 2016

Think about bare metal (ironic) deployment, we can do directly ironic call,
or use nova to deploy.
Right now I have a spec about implemented Ironic resources [1] in Heat.
Including Chassis, Port and some state setting feature for Node (including
node-set-xxx). In heat team discussion, we tend to not implement Node
deployment feature.

If we counting Ironic action into three parts:
1. Create the node in the ironic DB
2. Do a series of steps to get the node in a state where it's ready for
deployment (this may include introspection via ironic-inspector, or just
changing the state)
3. Select a node and drive a workflow that deploys an image on it.

We can do in Heat is to use Nova on (3) and hope someone already handles on
(1) and (2). If we consider (1) and (2) also part of Heat resources, we can
actually make entire management done in heat template.

The use case in my head was ironic+magnum case:
Ironic resource handles state we need, then through magnum resource, nova
will deploy that baremetal node and config it as part of COE.

The open question is if heat really implemented such feature, who will
benefit from it and how are they going to use it? We certainly don't want
to implement something that no one will use it or not even think it's a
good idea.
And which projects might be a good fit if it's not a good idea to do in
We can also think about the possibility of implement it with putting it in
Nova resource in heat if it's a baremetal case, Heat+Mistral, or just
Mistral will do.
Any idea or use cases?

[1] https://review.openstack.org/#/c/393108
May The Force of OpenStack Be With You,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161212/e5f00194/attachment.html>

More information about the OpenStack-dev mailing list