cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nux! <...@li.nux.ro>
Subject Re: Question about the userdata availability
Date Mon, 22 Dec 2014 21:27:41 GMT
Jeff,

Awesome, I'll steal your script. :)

Regards,
Lucian

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Jeff Moody" <jeff@fifthecho.com>
> To: dev@cloudstack.apache.org
> Sent: Monday, 22 December, 2014 15:07:29
> Subject: Re: Question about the userdata availability

> I have UserData init scripts that touch a file in the filesystem for the
> VM to show that the UD has run and won't re-run on reboot.
> 
> https://github.com/fifthecho/CloudStack-Template/blob/master/templates/cloud-run-userdata-rhel.j2
> for RHEL and
> https://github.com/fifthecho/CloudStack-Template/blob/master/templates/cloud-run-userdata-debian.j2
> for Debian/Ubuntu.
> 
> On 12/22/2014 07:33 AM, Nux! wrote:
>> Antoine,
>>
>> Ok, thanks for clarifying. So it's a feature, not a bug. I'll have to deal with
>> it client-side then.
>>
>> Regards,
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>>> From: "Coetsier, Antoine" <antoine.coetsier@exoscale.ch>
>>> To: dev@cloudstack.apache.org, "sebgoa" <runseb@gmail.com>, "Lambiel, Loic"
>>> <loic.lambiel@exoscale.ch>
>>> Sent: Monday, 22 December, 2014 11:55:47
>>> Subject: Re: Question about the userdata availability
>>> Hello,
>>>
>>> The user data should stay there until the VM is destroyed, this is the
>>> expected behavior for cloud-init for CloudStack but all other stacks too.
>>>
>>> --
>>>
>>> Antoine COETSIER
>>>
>>>
>>> Le 22.12.14 11:04, « sebgoa » <runseb@gmail.com> a écrit :
>>>
>>>> Pinging Loic on this, he most likely has first hand experience with thisŠ
>>>>
>>>>
>>>> On Dec 20, 2014, at 11:58 AM, Nux! <nux@li.nux.ro> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I notice that when a VM is deployed with userdata, this userdata is
>>>>> then available at http://VR/latest/user-data indefinitely, subsequent
>>>>> reboots of the VM will get the userdata again and again.
>>>>>
>>>>> When the userdata is retrieved is there a way to let the VR know it has
>>>>> been retrieved and can be deleted/deactivated?
>>>>> Like there is the case with the root password script which send a
>>>>> "DomU_Request: saved_password" header to confirm it.
>>>>>
>>>>> Lucian
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from the Delta quadrant using Borg technology!
>>>>>
>>>>> Nux!
> >>>> www.nux.ro

Mime
View raw message