Open Stack

[...]
>> The short explanation which clicked for me (granted it's probably an
>> oversimplification, but still) was this: Ironic provides an admin
>> API for managing bare metal resources, while Mogan gives you a user
>> API (suitable for public cloud use cases) to your Ironic backend. I
>> suppose it could have been implemented in Ironic, but implementing
>> it separately allows Ironic to be agnostic to multiple user
>> frontends and also frees the Ironic team up from having to take on
>> yet more work directly.
>
>
> ditto!
>
> I had a similar question at the PTG and this was the answer that convinced
> be
> may be worth the effort.
>
> Flavio
>

For Ironic, the question did come at the PTG up of tenant aware
scheduling of owned hardware, as in Customer A and B are managed by
the same ironic, only customer A's users should be able to schedule on
to Customer A's hardware, with API access control restrictions such
that specific customer can take action on their own hardware.

If we go down the path of supporting such views/logic, it could become
a massive undertaking for Ironic, so there is absolutely a plus to
something doing much of that for Ironic. Personally, I think Mogan is
a good direction to continue to explore. That being said, we should
improve our communication of plans/directions/perceptions between the
teams so we don't adversely impact each other and see where we can
help each other moving forward.

-Julia