Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/data-processing-rework-ui. Description: Summary ======= For both the Juno and Kilo summits, there has been a frustration expressed with the Data Processing user interface with respect to it not being intuitive or easy to use without a lot of experience. One of the solutions proposed was to add some help in the UI in the form of a guide for cluster creation as well as job executions. Motivation ======== The Data Processing system should be as easy and intuitive to use as possible. The existing set of panels provide a great deal of functionality, but little in the way of guidance to a user trying to figure out which order they need to set things up in order to get a cluster and/or a job to run. Description ========= In short, the Data Processing panel group should have a new "overview" (name TBD) panel that can give a quick glance at the status of the system (running clusters/jobs) and also have the ability to launch guides that will assist the user through the process of creating a cluster or executing a job. UX === After brief interactions with some UX people, it was decided that the best approach for this cycle would be to implement a page/panel that will guide the user through cluster/job execution creation via a fair amount of text that includes links to each of the necessary steps. This solution allows us to re-use much of our existing forms and provides the user with a meaningful way of navigating through them. Wireframes, Mocks, Videos and UI Markup --------------------------------------------------------- There are no wireframes/mocks/videos available. Testing ====== Tests will be added in Horizon to cover the guide pages. Outside Dependencies ================== N/A Requirements Update Required ======================== N/A Doc Impact ========= There is a dashboard user guide available in the Sahara documentation. It will need to be updated to reflect the changes. Specification URL (additional information): None
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548