Open Stack

On Thu, Sep 10, 2015 at 2:36 AM, Neil Jerram <Neil.Jerram at metaswitch.com> wrote:
> I think it should be a requirement for the client to provide back-compatibility; or else to use a standard deprecation pattern‎, i.e. to emit a deprecation warning message, for a cycle or two, before removing support for something.
>

Yes, +1 on that. Glance 1.0.0 returns an empty list for our public
cloud right now.

Thanks,
Curtis.

> (I was just caught out by the change from '--is-public=true' to '--visibility public', which - from an uninformed point of view - feels like an unnecessary irritation.)
>
> Regards,
>       Neil
>
> ‎
>   Original Message
> From: Nikhil Komawar
> Sent: Wednesday, 9 September 2015 23:42
> To: openstack-operators at lists.openstack.org
> Subject: [Openstack-operators] Adding v1 LIKE support to python-glanceclient    releases 1.x.x
>
> Hi all,
>
> We recently release python-glanceclient 1.0.0 and it has the default
> shell version as v2. This may result into some scripts not detecting the
> change by default and discomfort to an extent.
>
> So, I am reaching out to this list with the hope of getting some
> feedback on the requirements, pros and cons you all think exist for
> adding some support for v1 like calls as hidden command to the default
> python-glanceclient shell API that is v2 centric by default. This should
> unbreak the scripts to an extent and give a warning to users to update
> the scripts in a stipulated time period so that they use the v2 API.
>
> Here's the proposed patch https://review.openstack.org/#/c/219802/ . We
> are not yet sure if we need to get it merged by tomorrow so that it can
> be in stable/liberty by the end of the week. There has been one request
> to get those in and the feedback we received from the developer
> community was neutral.
>
> In order to form an opinion on what's best for our users, we need some
> feedback on this topic. Please send us your thoughts as soon as possible
> and we will try to accommodate the same if permissible within the
> technical limitations:
>
> 1. Whether you would like these commands added as hidden commands so
> that shell API works like before (to extent possible).
> 2. You would like to use v2 shell API of the client by default and don't
> care about this commit.
> 3. You don't care about the change. Your scripts are awesome and can
> adjust to the upgrade of the client easily.
> 4. Anything else.
>
> --
>
> Thanks,
> Nikhil
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



-- 
Twitter: @serverascode
Blog: serverascode.com