openstack/project-config
Code Issues Proposed changes

Set launch-timeout on nodepool providers

Browse Source 
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
This commit is contained in:
Clark Boylan 2024-09-24 15:25:56 -07:00
parent 3d72773921
commit 29f15bb14c
2 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
nodepool/nl01.opendev.org.yaml
View File

@ -198,6 +198,7 @@ providers:
# It should be changed carefully.
cloud: raxflex
boot-timeout: 120
launch-timeout: 600
diskimages: *provider_diskimages
pools:
- name: main

2
nodepool/nl03.opendev.org.yaml
View File

@ -107,6 +107,7 @@ providers:
# It should be changed carefully.
cloud: vexxhost
boot-timeout: 120
launch-timeout: 600
rate: 0.001
diskimages: &provider_diskimages
- name: centos-9-stream
@ -214,6 +215,7 @@ providers:
# It should be changed carefully.
cloud: vexxhost
boot-timeout: 120
launch-timeout: 600
rate: 0.001
diskimages: *provider_diskimages
pools: