Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add profile for Qumulo S3. #86

Merged
merged 1 commit into from
May 1, 2024
Merged

Add profile for Qumulo S3. #86

merged 1 commit into from
May 1, 2024

Conversation

Gandalf-
Copy link
Contributor

Qumulo is a multi-protocol scale-out NAS that has support for AWS compatible S3.

Our S3 documentation is here; https://docs.qumulo.com/administrator-guide/s3-api/index.html

I tested this profile against an internal cluster and everything works! Please let me know if there are any other testing steps you'd like to see.

@dkocher
Copy link
Contributor

dkocher commented Apr 14, 2024

The connection profile should be expanded to add configuration specifics for the limitations 1 of Qumulo.

        <key>Properties</key>
        <array>
            <string>s3.bucket.virtualhost.disable=true</string>
           <string>s3.versioning.enable=false</string>
            <string>s3.storage.class.options=STANDARD</string>
        </array>

It would also be great if custom disk image could be provided.

Footnotes

  1. https://docs.qumulo.com/administrator-guide/s3-api/supported-s3-functionality-known-limits.html

@dkocher dkocher marked this pull request as draft April 25, 2024 07:09
@Gandalf-
Copy link
Contributor Author

Thank you for the feedback! I added the properties you proposed and created a custom disk image; here's what it looks like

Screenshot 2024-04-30 at 11 42 45 AM

@Gandalf- Gandalf- marked this pull request as ready for review April 30, 2024 18:51
@dkocher dkocher merged commit 155d256 into iterate-ch:main May 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants