Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 04:36 PM, Chris Dent wrote: On Fri, 5 Feb 2016, Sean Dague wrote: I'd ask for folks to try to stay on the original question: What possible naming standards could we adopt, and what are the preferences. 1. service type as described in option 2 2. managed by the api-wg with appeal

Re: [openstack-dev] [all] the trouble with names

Sorry. SWIFT beat you to it. ;) Kevin From: gordon chung [g...@live.ca] Sent: Friday, February 05, 2016 1:00 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] the trouble with names On 05/02/2016 1:22 PM, Ryan Brown wrote: >

Re: [openstack-dev] [all] the trouble with names

On Fri, 5 Feb 2016, Sean Dague wrote: I feel like this is gone a bit "dead horse" of track from the question at hand. Which brings us in danger of ending up on solution #3 (do nothing, we're all burned out from having to discuss things anyway, lets farm goats). We should revisit this ^ issue a

Re: [openstack-dev] [all] the trouble with names

On 05/02/2016 1:22 PM, Ryan Brown wrote: > For example, I think "containers" will be one of those words that > everyone wants to use (buzzbuzzbuzzbuzz). Having at least a way for > projects to say "hm, someone else wants this" would be nice. too late, magnum[1] beat you to it. i'm not sure what

Re: [openstack-dev] [all] the trouble with names

On 05/02/16 20:09, "Jay Pipes" wrote: >On 02/05/2016 08:38 AM, Dean Troyer wrote: >> On Fri, Feb 5, 2016 at 7:00 AM, Chris Dent > > wrote: >> >> I think this discussion is dancing around the edges of a referendum on >> the "duplication" aspect of the big t

Re: [openstack-dev] [all] the trouble with names

#2 On 02/05/2016 02:24 PM, Sean Dague wrote: On 02/05/2016 02:09 PM, Jay Pipes wrote: On 02/05/2016 08:38 AM, Dean Troyer wrote: On Fri, Feb 5, 2016 at 7:00 AM, Chris Dent mailto:cdent...@anticdent.org>> wrote: I think this discussion is dancing around the edges of a referendum on t

Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 02:09 PM, Jay Pipes wrote: > On 02/05/2016 08:38 AM, Dean Troyer wrote: >> On Fri, Feb 5, 2016 at 7:00 AM, Chris Dent > > wrote: >> >> I think this discussion is dancing around the edges of a >> referendum on >> the "duplication" aspect of the bi

Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 08:38 AM, Dean Troyer wrote: On Fri, Feb 5, 2016 at 7:00 AM, Chris Dent mailto:cdent...@anticdent.org>> wrote: I think this discussion is dancing around the edges of a referendum on the "duplication" aspect of the big tent. It is also dancing around the separation of 'API'

Re: [openstack-dev] [all] the trouble with names

I have the benefit here of being a beginner to openstack and having experienced AWS as a user. I think that the current "nova", "cinder" etc naming was confusing to me at first, but that it's a needed stumbling block for devs and deployers/ops to be precise. However, for end-users, probably mo

Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 01:00 PM, Sean Dague wrote: On 02/05/2016 12:16 PM, Ryan Brown wrote: On 02/05/2016 09:08 AM, michael mccune wrote: On 02/04/2016 12:57 PM, Hayes, Graham wrote: On 04/02/2016 15:40, Ryan Brown wrote: [snipped lots] This isn't a perfect solution, but maybe instead of projects.ym

Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 12:16 PM, Ryan Brown wrote: > On 02/05/2016 09:08 AM, michael mccune wrote: >> On 02/04/2016 12:57 PM, Hayes, Graham wrote: >>> On 04/02/2016 15:40, Ryan Brown wrote: > [snipped lots] This isn't a perfect solution, but maybe instead of projects.yml there could be a `registry

Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 09:08 AM, michael mccune wrote: On 02/04/2016 12:57 PM, Hayes, Graham wrote: On 04/02/2016 15:40, Ryan Brown wrote: [snipped lots] This isn't a perfect solution, but maybe instead of projects.yml there could be a `registry.yml` project that would (of course) have all the project.

Re: [openstack-dev] [all] the trouble with names

On 05/02/16 13:50, Dean Troyer wrote: > On Fri, Feb 5, 2016 at 7:13 AM, Neil Jerram > wrote: > > On 04/02/16 11:40, Sean Dague wrote: > > What options do we have? > > > > 1) Use the names we already have: nova, glance, swift, etc. > > > >

Re: [openstack-dev] [all] the trouble with names

On 02/05/2016 07:56 AM, Chris Dent wrote: On Thu, 4 Feb 2016, Sean Dague wrote: 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the road. This is the only option presented thus far which meets the needs of end users and also

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 12:57 PM, Hayes, Graham wrote: On 04/02/2016 15:40, Ryan Brown wrote: On 02/04/2016 09:32 AM, michael mccune wrote: On 02/04/2016 08:33 AM, Thierry Carrez wrote: Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 1

Re: [openstack-dev] [all] the trouble with names

On Fri, Feb 5, 2016 at 7:13 AM, Neil Jerram wrote: > On 04/02/16 11:40, Sean Dague wrote: > > What options do we have? > > > > 1) Use the names we already have: nova, glance, swift, etc. > > > > Upside, collision problem is solved. Downside, you need a secret decoder > > ring to figure out what p

Re: [openstack-dev] [all] the trouble with names

On Fri, Feb 5, 2016 at 7:00 AM, Chris Dent wrote: > I think this discussion is dancing around the edges of a referendum on > the "duplication" aspect of the big tent. It is also dancing around the separation of 'API' from 'implementation'. There is a long-standing disagreement on whether OpenSt

Re: [openstack-dev] [all] the trouble with names

On 04/02/16 11:40, Sean Dague wrote: > What options do we have? > > 1) Use the names we already have: nova, glance, swift, etc. > > Upside, collision problem is solved. Downside, you need a secret decoder > ring to figure out what project does what. This is my preference. Yes, it means that there

Re: [openstack-dev] [all] the trouble with names

On Thu, 4 Feb 2016, gordon chung wrote: my concern with #2 is, we will just end up going to thesaurus.com and searching for alternate words that mean the same general thing and this will be equally confusing. with the big tent, we essentially agreed that duplication is possible, so no matter how

Re: [openstack-dev] [all] the trouble with names

On Thu, 4 Feb 2016, Sean Dague wrote: 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the road. This is the only option presented thus far which meets the needs of end users and also some of our stated goals about creating in

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 15:40, Ryan Brown wrote: > On 02/04/2016 09:32 AM, michael mccune wrote: >> On 02/04/2016 08:33 AM, Thierry Carrez wrote: >>> Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: >> On 04/02/2

Re: [openstack-dev] [all] the trouble with names

While we all consider to look at this problem from within the perspective of OpenStack, the consumer of OpenStack is somebody that is wanting to run a cloud, and not develop a cloud (granted there is overlap in said implementation). They are also comparing clouds and features (e.g. compute, storag

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 10:31 AM, Nick Chase wrote: > What about using a combination of two word names, and generic names. For > example, you might have > > cinder-blockstorage > > and > > foo-blockstorage > > The advantage there is that we don't need to do the thesaurus.com >

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 09:32 AM, michael mccune wrote: On 02/04/2016 08:33 AM, Thierry Carrez wrote: Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: On 04/02/2016 11:40, Sean Dague wrote: 2) Have a registry of "common"

Re: [openstack-dev] [all] the trouble with names

What about using a combination of two word names, and generic names. For example, you might have cinder-blockstorage and foo-blockstorage The advantage there is that we don't need to do the thesaurus.com thing, but also, it enables to specify just blockstorage via a registry. The

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 9:04 AM, Morgan Fainberg wrote: On Thu, Feb 4, 2016 at 4:51 AM, Doug Hellmann mailto:d...@doughellmann.com>> wrote: Excerpts from Sean Dague's message of 2016-02-04 06:38:26 -0500: > A few issues have crept up recently with the service catalog, API > headers, API end points, and

Re: [openstack-dev] [all] the trouble with names

Excerpts from Sean Dague's message of 2016-02-04 08:33:59 -0500: > On 02/04/2016 08:18 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > >> On 04/02/2016 11:40, Sean Dague wrote: > >>> A few issues have crept up recently with the service catalog, API

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 09:35 AM, Anne Gentle wrote: > > > On Thu, Feb 4, 2016 at 7:33 AM, Sean Dague > wrote: > > On 02/04/2016 08:18 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > >> On 04/02/2016 11:40, Sean Dague w

Re: [openstack-dev] [all] the trouble with names

On Thu, Feb 4, 2016 at 7:33 AM, Sean Dague wrote: > On 02/04/2016 08:18 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > >> On 04/02/2016 11:40, Sean Dague wrote: > >>> A few issues have crept up recently with the service catalog, API > >>> header

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 08:33 AM, Thierry Carrez wrote: Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: On 04/02/2016 11:40, Sean Dague wrote: 2) Have a registry of "common" names. Upside, we can safely use common names

Re: [openstack-dev] [all] the trouble with names

On Thu, Feb 4, 2016 at 4:51 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-02-04 06:38:26 -0500: > > A few issues have crept up recently with the service catalog, API > > headers, API end points, and even similarly named resources in different > > resources (e.g. backup), t

Re: [openstack-dev] [all] the trouble with names

On 02/04/2016 08:18 AM, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: >> On 04/02/2016 11:40, Sean Dague wrote: >>> A few issues have crept up recently with the service catalog, API >>> headers, API end points, and even similarly named resources in >>> d

Re: [openstack-dev] [all] the trouble with names

Hayes, Graham wrote: On 04/02/2016 13:24, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: On 04/02/2016 11:40, Sean Dague wrote: 2) Have a registry of "common" names. Upside, we can safely use common names everywhere and not fear collision down the roa

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 13:24, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: >> On 04/02/2016 11:40, Sean Dague wrote: >>> A few issues have crept up recently with the service catalog, API >>> headers, API end points, and even similarly named resources in >>> diff

Re: [openstack-dev] [all] the trouble with names

Excerpts from Hayes, Graham's message of 2016-02-04 12:54:56 +: > On 04/02/2016 11:40, Sean Dague wrote: > > A few issues have crept up recently with the service catalog, API > > headers, API end points, and even similarly named resources in > > different resources (e.g. backup), that are all c

Re: [openstack-dev] [all] the trouble with names

On 04/02/2016 11:40, Sean Dague wrote: > A few issues have crept up recently with the service catalog, API > headers, API end points, and even similarly named resources in > different resources (e.g. backup), that are all circling around a key > problem. Distributed teams and naming collision. > >

Re: [openstack-dev] [all] the trouble with names

Excerpts from Sean Dague's message of 2016-02-04 06:38:26 -0500: > A few issues have crept up recently with the service catalog, API > headers, API end points, and even similarly named resources in different > resources (e.g. backup), that are all circling around a key problem. > Distributed teams

[openstack-dev] [all] the trouble with names

A few issues have crept up recently with the service catalog, API headers, API end points, and even similarly named resources in different resources (e.g. backup), that are all circling around a key problem. Distributed teams and naming collision. Every OpenStack project has a unique name by virtu