Hi,
I see that tasks.yaml is going to be deprecated in the future MOS versions
[1]. I've got one question regarding the ordering of tasks between
different plugins.
With tasks.yaml, it was possible to coordinate the execution of tasks
between plugins without prior knowledge of which plugins were installed [2].
For example, lets say we have 2 plugins: A and B. The plugins may or may
not be installed in the same environment and the tasks execution should be:
1. Run task X for plugin A (if installed).
2. Run task Y for plugin B (if installed).
3. Run task Z for plugin A (if installed).
Right now, we can set task priorities like:
# tasks.yaml for plugin A
- role: ['*']
stage: post_deployment/1000
type: puppet
parameters:
puppet_manifest: puppet/manifests/task_X.pp
puppet_modules: puppet/modules
- role: ['*']
stage: post_deployment/3000
type: puppet
parameters:
puppet_manifest: puppet/manifests/task_Z.pp
puppet_modules: puppet/modules
# tasks.yaml for plugin B
- role: ['*']
stage: post_deployment/2000
type: puppet
parameters:
puppet_manifest: puppet/manifests/task_Y.pp
puppet_modules: puppet/modules
How would it be handled without tasks.yaml?
Regards,
Simon
[1] https://review.openstack.org/#/c/271417/
[2] https://wiki.openstack.org/wiki/Fuel/Plugins#Plugins_deployment_order
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
