Feature Overview

With this feature, a user is able to upload a local OVA file via the webbrowser "into" MTV for a regular OVA import.

Goals

• Who benefits from this feature, and how? The customer.
• What is the difference between today’s current state and a world with this feature? Today, OVA must be provided on the server side (ie NFS export). This feature is effectively make it a user-only workflow, not depending on an admin to put an OVA somewhere.

Requirements

(Optional) Use Cases

How will the user interact with this feature? 
Which users will use this and when will they use it?

• Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>
Questions to answer...

Out of Scope

1. High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>
**

Background, and strategic fit

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Assumptions

• <your text here>

Customer Considerations

• Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

User Experience Considerations

Provide information that needs to be considered and planned so that the user experience will meet customer needs. These could include impacts to the UI or other areas of the user experience, as well as user research needs. Please add the 'UXD' component to this JIRA if there are User Experience considerations. Initial completion during Refinement status.
<your text here>