Hi, 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 fuel-plugin-name-1.0.0.fp`) 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 environment, 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 conditions 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? Thanks, [1] https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg40878.html
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev