Open Stack

Hi, 

Thanks for your answer Anton. 

Actually the images we have required to  fetch/enable some components while booting the instance. In order to do that, we are using some scripts. ISO contains those scripts. We have mount the iso to the image at boot time by defining it into the image config file. 

The bottom line is that we need to run some scripts. Can you please give me an example how do I run the scripts at the boot time in Openstack?  And also where should I place those scripts? 

Regards..
Salman. 

Salman Toor
salman.toor at it.uu.se



On Nov 19, 2012, at 7:51 PM, Anton Haldin wrote:

> Hi Salman 
> 
> I'm not sure if I understand your question.
> If you want to launch instances by using your image , you need to load it in glance (storage service for images) 
> 
> If you want to push some data to the new instance ,  you can use "user data" parameter with "nova boot" command .Value of this parameter would be pushed into instance by file injection.  You can also use meta data with "nova boot" command. Values of meta data ( tags) would be available in instance through metadata service.
> 
> 
> Anton.
> 
> On Mon, Nov 19, 2012 at 5:06 PM, Salman Toor <salman.toor at it.uu.se> wrote:
> Hi, 
> 
> I have created a user-data.iso (only contains startup script) and I am using KVM in my setup. Right now I have tested my user-data.iso with virsh tool and now I want to use that iso file everytime I boot my instance in openstack. I read that there is a service call metadata service. Can somebody guide me how do I upload/use my iso file at boot time with the instances in openstack?
> 
> Thanks in advance. 
> 
> Regards 
> Salman.
> 
> 
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20121120/c5c2acc5/attachment.html>