Add kubevirt-ipi workflow

ci-operator/step-registry/ipi/conf/kubevirt/OWNERS

@@ -0,0 +1,6 @@
+approvers:
+  - bardielle
+  - ravidbro
+  - nirarg
+  - rgolangh
+  - chenyosef

ci-operator/step-registry/ipi/conf/kubevirt/ipi-conf-kubevirt-chain.metadata.json

@@ -0,0 +1,12 @@
+{
+	"path": "ipi/conf/kubevirt/ipi-conf-kubevirt-chain.yaml",
+	"owners": {
+		"approvers": [
+			"bardielle",
+			"ravidbro",
+			"nirarg",
+			"rgolangh",
+			"chenyosef"
+		]
+	}
+}

ci-operator/step-registry/ipi/conf/kubevirt/ipi-conf-kubevirt-chain.yaml

@@ -0,0 +1,9 @@
+chain:
+  as: ipi-conf-kubevirt
+  steps:
+  - ref: ipi-conf
+  - ref: ipi-conf-kubevirt
+  documentation: >-
+    This chain generates an install-config.yaml file configured to run clusters in the Kubevirt CI project.
+    The Kubevirt specific configs are added to the file generated by the ipi-conf steps.
+    This resulting file is stored in the shared directory for future consumption.

ci-operator/step-registry/ipi/conf/kubevirt/ipi-conf-kubevirt-commands.sh

@@ -0,0 +1,32 @@
+#!/bin/bash
+
+set -o nounset
+set -o errexit
+set -o pipefail
+
+CONFIG="${SHARED_DIR}/install-config.yaml"
+
+
+KUBEVIRT_BASE_DOMAIN="tenant1.origin-on-kubevirt.dev.openshift.com"
+KUBEVIRT_API_VIP=192.168.123.15
+KUBEVIRT_INGRESS_VIP=192.168.123.20
+KUBEVIRT_KUBECONFIG=${HOME}/.kube/config
+KUBEVIRT_NAMESPACE=tenantcluster
+KUBEVIRT_NETWORK_NAME=tenantcluster
+KUBEVIRT_TENANT_STORAGE_CLASS_NAME=standard
+KUBEVIRT_VOLUME_ACCESS_MODE=ReadWriteMany
+
+cat >> "${CONFIG}" << EOF
+baseDomain: ${KUBEVIRT_BASE_DOMAIN}
+platform:
+  kubevirt:
+    # TODO this section is WIP - see the installer PR
+    IngressVIP: ${KUBEVIRT_INGRESS_VIP}
+    apiVIP: ${KUBEVIRT_API_VIP}
+    kubeconfig: ${KUBEVIRT_KUBECONFIG}
+    namespace: ${KUBEVIRT_NAMESPACE}
+    networkName: ${KUBEVIRT_NETWORK_NAME}
+    storageClass: ${KUBEVIRT_TENANT_STORAGE_CLASS_NAME}
+    persistentVolumeAccessMode: ${KUBEVIRT_VOLUME_ACCESS_MODE}
+EOF
+

ci-operator/step-registry/ipi/conf/kubevirt/ipi-conf-kubevirt-ref.metadata.json

@@ -0,0 +1,12 @@
+{
+	"path": "ipi/conf/kubevirt/ipi-conf-kubevirt-ref.yaml",
+	"owners": {
+		"approvers": [
+			"bardielle",
+			"ravidbro",
+			"nirarg",
+			"rgolangh",
+			"chenyosef"
+		]
+	}
+}

ci-operator/step-registry/ipi/conf/kubevirt/ipi-conf-kubevirt-ref.yaml

@@ -0,0 +1,13 @@
+ref:
+  as: ipi-conf-kubevirt
+  from: base
+  commands: ipi-conf-kubevirt-commands.sh
+  resources:
+    requests:
+      cpu: 10m
+      memory: 100Mi
+  documentation: >-
+    This step configures an install-config.yaml file to depoloy to the KUBEVIRT project.
+    An existing install-config.yaml file should already exist in the shared directory.
+    The file is modified to configure the cluster to run in the KUBEVIRT project.
+    The resulting file remains in the shared directory for future consumption.

ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh

@@ -21,6 +21,7 @@ case "${CLUSTER_TYPE}" in
 aws) export AWS_SHARED_CREDENTIALS_FILE=${CLUSTER_PROFILE_DIR}/.awscred;;
 azure4) export AZURE_AUTH_LOCATION=${CLUSTER_PROFILE_DIR}/osServicePrincipal.json;;
 gcp) export GOOGLE_CLOUD_KEYFILE_JSON=${CLUSTER_PROFILE_DIR}/gce.json;;
+kubevirt) export KUBEVIRT_KUBECONFIG=${HOME}/.kube/config;;
 vsphere) ;;
 openstack) export OS_CLIENT_CONFIG_FILE=${CLUSTER_PROFILE_DIR}/clouds.yaml ;;
 openstack-vexxhost) export OS_CLIENT_CONFIG_FILE=${CLUSTER_PROFILE_DIR}/clouds.yaml ;;

ci-operator/step-registry/ipi/kubevirt/OWNERS

@@ -0,0 +1,6 @@
+approvers:
+  - bardielle
+  - ravidbro
+  - nirarg
+  - rgolangh
+  - chenyosef

ci-operator/step-registry/ipi/kubevirt/ipi-kubevirt-workflow.metadata.json

@@ -0,0 +1,12 @@
+{
+	"path": "ipi/kubevirt/ipi-kubevirt-workflow.yaml",
+	"owners": {
+		"approvers": [
+			"bardielle",
+			"ravidbro",
+			"nirarg",
+			"rgolangh",
+			"chenyosef"
+		]
+	}
+}

ci-operator/step-registry/ipi/kubevirt/ipi-kubevirt-workflow.yaml

@@ -0,0 +1,15 @@
+workflow:
+  as: ipi-kubevirt
+  steps:
+    pre:
+    - chain: ipi-kubevirt-pre
+    post:
+    - chain: ipi-kubevirt-post
+  documentation: |-
+    The IPI workflow provides pre- and post- steps that provision and
+    deprovision an OpenShift cluster with a default configuration on Kubevirt,
+    allowing job authors to inject their own end-to-end test logic.
+
+    All modifications to this workflow should be done by modifying the
+    `ipi-kubevirt-{pre,post}` chains to allow other workflows to mimic and extend
+    this base workflow without a need to backport changes.

ci-operator/step-registry/ipi/kubevirt/post/OWNERS

@@ -0,0 +1,6 @@
+approvers:
+  - bardielle
+  - ravidbro
+  - nirarg
+  - rgolangh
+  - chenyosef

ci-operator/step-registry/ipi/kubevirt/post/ipi-kubevirt-post-chain.metadata.json

@@ -0,0 +1,12 @@
+{
+	"path": "ipi/kubevirt/post/ipi-kubevirt-post-chain.yaml",
+	"owners": {
+		"approvers": [
+			"bardielle",
+			"ravidbro",
+			"nirarg",
+			"rgolangh",
+			"chenyosef"
+		]
+	}
+}

ci-operator/step-registry/ipi/kubevirt/post/ipi-kubevirt-post-chain.yaml

@@ -0,0 +1,8 @@
+chain:
+  as: ipi-kubevirt-post
+  steps:
+  - chain: ipi-conf-kubevirt
+  - chain: ipi-deprovision
+  documentation: |-
+    The IPI cleanup step contains all steps that deprovision an OpenShift
+    cluster on KubeVirt, provisioned by the `ipi-kubevirt-pre` chain.

ci-operator/step-registry/ipi/kubevirt/pre/OWNERS

@@ -0,0 +1 @@
+../OWNERS

ci-operator/step-registry/ipi/kubevirt/pre/ipi-kubevirt-pre-chain.metadata.json

@@ -0,0 +1,12 @@
+{
+	"path": "ipi/kubevirt/pre/ipi-kubevirt-pre-chain.yaml",
+	"owners": {
+		"approvers": [
+			"bardielle",
+			"ravidbro",
+			"nirarg",
+			"rgolangh",
+			"chenyosef"
+		]
+	}
+}

ci-operator/step-registry/ipi/kubevirt/pre/ipi-kubevirt-pre-chain.yaml

@@ -0,0 +1,8 @@
+chain:
+  as: ipi-kubevirt-pre
+  steps:
+  - chain: ipi-conf-kubevirt
+  - chain: ipi-install
+  documentation: |-
+    The IPI setup step contains all steps that provision an OpenShift cluster
+    with a default configuration on Kubevirt.

ci-operator/step-registry/ipi/kubevirt/pre/stableinitial/OWNERS

@@ -0,0 +1 @@
+../OWNERS

ci-operator/step-registry/ipi/kubevirt/pre/stableinitial/ipi-kubevirt-pre-stableinitial-chain.metadata.json

@@ -0,0 +1,12 @@
+{
+	"path": "ipi/kubevirt/pre/stableinitial/ipi-kubevirt-pre-stableinitial-chain.yaml",
+	"owners": {
+		"approvers": [
+			"bardielle",
+			"ravidbro",
+			"nirarg",
+			"rgolangh",
+			"chenyosef"
+		]
+	}
+}

ci-operator/step-registry/ipi/kubevirt/pre/stableinitial/ipi-kubevirt-pre-stableinitial-chain.yaml

@@ -0,0 +1,8 @@
+chain:
+  as: ipi-kubevirt-pre-stableinitial
+  steps:
+  - chain: ipi-conf-kubevirt
+  - chain: ipi-install-stableinitial
+  documentation: |-
+    The IPI setup step contains all steps that provision an OpenShift cluster
+    from stable-initial imagestream with a default configuration on KubeVirt.