<div dir="ltr">Hi, Alexander<div><br></div><div>Thank you for formalizing specifications and requirements! I will be glad to work on implementation of app actions, once we finish discussing them. I have created new <a href="https://blueprints.launchpad.net/murano/+spec/application-actions">blueprint</a> and referenced etherpad as specification. </div>
<div>Actually your specification in etherpad looks very comprehensive and quite enough to implement first version of the feature. I think I can start drafting implementation while we also working on specification at the same time.</div>
<div><br></div><div>I think Events should be based on Actions, so we can return to Events in the next milestone and revisit them.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 29, 2014 at 8:26 PM, Alexander Tivelkov <span dir="ltr"><<a href="mailto:ativelkov@mirantis.com" target="_blank">ativelkov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">Hi folks!</div><div class="gmail_default" style="font-size:small">
<br></div><div class="gmail_default" style="font-size:small">During the Atlanta Summit there was quite a lot of talks about the Application Lifecycle management and Murano's role in this process. There were several cross-project sessions between Murano, Heat and Solum teams ([1]) at which it was decided that Murano has its own place in the application-management ecosystem and should be able to define custom actions or workflows for its applications, while using Heat and its ALM capabilities as the underlying service. </div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">At the same time I had some conversation with potential customers and contributors, who have expressed strong interest in having actions in Murano in this cycle. </div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">That's why I've decided to drive this process forward and formalize the spec and requirements for the Actions feature in Murano.</div>
<div class="gmail_default" style="font-size:small">I've created a draft of the spec - please see the etherpad at [2] for details. I'd like some comments and discussion on the spec, and once we all agree on that, I will be happy to find a volunteer eager to implement this during Juno :) </div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">BTW, we have a number of blueprints already created on the topic ([3], [4], [5], [6]), but they lack the details and have some problems with terminology ('events' and 'actions' are definitely not the same, while the blueprints mix them). I think we should revisit these BPs and either change them to reflect the updated vision or to mark them as superseded and create more appropriate one. </div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">[1] <a href="https://etherpad.openstack.org/p/9XQ7Q2NQdv" target="_blank">https://etherpad.openstack.org/p/9XQ7Q2NQdv</a></div>
<div class="gmail_default" style="font-size:small">[2] <a href="https://etherpad.openstack.org/p/MuranoActions" target="_blank">https://etherpad.openstack.org/p/MuranoActions</a></div><div class="gmail_default" style="font-size:small">
[3] <a href="https://blueprints.launchpad.net/murano/+spec/external-events" target="_blank">https://blueprints.launchpad.net/murano/+spec/external-events</a></div>
<div class="gmail_default" style="font-size:small">[4] <a href="https://blueprints.launchpad.net/murano/+spec/api-list-events" target="_blank">https://blueprints.launchpad.net/murano/+spec/api-list-events</a></div><div class="gmail_default" style="font-size:small">
[5] <a href="https://blueprints.launchpad.net/murano/+spec/dsl-register-event" target="_blank">https://blueprints.launchpad.net/murano/+spec/dsl-register-event</a></div><div class="gmail_default" style="font-size:small">
[6] <a href="https://blueprints.launchpad.net/murano/+spec/ui-application-event-list" target="_blank">https://blueprints.launchpad.net/murano/+spec/ui-application-event-list</a></div>
<div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div><div dir="ltr"><font>--<br></font><div dir="ltr"><font>Regards,<br>Alexander Tivelkov</font></div>
</div></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><div dir="ltr"><div>Serg Melikyan, Senior Software Engineer at Mirantis, Inc.<br></div><div><a href="http://mirantis.com/" target="_blank">http://mirantis.com</a> | <a href="mailto:smelikyan@mirantis.com" target="_blank">smelikyan@mirantis.com</a><br>
<div><br>+7 (495) 640-4904, 0261</div><div>+7 (903) 156-0836</div></div></div>
</div>