[openstack-dev] [TripleO] UI Wireframes - close to implementation start

James Slagle james.slagle at gmail.com
Thu Dec 5 23:00:21 UTC 2013

On Tue, Dec 3, 2013 at 4:37 AM, Jaromir Coufal <jcoufal at redhat.com> wrote:
> I am sorry for mistake in tag - fixed in this reply and keeping the original
> text below.
> On 2013/03/12 10:25, Jaromir Coufal wrote:
> Hey folks,
> I opened 2 issues on UX discussion forum with TripleO UI topics:
> Resource Management:
> http://ask-openstackux.rhcloud.com/question/95/tripleo-ui-resource-management/
> - this section was already reviewed before, there is not much surprises,
> just smaller updates
> - we are about to implement this area
> http://ask-openstackux.rhcloud.com/question/96/tripleo-ui-deployment-management/
> - these are completely new views and they need a lot of attention so that in
> time we don't change direction drastically
> - any feedback here is welcome


This stuff looks really great. I like the flow quite a bit.  One thing
that stuck out to me though is that I didn't see anything around
troubleshooting a Deployment.  Since stuff does occassionally go wrong
:), it might be nice to mock up how troubleshooting that might look.

I think we already have the logs in Horizon, but bubbling that up to
the user on the deployment screen might be nice.  Or, perhaps links
back to the logs if something failed.

In the pdf for deployment[1], slide 13, there's shown a node that
failed.  But, I don't see much there in terms of getting at how/why it

I know I'm probably thinking way far out here :), but there was some
good discussion at the summit on Heat making it easier to debug stack
failures, adding retries, etc.  I know that's stuff still early, but
it might make sense to think about hooking into that once available.
[2].  There was also an idea of adopting a stack [3].  This might be a
way for folks who already have a deployment to bring it under the
control of Tuskar so to speak.

Anyway, it doesn't look like anything in the mockups would make it
difficult to hook into these new API's once avaiable, but I just
thought I would mention them.  Thanks!

[1] http://people.redhat.com/~jcoufal/openstack/tripleo/2013-12-03_tripleo-ui_03-deployment.pdf
[2] https://blueprints.launchpad.net/heat/+spec/troubleshooting-low-level-control
[3] https://blueprints.launchpad.net/heat/+spec/adopt-stack

> We need to get into implementation ASAP. It doesn't mean that we have
> everything perfect from the very beginning, but that we have direction and
> we move forward by enhancements.
> Therefor implementation of above mentioned areas should start very soon.
> If all possible, I will try to record walkthrough with further explanations.
> If you have any questions or feedback, please follow the threads on
> ask-openstackux.
> Thanks
> -- Jarda
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- James Slagle

More information about the OpenStack-dev mailing list