Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-2917 As a cloud operator, I want to provide bare metal as a service (ironic), so that my end-users can provision bare metal machines
  3. OSPRH-3061

As a cloud operator, I want to provide bare metal as a service (ironic), so that my end-users can provision bare metal machines

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • No Docs Impact
    • OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
    • ?
    • ?

      What is the probability and severity of the issue? I.e. the overall risk

      Does this affect specific configurations, hardware, environmental factors, etc.?

      Are any partners relying on this functionality in order to ship an ecosystem product?

      What proportion of our customers could hit this issue?

      Does this happen for only a specific use case?

      What proportion of our CI infrastructure, automation, and test cases does this issue impact?

      Is this a regression in supported functionality from a previous release?

      Is there a clear workaround?

      Is there potential doc impact?

      If this is a UI issue:
      Is the UI still fit for its purpose/goal?

      Does the bug compromise the overall trustworthiness of the UI?

      Overall context and effort – is the overall impact bigger/worse than the bug in isolation? For example, 1 workaround might seem ok, 5 is getting ugly, 20 might be unacceptable (rough numbers).

              Unassigned Unassigned
              jjoyce@redhat.com Jason Joyce
              rhos-dfg-hardprov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: