etcd-snapshot to openstack/ceph s3 backend, endpoint url issue

[mhazan01]

Hello all,
i've setup a rke2 cluster on openstack with terraform, while it partially work i have an issue with how the swift/s3 endpoint is passed down to the s3 client for the etcd backup and restore, this client limit the url used as endpoint to a hostname.fqdn:port format, while my openstack endpoint is configured with hostname.fqnd:port/swift/v1/AUTH_ to accomodate for multi tenancy ceph backend storage via openstack. this cause error and unreachable "snapshots" when trying to access them via the etcd containers (they are properly created by terraform). is there a switch option that would allow me to add the missing swift/v1/AUTH_ to the s3 endpoint ? or another method ?

Thanks !

[brandond]

We use the minio-go client library, which should work with any S3 compatible storage service. You're service does not seem to be 100% compatible, as this would appear to be a nonstandard path format.

Can you find an example of using your backend with minio-go, so we can see what specifically needs to be set?

[mhazan01]

i followed the doc from https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-ceph-guide.html and https://docs.ceph.com/en/latest/radosgw/keystone/ with the recommendation of rgw swift account in url = true

[brandond]

I have never seen any S3 services with a path prefix on the s3 endpoint.

I don't think Swift is interchangeable with s3. It looks like you need to deploy the Swift3 middleware, and point S3 clients at that: https://docs.openstack.org/mitaka/config-reference/object-storage/configure-s3.html

Only Swift clients can talk directly to the Swift service.

[mhazan01]

hah, that's my mistake then, for some reason terraform is still working with swift endpoint made me assume it was s3 compatible. thanks !