kubev2v / forklift-console-plugin

OpenShift Console Plugin For Forklift, the plugin adds a web based user interface for Migration Toolkit for Virtualization inside Openshift web console.
Apache License 2.0
5 stars 20 forks source link

Refresh the field labels in the create providers form #246

Closed yaacov closed 1 year ago

yaacov commented 1 year ago

Currently the create provider forms has labels from different development strata, each use a little different numenculture. We need to align all provider types to use one naming convention and field order.

the unified order and naming convention will be:

[all: vmWare, oVirt, Openstack, kubevirt] Provider resource namespace (default to migration operator namespace) Provider resource name (unique name for the new provider) Provider resource type (kubernetes, vmWare, oVIrt, Openstack)

[vmWare] Username for vCenter Password for vCenter Hostname or IP of the vCenter server

VDDK init image

Skip certificate validation (if checked, the provider's certificate won't be validated) SHA-1 fingerprint

[oVirt] Username for oVirt Password for oVirt Hostname or IP of the oVirt engine server

Skip certificate validation (if checked, the provider's certificate won't be validated) CA certificate

[Openstack] Username for Openstack Password for Openstack URL of the Openstack identity server

Region Project Domain

Skip certificate validation (if checked, the provider's certificate won't be validated) CA certificate

[kubevirt] URL of the kubernetes API server

Service account token

yaacov commented 1 year ago

@sgratch hi, I'm open to different naming conventions, the point of this issue is to have all the providers use the same naming convention and same order of vields