Re: [openstack-dev] [Fuel][Plugins][UX] Component registry

+1 to Evgeniy There should be no type of restrictions that cannot be overriden by user. On Mon, Nov 2, 2015 at 5:37 PM, Vitaly Kramskikh wrote: > Hi, > > I think having both compatibility and incompatibility lists is a good > idea. I think we need just to show a

Re: [openstack-dev] [Fuel][Plugins][UX] Component registry

Hi, I think having both compatibility and incompatibility lists is a good idea. I think we need just to show a warning if users pick options which are not in compatibility list and disable options which are in incompatibility list. We also need to be able to provide a message in case of

Re: [openstack-dev] [Fuel][Plugins][UX] Component registry

List (not for usage questions) < openstack-dev@lists.openstack.org> *Subject:* Re: [openstack-dev] [Fuel][Plugins][UX] Component registry Hi, I think having both compatibility and incompatibility lists is a good idea. I think we need just to show a warning if users pick options

Re: [openstack-dev] [Fuel][Plugins][UX] Component registry

Hi, The main reason why I think we should get all of the three states is we don't know exactly if those plugins (which developer didn't specify) are compatible or not, so we should not make any assumptions and prevent the user from enabling any plugins she/he wants. The best we can do here is to