Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2051655

Summary:	[Doc] Set vddkInitImage path as be part of "Add VMware provider" for MTV-2.3 and above
Product:	Migration Toolkit for Virtualization	Reporter:	Ilanit Stein <istein>
Component:	Documentation	Assignee:	Sasha Beskin <sbeskin>
Status:	CLOSED NEXTRELEASE	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:	Richard Hoch <rhoch>
Priority:	high
Version:	2.3.0	CC:	istein, jortel, mturley
Target Milestone:	---
Target Release:	2.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2051508	Environment:
Last Closed:	2022-04-03 11:00:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2051508
Bug Blocks:

Description Ilanit Stein 2022-02-07 17:41:14 UTC

This bug is to document the change in MTV-2.3 to have the VDDKInitImage path set in the VMware "Add provider" dialog.
In MTV-2.2/2.1 the VDDKInitImage path was set in the HyperConverged CR in the openshift-cnv project, as described in MTV-2.1/2.1 Documentation.

 
+++ This bug was initially created as a clone of Bug #2051508 +++

Description of problem:
further to Bug 2051504 Change of having vddkInitImage set via MTV API for MTV-2.3 and above, please add to "Add provider" the VddkInitImage settings.

Version-Release number of selected component (if applicable):
MTV-2.3

Additional info:
For this change we have those bugs:

* CNV Bug 2031033 - VM migration from VMware fail on missing v2v-vmware 
  ConfigMap in OCP-4.10/CNV-4.10
* MTV Bug 2051504 - Change vddkInitImage to be set via MTV API for MTV-2.3 and 
  above
* MTV Bug 2051508 - Change vddkInitImage to be set via MTV UI for MTV-2.3 and 
  above

Comment 1 Steve Goodman 2022-03-21 09:44:57 UTC

This will be done after MTV 2.3 GA.

Comment 2 Sasha Beskin 2022-03-30 11:38:09 UTC

Ilanit,

Comment 3 Sasha Beskin 2022-03-30 11:44:10 UTC

Ilanit,
Where will this setting appear in the "Add provider' procedure? Together with the username, password and SHA-1 fingerprint?

Comment 4 Sasha Beskin 2022-03-30 11:50:29 UTC

And from the CLI - in creating the Provider manifest as described in Bug 2051504?

Also, does the procedure of creating a VDDK image remain the same?

Comment 5 Mike Turley 2022-03-30 13:34:47 UTC

Sasha,

> Where will this setting appear in the "Add provider' procedure? Together with the username, password and SHA-1 fingerprint?

That's correct, although the SHA-1 fingerprint field has been removed as of Bug 1897276, replaced by a "Verify certificate" button which displays the fingerprint and asks if the user trusts it. You can see this in action via the static preview of our UI at http://konveyor-forklift-ui-preview.surge.sh/. Just navigate to the Providers page and click Add provider, select VMware, and enter any fake info and the "Verify certificate" button will enable.

Most of our UI can be previewed there, it is automatically updated as new pull requests are merged.


> And from the CLI - in creating the Provider manifest as described in Bug 2051504

That's correct.