add compatibility version for hosted engine dc and cluster

[kobihk]

in the latest version of 4.4, we have a new data center and cluster compatibility version - 4.5
by default, we use the latest data center and cluster compatibility version - 4.5
but we need also the option to define the hosted engine to stay with compatibility version 4.4

[ovirt-infra]

Hello contributor, thanks for submitting a PR for this project!

I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.

In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

1. Type ci test please on this PR to trigger automated tests for it.
2. Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow Add generic test for service status #3 option )
3. If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

[kobihk]

verified!!

[kobihk]

@arachmani @eslutsky could you please CR

[mwperina]

Isn't only ovirt-hosted-engine-setup interacting with this role? If so shouldn't this be exposed/fixed in the ovirt-hosted-engine-setup instead?

[arachmani]

Isn't only ovirt-hosted-engine-setup interacting with this role? If so shouldn't this be exposed/fixed in the ovirt-hosted-engine-setup instead?

It is also used when running the playbook directly.

[arachmani]

AFAIU, DC and cluster can be different versions, right?
If so let's use different vars and add the limitations to the README.

[mwperina]

Btw hosted-engine-setup has already been moved to https://github.com/ovirt/ovirt-ansible-collection so we are going to archive this repository soon (or at least archive master), so I suggest to move this PR to oVirt Ansible Collection and start switching the automation to use the collection

[kobihk]

Created new PR in:
oVirt/ovirt-ansible-collection#125

@arachmani @mwperina
maybe it will be better to add a deprecation comment as we have in:
https://github.com/oVirt/ovirt-ansible-repositories/pull/62/files

[kobihk]

merged in:
oVirt/ovirt-ansible-collection#125

[kobihk]

AFAIU the latest versions (4.4.2, 4.4.3) should not support the ansible collections.
so I think we still need to keep this repo updated.
@mwperina wdyt?

[mwperina]

AFAIU the latest versions (4.4.2, 4.4.3) should not support the ansible collections.
so I think we still need to keep this repo updated.
@mwperina wdyt?

On the contrary, from oVirt 4.4.3 are going to support only ansible 2.9.z with ovirt-ansible-collection, which will obsolete all oVirt modules in ansible core and all previously supported standalone oVirt roles.

[mwperina]

OK, we had an offline discussion and we need to help QE until they will switch automation to Ansible Collection. Asaf/Sandro, could you please merge this backport from collection here?

@arachmani @sandrobonazzola

[mwperina]

+1

[kobihk]

thank you @mwperina @arachmani @sandrobonazzola