The source network are not selected automatically when creating an ocp to ocp plan

[qiyuann]

When creating an ocp to ocp plan, the source network is not selected automatically.
When there are several networks, users have to remember the network of each source VM, and select it manually. If this could be improved, it'll be more user friendly.

[sgratch]

@qiyuann I noticed that the same issue (of source network/storage selected automatically for a plan) is reproduced for the oVirt source provider as well...
Is it a known issue?

[qiyuann]

@qiyuann I noticed that the same issue (of source network/storage selected automatically for a plan) is reproduced for the oVirt source provider as well... Is it a known issue?

@sgratch On my environment, the source network/storage are selected automatically for oVirt source provider.

[sgratch]

@sgratch On my environment, the source network/storage are selected automatically for oVirt source provider.

Correct. It was reproduced to me when selecting an oVirt source provider with installation issues. For a valid oVirt providers, the problem is not reproduced to me as well

[sgratch]

Note, the solution is divided into two parts:

1. For enabling the auto selection of the ocp network source mappings: Enable auto select for OCP source network mapping within a plan #689

2. For enabling the auto selection of the ocp storage source mappings: this is currently blocked by OCP: add /workloads endpoint forklift#542 since there is no way to fetch the Storage Classes of the selected plan VMs disks out of the VMs yaml. Need to add a /workload endpoint for the OCP provider for fetching the list of VMs with the expanded disk info.

[ahadas]

Note, the solution is divided into two parts:

1. For enabling the auto selection of the ocp network source mappings: Enable auto select for OCP source network mapping within a plan #689
2. For enabling the auto selection of the ocp storage source mappings: this is currently blocked by OCP: add /workloads endpoint forklift#542 since there is no way to fetch the Storage Classes of the selected plan VMs disks out of the VMs yaml. Need to add a /workload endpoint for the OCP provider for fetching the list of VMs with the expanded disk info.

@sgratch @yaacov so how about separating out the second part to a different issue that would be resolved later on and backport the first part to 2.5.0?

[sgratch]

@qiyuann this issue is for the network mapping, please update the title accordingly.

I opened a follow up issue for the storage mapping: #690

[yaacov]

closing all 2.5.0 issues that are none critical

cc:// @qiyuann ( feel free to reopen if needed )