Rackspace Support

[fardeem]

Any plans on bringing in Rackspace cloud files support any time soon?

[gsuess]

It was next on my list. Currently the focus is on extending the features of slingshot overall though.

But it is easy to add more storage services the slingshot. Have a look how AWS S3 and Google Cloud are implemented. Perhaps you may want to do a PR.

[fardeem]

It seems you have implemented this. Thanks. So when can we use it?

[gsuess]

Its still work in progress.

I'm implementing it according to http://docs.rackspace.com/files/api/v1/cf-devguide/content/Create_the_Form-d1a777.html, however can't figure out what they mean by "accountId". It seems that it is neither the username nor the account number.

[gsuess]

Ok the account id is the account number, but the main domain is region specific to the container.

[fardeem]

For Rackspace, is the download link of the CDN of the normal one? Or can
you configure it?

On Sun, Dec 14, 2014 at 6:36 PM, Garik Suess notifications@github.com
wrote:

Ok the account id is the account number, but the main domain is region
specific to the container.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

[fardeem]

The price with or without CDN is the same so I guess only implementing the
CDN link would be a smarter choice.

On Sun, Dec 14, 2014 at 9:55 PM, Fardeem Munir fardeem.munir@erubai.com
wrote:

For Rackspace, is the download link of the CDN of the normal one? Or can
you configure it?

On Sun, Dec 14, 2014 at 6:36 PM, Garik Suess notifications@github.com
wrote:

Ok the account id is the account number, but the main domain is region
specific to the container.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

Fardeem Munir
www.erubai.com
@awesomerubai

[gsuess]

It will be configurable. I've added CDN parameter to the directive in my working copy.

But I should standardize it across all the services.

[fardeem]

S3 and Google Cloud has a standalone CDN offering then how will you standardize it? Are you thinking about implementing the CDN features also?

[fardeem]

Also is there any way I can help with testing out the rackspace branch?

[gsuess]

S3 and Google Cloud has a standalone CDN offering then how will you standardize it? Are you thinking about implementing the CDN features also?

I was just thinking to have a cdn parameter in the directive in which you give the domain from which the download url is constructed:

Slingshot.createDirective("myFileUploads", Slingshot.S3Storage, {
  bucket: "mybucket",
  ...
  cdn: " https://d111111abcdef8.cloudfront.net"
});

If cdn is provided, download urls would be constructed as <cdn>/<key>.

Also is there any way I can help with testing out the rackspace branch?

Yes, I could use some help with getting the damn CORS set up in the easiest possible manner so that it can be described in the readme. So far I was not successful at it and that is what's holding it back.

Will push my latest stuff in a moment.

[fardeem]

Are you trying to set the CORS for the object or the container?

On Sun, Dec 21, 2014 at 6:05 PM, Garik Suess notifications@github.com
wrote:

S3 and Google Cloud has a standalone CDN offering then how will you
standardize it? Are you thinking about implementing the CDN features also?

I was just thinking to have a cdn parameter in the directive in which you
give the domain from which the download url is constructed:

Slingshot.createDirective("myFileUploads", Slingshot.S3Storage, {
bucket: "mybucket",
...
cdn: " https://d111111abcdef8.cloudfront.net"
});

If cdn is provided, download urls would be constructed as /.

Also is there any way I can help with testing out the rackspace branch?

Yes, I could use some help with getting the damn CORS set up in the
easiest possible manner so that it can be described in the readme. So far I
was not successful at it and that is what's holding it back.

Will push my latest stuff in a moment.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

[gsuess]

The container. Please check the readme on the rackspace branch. The CORS settings don't seem to be working properly.

[gsuess]

Ok the CDN stuff is done and works on S3 and Google Cloud. As for rackspace, CORS setup is still a hindrance.

[fardeem]

What stuff doesn't work with CORS? Is it absolutely necessary? Sorry if
this is a silly question but my networking skills are are not that great. :(

On Sun, Dec 21, 2014 at 7:35 PM, Garik Suess notifications@github.com
wrote:

Ok the CDN stuff is done and works on S3 and Google Cloud. As for
rackspace, CORS setup is still a hindrance.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

[gsuess]

Without CORS being properly configured on the container, the browser will refuse to upload any files to it. Setting the CORS as described on the readme and on rackspace docs, does not seem to have any effect. The CORS headers are still not sent out by rackspace.

[fardeem]

Ok, I might have something.

In the readme you are linking to the load balancer documentation. I did
some Googling and found this link:
http://docs.rackspace.com/files/api/v1/cf-devguide/content/CORS_Container_Headers-d1e1300.html
<-Looks legit

In the readme, did you get the link wrong or are you actually using the
load balancer documentation?

On Sun, Dec 21, 2014 at 8:22 PM, Garik Suess notifications@github.com
wrote:

Without CORS being properly configured on the container, the browser will
refuse to upload any files to it. Setting the CORS as described on the
readme and on rackspace docs, does not seem to have any effect. The CORS
headers are still not sent out by rackspace.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

[gsuess]

Well, yes, the link to load balancer docs is about getting the auth token, which is the same procedure there are for files. However the docs in files about retrieving the auth token are less detailed and less clear: http://docs.rackspace.com/files/api/v1/cf-devguide/content/Retrieving_Auth_Token.html which is for files, but in a better detail.

http://docs.rackspace.com/files/api/v1/cf-devguide/content/CORS_Container_Headers-d1e1300.html

this is what I used to derive the second part of the readme. Look at example 13.10.

[fardeem]

So, the auth tokens are not being generated?

On Sun, Dec 21, 2014 at 9:05 PM, Garik Suess notifications@github.com
wrote:

Well, yes, the link to load balancer docs is about getting the auth token,
which is the same procedure there are for files. However the docs in files
about retrieving the auth token are less detailed and less clear:
http://docs.rackspace.com/files/api/v1/cf-devguide/content/Retrieving_Auth_Token.html
which is for files, but in a better detail.

http://docs.rackspace.com/files/api/v1/cf-devguide/content/CORS_Container_Headers-d1e1300.html

this is what I used to derive the second part of the readme. Look at
example 13.10.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

[fardeem]

OMG THIS SOOO CONFUSING!

You could:

1. Give an actual url rather than *
2. Also in the first line, should be HEAD or POST

If everything fails, you could contact support. They're pretty nice.

On Sun, Dec 21, 2014 at 9:12 PM, Fardeem Munir fardeem.munir@erubai.com
wrote:

So, the auth tokens are not being generated?

On Sun, Dec 21, 2014 at 9:05 PM, Garik Suess notifications@github.com
wrote:

Well, yes, the link to load balancer docs is about getting the auth
token, which is the same procedure there are for files. However the docs in
files about retrieving the auth token are less detailed and less clear:
http://docs.rackspace.com/files/api/v1/cf-devguide/content/Retrieving_Auth_Token.html
which is for files, but in a better detail.

http://docs.rackspace.com/files/api/v1/cf-devguide/content/CORS_Container_Headers-d1e1300.html

this is what I used to derive the second part of the readme. Look at
example 13.10.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

Fardeem Munir
www.erubai.com
@awesomerubai

[gsuess]

You could:

1. Give an actual url rather than *

Yes I've tried that.

1. Also in the first line, should be HEAD or POST

POST might be better, because it does give feedback, but both should work and I did try both.

If everything fails, you could contact support. They're pretty nice.

That would be like the 6th time I'd be contacting them 😞, but will have to try again.

[fardeem]

I think they're away for the holidays.

All the best man, you're doing absolutely awesome with this plugin.

On Sun, Dec 21, 2014 at 9:32 PM, Garik Suess notifications@github.com
wrote:

You could:

1. Give an actual url rather than *
   Yes I've tried that.
2. Also in the first line, should be HEAD or POST POST might be
   better, because it does give feedback, but both should work and I did try
   both.

If everything fails, you could contact support. They're pretty nice.

That would be like the 6th time I'd be contacting them [image:
😞], but will have to try again.

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

Fardeem Munir
www.erubai.com
@awesomerubai

[gsuess]

Good news. Its working now. My code was mostly fine all the way along. I just messed up on setting the MetaDataKey properly.