-
Notifications
You must be signed in to change notification settings - Fork 28
OVA upload procedure #787
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
base: main
Are you sure you want to change the base?
OVA upload procedure #787
Conversation
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.
Generally looks good, just a few small nitpicks.
| + | ||
| A success message confirms the file upload. After several seconds, the number of virtual machines increases under the *Provider inventory* section. | ||
| + | ||
| * If your OVA appliance is large, you might receive a request timeout error message. |
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.
The OVA upload timeout was removed in time for GA so this line is unnecessary. See also: https://issues.redhat.com/browse/MTV-3617
| . Click the provider to open the *Details* page. Click the provider’s *YAML* tab. | ||
| + | ||
| For information about creating a provider, see xref:adding-source-provider_ova[Adding an Open Virtual Appliance (OVA) source provider]. | ||
| . Scroll down the provider’s YAML file to `spec.settings.applianceManagement`, and set `applianceManagement` to `'true'`: |
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.
This settings field is not displayed by default, they will need to add it. The example yaml is good, but the explanation in this bullet point may be misleading.
| [role="_abstract"] | ||
| You can configure Open Virtual Appliance (OVA) file upload by web browser to upload an OVA file directly to an NFS share. To configure OVA file upload, you first enable OVA appliance management in the `ForkliftController` custom resource (CR) and then enable OVA upload for each OVA provider. When you enable OVA upload for an OVA provider, the *Upload local OVA files* option populates on the provider’s *Details* page in the MTV UI. | ||
|
|
||
| .Prerequisites |
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.
The NFS share must be writable by the QEMU group (107).
| + | ||
| The Operator Details page opens in the *Details* tab. | ||
| . Click the *ForkliftController* tab, and open the `forklift-controller` resource. | ||
| . Click the `forklift-controller` *YAML* tab, and add the `feature_ova_appliance_management` field to the `spec` section of the `forklift-controller` custom resource (CR): |
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.
They should wait for the operator to redeploy the controller after changing the ForkliftController CR.
https://issues.redhat.com/browse/MTV-3358
Preview: https://jenny-anne.github.io/mtv-previews/MTV/MTV-3358#proc_configuring-ova-web-upload_ova