Thanks for the clarification. This input is really useful to Horizon team too.
I understand the goal is to know the beta implementation has the right
direction.
It is a good startline to discuss what it should be.
Thanks,
Akihiro
On Wed, Sep 3, 2014 at 2:02 PM, Josh Gachnang wrote:
> Right, the
Right, the ASAP part is just to have a working Horizon for Ironic
(proposed, not merged) with most of the features we want as we move towards
the vote for graduation. We definitely understand the end-of-cycle crunch,
as we're dealing with the same in Ironic. I'm just looking for a general
"This cod
On September 2, 2014 9:28:15 PM PDT, Akihiro Motoki wrote:
>Hi,
>
>Good to know we will have Ironic support. I can help the integration.
>
>Let me clarify the situation as Horizon core team. I wonder why it is
>ASAP.
>Horizon is released with integrated projects and it is true in Juno
>release
>
Hi,
Good to know we will have Ironic support. I can help the integration.
Let me clarify the situation as Horizon core team. I wonder why it is ASAP.
Horizon is released with integrated projects and it is true in Juno release
too.
Ironic is still incubated even if it is graduated for Kilo release
Hey all,
I published a patch to add an Ironic API wrapper in Horizon. Having code up
for Horizon is a graduation requirement for Ironic, so I'd like some
eyeballs on it to at least tell us we're going in the right direction. I
understand this code won't land until after Ironic is integrated.
Anot