Open Stack

Hello, Leslie

There seem to be some misnotation in this picture, in steps #2 and #4-7. In
#2, the 'node' means 'instance of nova-compute' which should handle the
request, and nova-scheduler selects that instance of nova-compute.

In #4 and #7, however, the 'node' means bare-metal server under management
of that compute node. That server is actually provisioned as an instance of
bare-metal cloud. It is assumed that all servers under management of single
instance of nova-compute are equal. Ironic does not perfrom any scheduling
or selection of bare-metal servers on its side, just picks the first one.

Ironic is considered to be a back-end to virt driver of Nova. That is why
nova-compute service talks to Ironic API, just as it talks to vCenter API,
for example, when VMWare is used as a virt back-end.

Hope it helps to clarify the picture.

--
Best regards,
Oleg Gelbukh


On Tue, Dec 24, 2013 at 12:28 PM, LeslieWang <wqyuwss at hotmail.com> wrote:

> Hi All,
>
> I'm investigating Ironic recently, and found below diagram describing the
> workflow between nova and ironic. I have one questions about step #4, #7. Why
> it is invoked by Nova Compute, not Nova Scheduler. Ironic is used to power
> on baremetal server, and deploy image. Seems like nova compute should be
> installed after this call. So I guess this call should be initiated from
> Nova Scheduler through either synchronous ironic API call, or asynchronous
> message queue.
>
>
>
>
>
> Can anyone please answer this question? Your input is highly appreciated.
>
> Best Regards
> Leslie
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131224/770f7390/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wentian2-1024x415.png
Type: image/png
Size: 188992 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131224/770f7390/attachment.png>