Skip to content
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.

Installation via Service Catalog #23

Open
JohnStrunk opened this issue Jun 28, 2018 · 0 comments
Open

Installation via Service Catalog #23

JohnStrunk opened this issue Jun 28, 2018 · 0 comments
Labels
epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items
Projects

Comments

@JohnStrunk
Copy link
Member

Describe the feature you'd like to have.
It should be possible to deploy a Gluster cluster via a Service Catalog.

What is the value to the end user? (why is it a priority?)
Using the service catalog, we can provide a "point-and-click", menu-driven method for installing a Gluster cluster... Answer a few questions and be on your way. Not all admins are interested in editing yamls to configure their storage, and this can provide a way to guide them to a working storage system in a "wizard-like" manner.

How will we know we have a good solution? (acceptance criteria)

  • A cluster admin can exclusively use the service catalog to deploy Gluster
  • Admin is guided through questions necessary to deploy the cluster and provided sensible defaults where possible.
  • Cluster can be destroyed in the same manner.

Additional context
I view this as just a wrapper around the yaml method. I think it would be beneficial for maintainability to keep the service catalog specific code/infra as light as possible.

@JohnStrunk JohnStrunk added epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items labels Jun 28, 2018
@JohnStrunk JohnStrunk added this to the future milestone Jun 28, 2018
@JohnStrunk JohnStrunk added this to Incoming in Planning via automation Jun 28, 2018
@JohnStrunk JohnStrunk moved this from Incoming to Epics in Planning Jun 28, 2018
@JohnStrunk JohnStrunk removed this from the future milestone Sep 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items
Projects
Development

No branches or pull requests

1 participant