Pluggable Architecture

Registered by David J. Easter on 2014-01-08

Partners are asking for ways to add their own value to Fuel so that customers will automatically have an option to utilize a partner’s offering. A more modular approach to Fuel must be implemented to enable partners and community members to add plug-ins to Fuel that will enable configuration and deployment of additional components within an OpenStack environment. This modularity should enable plug-ins to be either included in a distribution, be part of OpenStack core, or loaded onto the Fuel Master Node post-installation of Fuel.

Blueprint information

Status:
Complete
Approver:
Mike Scherbakov
Priority:
Essential
Drafter:
Alexander Kislitsky
Direction:
Approved
Assignee:
Alexander Kislitsky
Definition:
Obsolete
Series goal:
Accepted for future
Implementation:
Started
Milestone target:
None
Started by
Nikolay Markov on 2014-06-06
Completed by
Alexander Kislitsky on 2015-04-16

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/fuel-pluggable-architecture,n,z

Addressed by: https://review.openstack.org/125353
    Add Task and Role files

Addressed by: https://review.openstack.org/125940
    Add packing and installation of tasks and roles

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.