> > There is no SecurityGroup in RackSpace. > > If the global firewaller mode isn't enough to work around this, we > probably need a disabled firewaller mode too. What did you do for > this?
I just comment the security groups code for the test. > > The catalog returned with the token by Keystone had: > > > > * a different tenantid for object-store and compute > > That's odd. What impact did this actually have? I get an error that object-store or compute service was not found depending on which one I choose. I have attached the json response if you want to see. > > * The compute service twice (v1.0, v2) > > We should pick out the right version in goose, lp:1218218. > > > The retry-after header is a complete date/time string instead of the > > expected float. > > Apparently valid, lp:1218223. > > <http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.37> > > > In RackSpace's Ubuntu images cloud-init is not installed by default > > so you have to create a custom image and bootrap with it. > > For that you need to create public container (cdn) with the metadata. > > > > I discovered that the userdata field doesn't exist in the API but there > > is a field named "personality" that is doing more or less the same thing. > > It's not the same thing really, but can be used to do file injection. > However, without the metadata service, don't you still need to tell > cloud-init about the alternative data source? I'm not sure, I found that blog post and was planning trying that: http://andyleonard.com/2011/11/28/deploying-ubuntu-on-rackspace-using-fog-and-cloud-init/ > > So I've put the user-data in the personnality field but now > > I'm getting a 413 error (Request Entity Too Large). > > Did the cloud-config get gzip compressed, or was it given as raw yaml? I use what juju-core is sending by default. base64 encoded. > > Martin >
r.json
Description: application/json
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
