Component registry

Registered by Andriy Popovych

Today, in Fuel, a user can select two hypervisors (KVM/QEMU + vCenter), one networking back-end, and one Storage back-end (Ceph used for Glance, Nova, Cinder, and Swift).

In the future, the ideal case would be that a user can select multiple hypervisors, networking back-ends, and Storage back-ends specified by ephemeral, Cinder, Glance, object (and in the future, Manila).

For example, inside of the wizard, we would like a user to select KVM + vCenter hypervisors with VLAN + DVS networking back-ends (to support the dual hypervisors) and Ceph + NetApp Cinder back-ends, and NetApp for their ephemeral and Glance storage.

Problem 1: many of these back-ends are delivered in Fuel plugins, for which there is not an authoritative list when displaying the Fuel wizard.

Problem 2: when implementing multiple back-ends for a single set of functionality, there is a comma separated list that must be created in the config file, which plugins cannot create because they do not know about one another. (Greg – this I believe is where we talked about “extending” the config file – per Andrew, this is not possible because the field is not capable of being multi-line)

Problem 3: it is possible that the back-ends will need to execute in a specific order in order to be configured correctly

Blueprint information

Sheena Conant
Andriy Popovych
Andriy Popovych
Series goal:
Accepted for 8.0.x
Milestone target:
milestone icon 8.0
Started by
Sergii Golovatiuk
Completed by
Sergii Golovatiuk

Related branches



Gerrit topic:,topic:bp/plugin-registry,n,z

Addressed by:
    Plugin registry

Gerrit topic:,topic:bp/component-registry,n,z

Addressed by:

Addressed by:
    Plugin V4

Addressed by:
    Cluster creation wizard with components support

Addressed by:
    Sync component metadata into DB

Addressed by:
    Loading fixture for core components

Addressed by:
    Component handler

Addressed by:
    Validation for compatibility matrix metadata in FPB

Addressed by:
    Example plugin v4

Addressed by:
    Refactor component model

Addressed by:
    Store attributes of plugins in a separate table

Addressed by:
    Enable plugins by choosen components

Addressed by:
    Cluster creation wizard ported to components

Addressed by:
    Setup cluster setting by chosen components

Gerrit topic:,topic:8/component-registry,n,z

Addressed by:
    NSXv component registry


Work Items

This blueprint contains Public information 
Everyone can see this information.