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

pkgcloud support #258

Open
BobDickinson opened this issue Jun 14, 2016 · 2 comments
Open

pkgcloud support #258

BobDickinson opened this issue Jun 14, 2016 · 2 comments

Comments

@BobDickinson
Copy link

https://github.com/pkgcloud/pkgcloud

pkgcloud is a Node module that abstracts access to services (including storage) from different cloud providers. We used to have separate drivers in our product for Azure and AWS, and moved to pkgcloud when we needed OpenStack support (on IBM BlueMix), and now we use only pkgcloud to support all storage backends that we support (which is essentially every cloud storage platform in existence except for Joyent/Manta).

pgkcloud is the officially recommended SDK for accessing OpenStack storage from Node.js (per OpenStack.org, RackSpace, and IBM BlueMix docs). So pretty much anyone using OpenStack storage from Node.js is using pkgcloud.

I think adding Manta support to pkgcloud would be great, and is something that Joyent should want to support (it makes it much easier for someone coming from any other platform to start using Manta - if they're using pkgcloud, they literally would only have to change a few lines of config to make their app work on Manta).

I'm a maintainer of pkgcloud and would be happy to support this effort if anyone from the Manta team wanted to do it. If not, I'll do it myself (our product would benefit by being able to get rid of our custom manta driver and just using pkgcloud like we do for every other storage back end).

My biggest concern is that I can't very well drag manta into pkgcloud if it doesn't build/install cleanly (I'm looking specifically at #246 and #256).

@davepacheco
Copy link
Contributor

Thanks for that context. CC'ing @misterbisson, who may be interested in this.

As for the build issue: yes, we need to get that squared away. We haven't prioritized it because nearly all of our clients use Node 0.10 or 0.12, which don't run into the build problems. It's an unfortunate amount of work because many of the dependencies have jumped major versions, but I think we're getting some eyes on it.

@trentm
Copy link
Contributor

trentm commented Jun 29, 2016

@BobDickinson hopefully #246 and #256 aren't a blocker for you anymore.

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

No branches or pull requests

4 participants