Idea #7454
Updated by Peter Amstutz over 8 years ago
Currently we use CustomScriptForLinux to provision compute nodes. However, for some reason (we have not been able to get to the root cause) it fails to run the script reliably. To get around this we are using a cron job hack which re-runs CustomScriptForLinux until it succeeds. It would be better to solve the problem a different way. It turns out there is actually a simpler way to put a small file onto a newly provisioned node than what we have been trying to do with CustomScriptForLinux. Somehow I overlooked this feature before or I would have implemented this way originally. https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-how-to-inject-custom-data/ 1) Add custom data support to libcloud (done) 2) Update node manager to put the ping URL command and other information into custom data (done) 3) in /etc/waagent.conf: <pre> Restore the update script/cron job that we use on AWS and GCP for Provisioning.Enabled=y Provisioning.DecodeCustomData=y provisioning, and add support for reading the ping URL from Provisioning.ExecuteCustomData=y </pre> /var/lib/waagent/CustomData 4) Build a new image.