platforms, tmt: Rename and restructure cloud variants

We now have more than one cloud system that is essentially a KVM environment that uses cloud-init to boot, so now we declare that "generic" and have the OpenStack and Oracle images reuse those definitions. Also, in preparation for layered cloud image variants, rename them from "Cloud-" to "Cloud-Base-". Vagrant variants are similarly prefixed to make it clear who provides them. Finally, restructure the layout of the tmt plans to match the description structure.
2023-12-21 09:04:37 -05:00
parent f9b944d050
commit e6896b13c2
10 changed files with 43 additions and 40 deletions
@@ -0,0 +1,8 @@
+summary: Build AWS EC2 base image
+discover:
+    how: fmf
+environment:
+    image_type: oem
+    image_profile: Cloud-Base-AmazonEC2
+execute:
+    how: tmt
@@ -0,0 +1,8 @@
+summary: Build Azure base image
+discover:
+    how: fmf
+environment:
+    image_type: oem
+    image_profile: Cloud-Base-Azure
+execute:
+    how: tmt
@@ -0,0 +1,8 @@
+summary: Build GCP base image
+discover:
+    how: fmf
+environment:
+    image_type: oem
+    image_profile: Cloud-Base-GCE
+execute:
+    how: tmt
@@ -0,0 +1,8 @@
+summary: Build Generic base image
+discover:
+    how: fmf
+environment:
+    image_type: oem
+    image_profile: Cloud-Base-Generic
+execute:
+    how: tmt