Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-486

Epic to track the various requirements for the RRD

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • Release Readiness Dashboard
    • False
    • False
    • RHODS-7446RHOSi Dashboards - Release readiness reporting
    • No
    • To Do
    • RHODS-7446 - RHOSi Dashboards - Release readiness reporting
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined
    • No
    • Pending
    • None

      1. publish the current 4/8 version of the RRD as is. - Done
      2. Iteratively publish the RRD to the full version - in progress
      3. Factor in the RMs for the Managed Services. - Pending
      4. Manually make an entry for the SUMMIT readiness. This is only for internal tracking and the main one will be the GA RRD - Pending
      5. Need a way, perhaps via confluence to have a button that can be pushed to refresh the RRD - Pending
      6. Do we do it for all releases ? 
        1. What are the next set of releases ? - Pending
      7. Where do we want people to collaborate on ? Use the RRD. Confluence will only have a pointer.  - Pending
      8. Will automating the RRD itself create problems for adding in comments ?
        1. No. The RRD is a one time object. The charts are refreshed. So, comments can be added. 
      9. What is the overlap between the RRD & the Jira Dashboards ? - Pending
      10. We need to have User Guide & Design doc available for RRD generation tool. The Design doc need not document how the base repo etc works, it is sufficient if the DD has info on how the RHODS specific changes are implemented. - Pending
      11. The UG should have info on what needs to be done when additional releases are added. - Pending
      12. The UG or DD should have details for a RO access to the intermediate files, just incase someone wants to go through the data trail for understanding the metrics. - Pending
        1. These intermediate files can be under Arthy's id for now.
        2. Iteratively, move the ownership of these files to a ML that orchestrates the RRD.
      13. Have the RRD generation under a automated mechanism to refresh the RRD, say at a daily basis.
        1. Ability to notify via email when the RRD is refreshed. - Pending
        2. Ability to on-demand refresh the RRD - Refer point 5 -  Pending
        3. Can we have the ability for the on-demand refresh to be updating from 1 source of the data lake only ? For example, I want to just get the latest from Jira and no need to refresh from Polarion (Note : Bad idea) - Pending
      14. RRD needs to show add-on metrics like additional Perf+Scale metrics that we will bring in for RHODS - Pending
      15. Define the various Qlty controls, Say A thru F. F for live testing and A for BVT. The RRD/Dashboards should be able to show the RM snaps as the build moves through various QC points. - Pending

              Unassigned Unassigned
              giridhar.ramaraju@redhat.com Giridhar Ramaraju
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: