Add release-openshift-origin-installer-launch-ovirt task

[vrutkovs]

This adds a task, which would be used by cluster-bot to start an ovirt cluster

[Gal-Zaidman]

The env needs to be:
OVIRT_CLUSTERBOT_LEASED_RESOURCE

The OVIRT_UPGRADE_LEASED_RESOURCE has specific logic here https://github.com/openshift/release/blob/master/ci-operator/step-registry/ipi/conf/ovirt/generate-install-config-params/ipi-conf-ovirt-generate-install-config-params-commands.sh#L13

[vrutkovs]

I don't quite follow how leases work - does it have to be a unique env var?

[Gal-Zaidman]

It basically means that the lease name will be stored in an env var specified by leases.env.
So here what you did means that the lease name will be stored in en env var OVIRT_UPGRADE_LEASED_RESOURCE which will be available for all the steps.
On ovirt we have logic that the leases names correlate to secrets we have, that way we isolate openshift clusters from one another on the oVirt engine.
If you will use the OVIRT_UPGRADE_LEASED_RESOURCE env var, then the test will look for a secret with that name, which will not be there

[Gal-Zaidman]

/lgtm

[Gal-Zaidman]

/assign @petr-muller

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gal-Zaidman, petr-muller, vrutkovs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ci-operator/jobs/openshift/release/OWNERS [petr-muller]
• ci-operator/step-registry/openshift/e2e/ovirt/OWNERS [Gal-Zaidman,petr-muller,vrutkovs]
• core-services/prow/02_config/OWNERS [petr-muller]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@vrutkovs: Updated the following 3 configmaps:

• job-config-misc configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-release-infra-periodics.yaml using file ci-operator/jobs/openshift/release/openshift-release-infra-periodics.yaml
• step-registry configmap in namespace ci at cluster app.ci using the following files:
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/ovirt/clusterbot/OWNERS
  • key openshift-e2e-ovirt-clusterbot-workflow.metadata.json using file ci-operator/step-registry/openshift/e2e/ovirt/clusterbot/openshift-e2e-ovirt-clusterbot-workflow.metadata.json
  • key openshift-e2e-ovirt-clusterbot-workflow.yaml using file ci-operator/step-registry/openshift/e2e/ovirt/clusterbot/openshift-e2e-ovirt-clusterbot-workflow.yaml
• resources configmap in namespace ci at cluster app.ci using the following files:
  • key boskos.yaml using file core-services/prow/02_config/_boskos.yaml

In response to this:

This adds a task, which would be used by cluster-bot to start an ovirt cluster

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.