Open Stack

On 07/10/2018 04:20 PM, Jiří Stránský wrote:
> Hi,
> 
> with the move to config-download deployments, we'll be moving from
> executing external installers (like ceph-ansible) via Heat resources
> encapsulating Mistral workflows towards executing them via Ansible
> directly (nested Ansible process via external_deploy_tasks).
> 
> Updates and upgrades still need to be addressed here. I think we should
> introduce external_update_tasks and external_upgrade_tasks for this
> purpose, but i see two options how to construct the workflow with them.
> 
> During update (mentioning just updates, but upgrades would be done
> analogously) we could either:
> 
> A) Run external_update_tasks, then external_deploy_tasks.
> 
> This works with the assumption that updates are done very similarly to
> deployment. The external_update_tasks could do some prep work and/or
> export Ansible variables which then could affect what
> external_deploy_tasks do (e.g. in case of ceph-ansible we'd probably
> override the playbook path). This way we could also disable specific
> parts of external_deploy_tasks on update, in case reuse is undesirable
> in some places.
thanks

+1 on A from me as well

we currently cycle through a list of playbooks to execute which can be
given as a Heat parameter ... I suppose we'll need to find a way to make
an ansible variable override the Heat value
-- 
Giulio Fidente
GPG KEY: 08D733BA