Description of problem: Today we run ovirt-system-tests with the 3.6 sdk rpms & v3 of the API. We need to move master and 4.0 to start using v4 of the API, in order to start verifying it and add new tests for new features. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I've submitted a patch [1] to stop publishing sdk 3.6 to master nightly repo, Juan, should we just install the v4 sdk and we are ready to start using it? Or more actions are needed? [1] https://gerrit.ovirt.org/#/c/59766/
The initial plan for version 4.1 of oVirt is to remove the version 3 of th API, and version 3 of the SDKs and the CLI, so we will only support version 4 of the API and the SDKs. But I think it is still too early to make that change, as the decision isn't yet 100% finalized. So I believe that at this point it isn't OK to remove the 3.6 SDKs from the master nightly repo. To start using version 4 of the API and version 4 of the SDKs all you need to do is install the new SDKs, and adapt the ovirt-systems-test code to use the new versions.
There's also a huge benefit in still running the 3.6 API, as you are testing backwards compatibility this way. I agree it's a bit too early, though we need to test the v4 API as well. Need to think how to combine (without doubling our efforts).
Most of it is done...?