Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Align description of provider properties with the UI #432

Merged
merged 1 commit into from
Oct 8, 2023

Conversation

RichardHoch
Copy link
Collaborator

@RichardHoch RichardHoch commented Oct 3, 2023

MTV 2.5.1

Resolves: https://issues.redhat.com/browse/MTV-717 and https://issues.redhat.com/browse/MTV-703 by:

  1. Changing the description of the URL field for vSphere source providers.
  2. Changing the description of the URL field for RHV source providers.
  3. Removing note that said provider names cannot include "."
    4-6: Removing an inconsistent "/" in some URLs.

Previews:

  1. https://file.emea.redhat.com/rhoch/251_provider_fixes/html-single/#adding-source-providers [See definitions of "URL" for vSphere and RHV source providers; also see that note about provider names was removed]
  2. https://file.emea.redhat.com/rhoch/251_provider_fixes/html-single/#migrating-virtual-machines-cli_mtv [Step 1, callout 11 and steep 2, callout 2]
  3. https://file.emea.redhat.com/rhoch/251_provider_fixes/html-single/#migrating-virtual-machines-cli_mtv [step 6, callout 2]

@RichardHoch
Copy link
Collaborator Author

@bennyz @bkhizgiy @sgratch @yaacov @ahadas Please review this PR. It focuses on the changes we need to make to the documentation for the Create Providers UI (https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.5/html-single/installing_and_using_the_migration_toolkit_for_virtualization/index#adding-providers) -- NOT the error messages, only the documentation of the fields. The error messages are in other PRs.

@yaacov
Copy link
Member

yaacov commented Oct 3, 2023

@RichardHoch thank you for opening this PR 💚

I'll ping here once the text in kubev2v/forklift-console-plugin#744 and kubev2v/forklift-console-plugin#745 are merged so we have a stable point of reference.

@RichardHoch RichardHoch requested a review from ahadas October 3, 2023 11:18
@RichardHoch
Copy link
Collaborator Author

@ahadas I made the changes you suggested. Please review the PR again.

Copy link
Contributor

@sgratch sgratch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, except one comment.

documentation/modules/adding-source-provider.adoc Outdated Show resolved Hide resolved
@RichardHoch RichardHoch requested a review from sgratch October 3, 2023 14:36
@RichardHoch
Copy link
Collaborator Author

@sgratch Made the change you suggested.

@yaacov
Copy link
Member

yaacov commented Oct 3, 2023

@RichardHoch @sgratch the peorpose of this PR is to align with the UI

please wait for kubev2v/forklift-console-plugin#744 and kubev2v/forklift-console-plugin#745.

once @ahadas and @RichardHoch agree on them, I'll merge them and we will copy them here.

@RichardHoch
Copy link
Collaborator Author

@yaacov @ahadas I think this PR is ready for QA. Agree? The changes in it fit Sharon's PRs as far as I can tell (error messages are not part of the documentation).

@@ -100,7 +100,7 @@ ifdef::rhv[]
* *Provider resource name*: Name of the source provider
+
include::snip-provider-names.adoc[]
* *URL*: API endpoint of the {rhv-short} Manager on which the source VM is mounted
* *URL*: API endpoint of the {rhv-full} Manager (RHVM) on which the source VM is mounted, for example, `https://rhv-host-example.com/ovirt-engine/api`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in https://github.com/kubev2v/forklift-console-plugin/pull/744/files#diff-075b2af748cc5c8407a5cd156371011523517ef954d89d2bac7d9d5c72d9fe97R29

we chose to write:

URL of the Red Hat Virtualization Manager (RHVM) API endpoint. Ensure the URL includes the "/ovirt-engine/api" path. for example: https://rhv-host-example.com/ovirt-engine/api

I'm ok with current version and ok with uipdateing to match to UI

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

p.s. not that the for -> For was fixed in the UI in a folowup

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaacov I added "URL of the..." to all the URL descriptions.

@@ -78,7 +78,7 @@ ifdef::vmware[]
. Specify the following fields:

* *Provider resource name*: Name of the source provider.
* *URL*: vCenter host name or IP address - if a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate.
* *URL*: SDK endpoint of the vCenter on which the source VM is mounted, for example, `https://vCenter-host-example.com/sdk`. If a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In https://github.com/kubev2v/forklift-console-plugin/pull/745/files#diff-78ab8802dcf0222dfbd15eeeac4d1f58cefaec2614e5900cbd2146cd8738a9d8R30

we chose to wirte:

URL of the vCenter SDK endpoint. Ensure the URL includes the "/sdk" path. For example: https://vCenter-host-example.com/sdk

I'm ok with current version and ok with uipdateing to match to UI

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

p.s.

i see the fqdn comment apear here:
If a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate.

@ahadas if it's needed we can add it to the UI, and leave it here ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

p.p.s
from the text in the UI it sounds like it must end with /sdk ... (same with the oVIrt texts)
the URL does not need to end with this post fixes, it's a little misleading, but IMHO we can trust our users to understand this nuance

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaacov @sgratch "Ensure" means it must be so. If that is not 100% accurate, that is, if it is OK if the URL does not end in /sdk, then you might want do one of the following in the UI:

  • Remove the sentence.
  • Change it to "Ensure.../sdk path, if needed."
  • Change it to "It is recommended that URL includes..." [We try to avoid saying "it is recommended" but if you think it is useful, it is OK]

I'm not sure which of the above is technically correct. You can leave the UI alone, but I'd recommend you change it if the text might confuse users.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @RichardHoch , it did sound off to me.
IMHO "if needed" is best here, we want to ensure the user understand that the URL includes the postifx that can be "/sdk" but can also be other strings like "/east1/sdk/v1" or "/server",

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RichardHoch before this change we used the term "sdk path" to denote any path that lead to the sdk, instead of using "/sdk" that sounds like it must be "/sdk".
Can we say that it needs to include the sdk path, and then say that "/sdk" is the common path used as the sdk path ?

https://github.com/kubev2v/forklift-console-plugin/pull/745/files#diff-78ab8802dcf0222dfbd15eeeac4d1f58cefaec2614e5900cbd2146cd8738a9d8L111

Copy link
Member

@yaacov yaacov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@RichardHoch hi, not exactly as the UI, but the UI does not need to be verbatim copy of the docs (*)

I commented with the texts chosen for the UI copy of the docs, we can also do a PR for the UI to alight to the texts we end up using here.

cc:// @sgratch

(*) note that the docs is the "source of truth" for the UI, so the UI need to match the docs not the other way around.

@RichardHoch RichardHoch force-pushed the 251_provider_fixes branch 2 times, most recently from 2ed1b25 to 9d00f28 Compare October 5, 2023 11:05
@RichardHoch
Copy link
Collaborator Author

@ahadas @yaacov Added "URL of the.." to any URL definitions that did not have it. Please review again. I left the "Ensure ..." sentence out of the documentation since it sounded like it was not 100% necessary.

@RichardHoch
Copy link
Collaborator Author

RichardHoch commented Oct 5, 2023

@yaacov Our comments overlapped. Would it be better if I add "Ensure..., if needed." to the documentation?

@yaacov
Copy link
Member

yaacov commented Oct 5, 2023

@yaacov Our comments overlapped. Would it be better if I add "Ensure..., if needed." to the documentation?

makes sens to me, @ahadas WDYT ?

p.s. this comment is also for the ovirt engine path, it can be "ovirt-engine/api" and can also be some other pass leading to the ovirt engine api.

@RichardHoch RichardHoch requested a review from yaacov October 5, 2023 11:34
@yaacov
Copy link
Member

yaacov commented Oct 5, 2023

@RichardHoch the reason we changed the UI text to include the "please make sure you add the ovirt engine path in oVirt and the sdk path vSphere" was because of users feedback, in your current version, i don't see this emphasis on the need to add the API path.
@ahadas we can drop the "Ensure you add "/skd" "/ovier-engine" " but then, we will return to the original phrasing, the one that users didn't like, because they tried to enter the URL without the path, WDYT ?

@yaacov
Copy link
Member

yaacov commented Oct 5, 2023

@RichardHoch @sgratch I see the discussion moved here :-)
This is good, beacuse the docs is the "source of truth" for the UI.

@sgratch once we agree on text here, please make a PR to copy it the UI.

@RichardHoch
Copy link
Collaborator Author

@yaacov @ahadas How's this?

Copy link
Member

@yaacov yaacov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@RichardHoch RichardHoch requested a review from qiyuann October 5, 2023 16:07
@RichardHoch
Copy link
Collaborator Author

@qiyuann Please review this PR.

@sgratch
Copy link
Contributor

sgratch commented Oct 5, 2023

  • Regarding the FQDN comment appears here and not in the UI:
    "If a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate."
    I intentionally skipped that part in the UI since it seems to me like too much information to put for a field help text. And anyway, we can consider adding this as a help text for the CA certificate field and not for the URL field.

  • Regarding writing "Ensure the URL includes the xxx path...." for both RHV and vSphere providers URLs:
    Another option ,in addition to Richard's suggestions, is to to replace it with something like:
    "usually the URL includes the xxx path. For example..."

    The "...,if needed" suggested option seems a bit confusing to me, because the user won't know what are the terms for "needed".

Once we will agree on those two issues, I'll make the changes in the UI, if needed :)

@ahadas
Copy link
Member

ahadas commented Oct 8, 2023

  • Regarding the FQDN comment appears here and not in the UI:
    "If a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate."
    I intentionally skipped that part in the UI since it seems to me like too much information to put for a field help text. And anyway, we can consider adding this as a help text for the CA certificate field and not for the URL field.

yeah, I don't even think we must add that to the UI - from the cases we get, it looks like insecure connections become more common (but it's good to have it in the documentation and I think the way it is now, is better than moving it to the CA certificate field)

  • Regarding writing "Ensure the URL includes the xxx path...." for both RHV and vSphere providers URLs:
    Another option ,in addition to Richard's suggestions, is to to replace it with something like:
    "usually the URL includes the xxx path. For example..."
    The "...,if needed" suggested option seems a bit confusing to me, because the user won't know what are the terms for "needed".

I guess you referenced a previous state of this PR as I don't see ... , if needed now

Copy link
Contributor

@sgratch sgratch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@RichardHoch
Copy link
Collaborator Author

@ahadas @yaacov @sgratch Please review again.

Copy link
Member

@ahadas ahadas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor comment about the paths to align them with the message in the UI
and @RichardHoch we can we also remove the file snip-provider-names.adoc, right?

documentation/modules/adding-source-provider.adoc Outdated Show resolved Hide resolved
documentation/modules/adding-source-provider.adoc Outdated Show resolved Hide resolved
Copy link
Member

@yaacov yaacov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

p.s.
you changed the OCP provider text, URL of the endpoint of the API server
we will need to add more text here, but I do not think we need to change the text here, we will go over all the texts in the provider new creation form in Issue kubev2v/forklift-console-plugin#646, @sgratch

@sgratch
Copy link
Contributor

sgratch commented Oct 8, 2023

p.s. you changed the OCP provider text, URL of the endpoint of the API server we will need to add more text here, but I do not think we need to change the text here, we will go over all the texts in the provider new creation form in Issue kubev2v/forklift-console-plugin#646, @sgratch

It's ok to leave it just to have all URL text msgs start with: "URL of the....".
It will be revised with #646 of course, but for now it's better to leave it as it is now.

@RichardHoch RichardHoch requested a review from ahadas October 8, 2023 08:41
@RichardHoch
Copy link
Collaborator Author

@qiyuann This is ready for you.

@qiyuann
Copy link

qiyuann commented Oct 8, 2023

LGTM

Copy link
Collaborator

@anarnold97 anarnold97 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RichardHoch - good work

@RichardHoch RichardHoch merged commit c903456 into kubev2v:main Oct 8, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants