Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-17 Thread park
On 2015年03月17日 13:31, Christopher Yeoh wrote: On Tue, 17 Mar 2015 15:56:27 +1300 Robert Collins robe...@robertcollins.net wrote: On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: I am worried about SDKs making requests that have additional JSON attributes that were

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-17 Thread Joe Gordon
On Mon, Mar 16, 2015 at 6:06 PM, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: Hi Sean, 2015-03-16 23:15 GMT+09:00 Sean Dague s...@dague.net: Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use =

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-17 Thread Sean Dague
On 03/16/2015 10:56 PM, Robert Collins wrote: On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: I am worried about SDKs making requests that have additional JSON attributes that were previously ignored by v2, but will be considered invalid by the v2.1 validation code.

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-17 Thread Sean Dague
On 03/17/2015 04:17 PM, Robert Collins wrote: On 17 March 2015 at 23:48, Sean Dague s...@dague.net wrote: On 03/16/2015 10:56 PM, Robert Collins wrote: ... Better at the cost of forcing all existing users to upgrade just to keep using code of their own that already worked. Not really

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-17 Thread Robert Collins
On 17 March 2015 at 23:48, Sean Dague s...@dague.net wrote: On 03/16/2015 10:56 PM, Robert Collins wrote: ... Better at the cost of forcing all existing users to upgrade just to keep using code of their own that already worked. Not really 'better' IMO. Different surely. We could (should)

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Ken'ichi Ohmichi
Hi Sean, 2015-03-16 23:15 GMT+09:00 Sean Dague s...@dague.net: Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1:

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Robert Collins
On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: I am worried about SDKs making requests that have additional JSON attributes that were previously ignored by v2, but will be considered invalid by the v2.1 validation code. If we were to just strip out the extra items,

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Bhandaru, Malini K
is our shipped paste.ini going to be for Kilo On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: I am worried about SDKs making requests that have additional JSON attributes that were previously ignored by v2, but will be considered invalid by the v2.1 validation code. If we

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Ken'ichi Ohmichi
2015-03-17 0:08 GMT+09:00 John Garbutt j...@johngarbutt.com: On 16 March 2015 at 14:15, Sean Dague s...@dague.net wrote: Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use =

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Ken'ichi Ohmichi
2015-03-17 11:56 GMT+09:00 Robert Collins robe...@robertcollins.net: On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: I am worried about SDKs making requests that have additional JSON attributes that were previously ignored by v2, but will be considered invalid by the

[openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Sean Dague
Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1: openstack_compute_api_v2 /v2: openstack_compute_api_v2 /v2.1:

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread John Garbutt
On 16 March 2015 at 14:15, Sean Dague s...@dague.net wrote: Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1:

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Ed Leafe
On Mar 16, 2015, at 10:08 AM, John Garbutt j...@johngarbutt.com wrote: Drop of /v1.1 ? --- Only new deploys are really going to base off of our in tree config. I'm not convinced that we want to encourage people setting up new /v1.1 endpoint in tree. I'm not convinced there

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Sean Dague
On 03/16/2015 11:22 AM, Russell Bryant wrote: On 03/16/2015 11:08 AM, John Garbutt wrote: While its not under Nova's control, I think we need to consider the keystone catalog here. It feels nice to have an explicit entry for v2.1, that people start using once the client is updated to support

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Russell Bryant
On 03/16/2015 11:08 AM, John Garbutt wrote: While its not under Nova's control, I think we need to consider the keystone catalog here. It feels nice to have an explicit entry for v2.1, that people start using once the client is updated to support microversions. DefCore would eventually

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Jay Pipes
On 03/16/2015 11:22 AM, Russell Bryant wrote: On 03/16/2015 11:08 AM, John Garbutt wrote: While its not under Nova's control, I think we need to consider the keystone catalog here. It feels nice to have an explicit entry for v2.1, that people start using once the client is updated to support

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Christopher Yeoh
On Mon, 16 Mar 2015 11:22:12 -0400 Russell Bryant rbry...@redhat.com wrote: On 03/16/2015 11:08 AM, John Garbutt wrote: While its not under Nova's control, I think we need to consider the keystone catalog here. It feels nice to have an explicit entry for v2.1, that people start using

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Christopher Yeoh
On Mon, 16 Mar 2015 10:15:50 -0400 Sean Dague s...@dague.net wrote: Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1:

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread GHANSHYAM MANN
Hi Sean- On Mon, Mar 16, 2015 at 11:15 PM, Sean Dague s...@dague.net wrote: Our current top level shipped example paste.ini for Nova includes the following set of endpoint definitions: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Christopher Yeoh
On Tue, 17 Mar 2015 15:56:27 +1300 Robert Collins robe...@robertcollins.net wrote: On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: I am worried about SDKs making requests that have additional JSON attributes that were previously ignored by v2, but will be

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-16 Thread Alex Xu
2015-03-17 13:25 GMT+08:00 Christopher Yeoh cbky...@gmail.com: On Mon, 16 Mar 2015 11:22:12 -0400 Russell Bryant rbry...@redhat.com wrote: On 03/16/2015 11:08 AM, John Garbutt wrote: While its not under Nova's control, I think we need to consider the keystone catalog here. It