<div dir="ltr">On Thu, Aug 11, 2016 at 9:59 AM, Sebastian Laskawiec <span dir="ltr"><<a href="mailto:slaskawi@redhat.com" target="_blank">slaskawi@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hey!<div><br></div><div>I'm working on configuration management in cloud environment [1]. I put some finding in the ticket [1] but let me tell you more about the options I investigated:</div><div><ul><li>Kubernetes/OpenShift ConfigMaps [2][3]</li><ul><li>Those structures are specially designed to hold configuration data in any format (yaml, json, properties, xml, doesn't matter).</li><li>The configuration can be mounted into a pod as a directory (technically a volume). We can not mount it as a single file. Having said that we would need to either store cloud.xml file separately (standalone/cloud/<wbr>configuration?) or ask users to build configuration from whole standalone/configuration directory. Both options are valid in my opinion.</li></ul><li>OpenShift S2I [4] builder</li><ul><li>S2I builder takes a git repository and a Docker image and combines those two together.</li><li>We could store a cloud.xml file inside a git repository and modify our infinispan Docker image to support S2I scripts (if cloud.xml is detected in a git repository - replace the default configuration).</li><li>Unfortunately it's OpenShift specific thing.</li></ul><li>Extend the Infinispan Docker image</li><ul><li>We could ask users to extend our Docker image and put their specific configuration there</li><li>The biggest advantage - it will work regardless to the environment (pure Docker, Kubernetes, OpenShift, doesn't matter)</li></ul></ul><div>All options require restarting pods to update configuration (remember, pods were designed to be immutable).<br></div><div><br></div><div>I think we should support 2 options - ConfigMaps for Kubernetes and OpenShift and extending our Docker image for all other use cases (because this option gives the most flexibility).</div></div><div><br></div><div>What do you think?</div></div></blockquote><div><br><br></div><div>For static configuration use cases, I think they are all valid options, it's up to the user to pick the right one depending on the environment/use case. <br>With relation to the S2I specifically, it could be really interesting for the cases when custom code (marshallers, filters, taks, etc) need to be deployed along Infinispan: <br>the S2I machinery could build those jars, add custom configurations, combine with the jboss/infinispan-server and have it running on Openshift.<br></div><div><br>When dynamic configuration changes need to be applied, I think [1] is best option.<br><br>[1] <a href="https://issues.jboss.org/browse/ISPN-6000">https://issues.jboss.org/browse/ISPN-6000</a><br></div><div><br></div><div>Cheers,<br></div><div>Gustavo <br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks</div><div>Sebastian</div><div><br></div><div>[1] <a href="https://issues.jboss.org/browse/ISPN-6675" target="_blank">https://issues.jboss.org/<wbr>browse/ISPN-6675</a></div><div>[2] <a href="http://kubernetes.io/docs/user-guide/configmap/" target="_blank">http://kubernetes.io/docs/<wbr>user-guide/configmap/</a></div><div>[3] <a href="https://docs.openshift.org/latest/dev_guide/configmaps.html" target="_blank">https://docs.openshift.<wbr>org/latest/dev_guide/<wbr>configmaps.html</a></div><div>[4] <a href="https://github.com/openshift/source-to-image" target="_blank">https://github.com/<wbr>openshift/source-to-image</a></div></div>
<br>______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br></blockquote></div><br></div></div>