Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-4589

Dataupload object reporting improvements

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • OADP 1.3.4
    • None
    • velero
    • 4
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • 0
    • 0.000
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • None 

      NAME               STATUS      STARTED   BYTES DONE   TOTAL BYTES   STORAGE LOCATION   AGE     NODE
cirros-1-2w4w7     Completed   11m       1073741824   1073741824    dpa-sample-1       11m     ip-10-0-5-44.ec2.internal
cirros-2-6jkrk     Completed   5m15s     1073741824   1073741824    dpa-sample-1       5m44s   ip-10-0-5-44.ec2.internal
mysql-dm-1-p9m2g   Completed   57m       36956832     36956832      dpa-sample-1       58m     ip-10-0-5-44.ec2.internal
mysql-dm-2-pzzzb   Completed   54m       36956832     36956832      dpa-sample-1       54m     ip-10-0-5-44.ec2.internal
mysql-dm-3-49vpb   Completed   34m       36956832     36956832      dpa-sample-1       34m     ip-10-0-5-44.ec2.interna

      Using the above data as an example, we would like to improve the dataupload object summary.

      1. Open an upstream issue to address the following improvements
      2. A column that shows the creation to completion time.  This will show the speed / time it takes to move data off cluster.
      3. A column that shows the actual data xfered off cluster.    Bytes Done and Total Bytes is not representing the actual data moved off cluster.

      I would say it would be reasonable to target the improvement for Velero 1.15

       

              rhn-engineering-mpryc Michal Pryc
              wnstb Wes Hayutin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: