-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[files_external] swift tests #14077
[files_external] swift tests #14077
Conversation
'key'=>'$password', | ||
'bucket'=>'swift', | ||
'region' => 'DFW', | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
THe above lines are the ones where I'm not sure if I did that correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe see ccollicutt/docker-swift-onlyone#1
2fa9115
to
4529ff7
Compare
What's the status ? |
Needs further work, because I didn't figured out how to connect from ownCloud to swift ... maybe @Xenopathic can help here. Maybe we can use the ceph/demo docker container that also exposes swift. |
So, it turns out the PHP library we use to connect to Swift only supports Keystone authentication (v2), not Swift built-in authentication (v1), which the current Docker image and Ceph support. It will be possible to get Keystone integrated with Ceph, but it could take some time... |
@MorrisJobke nope. swift with ceph wont work because the libs we use don't support Keystone v1. @Xenopathic I think time would be better invested in a devstack docker container. see https://wiki.openstack.org/wiki/Docker ... it seems several people are trying this: https://hub.docker.com/search/?q=devstack&page=1&isAutomated=0&isOfficial=0&starCount=0&pullCount=0 |
@butonic With a bit of luck, setting up Keystone and connecting it to Ceph should be relatively straight-forward. Hopefully, I can avoid needing a MySQL database...: http://ceph.com/docs/master/radosgw/keystone/ |
@Xenopathic AFAIU you need to set up an openstack instance with keystone to make ceph hand over auth to that service. So ... twice the trouble. But please prove me wrong ;) |
@butonic Sorry to break the bad news, but I just got Keystone working with Ceph without needing the whole OpenStack full-stack. I nearly swallowed my own tongue when the little green dot appeared... |
4529ff7
to
3d9d47e
Compare
A new inspection was created. |
@MorrisJobke @butonic Get testing! The Docker image is available at https://hub.docker.com/r/xenopathic/ceph-keystone/, and I have full intentions of creating an S3 test around the same image. |
? Jenkins needs to be configured to actually run this one ;) |
@MorrisJobke No, in the admin interface, manually configuring it to see if it actually worked. But I can guarantee that Jenkins will fail, since one of the tests fails on Swift (good we've got unit testing now!) |
@icewind1991 @MorrisJobke @butonic Review? Note that the tests actually fail at the moment (two failures), but the tests do run, so this PR can be considered successful. |
Can we reuse the objectstore primary test setup here somehow? cc @Xenopathic @butonic |
@MorrisJobke The start/stop scripts are ever so slightly different, it might not be worth trying to combine them. These files are unlikely to change much, and when they do we can just port changes between them. BTW, I've added you as a collaborator on the xenopathic/ceph-keystone image, so if any changes need to be made you can make them directly 😄 |
Use netcat to check when the port opens, rather than an arbitrary timeout. Hard limit of 60 seconds in case something breaks
219a72e
to
c98b303
Compare
Can we get this retested and merged? |
Docker logs:
autotest logs:
|
Is this that btrfs loopback thing with Ceph again? |
Could be. |
Almost there:
Tests passed, there was just an issue when cleaning up. Might not be critical. |
The error code is still 0, so if this is run on CI it would like interpret it as a success.
👍 from me |
👍 looks good |
@MorrisJobke Please confirm if we need to port the Btrfs thing into this branch? |
Improved the command to get the ip for the swift container |
It doesn't work here directly but I need to investigate further because the startup of the container looks good (It needed a longer time to start than 60 seconds). I would accept this, if this runs fine on Jenkins. @DeepDiver1975 Can you setup the CI run for this? Thanks |
Can we move this forward ? There are at least 4 improvement PRs for SWIFT that are waiting for these tests. |
I'm fine with merging. @DeepDiver1975 The CI job shouldn't be that hard to setup, right? 😉 |
no |
Then please merge ;) |
[files_external] swift tests
I just gave this a try, but I guess someone with more knowledge about Swift should have a look.
There seem to be some authentication problems. Is this url parameter the URL for getting the authentication?
In the README of the docker container it is used like this:
(-A to specify the URL for the authentication token retrieval, -U for user and -K for the key)
Is this then the correct syntax in our files_external code?
cc @butonic @DeepDiver1975