[openstack-dev] [kolla] propose to remove COPY_ONCE feature

Paul Bourke paul.bourke at oracle.com
Thu Dec 1 10:29:56 UTC 2016

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 

On 01/12/16 02:27, Jeffrey Zhang wrote:
> Kolla has a config_strategy option during deployment. it supports
> COPY_ALWAYS.  which means whether copy the configuration files defined in
> config.json again during starting containers.
> COPY_ALWAYS: copy all configuration files always during every start (
> default
>              value now )
> COPY_ONCE: copy only once for the first start, then it
>            won't copy even the configuration is changed
> COPY_ALWAYS is more common for most users. change configuration, then
> restart
> containers and it works. but COPY_ONCE is not. after changing the
> configuration,
> should remove the container and start it again.
> for COPY_ONCE, the pro is keeping immutability of the container.  the con is
> making thing difficult. no matter for kolla code or end-user.
> I am curiosity does end-user really care about the immutability cause by
> configuration file? how many user really need such a feature?
> So I propose to remove COPY_ONCE.
> any idea is welcome ;)
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me <http://xcodest.me/>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list