Plugin-defined components can't be "bound" to settings checkboxes

[Dmitry Nikishov]

Fuel mitaka

Currently, plugins can utilize components registry interface to expose a component to nailgun. However, it might be possible that a certain plugin could expose a number of components, not just one.

Currently plugin-defined components automatically bind to "settings:plugin-name.metadata.enabled". It would be very helpful if these could also bind to arbitrary plugin-defined settings fields.
E.g. if following could work:

- name: storage:block:external-ceph
  bind:
    - "settings:external-ceph.cinder_ceph.value"
  incompatible:
  - name: storage:block:lvm
  - name: storage:block:ceph
  label: "External Ceph"
  description: "Use external Ceph cluster as a backend for Volumes"

- name: storage:image:external-ceph
  bind:
    - "settings:external-ceph.glance_ceph.value"
  incompatible:
  - name: storage:image:ceph
  - name: storage:image:swift
  label: "External Ceph"
  description: "Use external Ceph cluster as a backend for Images"

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/356493

[OpenStack Infra (hudson-openstack)]

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/356493
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.