> Why does Rackspace's API use "Keystone" auth instead of just API tokens or Oauth like everyone else? We would have to create a special Rackspace auth system just to support Rackspace with our service. Everyone else in the world uses Oauth or API tokens, or passwords which works a lot like API tokens, but Rackspace uses this crazy system nobody else in the world uses that requires refreshing tokens.

Actually, Token-based auth is quite common, as well as token refreshes. This is pretty standard for cloud provider APIs for compute, storage, etc. Amazon, Rackspace, Google and others all use the account -> API Key model. This actually uses API tokens which is the industry and OpenStack standard.

For OAuth - we've discussed this, there is a cloud partner in the cloud tools market place which does this. This isn't the first time I've gotten this request, so I'm going to pass it to the product teams as well.

So you may want to consider a way that the discount can be applied on any new services signed up for in the existing cloud panel.

While it's trivial for someone to sign up for a new account, it would make more sense (for your tracking purposes) to have people just enable the discount (once again on additional services) in an existing RS cloud account.

Besides would like to just manage everything from the same account generally.

Actually I'm talking about what you refer to as edge purge (http://www.rackspace.com/blog/cloud-files-cdn-gets-edge-purg...) and AWS refers to as invalidations.

Thanks!