Bug 1127989 - [RFE][horizon]: [data processing] Changes to streamline cluster creation
Summary: [RFE][horizon]: [data processing] Changes to streamline cluster creation
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_none upstream_defi...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-08 04:05 UTC by RHOS Integration
Modified: 2016-10-29 04:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description RHOS Integration 2014-08-08 04:05:06 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/data-processing-streamline-cluster-creation.


** Most likely a Kilo item **
The current workflow for cluster creation is often sub-optimal for the most common use cases.  This blueprint aims to streamline the process for common cluster creation use cases.

For instance, common clusters have 1 master and N workers, for a given plugin the master always has the same set of processes and so does the worker.
Given that, ideally, we could provide cluster launch workflow w/ just a "how big (how many workers)?" question.  This might require either the sahara service or the plugins to provide some sort of "default master/worker" template, or possibly the dashboard could have defaults generated (but wouldn't be useable outside of the dashboard, so I prefer the default templates being defined elsewhere)

Even if we don't get the "default templates", the UI cluster launch workflow could have a new tab that would allow the user to modify the number of instances of each node group.  When that is submitted, the dashboard could modify the cluster creation call to use the updated instance numbers (which might require the dashboard to "reconstruct" the template on the fly). 

In either case, the spirit of this blueprint is that the user should NOT have to recreate a whole cluster template just to change the number of workers in their launched cluster.

Specification URL (additional information):


Note You need to log in before you can comment on or make changes to this bug.