Here is the blueprint:

The problem is much bigger then it seems to. Action parameters are very
similar to regular application properties and thus there should be a
dedicated dynamic UI form (think ui.yaml) for each action describing its
We discussed it many times and each time the resolution was that it is
better to do major refactoring of dynamic UI forms before introducing
additional forms. The intention was to either simplify or completely get
rid of ui.yaml because it is yet another DSL to learn. Most of the
information from ui.yaml could be obtained by examining MuranoPL class
properties. And what is missing could be added as additional metadata right
to the classes. However a lot of work requires to do it properly (starting
from new API that would be MuranoPL-aware). That's why we still have no
proper UI for the actions.

Maybe we should reconsider and to have many ui forms in single package
until we have a better solution.

Sincerely yours,
Stan Lagun
Principal Software Engineer @ Mirantis


On Fri, Dec 4, 2015 at 5:42 AM, WANG, Ming Hao (Tony T) <> wrote:

> Dear Stan and Murano developers,
> The current murano-dashboards can add the action button for the actions
> defined in Murano class definition automatically, which is great.
> Is there any blueprint to add argument collection UI for the action?
> Currently, the murano-dashboards only uses environment_id + action_id to
> run the actions, and user has no way to provide action arguments from
> UI.
> Thanks in advance,
> Tony
OpenStack Development Mailing List (not for usage questions)

Reply via email to