Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-4683

Use multi-payload by default for Power VS

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • IBM P Dev, MA-Compute Dev
    • None
    • Multi-Payload PowerVS
    • False
    • None
    • False
    • Not Selected
    • NEW
    • In Progress
    • x86_64, ppc64le
    • NEW
    • 67% To Do, 0% In Progress, 33% Done

      Epic Goal

      • The goal of this epic is switch the default payload target for Power VS installations to the multi-payload.

      Why is this important?

      • This is important because customers using Power VS have a lot are being promoted content showing them how to leverage the multi-payload to add amd64 workers. This eliminates an extra step for them (migrating to the multi-payload), and doesn't carry the risk of challenges for disconnected clusters since most cloud based clusters will be connected.

      Acceptance Criteria

      • Red Hat OCM console offers a multi-payload default installer to users deploying on Power VS
      • All links in the OCM console for Power VS direct to the download mirror's "multi" tree instead of the "ppc64le" tree

      Dependencies (internal and external)
      1. OCMUI team to update the console

              mturek.coreos Michael Turek
              jpoulin Jeremy Poulin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: