<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hello folks,
<div><br>
</div>
<div>Ade raised concerns about the approach taken in the SSL cert CR here: <a href="https://review.openstack.org/#/c/107190/" target="_blank" style="font-size: 10pt;">https://review.openstack.org/#/c/107190/</a></div>
<div><br>
</div>
<div>In short, he suggests that a state machine approach that gives plugins a lot of control over workflow is not needed, and could lead to plugin developers having more difficulty creating new plugins. I think he has valid points, so I created an etherpad
that details a 'generic' workflow approach, and an approach that simplifies what the plugins need to do (offloading logic to Barbican): <a href="https://etherpad.openstack.org/p/barbican-order-cert-gen-interactions" target="_blank" style="font-size: 10pt;">https://etherpad.openstack.org/p/barbican-order-cert-gen-interactions</a></div>
<div><br>
</div>
<div>Please take a look at the etherpad and weigh in if you can.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>John</div>
<div><br>
</div>
<div><br>
</div>
</div>
</body>
</html>