Open Stack

I think app names should be unique per tenant. My opinion is that this should be solums default behavior and does not require an extra setting in the config file.

I feel the pain of non unique names when I play with my own vagrant environment and deploy multiple 'test' apps. To identify the right app, I either need to save the uuid in a notepad to refer to later, or I just deploy them with unique names, which makes non unique names unnecessary.

I wouldn't want to list my apps and see multiple apps with the same name. If I do, and don't have the uuid saved somewhere, I'm totally lost.



On Jun 15, 2015, at 9:37 AM, Devdatta Kulkarni <devdatta.kulkarni at RACKSPACE.COM<mailto:devdatta.kulkarni at RACKSPACE.COM>> wrote:


Hi Adrian,


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.


Thanks,

- Devdatta


________________________________
From: Adrian Otto <adrian.otto at rackspace.com<mailto: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?

Team,

While triaging this bug, I got to thinking about unique names:

https://bugs.launchpad.net/solum/+bug/1434293

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?

Thanks,

Adrian
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150616/c4941c49/attachment-0001.html>