Remove linaro cloud from Nodepool

This should be done after we are happy with the cleanups that nodepool
has performed particularly against the zk database. Otherwise we may
need to do manual cleanup after this provider config is removed.

We also remove the auto generation of the linaro cloud grafana dashboard
rules but don't remove the dashboard itself. We typically keep the
dashboards around for a while as the information exposed there may
continue to be useful after the cloud is gone.

Change-Id: I40acd28146484cb81f87ee825787d578eb964de8
This commit is contained in:
Clark Boylan 2024-07-26 14:58:53 -07:00
parent 3801f3530c
commit cbd7938596
3 changed files with 0 additions and 26 deletions

View File

@ -20,7 +20,6 @@ function create {
}
create Rackspace 'rax-*' nodepool-rax.yaml
create Linaro 'linaro-*' nodepool-linaro.yaml
create OVH 'ovh-*' nodepool-ovh.yaml
create Vexxhost 'vexxhost-*' nodepool-vexxhost.yaml
create OSUOSL 'osuosl-*' nodepool-osuosl.yaml

View File

@ -12,14 +12,6 @@ zookeeper-servers:
port: 2281
providers:
- name: linaro-regionone
region-name: 'RegionOne'
cloud: linaro
rate: 0.25
# 6 hours
image-upload-timeout: 21600
diskimages: []
- name: osuosl-regionone
region-name: 'RegionOne'
cloud: osuosl

View File

@ -366,23 +366,6 @@ providers:
diskimage: rockylinux-9
key-name: infra-root-keys-2024-04-08
- name: linaro-regionone
region-name: 'RegionOne'
# Changing this cloud value impacts things like mirror names in jobs.
# It should be changed carefully.
cloud: linaro
boot-timeout: 600
launch-timeout: 800
rate: 0.001
diskimages: []
pools:
- name: main
# Network assignment is 147.28.149.96/27, one host is the
# mirror node.
# Set to zero in preparation for cloud shutdown
max-servers: 0
labels: []
- name: osuosl-regionone
region-name: 'RegionOne'
# Changing this cloud value impacts things like mirror names in jobs.