+1 A few comments: 1. Bear in mind that sometimes a user may not have access to any Ephemeral flavors, so the tabbing should ideally be adaptive. An alternative would not to bother with the tabs and just show a flavor list. In our deployment we have no flavors with ephemeral disk space larger than 0. 2. Whenever there's a selection, but only one choice, make it a default choice. It's tedious to choose the only selection only because you have to. It's common for our users to have one network/subnet defined, but the current UI requires them to switch tabs and select the network which is rather tedious. 3. The selection of the flavor is divorced from the quota available and from the image requirements. Ideally those two items should somehow be incorporated. A user needs to know up-front that the server will build based on both their quota and the image minimum requirements. 4. We'd like to see options for sorting on items like flavors. Currently the sort is by 'id' and we'd like to see an option to sort by name alphabetically. On 11 October 2013 18:53, Cédric Soulas <cedric.soulas at cloudwatt.com> wrote: > Hi, > > I just started a draft with suggestions to enhance the UX of the "Launch > Instance" form: > > https://docs.google.com/document/d/1hUdmyxpVxbYwgGtPbzDsBUXsv0_rtKbfgCHYxOgFjlo > > Try the live prototype: > http://cedricss.github.io/openstack-dashboard-ux-blueprints/launch-instance > > Best, > > Cédric > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Jesse Pretorius mobile: +27 83 680 5492 email: jesse.pretorius at gmail.com skype: jesse.pretorius -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131011/e3adf250/attachment.html>