Release as a plugin
As a Mirantis Engineer I want to express a Fuel Release as a Fuel Plugin so
that I could define, maintain and deploy various flavors of customized
OpenStack deployments in a clean isolated way, externalized from common
Fuel provisioning layer.
The nailgun repo sill holds onto one of the remaining parts of the data model
the release fixture. This fixture is used to describe everything about the
deployment from the ground up and is where every change can possibly be
expressed.
By moving the release fixtures ``openstack.yaml`` completely into the plugin
framework we opening road to following changes:
* To make ``fuel-library`` repo a plugin.
* It is possible to ship multiple openstack version release packages as
each is its own plugin.
* Next steps allowing Fuel to have different releases bundled or no pre-bundled
releases at all (lightweight version) are possible as well.
Blueprint information
- Status:
- Not started
- Approver:
- Andrey Maximov
- Priority:
- Undefined
- Drafter:
- Ilya Kutukov
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Release as a plugin example
Gerrit topic: https:/
Addressed by: https:/
Rename existing BaseValidator to LegacyBaseValidator
Addressed by: https:/
Release as a plugin spec.
Gerrit topic: https:/
Addressed by: https:/
Plugins v 5.0.0 support in plugins adapters
Addressed by: https:/
Plugins v 5.0.0 support in plugins adapters
Gerrit topic: https:/
Addressed by: https:/
Fuel plugin builder v5
Addressed by: https:/
Fuel plugin builder v5