<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">@sdake</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">we can keep COPY_ONCE and COPY_ALWAY in docker images. But in </div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">kolla-ansible side, only implement COPY_ALWAY.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">And does kolla-k8s will only implement COPY_ONCE?</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">@Gerard</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">COPY_ALWAYS only affect the configuration file, like /etc/nova/nova.conf.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">others are still immutable.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">@Paul</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">For the end-user, either COPY_ONCE or COPY_ALWAYS is transparent. When he</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">running kolla-ansible, there is no big difference.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 1, 2016 at 6:29 PM, Paul Bourke <span dir="ltr"><<a href="mailto:paul.bourke@oracle.com" target="_blank">paul.bourke@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">While I would be interested to know how many people actually do use COPY_ONCE, I think if I was in charge of a production deployment I would use COPY_ONCE.<div><div class="h5"><br>
<br>
On 01/12/16 02:27, Jeffrey Zhang wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Kolla has a config_strategy option during deployment. it supports<br>
COPY_ONCE and<br>
COPY_ALWAYS. which means whether copy the configuration files defined in<br>
config.json again during starting containers.<br>
<br>
COPY_ALWAYS: copy all configuration files always during every start (<br>
default<br>
value now )<br>
COPY_ONCE: copy only once for the first start, then it<br>
won't copy even the configuration is changed<br>
<br>
COPY_ALWAYS is more common for most users. change configuration, then<br>
restart<br>
containers and it works. but COPY_ONCE is not. after changing the<br>
configuration,<br>
should remove the container and start it again.<br>
<br>
for COPY_ONCE, the pro is keeping immutability of the container. the con is<br>
making thing difficult. no matter for kolla code or end-user.<br>
<br>
I am curiosity does end-user really care about the immutability cause by<br>
configuration file? how many user really need such a feature?<br>
<br>
So I propose to remove COPY_ONCE.<br>
<br>
any idea is welcome ;)<br>
<br>
--<br>
Regards,<br>
Jeffrey Zhang<br></div></div>
Blog: <a href="http://xcodest.me" rel="noreferrer" target="_blank">http://xcodest.me</a> <<a href="http://xcodest.me/" rel="noreferrer" target="_blank">http://xcodest.me/</a>><span class=""><br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Regards,</font></span></div><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Jeffrey Zhang</font></span></div><div><span style="font-family:monospace,monospace;font-size:12.8px">Blog: </span><a href="http://xcodest.me/" style="font-family:monospace,monospace;font-size:12.8px" target="_blank">http://xcodest.me</a><font face="monospace, monospace"><br></font></div></div></div></div></div></div></div></div></div>
</div>