Hi Matthew,
Thanks for the reply.
On Tue, May 17, 2016 at 5:33 PM, Matthew Mosesohn
wrote:
> Hi Simon,
>
> For 8.0 and earlier, I would deploy ElasticSearch before deploy_end
> and LMA collector after post_deploy_start
>
>
Unfortunately this isn't possible because the final bits of the
Elastics
Hi Simon,
For 8.0 and earlier, I would deploy ElasticSearch before deploy_end
and LMA collector after post_deploy_start
For Mitaka and Newton releases, the task graph now skips dependencies
that are not found for the role being processed. Now this "requires"
dependency will work that previously e
I'm resurrecting this thread because I didn't manage to find a satisfying
solution to deal with this issue.
First let me provide more context on the use case. The Elasticsearch/Kibana
and LMA collector plugins need to synchronize their deployment. Without too
many details, here is the workflow whe
On Fri, Jan 29, 2016 at 4:27 PM, Igor Kalnitsky
wrote:
> Hey folks,
>
> Simon P. wrote:
> > 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).
>
> Simon, could you please explain do you need this at the first pl
Hey folks,
Simon P. wrote:
> 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).
Simon, could you please explain do you need this at the first place? I
can imagine this case only if your two plugins are kinda depende
On 27.01.2016 14:44, Simon Pasquier wrote:
> 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
> betwee
On Jan 27, 2016 4:58 PM, "Andrew Woodward" wrote:
>
> Simon, you should use the deployment_tasks.yaml interface (which will
likely eventually move to '*/tasks.yaml' (to mimic library) This uses the
same task system as granular deploy. you can set task ordering between
known tasks and roles names,
Simon, you should use the deployment_tasks.yaml interface (which will
likely eventually move to '*/tasks.yaml' (to mimic library) This uses the
same task system as granular deploy. you can set task ordering between
known tasks and roles names, in the case that they are not registered they
will simp
