I’m testing the new Vmware guestinfo functionality in v1.1.0 but it’s a bit unclear to me what I’m actually capable to do with it.
My dream is to run RancherOS on disk less virtual machines, booting the rancheros.iso. I would also prefer to have only one cloud config to administer. It could be a shell script that behaves differently depending on the machine running it. Putting such config in guestinfo.cloud-init.config.url were my initial idea, but since no network device has been configured at this point in the boot process this won’t work. My next alternative would be to put it in guestinfo.cloud-init.config.data. But then it would need some meta data to be able to differentiate our machines. Do you have any suggestion of accessible meta data one could use? My next obstacle would be the file system. My cloud-init script seems unable to write to the file system. Is a guestinfo.cloud-init.config.data script executed before even the file system has been created?
I don’t have any answers for you yet, and I have a different use case I’m trying to work through.
I want to use RancherOS as the base operating system for a product shipped as a virtual appliance on VMware.
I need someway to configure the appliance at deployment not install time - I’m currently thinking that using the ovf properties and cloud configuration is the way to go, but I’m still working out what needs to be done in the os to extract the data into application / environment configuration for my software to “see”.
that script uses machine to set the guestinfo IP and cloud-init, and then is the same script that is the guestinfo cloud-init.
note that there is a bug in docker-machine where it seems to only manage to send the cloud-init as an encoded text if its specified as a relative path - and ~ doesn’t work either.
I accomplished what I wanted by adding the guestinfo hostname+interface+dns settings in Vmware Vsphere, and putting the following script (encoded to base64) in guestinfo.cloud-init.config.data.