<div dir="ltr">I'm not sure what meeting you are talking about. Templates do not compare with daemonsets. Templates is the ability to substitute variables in an object. Your comparison is incorrect. A better comparison is that Deployments (or DeploymentConfig in OpenShift) allow for rollback, upgrades, etc. True, today daemonsets do not have that upgrade ability, but it is going to be added.<div><br></div><div>Templates themselves provide no benefit to our deployments.</div><div><br></div><div>- Luis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 8, 2016 at 10:34 AM, Humble Chirammal <span dir="ltr"><<a href="mailto:hchiramm@redhat.com" target="_blank">hchiramm@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">As I pointed out in our meeting, templates bring us the main advantage of upgrading our solution with different strategies like rolllback and upgrade to a particular version ..etc which is not possible with just a config artifact like Deamonset. So, according to me we should keep it.<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 2, 2016 at 8:32 PM, Jose A. Rivera <span dir="ltr"><<a href="mailto:jarrpa@redhat.com" target="_blank">jarrpa@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Okay, what are these advantages? :) It would be a lot easier to<br>
maintain one set of files for both Kube and OpenShift than separate<br>
files for each.<br>
<span class="m_-1685897679813955567HOEnZb"><font color="#888888"><br>
--Jose<br>
</font></span><div class="m_-1685897679813955567HOEnZb"><div class="m_-1685897679813955567h5"><br>
On Fri, Dec 2, 2016 at 8:11 AM, Humble Chirammal <<a href="mailto:hchiramm@redhat.com" target="_blank">hchiramm@redhat.com</a>> wrote:<br>
> More or less, there are different advantages we get when we use Templates,<br>
> so I am negative to drop templates from our deployment model.<br>
><br>
> On Fri, Dec 2, 2016 at 7:37 PM, Humble Chirammal <<a href="mailto:hchiramm@redhat.com" target="_blank">hchiramm@redhat.com</a>><br>
> wrote:<br>
>><br>
>> Hi jose,<br>
>><br>
>> Iic, templates are the recommended way to deploy an application in<br>
>> openshift. Also 'Deamonset' can be inside a template. So I dont see a reason<br>
>> to move away from Templates :)<br>
>><br>
>> On Thu, Dec 1, 2016 at 5:46 AM, Jose A. Rivera <<a href="mailto:jarrpa@redhat.com" target="_blank">jarrpa@redhat.com</a>> wrote:<br>
>>><br>
>>> Heyo,<br>
>>><br>
>>> Naturally, as soon as I upload OpenShift support for the gk-deploy<br>
>>> script, I find myself wondering: why do we have templates for heketi<br>
>>> for OpenShift? Specifically, why do we create Template objects instead<br>
>>> of the direct objects (e.g. Service, DeploymentConfig)? Do we have a<br>
>>> need for the ability to recreate heketi pods with different parameters<br>
>>> within the same namespace? We live without them in Kubernetes, and at<br>
>>> present even with Templates the deployment of heketi in OpenShift is<br>
>>> not much easier for a sysadmin if at all.<br>
>>><br>
>>> --Jose<br>
>>><br>
>>> P.S. This all comes as I'm trying to bring a DaemonSet GlusterFS to<br>
>>> OpenShift. ;)<br>
>>> ______________________________<wbr>_________________<br>
>>> heketi-devel mailing list<br>
>>> <a href="mailto:heketi-devel@gluster.org" target="_blank">heketi-devel@gluster.org</a><br>
>>> <a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/heketi-devel</a><br>
>><br>
>><br>
><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
heketi-devel mailing list<br>
<a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
<br></blockquote></div><br></div>