Hi,
Thanks for the wireframes and the walkthrough. Very useful. I've a few
comments.
- I'd like to echo the comments from the recording about "Role" I think
the term probably isn't specific enough but I don't have a great
suggestion. However, this is probably suited better to the other thread.
- We will have a number of long processes, for example, when a deploy or
re-size is happening. How do we keep the user informed of the progress
and errors? I don't see anything in the wireframes, but maybe there is a
Horizon standard approach I'm less familiar with. For example, I have 50
compute nodes, then I add 10 but I want to know how many are ready etc.
- If I remove some instances, do I as the administrator need to care
which are removed? Do we need to choose or be informed at the end?
On 10/01/14 14:58, Jaromir Coufal wrote:
Hi everybody,
there is first stab of Deployment Management section with future
direction (note that it was discussed as a scope for Icehouse).
I tried to add functionality in time and break it down to steps. This
will help us to focus on one functionality at a time and if we will be
in time pressure for Icehouse release, we can cut off last steps.
Wireframes:
http://people.redhat.com/~jcoufal/openstack/tripleo/2014-01-10_tripleo-ui_deployment-management.pdf
Recording of walkthrough:
https://www.youtube.com/watch?v=9ROxyc85IyE
We sare about to start with first step as soon as possible, so please
focus on our initial steps the most (which doesn't mean that we should
neglect the direction).
Every feedback is very welcome, thanks
-- Jarda
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
