[openstack-dev] [Fuel][Plugins] UI workflow, plugins enabling/disabling

Evgeniy L eli at mirantis.com
Wed Dec 24 13:15:07 UTC 2014


Recently we've discussed what plugins should look like from user point of
view [1].
On one of the meeting it was decided to have the next flow:

1. user installs fuel plugin (as usually with `fuel plugins install
2. after that plugin can be seen on Plugins page, the button for this page
will be placed
    somewhere between Environments and Releases buttons
3. each plugin on the page has checkbox, the checkbox represents the
default state of
    plugin for new environments, if checkbox is checked, when user creates
    he can see all of the buttons which are related to plugin, e.g. in case
of Contrail
    he can see new option in the list of network providers on Network tab
in the wizard
4. during the environment configuration user should select options which
are related to the plugin,
    the information about the list of options and where they should be
placed is described by
    plugin developer
5. when user starts deployment, Nailgun parses tasks and depending on
    sends them to Astute, the conditions are described for each task by
plugin developer,
    example of condition "cluster:net_provider != 'contrail' ", if task
doesn't have conditions,
    we always execute it

Any comments on that?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141224/037119d4/attachment.html>

More information about the OpenStack-dev mailing list