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
Thanks for the feedback, John and Emilien.
On 13.7.2018 01:35, Emilien Macchi wrote:
+1 for Option A as well, I feel like it's the one which would give us the
more of flexibility and also I'm not a big fan of the usage of Anchors for
this use case.
Some folks are currently working on extracting
On Tue, Jul 10, 2018 at 10:22 AM 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
On Tue, Jul 10, 2018 at 10:21 AM 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
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
