Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-02-01 Thread Brant Knudson
On Wed, Jan 27, 2016 at 1:47 PM, michael mccune wrote: > hi all, > > there have been a few reviews recently where the issue of service type > versus project name have come up for use in the headers. as usual this > conversation can get quite murky as there are several good

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-02-01 Thread Sean Dague
On 02/01/2016 09:13 AM, Brant Knudson wrote: > > > On Wed, Jan 27, 2016 at 1:47 PM, michael mccune > wrote: > > hi all, > > there have been a few reviews recently where the issue of service > type versus project name have come up for use

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-31 Thread Ken'ichi Ohmichi
2016-01-28 5:37 GMT+09:00 Ryan Brown : >> >> I think we would be better served in selecting these things thinking >> about the API consumers first. We already have enough for them to wade >> through, the API-WG is making great gains in herding those particular >> cats, I

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-30 Thread Mike Perez
On 10:55 Jan 28, Kevin L. Mitchell wrote: > On Thu, 2016-01-28 at 11:06 +, Chris Dent wrote: > > I think it is high time we resolve the question of whether the > > api-wg guidelines are evaluating existing behaviors in OpenStack and > > blessing the best or providing aspirational guidelines of

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 Thread Kevin L. Mitchell
On Thu, 2016-01-28 at 11:06 +, Chris Dent wrote: > I think it is high time we resolve the question of whether the > api-wg guidelines are evaluating existing behaviors in OpenStack and > blessing the best or providing aspirational guidelines of practices > which are considered best at a more

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 Thread Jay Pipes
On 01/27/2016 08:31 PM, Dean Troyer wrote: On Wed, Jan 27, 2016 at 1:47 PM, michael mccune > wrote: i am not convinced that we would ever need to have a standard on how these names are chosen for the header values, or if we would even need to

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 Thread Jay Pipes
Couldn't agree more, Chris. -jay On 01/28/2016 11:06 AM, Chris Dent wrote: On Wed, 27 Jan 2016, Dean Troyer wrote: I think we would be better served in selecting these things thinking about the API consumers first. We already have enough for them to wade through, the API-WG is making great

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 Thread Chris Dent
On Wed, 27 Jan 2016, Dean Troyer wrote: I think we would be better served in selecting these things thinking about the API consumers first. We already have enough for them to wade through, the API-WG is making great gains in herding those particular cats, I would hate to see giving back some

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 Thread Alex Meade
I'd like an answer on this specific issue. I agree with Chris and I wonder if our goal is consistency across services or an ideal standard. Nova has 'X-OpenStack-Nova-API-Version' and Manila has 'X-Openstack-Manila-Api-Version'. If we deviate from this, we should suggest that those projects add

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-28 Thread michael mccune
On 01/28/2016 06:32 AM, Jay Pipes wrote: Couldn't agree more, Chris. -jay On 01/28/2016 11:06 AM, Chris Dent wrote: On Wed, 27 Jan 2016, Dean Troyer wrote: I think we would be better served in selecting these things thinking about the API consumers first. We already have enough for them

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-27 Thread Ravi, Goutham
-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [api] service type vs. project name for use in headers On Wed, Jan 27, 2016 at 1:47 PM, michael mccune <m...@redhat.com<mailto:m...@redhat.com>> wrote: i am not convinced that we would ever need to have a standard on how t

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-27 Thread Dean Troyer
On Wed, Jan 27, 2016 at 1:47 PM, michael mccune wrote: > i am not convinced that we would ever need to have a standard on how these > names are chosen for the header values, or if we would even need to have > header names that could be deduced. for me, it would be much better

[openstack-dev] [api] service type vs. project name for use in headers

2016-01-27 Thread michael mccune
hi all, there have been a few reviews recently where the issue of service type versus project name have come up for use in the headers. as usual this conversation can get quite murky as there are several good examples where service type alone is not sufficient (for example if a service

Re: [openstack-dev] [api] service type vs. project name for use in headers

2016-01-27 Thread Ryan Brown
On 01/27/2016 03:31 PM, Dean Troyer wrote: On Wed, Jan 27, 2016 at 1:47 PM, michael mccune > wrote: i am not convinced that we would ever need to have a standard on how these names are chosen for the header values, or if we would even need to