Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-5153 [DOC] OADP will ship with two AWS plugins
  3. OADP-5154

(QE) Verify for ( [DOC] OADP will ship with two AWS plugins )

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • OADP 1.4.2
    • None
    • QE-Task
    • None
    • False
    • Hide

      None

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

      The OADP engineering team has to release a new AWS plugin image for s3 providers that are NOT fully s3 compatible.

      AWS

      This plugin is to support running Velero on AWS:

      • An object store plugin for persisting and retrieving backups on AWS S3. Content of backup is Kubernetes resources and metadata files for CSI objects, progress of async operations.
        It is also used to store the result data of backups and restores including log files, warning/error files, etc.
      • A volume snapshotter plugin for creating snapshots from volumes (during a backup) and volumes from snapshots (during a restore) on AWS EBS.
      • Since v1.4.0 the snapshotter plugin can handle the volumes provisioned by CSI driver ebs.csi.aws.com

      Legacy AWS

       

      This plugin is to support running Velero on AWS:

       

      • An object store plugin for persisting and retrieving backups on AWS S3. Content of backup is kubernetes resources and metadata files for CSI objects, progress of async operations.
      • It is also used to store the result data of backups and restores including log files, warning/error files, etc.
      • A volume snapshotter plugin for creating snapshots from volumes (during a backup) and volumes from snapshots (during a restore) on AWS EBS.

      Since v1.4.0 the snapshotter plugin can handle the volumes provisioned by CSI driver ebs.csi.aws.com

      Velero links:

       

      Documentation

      This will be two new sections in the existing AWS documentation, one for each plugin.
      There is no need for a new AWS section.
      There will need to be:

      • An explanation of why there are two plugins
      • A use case for each plugin

      There will also be a tidy-up of existing documentation.

              Unassigned Unassigned
              talayan@redhat.com Tareq Alayan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: