Feature Overview

• As a User or Admin, I want to be able to passthrough USB-devices connected to the OCP Node to my VMs
• As a Buyer, I want to be sure that the system is SVVP certified - which requires USB-passthrough to pass the certification - see https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/microsoft-usb-test-tool--mutt--devices

Goals

Today we can passthrough PCI devices, but not USB devices from the OpenShift Node. As quite some hostdevices (e.g. weatherforecast) are USB devices, we need a way to easily forward a USB device to a VM. This will help all customers that need USB device passthrough.
We also need to be able to easily pass SVVP certification without major efforts.

Requirements

A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts.  If a non MVP requirement slips, it does not shift the feature.

Out of Scope

N/A
 

Background, and strategic fit

All our other Virt solutions (RHV, RHOSP and RHEL) are able to do USB device passthrough. With that it is required to have this feature in OCP Virt as well.

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Customer Considerations

See https://access.redhat.com/solutions/479683
 

Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

<What does success look like?>

• Ability for an end user to passthrough a device connected to an OpenShift node to the Virtual Machine - and to receive full support from Red Hat without work arounds.

< Does this feature have doc impact?  Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact>

• Updates to existing content - add content to existing "PCI device passthrough" documentation

 <If unsure and no Technical Writer is available, please contact Content Strategy. If yes, complete the following.>

• <What concepts do customers need to understand to be successful in [action]?>
• <How do we expect customers will use the feature? For what purpose(s)?>
• <What reference material might a customer want/need to complete [action]?>
• <Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available. >
• <What is the doc impact (New Content, Updates to existing content, or Release Note)?>

Interoperability Considerations

< Which other products and versions in our portfolio does this feature impact? >

• None

<If other products will be impacted set the ‘LP_Interop’ label on the Feature>

• NA

< What interoperability test scenarios should be factored by the layered product(s)? >

Questions