<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">In OpenStack, we have a very common problem of VM's needing to talk to OpenStack Services.<br>
<br>
Heat, Trove, Sahara, Octavia, Magnum, other services that provision vm's, all have need to either have a guest agent talk to a controller via Zaqar using a Keystone credential, or fetch Secrets from Barbican which needs a Keystone credential.<br>
<br>
The fledgling Global App Catalog project really needs it as well to enable generic heat templates to be able to be written and contributed. It takes a long time to build up a community around such features so delay now delays the app catalog resources much
further out.<br>
<br>
The lack of the Instance User feature is causing OpenStack projects to come up with their own solutions and its causing a lot of duplicate work and a lot of suboptimal implementations to come about. This really need to be fixed once and for all.<br>
<br>
I met with a lot of the teams during the last Summit. We came up with a plan, and have spent a significant amount of time bashing out the details out in the Nova spec. We've gotten +1's from both the Barbican and Keystone PTL's. It seems to have gotten stuck
in Nova's review queue and has such missed the hard deadline. I believe this is very detrimental to OpenStack in general.<br>
<br>
So, I'd formally like to request either a Spec freeze exception be granted so that the Nova team will have time to review their part of the spec, or that the Spec be approved and we can hash out the remaining details when the code enters the review process.
There is still plenty of time for that.<br>
<br>
<a href="https://review.openstack.org/#/c/186617/" target="_blank">https://review.openstack.org/#/c/186617/</a><br>
<br>
Thanks,<br>
Kevin<br>
</div>
</body>
</html>