project-config/nodepool
Clark Boylan 29f15bb14c Set launch-timeout on nodepool providers
The nodepool openstack provider implementation has a launch timeout
default of 3600 seconds or one hour. This is problematic for us because
a node request will be attempted three times by a provider before being
passed onto the next provider. This means we may wait up to three hours
per failed provider to launch a single node.

Fix this by setting a timeout of 10 minutes on the three providers that
didn't already set a lower timeout (raxflex and the two vexxhost
providers). Looking at grafana graphs for time to ready this should be
plenty of time for normal booting conditions and reduces the time we
wait from 3 hours per provider to 30 minutes.

Change-Id: I0a4af9f5519ff2b64c737b1822590fbb2608e8bb
2024-09-24 15:25:56 -07:00
..
elements Convert python2 dib element scripts to python3 2024-09-12 10:33:57 -07:00
scripts Restore blank nodepool/scripts 2020-03-03 15:01:23 +11:00
nb01-test.opendev.org.yaml nodepool: Add nb01-test.opendev.org config file 2020-03-03 11:06:05 +11:00
nb04.opendev.org.yaml Convert python2 dib element scripts to python3 2024-09-12 10:33:57 -07:00
nl01.opendev.org.yaml Set launch-timeout on nodepool providers 2024-09-24 15:25:56 -07:00
nl02.opendev.org.yaml Add nested virt labels to raxflex and openmetal providers 2024-09-12 10:58:35 -07:00
nl03.opendev.org.yaml Set launch-timeout on nodepool providers 2024-09-24 15:25:56 -07:00
nl04.opendev.org.yaml Stop building centos 8 stream images 2024-07-30 14:01:53 -07:00
nodepool.yaml Add Nodepool images to Rackspace Flex 2024-09-04 18:36:27 +00:00