On 06/11/12 21:33, Ian Main wrote: > On Fri, Nov 02, 2012 at 11:07:16AM +0200, [email protected] wrote: >> On 02/11/12 11:02, Michal Fojtik wrote: >>> On 11/01/2012 08:51 PM, Ian Main wrote: >>> >>> ACK. >>> >> >> hold on, am a bit confused. 'user-data' is already supported by the >> 'server personality' as documented in the API [1] ... is 'user-data' >> something different? >> > > I think it is slightly different. Basically this mimics the ec2 style > user-data where the data can be grabbed via http from some part of the > cloud engine. See eg: > > http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AESDG-chapter-instancedata.html >
indeed - now I understand. Right now the Openstack driver uses the ruby-openstack rubygem [1] (which we co-maintain) to 'talk' to the Openstack provider. In other words we only consume/interact with the 'native' Openstack (nova/swift/etc) APIs and not with the EC2 API that a given Openstack provider may expose. This means that even though you are passing 'user_data' to the server create method in your patch, this will just be ignored (as the Openstack rubygem and the Openstack API in general have no idea about 'user_data'). I have to work out the details around this in order to add what you want - for example use the appoxy/aws rubygem to talk to the ec2 endpoint of the openstack server. I opened a JIRA ticket [2] to track this so it doesn't get lost in the mailing list. Is there an urgency attached to this request (may be a bit busy with CIMI over the next few days), marios [1] https://github.com/ruby-openstack/ruby-openstack [2] https://issues.apache.org/jira/browse/DTACLOUD-358 > Since this is how cloud-init uses the data, this is how we will want to > consume it. I suspect we will have to look into this more with other > cloud providers but for now it seems to me it should be added. > > Ian >
