XMLWordPrintable

    • Managed hub status
    • False
    • None
    • False
    • Green
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      OCP/Telco Definition of Done
      https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
      Epic Template descriptions and documentation.
      https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
      ACM-wide Product Requirements (Top-level Epics)
      https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      2 Scenarios for the ACM Managed hub cluster are unknown:

      • ACM cluster status unknown -> agent running -> ignore the ACM cluster status
      • ACM cluster status unknown -> agent destroy

      So we need to define the hub cluster status by the agent status

      Agent status -> agent heartbeat interval[ 1 minutes ]       k8s - node kubelet(heartbeat) 

      goroutine -> heartbeat -> agent status

      Epic Goal

      Provide a way to determine the managed hub cluster status, and based on the status update the policy, managed cluster, compliance, and history. 

      Reference: https://issues.redhat.com/browse/ACM-8849

      Why is this important?

      ...

      Scenarios

      Acceptance Criteria

       1. status column added to the database

      2. cleanup the resource when the status from active into inactive

      3. resync the resource when the status from inactive to active

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      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 - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.

              rh-ee-myan Meng Yan
              rh-ee-myan Meng Yan
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: