parallel nodes deploy

[Michał Górniak]

When we creating new mos deploy we have dependency which told in what order we need to deploy nodes, for example:

1. Primary controller
2. Other controlers
3. Storage nodes
4. Compute nodes

I will focuses on first 2.

Deploy Primary controller take ~10min (example!!!)
Deploy Second controller take ~10min (example!!!)

Total deploy of this 2 nodes take 20min, but in each node we have several task to make, and if we finish one task usually we can do the same task to 2-nd node not wating for hole deploy.

Example of tasks order (very example)
node-1 (primary controller)
node-2 (second controller)

1. Start fuel_pkgs.pp on node-1
2. Finish fuel_pkgs.pp on node 1
3. Start globals.pp on node-1 and start fuel_pkgs.pp on node-2
3.Finish fuel_pkgs.pp on node-2
4. Finish globals.pp on node-1
5.Start logging.pp on node-1 and start globals.pp on node-2
etc.

In examples times this can reduce time need to deploy from ~20min (EXAMPLE!!) to ~12min (EXAMPLE!!)

[Sergii Golovatiuk (sgolovatiuk)]

This issue is related to orchestrator and how we call granular tasks. However, I'd say that some parallelism is implemented as we deploy primary-controller and then all other controllers in parallel.

[Dmitriy Novakovskiy (dnovakovskiy)]

This is covered by existing 8.0 Epic for "Task-based deployment framework in Fuel".

[Alexey Shtokolov (ashtokolov)]

Fixed by Task-based deployment (experimental feature in 8.0 and will be by default in 9.0)