Hi, Alexander 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 blueprint <https://blueprints.launchpad.net/murano/+spec/application-actions> and referenced etherpad as specification. 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.
I think Events should be based on Actions, so we can return to Events in the next milestone and revisit them. On Thu, May 29, 2014 at 8:26 PM, Alexander Tivelkov <ativel...@mirantis.com> wrote: > Hi folks! > > 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. > > 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. > > That's why I've decided to drive this process forward and formalize the > spec and requirements for the Actions feature in Murano. > 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 :) > > 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. > > > [1] https://etherpad.openstack.org/p/9XQ7Q2NQdv > [2] https://etherpad.openstack.org/p/MuranoActions > [3] https://blueprints.launchpad.net/murano/+spec/external-events > [4] https://blueprints.launchpad.net/murano/+spec/api-list-events > [5] https://blueprints.launchpad.net/murano/+spec/dsl-register-event > [6] > https://blueprints.launchpad.net/murano/+spec/ui-application-event-list > > > -- > Regards, > Alexander Tivelkov > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Serg Melikyan, Senior Software Engineer at Mirantis, Inc. http://mirantis.com | smelik...@mirantis.com +7 (495) 640-4904, 0261 +7 (903) 156-0836
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev