-
Notifications
You must be signed in to change notification settings - Fork 24
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
Conversation
b2f84c8
to
83555fb
Compare
@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. |
@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. |
@ahadas I made the changes you suggested. Please review the PR again. |
There was a problem hiding this 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.
@sgratch Made the change you suggested. |
1b63341
to
d323942
Compare
@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. |
@@ -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` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
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 ?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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",
There was a problem hiding this comment.
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 ?
There was a problem hiding this 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.
2ed1b25
to
9d00f28
Compare
@yaacov Our comments overlapped. Would it be better if I add "Ensure..., if needed." to the documentation? |
@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. |
@RichardHoch @sgratch I see the discussion moved here :-) @sgratch once we agree on text here, please make a PR to copy it the UI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@qiyuann Please review this PR. |
Once we will agree on those two issues, I'll make the changes in the UI, if needed :) |
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)
I guess you referenced a previous state of this PR as I don't see |
8682805
to
ec61d08
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
82d07a1
to
6f88d55
Compare
There was a problem hiding this 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?
There was a problem hiding this 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
It's ok to leave it just to have all URL text msgs start with: "URL of the....". |
Signed-off-by: RichardHoch <[email protected]>
d0cd9b8
to
97eb324
Compare
@qiyuann This is ready for you. |
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RichardHoch - good work
MTV 2.5.1
Resolves: https://issues.redhat.com/browse/MTV-717 and https://issues.redhat.com/browse/MTV-703 by:
4-6: Removing an inconsistent "/" in some URLs.
Previews: