Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-16451

document how to reserve OTU devices

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • rhos-18.0.10 FR 3
    • rhos-18.0.10 FR 3
    • documentation
    • None
    • Document how to reserve OTU devices
    • M
    • False
    • Hide

      None

      Show
      None
    • False
    • RHOSSTRAT-733Support devices for RHOSO18 that will not be re-allocated until after some operator action is taken
    • Not Selected
    • ?
    • ?
    • Done
    • RHOSSTRAT-733 - Support devices for RHOSO18 that will not be re-allocated until after some operator action is taken
    • ?
    • rhos-workloads-compute
    • ?
    • 0% To Do, 0% In Progress, 100% Done

      Goal: 

      < Goal based statement, with context - remove these notes before saving -->

      • For example:

      As an operator, I want to provide passthrough devices to instances with known- safe firmware and device state.

      As a special-purpose cloud operator, I may have specialized hardware that requires special handling after use (power or bus resets, config initialization, etc).

      As a cloud operator, I want to provide fast direct-passthrough storage support, but without risking information leakage between tenants.

      As a cloud operator, I want to check the write-wear indicator on my passthrough NVMe devices after each user to avoid returning devices over the safety threshold to be allocated.

      Acceptance Criteria:

       

              erpeters@redhat.com Erin Peterson
              sbauza@redhat.com Sylvain Bauza
              rhos-workloads-compute
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: