yahoo-eng-team team mailing list archive

[Dolph Mathews <1394730@xxxxxxxxxxxxxxxxxx>]

I believe this was by design, but I don't know of any deployments that
actually deploy multiple services of the same type in the same cloud
(and multiple branded services to do it, instead of regions). As a "bug"
this strikes me as super low priority, and obviously has the potential
to break anyone relying on this behavior. Further, I don't really see a
misbehavior here that the proposed solution is fixing, beyond the
proverbial "keystone provides a footgun with no safety."

Also, Nova abuse of service types to version their endpoints is a bit of
an abomination, but I don't see how it's related to the issue described
here.

** Changed in: keystone
   Importance: Undecided => Low

** Changed in: keystone
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1394730

Title:
  Keystone should not allow creation multiple service with same type

Status in OpenStack Identity (Keystone):
  Opinion

Bug description:
  In service table only "ID" is primary not type.

  (i.e) I can create two service of type "compute". Assume if I do so,
  then   horizon  and other services clients will throw exception since
  they don't know which service to pick it up.

  Best to way to avoid this, is to not allow creation of two service
  with same type.

  Note: 
    In order to support differnt version, services use differnt type.   e.g Nova creates  service of  type "compute" and "computev3"  

  
  This is related to https://bugs.launchpad.net/bugs/1369401 which is closed as "won't fix"

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1394730/+subscriptions