<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Dev, thanks for bringing up the item about Heat enforcing unique stack names.. My mistake on thinking it supported non-unique stack names. I remember it working early on, but probably got changed/fixed somewhere along the way.</div>
<div><br>
</div>
<div>My argument in IRC was one based on consistency with related/similar projects... So, as Murali pointed out, if things aren't consistent within OpenStack, then that certainly leaves much more leeway in my opinion for Solum to determine its own path without
concern for falling in line with what the other projects have done (since a precedent can't be established). </div>
<div><br>
</div>
<div>To be honest, I don't agree with the argument about github, however. Github (and also Heroku) are using URLs, which are Unique IDs. I caution against conflating a URL with a name, where a URL in the case of github serves both purposes, but each (both
a name and an ID) have merit as standalone representations. </div>
<div><br>
</div>
<div>I am happy to give my support to enforcing unique names as the Solum default, but I continue to highly encourage things be architected in a way that non-unique names could be supported in the future on at least a per-tenant basis, should that need become
validated by customer asks.</div>
<div><br>
</div>
<div>Kind regards,</div>
<div>-Keith</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Murali Allada <<a href="mailto:murali.allada@RACKSPACE.COM">murali.allada@RACKSPACE.COM</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, March 11, 2015 2:12 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [Solum] Should app names be unique?<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div><style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
<div dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>The only reason this came up yesterday is because we wanted Solums 'app create' behavior to be consistent with other openstack services.<br>
</p>
<p><br>
</p>
<p>However, if heat has a unique stack name constraint and glance\nova don't, then the argument of consistency does not hold.<br>
</p>
<p><br>
</p>
<p>I'm still of the opinion that we should have a unique name constraint for apps and languagepacks within a tenants namespace, as it can get very confusing if a user creates multiple apps with the same name.<br>
</p>
<p><br>
</p>
<p>Also, customer research done here at Rackspace has shown that users prefer using 'names' rather than 'UUIDs'.<br>
</p>
<p><br>
</p>
<p>-Murali<br>
</p>
<p><br>
</p>
<p><br>
</p>
<div dir="ltr" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri,sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Devdatta Kulkarni <<a href="mailto:devdatta.kulkarni@RACKSPACE.COM">devdatta.kulkarni@RACKSPACE.COM</a>><br>
<b>Sent:</b> Wednesday, March 11, 2015 2:48 PM<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><br>
<b>Subject:</b> [openstack-dev] [Solum] Should app names be unique?</font>
<div> </div>
</div>
<div>
<p>Hi Solum team,</p>
<p><br>
</p>
<p>In yesterday's team meeting the question of whether Solum should enforce unique app name constraint
</p>
<p>within a tenant came up.</p>
<p><br>
</p>
<p>As a recollection, in Solum one can create an 'app' using: </p>
<p>solum app create --plan-file <plan-file> --name <app-name></p>
<p><br>
</p>
<p>Currently Solum does support creating multiple apps with the same name. </p>
<p>However, in yesterday's meeting we were debating/discussing whether this should be the case.</p>
<p>The meeting log is available here:<br>
</p>
<p><a href="http://eavesdrop.openstack.org/meetings/solum_team_meeting/2015/solum_team_meeting.2015-03-10-21.00.log.html">http://eavesdrop.openstack.org/meetings/solum_team_meeting/2015/solum_team_meeting.2015-03-10-21.00.log.html</a><br>
<br>
</p>
<p><br>
</p>
<p>To set the context for discussion, consider the following:</p>
<p>- heroku does not allow creating another app with the same name as that of an already existing app</p>
<p>- github does not allow creating another repository with the same name as that of an already existing repo</p>
<p><br>
</p>
<span dir="ltr" style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font face="Calibri,Arial,Helvetica,sans-serif">
<div style="margin-top:0; margin-bottom:0">Thinking about why this might be in case for heroku, one aspect that comes to mind is the setting of a 'remote' using<br>
the app name. When we do a 'git push', it happens to this remote.<br>
When we don't specify a remote in 'git push' command, git defaults to using the 'origin' remote.<br>
<span dir="ltr" style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font face="Calibri,Arial,Helvetica,sans-serif">
<div style="margin-top:0; margin-bottom:0">Even if multiple remotes with the same name were to be possible, when using an implicit command such as 'git push',
<br>
in which some of the input comes from the context, the system will not be able to disambiguate which remote to use.
</div>
</font></font></span><span dir="ltr" style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font face="Calibri,Arial,Helvetica,sans-serif">
<div style="margin-top:0; margin-bottom:0">So requiring unique names ensures that there is no ambiguity when using such implicit commands.<br>
<span dir="ltr" style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font face="Calibri,Arial,Helvetica,sans-serif">This might also be the reason why on github we cannot create repository with an already existing name.</font></font></span><br>
<br>
But this is just a guess for why unique names might be required. I could be totally off.<br>
</div>
</font></font></span></div>
</font></font></span><span dir="ltr" style="font-size:12pt; background-color:white"><font face="Calibri,Arial,Helvetica,sans-serif"><font face="Calibri,Arial,Helvetica,sans-serif">
<div style="margin-top:0; margin-bottom:0"><br>
</div>
<div style="margin-top:0; margin-bottom:0">I think Solum's use case is similar.<br>
</div>
<div style="margin-top:0; margin-bottom:0"><br>
</div>
<div style="margin-top:0; margin-bottom:0">Agreed that Solum currently does not host application repositories and so there is no question of
</div>
<div style="margin-top:0; margin-bottom:0">Solum generated remotes. But by allowing non-unique app names</div>
<div style="margin-top:0; margin-bottom:0">it might be difficult to support this feature in the future.
</div>
<div style="margin-top:0; margin-bottom:0"><br>
As an aside, I checked what position other Openstack services take on this issue.<br>
1) Heat enforces unique stack-name constraint.<br>
2) Nova does not enforce this constraint.<br>
</div>
</font></font></span><span dir="ltr" style="font-size:12pt; background-color:white"></span>
<p><br>
</p>
<p>So it is clear that within Openstack there is no consistency on this issue.<br>
</p>
<p><br>
</p>
<p>What should Solum do?</p>
<p><br>
</p>
<p>Thoughts?</p>
<p><br>
</p>
<p>Best regards,</p>
<p>Devdatta<br>
</p>
<p><br>
</p>
<p><br>
</p>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>