[heketi-devel] OpenShift Templates: Unnecessary?

Luis Pabon lpabon at chrysalix.org
Thu Dec 1 20:15:18 UTC 2016


Hi José,
  When the project first started, OpenShift Templates was the only way to
deploy.
Now that we have (or about to have) DaemonSets, we no longer need to use
OpenShift Templates.

- Luis

On Wed, Nov 30, 2016 at 7:16 PM, Jose A. Rivera <jarrpa at redhat.com> wrote:

> Heyo,
>
> Naturally, as soon as I upload OpenShift support for the gk-deploy
> script, I find myself wondering: why do we have templates for heketi
> for OpenShift? Specifically, why do we create Template objects instead
> of the direct objects (e.g. Service, DeploymentConfig)? Do we have a
> need for the ability to recreate heketi pods with different parameters
> within the same namespace? We live without them in Kubernetes, and at
> present even with Templates the deployment of heketi in OpenShift is
> not much easier for a sysadmin if at all.
>
> --Jose
>
> P.S. This all comes as I'm trying to bring a DaemonSet GlusterFS to
> OpenShift. ;)
> _______________________________________________
> heketi-devel mailing list
> heketi-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/heketi-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/heketi-devel/attachments/20161201/6259598c/attachment.html>


More information about the heketi-devel mailing list