<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} p
{margin-top:0;
margin-bottom:0}--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<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>
</body>
</html>