Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-1422

Allow turning on EFS CSI usage metrics

    XMLWordPrintable

Details

    • Allow turning on EFS CSI usage metrics
    • 3
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0
    • 0% 0%

    Description

      Epic Goal*

      This goal of this epic is to provide a way to admin to turn on EFS CSI usage metrics. Since this could lead to performance because the CSI driver would walk through the whole volume this option will not be enabled by default; admin will need to explicitly opt-in.

       
      Why is this important? (mandatory)

      Turning on EFS metrics allows users to monitor how much EFS space is being used by OCP.

       
      Scenarios (mandatory) 

      Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

      1. As an admin I would like to turn on EFS CSI metrics 
      2. As an admin I would like to visualise how much EFS space is used by OCP.

       
      Dependencies (internal and external) (mandatory)

      None

      Contributing Teams(and contacts) (mandatory) 

      • Development - STOR
      • Documentation - STOR
      • QE - STOR
      • PX - Yes, knowledge transfer
      • Others -

      Acceptance Criteria (optional)

      Enable CSI metrics via the operator - ensure the driver is started with the proper cmdline options. Verify that the metrics are sent and exposed to the users.

      Drawbacks or Risk (optional)

      Metrics are calculated by walking through the whole volume which can impact performances. For this reason enabling CSI metrics will need an explicit opt-in from the admin. This risk needs to be explicitly documented.

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

      Attachments

        Activity

          People

            fbertina@redhat.com Fabio Bertinatto
            rh-gs-gcharot Gregory Charot
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: