Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-564

R&D Multiarch Builds Architecture

    XMLWordPrintable

Details

    • 5
    • Build + Jenkins Sprint 232, Build + Jenkins Sprint 233, Build + Jenkins Sprint #234, Pipeline Integrations #235, Pipeline Integrations #236, Pipeline Integrations #237, Pipeline Integrations #238, Pipeline Integrations #239, Pipeline Integrations #240

    Description

      Story

      As a Developer working on OpenShift Builds v1, I would like to understand the overall architecture changes and specific details of implementing support for heterogeneous builds on a multi-arch OpenShift cluster, including any changes that would be needed to the Build API and other supporting components.

      Background

      With the enablement of OpenShift clusters with mixed architecture capable compute nodes it is necessary to have support for manifest listed images so the correct images/binaries can be pulled onto the relevant nodes. __ 

      Out of scope

      Deliverables for this Story DO NOT include:

      • A working Proof of Concept

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      No dependencies identified.

      Acceptance Criteria

      Deliverables for this Story DO include:

      • A pull request to the OpenShift Enhancement Proposals repository which should include specifics about the implementation details of supporting heterogeneous builds on OpenShift Builds v1.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

      Attachments

        Activity

          People

            rhn-engineering-nalin Nalin Dahyabhai
            cdaley Corey Daley
            Nalin Dahyabhai Nalin Dahyabhai
            Nalin Dahyabhai Nalin Dahyabhai
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: