[openstack-dev] [Solum] Why do app names have to be unique?
devdatta.kulkarni at RACKSPACE.COM
Mon Jun 15 14:33:25 UTC 2015
The new app resource that is being implemented (https://review.openstack.org/#/c/185147/)
does not enforce name uniqueness.
This issue was discussed here sometime back.
Earlier thread: http://lists.openstack.org/pipermail/openstack-dev/2015-March/058858.html
The main argument for requiring unique app names within a tenant was usability. In customer research
it was found that users were more comfortable with using names than UUIDs. Without the unique app name constraint, users would have to resort to using UUIDs when they create multiple apps with the same name.
As a way to accommodate both requirements -- unique names when desired, and making them optional when
its not an issue -- we had said that we could make app uniqueness per tenant configurable.
So I would be okay if we open a new blueprint to track this work.
From: Adrian Otto <adrian.otto at rackspace.com>
Sent: Friday, June 12, 2015 6:57 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Solum] Why do app names have to be unique?
While triaging this bug, I got to thinking about unique names:
Should our app names be unique? Why? Should I open a blueprint for a new feature to make name uniqueness optional, and default it to "on". If not, why?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev