Project

General

Profile

Actions

Tracker #19568

closed

Migrate to oVirt APIv4 API

Added by Ivan Necas about 7 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Compute resources - oVirt
Target version:
-
% Done:

0%

Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

oVirt is going to drop API v3 in version 4.2. We need to migrate to the new version
in order to be able to continue supporting oVirt as a compute provider. Expected path is:

1. take ownership of fog-ovirt to extract it from ovirt core https://github.com/fog/fog/issues/3942
2. migrate the fog code from rbovirt to https://github.com/oVirt/ovirt-engine-sdk-ruby to use the v4 API
3. update the foreman to use the updated backend

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1399750


Related issues 8 (0 open8 closed)

Related to Foreman - Refactor #20528: Remove direct connection to rbovirt clientClosedOri Rabin08/08/2017Actions
Related to Foreman - Refactor #23067: Expose use_v4 setting for ovirt compute resourceClosedIvan Necas03/29/2018Actions
Related to Foreman - Bug #23370: @vm_start_with_cloudinit@ is not supported in fog-ovirt APIv4ResolvedOri RabinActions
Related to Foreman - Bug #23916: Create Host -> RHEV Image: Incorrect CPU cores count filled when using APIv4ClosedShira MaximovActions
Related to Foreman - Bug #23836: RHEV API v4 VM Import: undefined method `update_vm'ClosedOri Rabin06/06/2018Actions
Related to Foreman - Bug #23815: RHEV api v4 host creation: undefined method `clusters'ClosedOri Rabin06/05/2018Actions
Related to Foreman - Bug #24924: oVirt API v4 incorrectly enabled VM optionsResolvedActions
Has duplicate Foreman - Bug #20191: oVirt 4.2 is not supportedDuplicate07/03/2017Actions
Actions

Also available in: Atom PDF