<p dir="ltr">Right, I understand that. However, the point is that the tenant name is being stored outside of Keystone and it doesn't ever appear to be updated. </p>
<p dir="ltr">I had proposed a spec to cache the tenant names for the Big Switch code and it was declined because of the duplication of information. </p>
<div class="gmail_quote">On Sep 22, 2014 10:52 AM, "Mohammad Banikazemi" <<a href="mailto:mb@us.ibm.com">mb@us.ibm.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<p><font face="sans-serif">In the patch being referred to here and in the IBM controller, the project ID is the unique identifier used. The name is simply an additional piece of information that may perhaps be used for debugging. The back-end (controller) keeps a name not as a unique identifier but in addition to the unique identifier which is the project ID. For all practical purposes, we can set the project name for all projects to Kevin Benton and nothing will change functionally.</font><br>
<br>
<font face="sans-serif">This should be obvious from the code and how the project id and not the name has been used in the plugin. Perhaps the commit message can specify this clearly to avoid any confusion.</font><br>
<br>
<font face="sans-serif">Best,</font><br>
<br>
<font face="sans-serif">Mohammad</font><br>
<br>
<br>
<br>
<img width="16" height="16" src="cid:1__=0ABBF7C8DFCC3D2B8f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for Dolph Mathews ---09/22/2014 10:53:29 AM---On Sun, Sep 21, 2014 at 3:58 PM, Kevin Benton <blak111@gmai"><font color="#424282" face="sans-serif">Dolph Mathews ---09/22/2014 10:53:29 AM---On Sun, Sep 21, 2014 at 3:58 PM, Kevin Benton <<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>> wrote: > So based on those guideli</font><br>
<br>
<font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com" target="_blank">dolph.mathews@gmail.com</a>></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">09/22/2014 10:53 AM</font><br>
<font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">Re: [openstack-dev] [Neutron] - what integration with Keystone is allowed?</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091a5"><br>
<br>
<br>
<br>
<font size="3" face="serif">On Sun, Sep 21, 2014 at 3:58 PM, Kevin Benton <</font><a href="mailto:blak111@gmail.com" target="_blank"><font size="3" color="#0000FF" face="serif"><u>blak111@gmail.com</u></font></a><font size="3" face="serif">> wrote:</font>
<ul style="padding-left:9pt"><font size="3" face="serif">So based on those guidelines there would be a problem with the IBM patch because it's storing the tenant name in a backend controller, right?</font></ul>
<br>
<font size="3" face="serif">It would need to be regarded as an expiring cache if Neutron chose to go that route. I'd wholly recommend against it though, because I don't see a strong use case to use names instead of IDs here (correct me if I'm wrong).</font><br>
<font size="3" face="serif"> </font>
<ul style="padding-left:9pt"><font size="3" face="serif">On Sep 21, 2014 12:18 PM, "Dolph Mathews" <</font><a href="mailto:dolph.mathews@gmail.com" target="_blank"><font size="3" color="#0000FF" face="serif"><u>dolph.mathews@gmail.com</u></font></a><font size="3" face="serif">> wrote:</font>
<ul style="padding-left:9pt"><font size="3" face="serif">Querying keystone for tenant names is certainly fair game.</font><br>
<br>
<font size="3" face="serif">Keystone should be considered the only source of truth for tenant names though, as they are mutable and not globally unique on their own, so other services should not stash any names from keystone into long term persistence (users, projects, domains, groups, etc-- roles might be an odd outlier worth a separate conversation if anyone is interested).</font><br>
<br>
<font size="3" face="serif">Store IDs where necessary, and use IDs on the wire where possible though, as they are immutable.</font><br>
<br>
<font size="3" face="serif">On Sat, Sep 20, 2014 at 7:46 PM, Kevin Benton <</font><a href="mailto:blak111@gmail.com" target="_blank"><font size="3" color="#0000FF" face="serif"><u>blak111@gmail.com</u></font></a><font size="3" face="serif">> wrote:</font>
<ul style="padding-left:9pt"><font size="3" face="serif">Hello all,<br>
<br>
A patch has come up to query keystone for tenant names in the IBM<br>
plugin.[1] As I understand it, this was one of the reasons another<br>
mechanism driver was reverted.[2] Can we get some clarity on the level<br>
of integration with Keystone that is permitted?<br>
<br>
Thanks<br>
<br>
1. </font><a href="https://review.openstack.org/#/c/122382" target="_blank"><font size="3" color="#0000FF" face="serif"><u>https://review.openstack.org/#/c/122382</u></font></a><font size="3" face="serif"><br>
2. </font><a href="https://review.openstack.org/#/c/118456" target="_blank"><font size="3" color="#0000FF" face="serif"><u>https://review.openstack.org/#/c/118456</u></font></a><font size="3" color="#888888" face="serif"><br>
<br>
--<br>
Kevin Benton<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><font size="3" color="#0000FF" face="serif"><u>OpenStack-dev@lists.openstack.org</u></font></a><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="#0000FF" face="serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a></ul>
<br>
<font size="3" face="serif"><br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><font size="3" color="#0000FF" face="serif"><u>OpenStack-dev@lists.openstack.org</u></font></a><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="#0000FF" face="serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size="3" face="serif"><br>
</font></ul>
<font size="3" face="serif"><br>
_______________________________________________<br>
OpenStack-dev mailing list</font><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><font size="3" color="#0000FF" face="serif"><u>OpenStack-dev@lists.openstack.org</u></font></a><font size="3" color="#0000FF" face="serif"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><font size="3" color="#0000FF" face="serif"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></a><font size="3" face="serif"><br>
</font></ul>
<tt><font>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
</font></tt><tt><font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><tt><font><br>
</font></tt><br>
</p></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div>