-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
-
We added new feature in https://github.com/kubev2v/forklift/pull/688 , to allow the perseverance of the cluster CPU from oVirt provider.
In order to do that, the user needs to specify he wish to preserve it by setting it within the plan:
`preserveClusterCpuModel=true`
e.g the plan will look like:
```apiVersion: forklift.konveyor.io/v1beta1
kind: Plan
metadata:
annotations:
populatorLabels: 'True'
creationTimestamp: '2024-01-02T15:15:51Z'
generation: 1
name: testcluster
namespace: konveyor-forklift
resourceVersion: '7403505'
uid: 53e13421-6590-49d9-84b0-735abf98e738
spec:
archived: false
description: ''
map:
network:
name: testcluster-xzklj
namespace: konveyor-forklift
storage:
name: testcluster-lmqbt
namespace: konveyor-forklift
preserveClusterCpuModel: true
provider:
destination:
name: host
namespace: konveyor-forklift
source:
name: ovirt
namespace: konveyor-forklift
targetNamespace: konveyor-forklift
vms:
- hooks: []
id: 41f2988a-a579-40a8-ab25-4584b1f696dc
warm: false
```
where you can see the new flag under the spec (like warm migrations).
The field is optional, but to select using the feature is must be there and set to `true`.
In the UI a tick flag option for oVirt providers to use it will ease on the users, which need to do it using CLI now.
It is also required for UI usage, e.g duplicate plan - which don't duplicates this field when exists.
Since @rszwajko is now working on the new plan dialog, I'm tagging you.
URL: https://github.com/kubev2v/forklift-console-plugin/issues/803
- is related to
-
MTV-547 Set CPU model on VMs migrated from RHV to OCPv
- Closed