Jeffrey, The kolla-kubernetes deliverable requires COPY_ONCE not COPY_ALWAYS.
Some operators prefer immutability over hand-modification of configuration files on all nodes. Therefore, I propose we keep both in place. Regards -steve From: Jeffrey Zhang <zhang.lei....@gmail.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Wednesday, November 30, 2016 at 7:27 PM To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [kolla] propose to remove COPY_ONCE feature Kolla has a config_strategy option during deployment. it supports COPY_ONCE and 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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev