How to manage cloud-init on physical server?

[Green John]

Hello everyone, I have one question about cloud-init. If I install CoreOS on some common physical servers instead of vm,what's the best way to batch manage the user_data?If we ever need to update the configuration,must I login every machine and modify the user_data file or remount the config drive one by one ervery time?

[Rimas Mocevicius]

For me it works this way - sudo /usr/bin/coreos-cloudinit --from-file /home/core/user-data

[Denis Jannot]

Hi John,

You can edit the /usr/share/oem/cloud-config.yml on each machine instead of using a config drive.

Best regards,
Denis

[Kelsey Hightower]

On Wednesday, July 9, 2014 2:26:56 AM UTC-7, Green John wrote:

Hello everyone, I have one question about cloud-init. If I install CoreOS on some common physical servers instead of vm,what's the best way to batch manage the user_data?If we ever need to update the configuration,must I login every machine and modify the user_data file or remount the config drive one by one ervery time?

I wonder if something like confd would be useful for this. Basically means storing your user_data in etcd, but then confd could update the file when user_data changes and issue the "sudo /usr/bin/coreos-cloudinit --from-file /home/core/user-data" command.

[Rimas Mocevicius]

Kelsey,

Very good idea to use confd for the user_data changes, but I would extend that not only for the bare-metal machines 

but also for the cloud ones too. So we can have a consistency there.

Right now AWS, GCE, bare-metal machines all have different approaches to change cloud-config settings.