+2 to Stan: there is a strong need for v2 API which would satisfy the needs
of Murano 0.5+. The current one is definitely outdated.
I'd like to point that there are at least two major flaws in the v1 design:
1. Sessions. Actually, they violate one of the core principles of RESTful
design - the cl
I think API need to be redesigned at some point. There is a blueprint for
this: https://blueprints.launchpad.net/murano/+spec/api-vnext
It seems reasonable to implement new API on new framework at once
Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis
On Mon, Jun 2, 2014 at 1
Let's follow the standard procedure. Both blueprints lack specification of
implementation details. There also has to be someone willing to implement these
blueprints in near feature.
I'm not opposed to these ideas and I'd really like to see Pecan added during
Juno, but we still need to follow the
Hi all,
We need to rewrite Murano API on new API framework and we have the commit:
https://review.openstack.org/#/c/60787
(*Sergey*, sorry, but -1 from me, need to fix small isses)
Also, today I created blueprint:
https://blueprints.launchpad.net/murano/+spec/murano-api-workers
this feature allow
