I'd like to make use of cloud-init, which functions somewhat to Linode's StackScripts in that it can automatically configure a system on boot, but unlike StackScripts, cloud-init is vendor-agnostic and already in use by multiple major cloud providers. The most obvious way to do this, that several providers do, is to provide access to an AWS-style metadata service at http://169.254.269.254
, which provides information to the VM about itself, including an arbitrary blob defined by the user before starting the VM. However, there are some other options for getting this blob into the VM in such a way that cloud-init supports are outlined at http://cloudinit.readthedocs.io/en/late ... umentation
and mostly involve setting up a specific IP or domain to respond with this user data blob, or attaching a specifically named and formatted disk to the machine before boot with the user data in a particular file. If Linode created any mechanism to get such a user-defined blob of data into a VM in such a way that the VM could pull on first boot, it would be greatly appreciated. Even if cloud-init does not support it, they seem willing to accept patches for different vendor-specific metadata retrieval.
Is this something that Linode supports and I have completely missed? If not, is it something that Linode would consider supporting?