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.
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)
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.