Automating Bucket, Policy, and User Creation in Apache Ozone

[the-Fitz]

Introduction

I'm currently migrating from MinIO to Apache Ozone for block storage solutions on my cluster. In MinIO, I utilized a configuration file to automate the creation of buckets, policies, and users. I'd like to achieve similar functionality in Apache Ozone.

Current MinIO Configuration

My current MinIO configuration looks something like this:

buckets:
  - name: bucket1
    policy: none
    purge: false
  - name: bucket2
    policy: none
    purge: false

policies:
  - name: policy1
    statements:
      - resources:
          - "arn:aws:s3:::bucket1/*"
        actions:
          - "s3:*"
  - name: policy2
    statements:
      - resources:
          - "arn:aws:s3:::bucket2/*"
        actions:
          - "s3:*"

users:
  - accessKey: accessKey1
    secretKey: secretKey1
    policy: policy1
  - accessKey: accessKey2
    secretKey: secretKey2
    policy: policy2

I was hoping something like the following would be available (via the Apache Ozone helm chart), but I couldn't find any config items that seem to match the concept of auto-creating or pre-defining these types of resources:

om:
  env:
    - name: OZONE-SITE.XML_ozone.om.bucket.autocreate
      value: "true"
    - name: OZONE-SITE.XML_ozone.om.bucket.autocreate.buckets
      value: "bucket1,bucket2,bucket3"

Discussion Points and Questions

I'd like to know if it's possible to achieve similar automation in Apache Ozone. Is there a configuration item or path that allows me to define buckets, policies, and users in a single step? If not, are there any plans to add this feature in future releases?

I've researched the Apache Ozone documentation and source code, but I couldn't find any information on this specific topic. Any guidance or feedback from the community would be greatly appreciated.

Automating the creation of buckets, policies, and users would simplify the deployment and management of my cluster. It would also reduce the risk of human error and ensure consistency across my environment.

[kerneltime]

Ozone clusters are typically long-lived clusters where buckets are created as and when needed based on new use cases being onboarded and authorized based on changing security policies enforced by Apache Ranger (in many production deployments). The ability to create a fixed namespace via boot-up configuration has not yet been implemented. Apache Ozone is a top-level Apache Software Foundation project, and contributions are welcome.

[ivandika3]

For cloud-native environment, one possible exploration is to develop Kubernetes operators similar to Ceph's Rook.