Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Add S3 destination to na_elementsw_backup module #1

Open
scaleoutsean opened this issue Jun 21, 2021 · 0 comments
Open

Add S3 destination to na_elementsw_backup module #1

scaleoutsean opened this issue Jun 21, 2021 · 0 comments

Comments

@scaleoutsean
Copy link

scaleoutsean commented Jun 21, 2021

SUMMARY
  • There appears to be no S3-related inputs for this module as of mid 2021, so it seems like only SF to SF backups are supported.
  • snapshot_id param could be added
ISSUE TYPE

One of two backup destinations is supported - S3/Swift (okay, nobody uses Swift) is not yet, and it requires slightly different input parameters from what is currently available so it appears that the current module cannot work with Backup to S3.

image

Notice how the API allows the useful snapshot_id param which isn't currently available or exposed in the UI. That could be added both here and to existing (SF to SF) module.

TFM says if snapshot_id = 0, then ad-hoc snapshot is made, but snapshot_id = "" is effectively the same, that's why the current module works fine without it.

COMPONENT NAME
  • na_elementsw_backup module
ADDITIONAL INFORMATION
- name: example netapp solidfire
  hosts: localsf
  gather_facts: no
  connection: local

  tasks:  
    - name: SolidFire backup to S3 
      na_elementsw_backup:
        hostname: "https://s3.com.org:18443"
        src_volume_id: 201
        src_snapshot_id: 18437
        dest_hostname: "{{ s3_hostname }}"
        dest_username: "{{ s3_bucket }}"
        dest_s3_access_key: "{{ s3_keya }}"
        dest_s3_secret_key: "{{ s3_keys }}"
        dest_s3_destination_bucket: "backups"
        dest_s3_tags: ["monday","snap"]
        format: "native"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant