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

Status:
Complete
Approver:
Sheena Conant
Priority:
Undefined
Drafter:
Andriy Popovych
Direction:
Approved
Assignee:
Andriy Popovych
Definition:
Approved
Series goal:
Accepted for 8.0.x
Implementation:
Implemented
Milestone target:
milestone icon 8.0
Started by
Sergii Golovatiuk
Completed by
Sergii Golovatiuk

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/plugin-registry,n,z

Addressed by: https://review.openstack.org/229306
    Plugin registry

Gerrit topic: https://review.openstack.org/#q,topic:bp/component-registry,n,z

Addressed by: https://review.openstack.org/233559
    Component-registry

Addressed by: https://review.openstack.org/234353
    Plugin V4

Addressed by: https://review.openstack.org/234804
    Cluster creation wizard with components support

Addressed by: https://review.openstack.org/234964
    Sync component metadata into DB

Addressed by: https://review.openstack.org/237857
    Loading fixture for core components

Addressed by: https://review.openstack.org/238023
    Component handler

Addressed by: https://review.openstack.org/239317
    Validation for compatibility matrix metadata in FPB

Addressed by: https://review.openstack.org/240079
    Example plugin v4

Addressed by: https://review.openstack.org/241289
    Refactor component model

Addressed by: https://review.openstack.org/220188
    Store attributes of plugins in a separate table

Addressed by: https://review.openstack.org/244123
    Enable plugins by choosen components

Addressed by: https://review.openstack.org/246889
    Cluster creation wizard ported to components

Addressed by: https://review.openstack.org/247913
    Setup cluster setting by chosen components

Gerrit topic: https://review.openstack.org/#q,topic:8/component-registry,n,z

Addressed by: https://review.openstack.org/261925
    NSXv component registry

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.