[openstack-dev] [Mistral][Horizon][Tuskar-ui] Mistral Dashboard
Tripp, Travis S
travis.tripp at hp.com
Fri Jul 10 22:42:11 UTC 2015
In my opinion there is only one major actual bug left on Launch Instance. That is the webroot bug  and this actually affects all of the angular work, not just Launch Instance. There was a working fix for it ready earlier this week, but then additional considerations for the approach on it were brought up. This fix is definitely Liberty specific and we need a version of it prepared specifically for Kilo as it has affected some community members wanting to use angular APIs in Kilo. You can see them at the URL listed below . Some stalled out due to lack of reviews, so clearly not considered very major. Once that is fixed, I believe we need to make the angular based launch instance enabled by default so that we have more opportunity to find any more bugs before the end of Liberty.
All of that said, the highest priority effort going on is that we learned that the way the angular code was structured in horizon was not conducive for sustainable development or for plug-ins. So there has been a lot of effort to create a structure more friendly to angular development here in Liberty. That effort is starting to wind down and hopefully will be wrapped up within a few weeks. There is a horizon mid cycle in a week and half where this will all be discussed / worked on . If you are able to join, you should add your name to the list and join us!
From: Rajat Vig
Reply-To: OpenStack List
Date: Thursday, July 9, 2015 at 9:51 AM
To: OpenStack List
Subject: Re: [openstack-dev] [Mistral][Horizon][Tuskar-ui] Mistral Dashboard
What bugs exist on the Launch Instance based off Angular?
I'd like to help fix some.
On Tue, Jul 7, 2015 at 8:29 AM, Rob Cresswell (rcresswe) <rcresswe at cisco.com<mailto:rcresswe at cisco.com>> wrote:
The current issue is that we can’t force Angular when we have so little code ourselves. The framework is fairly solid now, but there is little in the way of code examples; launch instance, which last I checked has a few major bugs, the unfinished (?) identity dashboard and a few metadata modals IIRC.
I strongly advise people to write new code with AngularJS, but I don’t support enforcing it as a hard requirement for Horizon/ Horizon plugins… yet :)
From: niuzhenguo <niuzhenguo at huawei.com<mailto:niuzhenguo at huawei.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, 7 July 2015 08:16
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [Mistral][Horizon][Tuskar-ui] Mistral Dashboard
As Horizon is moving towards an Angular application, I think it’s high time that we should make a standard for other projects which want to horizon compatible on whether they should based on Angular Dashboard or the current Horizon framework. For new project, I think it makes more sense to build the dashboard on Angular. But for “old” project like Mistral-Dashboard and Tuskar-UI, they works fine with Django framework now, do they have to move towards Angular also, and when that should be done.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStackemail@example.com?subject:unsubscribe>
More information about the OpenStack-dev