In Fuel 5.1 we had an experimental feature - 'patching openstack env'.
The idea was to update and to rollback OpenStack environments between
minor releases. However, we have encounter a lot of problems with
restoring OpenStack databases andresolving dependency hell in packages,
so we buried it and never release it.
This patch removes legacy code from the source tree. We can do it
without fear, since it wasn't released in public.
Related-Bug: #1511499
Change-Id: I58b3fedd239eb7fe4226e51c2d6386efab14395d
Now JSON fields will be serialized to MutableDict and MutableList
objects on all levels. Before Mutable(Dict/List) was only on top
level (root element), on other levels was builtin list/dict objects.
As result change events have been catched in root element only.
Now any change of JSON tree will mark corresponding field as dirty.
Change-Id: I350e45067187ad23b38acd03592407b0707a3f9b
Partial-Bug: 1482658
Modifying cluster creation API (POST /api/clusters) for handling
components data and setup proper values of cluster attributes by
components from wizard. Change storage components metadata.
Implements: blueprint component-registry
Change-Id: Ic2b6774881aab47b5a0914518c5f5db9ab28f3b6
Modifying POST /clusters for handling components data
Enabling proper plugins by components from wizard
Change-Id: If6c0e9c2cb41652def663ba3c8c95484bd3430e9
Implements: blueprint component-registry
We need to use both core node roles and plugins ones. In order to
achieve this we need to mix them into one dictionary in objects.Cluster.
Implements: blueprint role-as-a-plugin
Change-Id: I5d46cabace12795ec621e713ae4d3f35e7c88faa
Signed-off-by: Igor Kalnitsky <igor@kalnitsky.org>
In Fuel 7.0 we want to have ability to extend node roles on fly by using
plugins. In order to achieve this, we want to have declarative
schemaless approach, so we won't require database object manipulations
(CRUD) each time we somehow change node role.
This commit drops such tables like:
* roles
* pending_roles
* node_roles
and use postgresql arrays in nodes tables instead:
* roles
* pending_roles
* primary_roles
Implements blueprint role-as-a-plugin
Change-Id: I2d3fccb7187fa4e82595c9ca6b27ef8ce90ee4b2
Signed-off-by: Igor Kalnitsky <igor@kalnitsky.org>
We need it to be possible to set priorities (pinning)
for deb and rpm repositories. This patch moves repo_metadata
to cluster attributes and changes its format.
Plugins' repos should have higher priority than default ones,
so we're setting them according to settings.yaml.
Implements: blueprint consume-external-ubuntu
Change-Id: I5a98469b9547014abec9406a7b36f1cf22ba8086
- Task serialization logic for pre/post hooks
- PluginSerializer object added
- API for interaction with Plugins db schema
General API requests supported
GET/POST /plugins
GET/PUT/DELETE /plugins/<plugin_id>
- Plugins and ClustersPlugins db models added
ClusterPlugins used to identify enabled plugins for a
given cluster
- Configuration uploading logic stored in Plugin wrapper
Co-authored-by: Dima Shulyak <dshulyak@mirantis.com>
Co-authored-by: Evgeniy L <eli@mirantis.com>
implements: blueprint cinder-neutron-plugins-in-fuel
Change-Id: I986f5be9ed3c3adaf7583d1bfc546cbe705db9ec
In Fuel 6.0 we're going to introduce diff-based releases, so the
fuel-upgrade script has to handle and install it properly.
Change-Id: If05ac74b680691bf9adb54caf8958e235ec767ef
Blueprint: reduce-tarball-size
In order to force customers moving to new releases or for technical
reasons we want to forbid deploying some releases. For this reason we
need to introduce a special field in the Relases model.
Please note, the field has no affect in experimental mode.
Change-Id: Iaf315d291ce9f18ad52b15c030be193d0d5ea6f9
Closes-Bug: #1368100
- removed wizard.json
- all wizard config moved to base_release config
- migration for 5.1 changed: already existing releases'
"wizard_metadata" attribute is updated with
proper data (i.e. without nsx info).
Change-Id: Ie6928b0e4b82882383fc74043a76f22400698b91
Closes-bug: 1348627
Andreas Jaeger