Open Stack

Paul,

This is a good question probably best sent to the operators list.  I’m not sure also if operators know the difference in Kolla’s implementation.  I don’t believe Kolla’s documentation explains it particularly well.

I never wanted COPY_ALWAYS in the code base, but I tolerated it as COPY_ONCE was still the default and COPY_ALWAYS has a use case that developers want.  The default was changed from COPY_ONCE to COPY_ALWAYS, and I again tolerated that since operators can always change the default.  I am not tolerant of removal without a significant dialogue with operators.  This would take some work on the Kolla core team’s part to make sure operators really understood the two models and had a good comprehension of what they would be giving away permanently if COPY_ONCE were deprecated.

Putting myself into an operator’s shoes, I believe COPY_ONCE is how I would deploy Kolla if I understood the differences between COPY_ONCE and COPY_ALWAYS.  As a developer of the original two models in Kolla I do understand in great detail the differences.  Some/many developers that work on Kolla don’t understand the difference (this I know for fact).  I’m not sure the delta here has been made clear to the operator or developer community.  It requires an in-depth explanation.

Currently Kolla deployments are at 1%, testing at 4%, and interested at 11% [1].  Given these facts, it is not clear to me that enough operators have enough experience with Kolla to have this conversation at this time.

Regards
-steve

[1] https://www.openstack.org/analytics

-----Original Message-----
From: Paul Bourke <paul.bourke at oracle.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Date: Thursday, December 1, 2016 at 3:29 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

    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.
    
    On 01/12/16 02:27, Jeffrey Zhang wrote:
    > 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-request at lists.openstack.org?subject:unsubscribe
    > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
    >
    
    __________________________________________________________________________
    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