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

QE verification of KCS for IBM Fusion use case

XMLWordPrintable

    • Quality / Stability / Reliability
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Workload Mgmt Train 30 - 2, Workload Mgmt Train 31 - 1
    • None

      This is the summary from srangana@redhat.com 

       

      Starting this slack thread in the context of the case: https://access.redhat.com/support/cases/#/case/04093129The problem that IBM-Fusion/HCI systems has with a handful of customers that are using it to host HCP clusters, is that as of pre-ACM-2.11 release, the ACM hub needed to be co-hosted with the MCE hub for these operations.For DR, and other more fleet wide management functionality, the ACM hub needs to be hosted as a separate entity and not per Fusion rack instance. This is supported since ACM 2.11 and Fusion has now shifted to only installing the MCE bundle on each HCI rack, and suggesting the customer to install an ACM hub external to these racks.This brings us to the above problem, where we still need to "upgrade" some customers who are using the older functionality, from older than ACM 2.11, to a more central ACM hub.Towards this, the ask is, if it would be feasible to support a bare bones KCS (mock attached), that deals with a strict use-case where ACM hub was co-hosted with MCE for ONLY the purposes of managing HCP clusters, to allow the uninstall of ACM hub while leaving behind the MCE and hosted cluster instance. 

       

      They want to publish a KCS so that IBM Fusion and other users could follow it in the future for similar situations.

       

      The initial KCS doc content is attached. We would like to ask ACM QE to verify the doc to ensure that there is no surprise although we acknowledge that this is not an officially supported feature.

       

      Product versions to be used

      • OCP 4.18
      • ACM 2.12
      • ODF 4.18
      • OpenShift Virtualization
      • this can be verified in AWS with BareMetal EC2 instances

       

      Prereqs

      • existing hosted cluster with kubevirt platform

       

      Tests

      • follow the doc to uninstall ACM only to turn the ACM hub into MCE hub. MCE instance and the HCPs must remain in tact
      • Check if MCE is working
        • run the server foundation pipeline?
        • run the MCE installation pipeline?
      • Ensure the HCP is still working
        • is still managed by MCE
        • MCE agents are still installed
        • ACM agents are removed

              rhn-support-dhuynh David Huynh
              rokejungrh Roke Jung
              Matthew Smigielski Matthew Smigielski
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: