On 11/27/2016 10:27 PM, Zhenguo Niu wrote:
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.
I don't see any compelling reason not to work with the Nova and Ironic
projects and add the functionality you wish to see in those respective
projects.
For the RackScale Architecture stuff, the Valence project seems to be
doing that and I'm not sure what role Nimble would play.
Best,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
