Rob Thijssen [:grenade (EET/UTC+0300)] Assignee
	Description • 9 years ago

The Puppet installed nxlog instances contain configuration pointing to the log aggregator for the AWS site where the golden ami was created. This needs to be changed at first boot for the spot instance. Most likely using the userdata mechanism.

	Rob Thijssen [:grenade (EET/UTC+0300)] Assignee
	Comment 1 • 9 years ago

Mark, do you know if Windows spot instances will try to run the same userdata script as golden? Do they use the same cloud-tools configs (https://github.com/mozilla/build-cloud-tools/blob/master/configs/b-2008, https://github.com/mozilla/build-cloud-tools/blob/master/configs/try-2008) as golden, or are they configured elsewhere?

I'm wondering where to put the nxlog config adjustment script.

	Mark Cornmesser [:markco] OOO 2024/04/15
	Comment 2 • 9 years ago

They will not be the same. The spot instance userdata has not been worked out as of yet.

	Rob Thijssen [:grenade (EET/UTC+0300)] Assignee
	Comment 3 • 9 years ago

Further to discussion about where to put the nxlog config adjustment script, I have not seen any way in which ec2config could be used for this. From what I can see, ec2config tasks are predefined by Amazon and don't contain a mechanism (other than userdata) for executing a custom task. As far as I can tell, the only way to run an arbitrary task is through userdata. I think that spot instances will therefore need their own configs and userdata scripts which differ from those used by the golden ami creation process.

	Rob Thijssen [:grenade (EET/UTC+0300)] Assignee
	Comment 4 • 9 years ago

Fixed in PR: https://github.com/mozilla/build-cloud-tools/pull/93