-
Notifications
You must be signed in to change notification settings - Fork 133
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
Unable to benchmark custom s3 endpoint from openstack vm #18
Comments
Btw, This is what i get from baremetal host located outside of openstack:
|
did you try to set the credentials in your env like:
I was able to benchmark RadosGW that way. |
Hi, Have the same issue with export option.
Best Regards |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Environment setup:
testvm => 2x harpoxy-s3 => 3x ceph radosgw
Rados gw runs on dedicated hardware while testvm and haproxy-s3 runs on openstack. This setup works good since i was able to use rclone to POST/GET objects on this custom s3. Note that radosgw are completly standalone and not integrated with openstack keystone at all.
Problem definition:
As a second step i wanted to run s3-benchmark just to check overall long term performance.
This is how my credentials are set:
I get something like that:
I believe the issue is caused by fact that aws-go-sdk recognizes our openstack api as a valid aws api and tries to obtain s3 credentials this way.
Would it possible to force s3-benchmark to skip aws autodetection ??
Regards,
Bart
The text was updated successfully, but these errors were encountered: