Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-1498

RFE: easy way to determine what containers to mirror for disconnected installation

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • None
    • DevOps
    • RFE: easy way to determine what ACM containers to mirror for disconnected installation
    • False
    • None
    • False
    • To Do
    • ACM-633 - RHACM Assembly and Channels for Market Consumption

      Epic Goal

      • As a customer I would like a list of ACM containers to download for each piece of functionality that i wish to implement. Ideally being able to limit the mirroring processes to specific architectures to deal with limited bandwidth and/or storage space in the disconnected environment. Having this be a web page on console.redhat.com where I can select the functionality and architecture and get the commands to pull the container directly from Red Hat to my local mirror.

      Why is this important?

      • Cruise ship company has OCP clusters on their ships that are connected to the Internet via a 200kbps satellite connection. This is not a "Red Hat" edge case as all we consider Edge is limited compute power and this isn't the case for customer. They are limited in bandwidth and storage, hence wanting to limit the number of containers to push to the ships and only pushing the x86_64 containers.

      Scenarios

      • customer wants to deploy a sub-set of functionality in ACM
      • They are constrained on bandwidth and storage where they run their OCP clusters that they want to manage/monitor with ACM
      • They need to limit the containers they push to the remote data centers to only the functionality and architecture they are running

      Acceptance Criteria

      • minimally, we have a ACM documentation that lists the containers necessary to run each piece of functionality, their name and how to find the current version to mirror it.
      • best case, this is either a Portal Lab or a page on cloud.redhat.com where the customer can select the functionality and architecture and get the list of commands to mirror the containers locally to the quay mirror registry.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              Gurney.Buchanan@ibm.com Gurney Buchanan
              rhn-support-kperrier Kent Perrier
              Christopher Bynum Christopher Bynum
              Gurney Buchanan Gurney Buchanan
              Scott Berens Scott Berens
              Votes:
              5 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: