-
Notifications
You must be signed in to change notification settings - Fork 29
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
add delete home to the storage provider #95
Conversation
This API call should be part of an Admin API, we have discussed it in the past and now with this need arising is the right moment to create it. @C0rby can you add this new API here: |
Cool. |
thanks for the clarification, I meant |
b9c5fb8
to
f671ad5
Compare
f671ad5
to
49b3aed
Compare
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.
@C0rby I've added some comments, overall looks pretty good.
4475d7d
to
f8e2003
Compare
f8e2003
to
77d64c9
Compare
I rebased the branch. |
@C0rby could you rebase please? Would be nice to get this in. :-) |
@C0rby are you online this week? Can you rebase this and we can try to push it along. There are things that depend on this that are waiting. |
77d64c9
to
07ef96d
Compare
@C0rby it LGTM, could we get @ishank011 to have another pair of eyes? :) |
@C0rby looks good but how will |
I see your point. |
As discussed at the CS3 we should pick a more generic name for Other options were CreateTree, CreateSpace, CreateSubTree, and CreateRoot but they are either too abstract / graph theory influenced (anything with tree or root) or would invent a new term (space). Storage space seems to be a good middle ground. Furthermore it can be used not only for user homes but also other spaces eg. project or group spaces. The method needs an owner (which can be a user or a group), optionally quota and opaque data as usual. cc @ishank011 @C0rby |
@jfd, wouldn't CreateStorageSpace also need a |
CreateStorageSpace where? In the gateway? there it would need an indication of which storage should create the space. might be done by path or by storageid. In a storage provider? No, It is up to the storage provider to determine where to put the new root of the storeage. In the storage registry? Yes, it needs to know where to mount a storage space. Not only a strorage provitder. But this is a bigger change. For now, I would limit this change to the StorageProvider Api in the context of the UserProvisioning api: the Gateway can determine the responsible storage provider by calling |
@C0rby While you are at it could you also add an |
blocks owncloud/ocis#1290 |
The storage space api should make it possible to provision and deprovision spaces ('home', 'shares', 'project' etc...) for users. Using this api we should also be able to deprovision spacess Co-authored-by: Jörn Friedrich Dreyer <[email protected]>
07ef96d
to
064a93b
Compare
@ishank011 @labkode, @butonic and I now implemented the storage API how we think it should be. |
@C0rby is there a PR to |
@phil-davis, not yet. We still have to do that. It will most likely happen within the coming sprint. |
Added a delete home method to the storage provider to be able to clean up when removing a user.