| 2016-02-02 21:16:18 |
Dimitry Ushakov |
description |
Bay create in devstack gate takes about 25 minutes. More data can be found in this gist: https://gist.github.com/dimtruck/1d59b7b8d2869190ccba#file-output-sh (and surrounding log files)
High level break down: heat workflow takes about 25 minutes. Most of the time is spent in swarm_masters and swarm_nodes.
In swarm_masters and swarm_nodes:
~5 minutes in resource creation (nova, neutron, cinder)
~5 minutes in cloud-init (both cloud-init modules and heat fragments we run as part of cloud-init)
~3 minutes unaccounted for
The challenge is that due to this slowness, our test suite is limited since we hit the time constraint of 2 hours after only 2 bay-creates (accounting for devstack spin-up time) |
Bay create in devstack gate takes about 25 minutes. More data can be found in this gist: https://gist.github.com/dimtruck/1d59b7b8d2869190ccba#file-output-sh (and surrounding log files)
High level break down: heat workflow takes about 25 minutes. Most of the time is spent in swarm_masters and swarm_nodes.
In swarm_masters and swarm_nodes:
~5 minutes in resource creation (nova, neutron, cinder)
~5 minutes in cloud-init (both cloud-init modules and heat fragments we run as part of cloud-init)
~3 minutes unaccounted for
The challenge is that due to this slowness, our test suite is limited since we hit the time constraint of 2 hours after only 2 bay-creates (accounting for devstack spin-up time)
One of the ways to expedite this is to remove the dependency for swarm_masters for swarm_nodes to make these resources execute in parallel. |
|
