I left some comments on the wireframes themselves. One general concept I would like to see capture is to make sure that things across the UI and CLI have parity.
Specifically things like if I register nodes on the CLI we use a JSON file format: http://tripleo.org/environments/environments.html#instackenv Supporting individual nodes to be created is fine as well since a command line user could just run Ironic client commands directly too. I also left a comment about the screen with multiple plans. I like this idea and it is something that we can pursue but due to fact that we use a flat physical deployment network there would need to be some extra care in setting up the network ranges, vlans, etc across multiple plans. Again this is something I would like to see us support and document with the CLI before we go and expose the capability in the UI. Dan On Mon, 2016-06-06 at 15:03 -0400, Liz Blanchard wrote: > Hi All, > > I wanted to share some brainstorming we've done on the TripleO UI. I > put together wireframes[1] to reflect some ideas we have on moving > forward with features in the UI and would love to get any feedback > you all have. Feel free to comment via this email or comment within > InVision. > > Best, > Liz > > [1] https://invis.io/KW7JTXBBR > _____________________________________________________________________ > _____ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs > cribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev