Open Stack

hi Jay,

Ironic's existing API is admin only, which should not be exposed to end
users, it is best thought of as a bare metal hypervisor API.
And Ironic lacks the ability of scheduling, quotas management and
multi-tenancy support, it heavily depends on Nova to expose API to
end users.

Nova focuses on VM management and provides virtualization specific
features, although the ironic driver makes it possible to manage
bare metal via Nova's API, it doesn't work well. It's hard to add bare
metal specific features, as Nova API is for all hypervisors,
especially virtualization hypervisors. And in order to work with Nova, we
have to adapt the way to manage VMs, for example, we only
have one compute host for all bare metal nodes, so all capabilities based
on compute hosts can't apply to bare metals like availability
zones, host aggregates, etc.

Like containers and virutalizations, bare metal is also a different
technology, different resource. I think they don't work better
together within a same nova compute and bounded by Nova unified API. So we
decide to create a new project which decouples the two
technologies by separating baremetal management into it's own set of API.

Another reason is we also want to support RSD bared servers. Then composing
resouces work will be done in Nimble, Ironic only need
to add RedFish driver to support this type of servers.

Thanks,


On Mon, Nov 28, 2016 at 8:16 AM, Jay Pipes <jaypipes at gmail.com> wrote:

> On 11/25/2016 04:41 AM, Zhenguo Niu wrote:
>
>> hi all,
>>
>> We are pleased to introduce Nimble, a new OpenStack project which aims
>> to provide bare metal computing management.
>> Compared with Nova, it's more bare metal specific and with more advanced
>> features that VM users don't need, it's not
>> bounded by Nova's API.
>>
>> As we know, Ironic API should never be exposed to end users, users have
>> to talk to Nova to request a bare metal compute
>> instance even if you're only providing bare metal, even if it's only
>> internally, you still have to talk to nova, Ironic doesn't have
>> a concept of users, tenants, and quotas. Nimble wants to decouple
>> virtualization and baremetal technologies by breaking
>> baremetal computing management into its own set of application program
>> interfaces.
>>
>> Not only does Nimble provide pre-set configuration servers, but it also
>> wants to support RSD(Rack Scale Design) which makes
>> it possible to dynamically compose physical resouces.
>>
>> For more information, including architecture, use cases, etc., are
>> described on the project wiki [0].
>> And please feel free to browse our source code [1][2].
>>
>
> I'm a little confused why you are choosing to create a new RESTful API
> service instead of working to adapt Ironic's existing API, or alternately,
> working with the Nova team to add features that you feel were/are necessary
> for baremetal management.
>
> What were the primary reasons you decided not to work with either (or
> both) of the Ironic or Nova communities?
>
> -jay
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Best Regards,
Zhenguo Niu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161128/e48d8f91/attachment-0001.html>