OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|cluster_upgrade||2 years ago|
|specs||2 years ago|
|tools||2 years ago|
|.coveragerc||2 years ago|
|.gitignore||2 years ago|
|.gitreview||1 month ago|
|AUTHORS||2 years ago|
|LICENSE||2 years ago|
|MANIFEST.in||2 years ago|
|README.rst||2 years ago|
|bindep.txt||2 years ago|
|conftest.py||2 years ago|
|nailgun-test-settings.yaml||2 years ago|
|requirements.txt||2 years ago|
|setup.cfg||2 years ago|
|setup.py||2 years ago|
|test-requirements.txt||2 years ago|
|tox.ini||2 years ago|
This extension for Nailgun provides API handlers and logic for cluster upgrading. This extension used by the fuel-octane project.
nailgun_syncdb- migrate database
Every transformation manager has default config that hardcoded, but you can overwrite this config with your own transformations extensions. This could be done by extending
CLUSTER_UPGRADE: transformations: cluster: 7.0: [transform_vips] 9.0: [first_transformation, second_transformation] ...
In extension you should define a entrypoint is such way:
nailgun.cluster_upgrade.transformations.cluster.7.0 = transform_vips = my_project.transformations:transform_cluster_vips
on first line we have entripoint name where
nailgun.cluster_upgrade.transformations- namespace where all transformations defined.
cluster- name of object which data transformed
7.0- cluster version where these transformations should happen
on the second line
transform_vips- unique transformation name that you can use in configuration file or in transformation manager
my_project.transformations- module name
transform_cluster_vips- transformer function name
Transformation function must take only one argument - data to transform. When you call
manager.apply(from_version, to_version, data) all transformer functions ordered by a version called one by one, and output of one transformer used as input to the other.
In out example calling
cluster_manager.apply('6.0', '9.1', data) will call three functions