<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 26, 2013 at 10:03 AM, Brad Topol <span dir="ltr"><<a href="mailto:btopol@us.ibm.com" target="_blank">btopol@us.ibm.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><font face="sans-serif">Agreed, but the history portion of what
you wrote that that takes us from the beginning to where we are now today
has all been implemented. That portion I thought could be added to
the project as it really tells a nice narrative of why what you see in
the keystone code base is actually there.</font>
<br></blockquote><div><br></div><div style>There is room for this type of narrative in the documentation, but I prefer historical context such as [1] to future-looking statements. I definitely like the idea of answering "why" and the Swift example does it nicely. </div>
<div style><br></div><div style>Anne</div><div style><br></div><div style>1. <a href="http://docs.openstack.org/developer/swift/overview_ring.html#history">http://docs.openstack.org/developer/swift/overview_ring.html#history</a></div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br><font face="sans-serif">Thanks.</font>
<br><div class="im">
<br><font face="sans-serif">Brad</font>
<br><font face="sans-serif"><br>
Brad Topol, Ph.D.<br>
IBM Distinguished Engineer<br>
OpenStack<br>
<a href="tel:%28919%29%20543-0646" value="+19195430646" target="_blank">(919) 543-0646</a><br>
Internet: <a href="mailto:btopol@us.ibm.com" target="_blank">btopol@us.ibm.com</a><br>
Assistant: Cindy Willman <a href="tel:%28919%29%20268-5296" value="+19192685296" target="_blank">(919) 268-5296</a></font>
<br>
<br>
<br>
<br><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">Adam Young <<a href="mailto:ayoung@redhat.com" target="_blank">ayoung@redhat.com</a>></font>
<br></div><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif"><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">07/25/2013 09:59 PM</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: [openstack-dev]
A vision for Keystone</font>
<br><div class=""><div class="h5">
<hr noshade>
<br>
<br>
<br><font size="3">On 07/19/2013 10:56 AM, Brad Topol wrote:</font>
<br><font face="sans-serif">Adam,</font><font size="3"> <br>
</font><font face="sans-serif"><br>
Your essay below is outstanding! Any chance part of it could be included
within the keystone project documentation? I think having it in the
project and at folks fingertips would really help folks that are
trying to get up to speed with keystone!</font><font size="3"> </font>
<br><font size="3">Thanks for the input. I think it could be included
in the future, but we have along way to go to implement this vision, and
we are moving toward it one step at a time. When we are closer, I will
revise the essay to reflect reality and maybe more relevant details. At
that point, yes, it can be part of the documentation.<br>
<br>
</font>
<br><font face="sans-serif"><br>
Thanks again for writing this up!</font><font size="3"> <br>
</font><font face="sans-serif"><br>
--Brad</font><font size="3"> </font><font face="sans-serif"><br>
<br>
Brad Topol, Ph.D.<br>
IBM Distinguished Engineer<br>
OpenStack<br>
<a href="tel:%28919%29%20543-0646" value="+19195430646" target="_blank">(919) 543-0646</a><br>
Internet: </font><a href="mailto:btopol@us.ibm.com" target="_blank"><font color="blue" face="sans-serif"><u>btopol@us.ibm.com</u></font></a><font face="sans-serif"><br>
Assistant: Cindy Willman <a href="tel:%28919%29%20268-5296" value="+19192685296" target="_blank">(919) 268-5296</a></font><font size="3"> <br>
<br>
<br>
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
From: </font><font size="1" face="sans-serif">Adam
Young </font><a href="mailto:ayoung@redhat.com" target="_blank"><font size="1" color="blue" face="sans-serif"><u><ayoung@redhat.com></u></font></a><font size="3">
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
To: </font><font size="1" face="sans-serif">OpenStack
Development Mailing List </font><a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><font size="1" color="blue" face="sans-serif"><u><openstack-dev@lists.openstack.org></u></font></a><font size="3">
</font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Date: </font><font size="1" face="sans-serif">07/18/2013
02:21 PM</font><font size="3"> </font><font size="1" color="#5f5f5f" face="sans-serif"><br>
Subject: </font><font size="1" face="sans-serif">[openstack-dev]
A vision for Keystone</font><font size="3"> <br>
</font>
<hr noshade><font size="3"><br>
<br>
</font><tt><font><br>
I wrote up an essay that, I hope, explains where Keystone is headed as
<br>
far as token management.<br>
</font></tt><font size="3" color="blue"><u><br>
</u></font><a href="http://adam.younglogic.com/2013/07/a-vision-for-keystone/" target="_blank"><tt><font color="blue"><u>http://adam.younglogic.com/2013/07/a-vision-for-keystone/</u></font></tt></a><tt><font><br>
<br>
It is fairly long (2000 words) but I attempted to make it readable, and
<br>
to provide the context for what we are doing.<br>
<br>
There are several blueprints for this work, many of which have already
<br>
been implemented. There is at least one that I still need to write up.<br>
<br>
This is not new stuff. It is just an attempt to cleanly lay out the
story.<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list</font></tt><tt><font color="blue"><u><br>
</u></font></tt><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><tt><font color="blue"><u>OpenStack-dev@lists.openstack.org</u></font></tt></a><font size="3" color="blue"><u><br>
</u></font><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font color="blue"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font><br>
</font></tt><font size="3"><br>
<br>
<br>
</font>
<br><tt><font size="3">_______________________________________________<br>
OpenStack-dev mailing list<br>
</font></tt><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank"><tt><font size="3" color="blue"><u>OpenStack-dev@lists.openstack.org</u></font></tt></a><tt><font size="3"><br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font size="3" color="blue"><u>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</u></font></tt></a><tt><font size="3"><br>
</font></tt>
<br><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><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font><br>
</font></tt>
<br></div></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><br><br clear="all"><div><br></div>-- <br>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>
</div></div>