https://blueprints.launchpad.net/fuel/+spec/murano-fuel-plugin
Now Murano is aligned with Fuel releases, and if user wants to get new Murano features for its OpenStack environment deployed by Fuel user should wait for new Fuel release, then upgrade whole cluster (all OpenStack components). Main problem here that Fuel releases only every six month.
The main goal of moving Murano to plugin is to provide flexibility for Murano: to support multiple releases and versions (for some Fuel version), also provide ability to detach Murano from controller node as separate node.
Murano Fuel plugin can solve problem with getting new Murano features for OpenStack environment deployed by Fuel. Murano as plugin for Fuel can be continiously delivered and updated. Plugin will include Murano service packages and upstream puppet-murano module for deployment, so support of new features will come very fast.
User doesn’t need to upgrade or reinstall whole Fuel cluster, he should get only new Murano service packages and deployment manifests and run upgrade script. This script will include backing up Murano database, updating puppets for Murano and will be runned by Octane tool.
For Fuel 9.0 Murano as a plugin should support Murano Mitaka with identity API v3 version for Murano services. Also there are two Murano features in upstream: Glance Artifact repository and Cloud Foundry Service Broker API features. These two feature can’t work simultaneously. Hence will be added possibility to choose only one of them.
Transition from Fuel default box to Fuel plugin deployment should follow next way:
Implementation of these transition steps means successfull transfer to Murano plugin deployment.
Murano will be deprecated on the Web UI: we will add deprecation message for Murano and helper text, pointing to the plugin for at least one cycle.
Nailgun tests for Murano will be removed, config in openstack.yaml fixture will be kept. Whole Nailgun stuff will be removed in Fuel 10.0 release.
None
None
None
None
All related Murano manifests in fuel-library will be kept in Fuel 9.0, but will be removed in Fuel 10.0 release.
As alternative, manual configuration of Murano services can be used, by using Debian/UCA/RDO packages and upstream puppet manifests. But it this way requires expertise in Murano configuration and puppet knowledge.
It should be possible to upgrade Fuel 8.0 environment with Murano to Fuel 9.0 environment using Murano plugin manifests and service packages.
None
None
We will show warning on the Fuel Web UI that Murano deployment from box is deprecated and it is recommended to use Fuel Murano plugin.
None
When Fuel Murano deployment will be deprecated, Murano will be available via plugin and from box for Fuel 9.0. All Murano related stuff will be removed in Fuel 10.0 release.
On a deployment process side there are no any actual important changes - all current Murano’s features, which already exist in Fuel, will be kept. Murano deployment from box will not support any new features.
None
This feature requires additional CI tests for plugin repository. These CI jobs should deploy simple Fuel environment with Murano plugin installed on each commit to Murano plugin repository.
Murano can be used as built in Fuel and as plugin. It will be possible to deploy Murano as plugin in the same time with Murano from box. In case when Murano has new code dependencies, which can not be installed on existing node (controller nodes), it must be noted in plugin release notes that Murano can’t be installed on controller nodes anymore because those new dependencies could break other OpenStack componens. Since this moment Murano will require standalone node.
Also should be noted: Murano deployment as built in Fuel is deprecated.
Murano should be deprecated in base Fuel installation.
Murano plugin should include following components for deployment: