<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 14, 2017 at 11:59 AM, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 05/11/2017 02:32 PM, Lance Bragstad wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hey all,<br>
<br>
One of the Baremetal/VM sessions at the summit focused on what we need<br>
to do to make OpenStack more consumable for application developers [0].<br>
As a group we recognized the need for application specific passwords or<br>
API keys and nearly everyone (above 85% is my best guess) in the session<br>
thought it was an important thing to pursue. The API<br>
key/application-specific password specification is up for review [1].<br>
<br>
The problem is that with all the recent churn in the keystone project,<br>
we don't really have the capacity to commit to this for the cycle. As a<br>
project, we're still working through what we've committed to for Pike<br>
before the OSIC fallout. It was suggested that we reach out to the PWG<br>
to see if this is something we can get some help on from a keystone<br>
development perspective. Let's use this thread to see if there is anyway<br>
we can better enable the community through API keys/application-specific<br>
passwords by seeing if anyone can contribute resources to this effort.<br>
</blockquote>
<br></span>
In the session, I signed up to help get the spec across the finish line. I'm also going to do my best to write up something resembling a user story so that we're all on the same page about what this is, what it isn't and what comes next.<br></blockquote><div><br></div><div>Thanks Monty. If you have questions about the current proposal, Ron might be lingering in IRC (rderose). David (dstanek) was also documenting his perspective in another spec [0].</div><div><br></div><div><br></div><div>[0] <a href="https://review.openstack.org/#/c/440593/">https://review.openstack.org/#/c/440593/</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I probably will not have the time to actually implement the code - but if the PWG can help us get resources allocated to this I'll be happy to help them.<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[0] <a href="https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal" rel="noreferrer" target="_blank">https://etherpad.openstack.org<wbr>/p/BOS-forum-using-vm-and-bare<wbr>metal</a><span class="gmail-"><br>
<<a href="https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal" rel="noreferrer" target="_blank">https://etherpad.openstack.or<wbr>g/p/BOS-forum-using-vm-and-bar<wbr>emetal</a>><br>
[1] <a href="https://review.openstack.org/#/c/450415/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/450415/</a><br></span>
<<a href="https://review.openstack.org/#/c/450415/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/450415/</a>><br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote></div><br></div></div>