Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-2482

Gather requirements for MSO development

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • MSO MVP
    • False
    • None
    • False
    • monitoring
    • Not Selected
    • NEW
    • To Do
    • Impediment
    • NEW
    • 0
    • 0% 0%
    • XL
    • 0

      Epic Goal

      • Gather requirements for monitoring deployments from prospective users (Managed Services, maybe multi cluster initiatives like hypershift)
      • Map out development items to fulfill the gathered requirements.
      • Develop a v1.0 of monitoring-stack-operator.

      Why is this important?

      • Out current monitoring stack (deployed by CMO) is not flexible enough to cover all use cases

      Scenarios

      1. Which HA topology is needed.
      2. What are auth[n,z] requirements.
      3. ...

      Acceptance Criteria

      • Prospective users have confirmed their requirements
      • Requirements are implementable
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. https://issues.redhat.com/browse/MON-2256

      Previous Work (Optional):

      1. https://issues.redhat.com/browse/MON-2279

      Open questions::

        1.
        Docs Tracker Sub-task To Do Undefined Unassigned
        2.
        QE Tracker Sub-task To Do Undefined Unassigned
        3.
        TE Tracker Sub-task To Do Undefined Unassigned

            Unassigned Unassigned
            jfajersk@redhat.com Jan Fajerski
            Archiver:
            jfajersk@redhat.com Jan Fajerski
            Joao Marcal, Simon Pasquier, Sunil Thaha

              Created:
              Updated:
              Archived: