Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start
Hey Matt, thanks for the comments, I'll try to reply below: On 2013/05/12 20:32, Matt Wagner wrote: On Tue Dec 3 06:53:04 2013, Jaromir Coufal wrote: I've somehow overlooked the 'Node tags' previously. I'm curious what format these would take, or if this is something we've discussed. I remember hearing us kick around an idea for key-value pairs for storing arbitrary information, maybe ram=64g or rack=c6. Is that what the tags you have are intended for? Not exactly. This is not key-value approach but more like an arbitrary information (or grouping), what user can enter in. It can be very efficient way for the user to express various meta-information about the node if he cares. For example from the beginning, when we are missing some functionality from Ironic (like location, rack information, etc), we can use manual tagging instead. This might be already part of Ironic, so we just need to check if that's correct One thing I notice here -- and I really hope I'm not opening a can of worms -- is that this seems to require that you manage many nodes. I know that's our focus, and I entirely agree with it. But with the way things are represented in this, it doesn't seem like it would be possible for a user to set up an all-in-one system (say, for testing) that ran compute and storage on the same node. I think it would be very fair to say that's just something we're not focusing on at this point, and that to start out we're just going to handle the simple case of wanting to install many nodes, each with only one distinct type. But I just wanted to clarify that we are, indeed, making that decision? I am convinced that this was never scope of our efforts. We are focusing not just about installation of overcloud but also about monitoring and furthermore easy *scaling*. Mixing compute and storage services at one node would be very inefficient and for vast majority of deployments unrealistic scenario. Though, in the future if we find out that there are multiple cases of this being a way how people setup their deployments, we might reconsider to support this approach. But I have never heard about that so far and I don't think that it will happen. Cheers -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start (Jaromir Coufal)
Let me know if I can be of assistance in the visual design of this. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start
On Tue Dec 3 06:53:04 2013, Jaromir Coufal wrote: Wireframes walkthrough: https://www.youtube.com/enhance?v=oRtL3aCuEEc On 2013/03/12 10:25, Jaromir Coufal wrote: Hey folks, I opened 2 issues on UX discussion forum with TripleO UI topics: Hey Jarda, thanks for sharing these! Some comments inline below: 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 I've somehow overlooked the 'Node tags' previously. I'm curious what format these would take, or if this is something we've discussed. I remember hearing us kick around an idea for key-value pairs for storing arbitrary information, maybe ram=64g or rack=c6. Is that what the tags you have are intended for? 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 One thing I notice here -- and I really hope I'm not opening a can of worms -- is that this seems to require that you manage many nodes. I know that's our focus, and I entirely agree with it. But with the way things are represented in this, it doesn't seem like it would be possible for a user to set up an all-in-one system (say, for testing) that ran compute and storage on the same node. I think it would be very fair to say that's just something we're not focusing on at this point, and that to start out we're just going to handle the simple case of wanting to install many nodes, each with only one distinct type. But I just wanted to clarify that we are, indeed, making that decision? Overall I think these look good. Thanks! -- Matt Wagner Software Engineer, Red Hat signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] {TripleO] UI Wireframes - close to implementation start
On Dec 3, 2013, at 9:30 AM, Tzu-Mainn Chen tzuma...@redhat.com 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 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev These wireframes look really good! However, would it be possible to get the list of requirements driving them? For example, something on the level of: 1) removal of resource classes and racks 2) what happens behind the scenes when deployment occurs 3) the purpose of compute class 4) etc I completely agree with Mainn on this. It would be also be great to see use cases built from requirements that we can consider while reviewing wireframes. These would allow us to think in terms of how the user would come to the UI and perform the actions needed to complete their task. Here are some additional thoughts/questions regarding the current designs: Deployment Management Slide 3 - I like that we are making it clear to the user which types of nodes they could add to their deployment and how many of each node will be added, but why aren't we continuing to use this method as the user may want to scale out their deployment? It seems very inconsistent to use this design just for this one use case. - The section is labeled Resource distribution but the user is has a number of unallocated nodes. I think we should try to make these terms consistent. Either Resource distribution and Undistributed resources or Node Allocation and Unallocated Nodes. This would limit the terminology that a user would need to try to learn. - Would the More details link bring up a description of the type of node? If so, should this just be a ? next to the title that the user could roll over? Okay. After reviewing the youtube video I understand the point of this link now. I think this should be labeled accordingly. The controller link should probably read Controller to match up with the navigation section. It might be better to label these both Controller Nodes. - Somehow, we should make it easier for the user to walk through these details steps. It's great that this initial screen allows them to just assign nodes and then quickly deploy, but when they want to dive into the details I think we need to make it much clearer how to do this without the user needing to remember that they have to select each node type section and click Deploy. Maybe a wizard would work better? - Would the user be able to click on the text and enter a number of nodes into the text box rather than have to click the up or down arrow? Slide 5 - It might be a helpful hint to the user to maybe list the number of nodes that need action in each section next to the navigation item. I'm just trying to think of better ways to walk the user through if they want to look at more details on each of the nodes (or types of nodes) before deploying. - Would there be other states that a node could be in within the Nodes waiting for action section? If not, this could just be the Nodes waiting to be deployed section. - I like that the stacked representation of the nodes will save space, but will the user be able to perform the actions that they would need to quickly on this page? It's also inconsistent with the original first use design used in Slide 3. Maybe we could repeat this interaction and allow the user to add/remove the number of nodes quickly here? We could still use this stacked representation to monitor like nodes as you are showing in Slide 11. Slide 6 -The addition of Create New Compute Class makes it seem like the user will be able to deploy these 27 nodes without being attached to a class. Or is this initial group a default resource class? How would the user move nodes from one class to another? Slide 7 - This icon seems to be a way of telling the user that they've added all of these nodes to their plan and now they need to act on it. Would these notifications show as they change
[openstack-dev] {TripleO] UI Wireframes - close to implementation start
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 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start
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 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start
Wireframes walkthrough: https://www.youtube.com/enhance?v=oRtL3aCuEEc 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 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] {TripleO] UI Wireframes - close to implementation start
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 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev These wireframes look really good! However, would it be possible to get the list of requirements driving them? For example, something on the level of: 1) removal of resource classes and racks 2) what happens behind the scenes when deployment occurs 3) the purpose of compute class 4) etc I think it'd be easier to understand the big picture that way. Thanks! Mainn ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] UI Wireframes - close to implementation start
Please, instead of 'enhance', use 'watch': http://www.youtube.com/watch?v=oRtL3aCuEEc (this link is correct) Thanks -- Jarda On 2013/03/12 12:53, Jaromir Coufal wrote: Wireframes walkthrough: https://www.youtube.com/enhance?v=oRtL3aCuEEc 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 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@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
