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
rgw: implement support for creating swift sub-users via the user CR #13808
base: master
Are you sure you want to change the base?
Conversation
a6ac45b
to
198b47b
Compare
Related to #13807 : is either of these PRs needed as a basis for the other? |
They don't strictly depend on each other. Each will do what it's meant to do on its own. However, creating sub-users probably isn't that useful without also being able to configure Swift. |
I just realized I missed something in this one, so I'm converting it back to a Draft for now. |
This pull request has merge conflicts that must be resolved before it can be merged. @Lykos153 please rebase it. https://rook.io/docs/rook/latest/Contributing/development-flow/#updating-your-fork |
1 similar comment
This pull request has merge conflicts that must be resolved before it can be merged. @Lykos153 please rebase it. https://rook.io/docs/rook/latest/Contributing/development-flow/#updating-your-fork |
The design document for the swift and keystone integration contains incorrectly numbered annotations. Thie commit fixes the numeration of the annotations. Additionally some minor wording changes are made. Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
For the specification see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
* The parameter lists of the API call have changes, as parameters ignored by the RGW Admin Ops API are no longer serialized, therefore the mock has to be adapted. * There is now validation for the user keys that are passed to the User get API, therefore things failed when we had empty keys in our User proxy object. Co-authored-by: Jan Klippel <jan.klippel@uhurutec.com> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
For the specification see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> Co-authored-by: Jan Klippel <jan.klippel@uhurutec.com> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
This pull request has merge conflicts that must be resolved before it can be merged. @Lykos153 please rebase it. https://rook.io/docs/rook/latest/Contributing/development-flow/#updating-your-fork |
For the specification see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
For the specification see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
For the specification of the swift and keystone integration see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
ba29b63
to
07443af
Compare
Key @Lykos153 this is great work! We are interested in speeding this PR up as well, can you address review comments or let us know if we can help you. Thanks! |
This PR implements using k8s custom resources to create swift sub-users as described in the already existing design document swift-and-keystone-integration (see #9444 for the design request and #9088 for the general issue).
The design document describes another feature namely the authentication using keystone of swift and s3 which is implemented in a #13807.
Checklist: