<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>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.</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>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.<br>
<br>
<div><br>
</div>
</div>
<div><br>
On Jun 15, 2015, at 9:37 AM, Devdatta Kulkarni <<a href="mailto:devdatta.kulkarni@RACKSPACE.COM">devdatta.kulkarni@RACKSPACE.COM</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p>Hi Adrian,</p>
<p><br>
</p>
<div class="boardCommentBody">
<div class="comment-text" itemprop="commentText">
<p>The new app resource that is being implemented (<a rel="nofollow" href="https://review.openstack.org/#/c/185147/">https:/<wbr>/review.<wbr>openstack.<wbr>org/#/c/<wbr>185147/</a>)<br>
does not enforce name uniqueness.</p>
<p><br>
</p>
<p>This issue was discussed here sometime back.<br>
Earlier thread: <a rel="nofollow" href="http://lists.openstack.org/pipermail/openstack-dev/2015-March/058858.html">
http://<wbr>lists.openstack<wbr>.org/pipermail/<wbr>openstack-<wbr>dev/2015-<wbr>March/058858.<wbr>html</a></p>
<p><br>
</p>
<p>The main argument for requiring unique app names within a tenant was usability. In customer research
</p>
<p>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.</p>
<p><br>
</p>
<p>As a way to accommodate both requirements -- unique names when desired, and making them optional when</p>
<p>its not an issue -- we had said that we could make app uniqueness per tenant configurable.
</p>
<p>So I would be okay if we open a new blueprint to track this work.</p>
</div>
</div>
<p><br>
</p>
<p>Thanks,<br>
</p>
<p>- Devdatta<br>
</p>
<p><br>
</p>
<div style="word-wrap:break-word">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Adrian Otto <<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>><br>
<b>Sent:</b> Friday, June 12, 2015 6:57 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> [openstack-dev] [Solum] Why do app names have to be unique?</font>
<div> </div>
</div>
<div>Team,
<div class=""><br class="">
</div>
<div class="">While triaging this bug, I got to thinking about unique names:</div>
<div class=""><br class="">
</div>
<div class=""><a rel="nofollow" class="external free" href="https://bugs.launchpad.net/solum/+bug/1434293">https://bugs.launchpad.net/solum/+bug/1434293</a> </div>
<div class=""><br class="">
</div>
<div class="">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?</div>
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class=""><br class="">
</div>
<div class="">Adrian</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>__________________________________________________________________________</span><br>
<span>OpenStack Development Mailing List (not for usage questions)</span><br>
<span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe</span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</div>
</blockquote>
</body>
</html>