CI: Move helm builds to larger instance

Instead of specifying a VOLUME_SIZE and causing the cloud to generate a
volume from the boot image, we should be launching directly against the
boot image. To get the same (or in this case larger) disk we need to
bump up the flavor size to achieve our goals.

Issue-ID: CIMAN-33
Change-Id: Id6c2d6f0ef8ac84480d155e592e82b7aeddad286
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>

diff --git a/jenkins-config/clouds/openstack/cattle/ubuntu1804-helm-2c-1g.cfg b/jenkins-config/clouds/openstack/cattle/ubuntu1804-helm-2c-1g.cfg
index d35f0e9..970d9ab 100644 (file)
--- a/jenkins-config/clouds/openstack/cattle/ubuntu1804-helm-2c-1g.cfg
+++ b/jenkins-config/clouds/openstack/cattle/ubuntu1804-helm-2c-1g.cfg
@@ -1,4 +1,3 @@
-IMAGE_NAME=ZZCI - Ubuntu 18.04 - helm -  - 20220419-175332.347
+IMAGE_NAME=ZZCI - Ubuntu 18.04 - helm -  - 20210318-054700.866
 LABELS=ubuntu1804-helm-2c-1g
-HARDWARE_ID=v3-standard-2
-VOLUME_SIZE=50
+HARDWARE_ID=v3-standard-4