Skip to content
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

Get RG drivers up to speed with stable interface #63

Open
jcnelson opened this issue Dec 20, 2013 · 6 comments
Open

Get RG drivers up to speed with stable interface #63

jcnelson opened this issue Dec 20, 2013 · 6 comments
Labels
Milestone

Comments

@jcnelson
Copy link
Member

We already have disk and S3 working. Make sure that we can get them installed and configured automatically.

Glacier, GStorage, Dropbox, and Box.net DO NOT WORK right now. They need to be tested and upgraded to use the latest RG driver API.

@muneeb-ali
Copy link
Collaborator

I'll look at this over the weekend and upgrade to the latest driver API.

@jcnelson
Copy link
Member Author

Take a look at the S3 driver architecture--it's already updated :)

@muneeb-ali
Copy link
Collaborator

Just looked at it and liking the new organization/interface! I noticed that the other drivers have also moved into folders with respective replica.py files etc. I'm assuming that only S3 complies right now and others need fixing. Looking at Dropbox first.

@jcnelson
Copy link
Member Author

Right. S3 works; disk should work; everything else is as you left it.

I've updated the RG wiki page to describe the new interface. Link: https://github.com/jcnelson/syndicate/wiki/Replica-Gateways

@muneeb-ali
Copy link
Collaborator

Very helpful. Thanks! I'll first push Dropbox and we can test it out to see if it complies correctly and then upgrade others in a similar way

@jcnelson
Copy link
Member Author

One aspect of this that needs attention is that the UG will need to pass driver directives to the RG.

To do this, we should add an "RG" and "RG_secret" namespace. RG.$ATTRNAME values will be passed as keyword arguments to the RG, and RG_secret.$ATTRNAME values will be encrypted with the RG's public key first before being sent.

EDIT: Now tracked in issue #105

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants