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 <j...@pcsforeducation.com> wrote: > 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 code > looks reasonable" or "Woah, don't do it like that", not trying to get it > merged this late in the cycle. > > As for graduation, as I understand, we need to have code proposed to Horizon > that we can work to merge after we graduate. > > Thanks! > > --- > Josh Gachnang > Tech Blog: ServerCobra.com, @ServerCobra > Github.com/PCsForEducation > > > On Tue, Sep 2, 2014 at 9:37 PM, Jim Rollenhagen <j...@jimrollenhagen.com> > wrote: >> >> >> >> On September 2, 2014 9:28:15 PM PDT, Akihiro Motoki <amot...@gmail.com> >> 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 >> >too. >> >Ironic is still incubated even if it is graduated for Kilo release. >> >What is the requirement for graduation? More detail clarification is >> >needed. >> >All teams of the integrated projects are focusing on Juno releases and >> >we all features will be reviewed after rc1 is shipped. The timing is a >> >bit >> >bad. >> >> Right, the Ironic team does not expect this to land in the Juno cycle. The >> graduation requirement is that Ironic has made a good faith effort to work >> toward a Horizon panel. >> >> We would like some eyes on the code to make sure we're moving the right >> direction, but again, we don't expect this to land until Kilo. >> >> // jim >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev