Re: [Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

[Flavio Percoco]

On 09/09/15 21:46 -0400, Clayton O'Neill wrote:

I'd be glad to see the backwards compatibility parts go in.  I got bitten by
this earlier this week and ended up switching my scripts over to using the
python-openstackclient library to work around it.



Hey Clayton,

Thanks for the feedback.

Could you be more precise on what incompatibility affected you?

The patch that Nikhil linked in his email brings in several
"compatibilities" with v1. I personally think they should be examined
1 by 1 rather than pulling them all in, hence my question.

Switching to python-openstack client must have required some effort
and I'm curious to know why you decided to do that rather than
adapting your scripts to use the v2 cli. Do you have Glance's v2
deployed?

Ideally, I think we should just move to use openstackclient, really.
But glanceclient is what we have now and that's what the Glance team
has focused on the most lately so I'd appreaciate as much feedback as
possible from you and others.

Thanks for your time,
Flavio



On Wed, Sep 9, 2015 at 6:41 PM, Nikhil Komawar  wrote:

   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@lists.openstack.org
   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators





___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



--
@flaper87
Flavio Percoco


pgpdHvfcNV6Cq.pgp
Description: PGP signature
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

[Clayton O'Neill]

I ran into this issue on my laptop where I had just pip installed glance
client and gotten the latest version.  The script I was working on I want
to run in multiple environments, so it was easier to rely on the openstack
client which has the same CLI API (and generally easier to integrate with)
than to make it work with two versions of the glance client or to force a
specific version on systems I may not control.

I don't remember the exact behavior change that bit me, but since it was
trying to upload an image if it didn't already exist by name, I suspect
that it was the --is-public/--is-protected change.

I think one of the issues here is that a lot of our users also install from
pip, and from their standpoint this is an "unannounced" change.  Not
because it's literally unannounced, but because many of them probably don't
install specific versions of the clients even though we do recommend
specific versions.  From their standpoint I think they consider this
"unannounced" mostly because I doubt any of them follow any of the mailing
lists where it would have been announced.  I'm not sure what the right
answer here is, but it's definitely a difficult situation.

On Mon, Sep 14, 2015 at 7:18 AM, Flavio Percoco  wrote:

> On 09/09/15 21:46 -0400, Clayton O'Neill wrote:
>
>> I'd be glad to see the backwards compatibility parts go in.  I got bitten
>> by
>> this earlier this week and ended up switching my scripts over to using the
>> python-openstackclient library to work around it.
>>
>
>
> Hey Clayton,
>
> Thanks for the feedback.
>
> Could you be more precise on what incompatibility affected you?
>
> The patch that Nikhil linked in his email brings in several
> "compatibilities" with v1. I personally think they should be examined
> 1 by 1 rather than pulling them all in, hence my question.
>
> Switching to python-openstack client must have required some effort
> and I'm curious to know why you decided to do that rather than
> adapting your scripts to use the v2 cli. Do you have Glance's v2
> deployed?
>
> Ideally, I think we should just move to use openstackclient, really.
> But glanceclient is what we have now and that's what the Glance team
> has focused on the most lately so I'd appreaciate as much feedback as
> possible from you and others.
>
> Thanks for your time,
> Flavio
>
>
>
>> On Wed, Sep 9, 2015 at 6:41 PM, Nikhil Komawar 
>> wrote:
>>
>>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@lists.openstack.org
>>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>>
> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
> --
> @flaper87
> Flavio Percoco
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

[Neil Jerram]

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. 

(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@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@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

[Nikhil Komawar]

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@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

[Clayton O'Neill]

I'd be glad to see the backwards compatibility parts go in.  I got bitten
by this earlier this week and ended up switching my scripts over to using
the python-openstackclient library to work around it.

On Wed, Sep 9, 2015 at 6:41 PM, Nikhil Komawar 
wrote:

> 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@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

[Sam Morrison]

I’d just like things like image-list to work under the new client :-)

https://bugs.launchpad.net/python-glanceclient/+bug/1492887


> On 10 Sep 2015, at 8:41 am, Nikhil Komawar  wrote:
> 
> 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@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators