[07:23] <amitprakash> Hi, would it be possible to use cloud-init to populate specific conf.d files?
[13:31] <amitprakash> Hi, would it be possible to use cloud-init to populate specific conf.d files?
[13:35] <jrwren> amitprakash: i don't know what that means. There is a write_files module which can write any file on the system.
[13:38] <amitprakash> jrwren, aight thanks :)
[13:39] <amitprakash> jrwren, what if I want to pass things link nproc to write_files ?
[13:39] <amitprakash> specifically, I wish to specify number of cpus, ram available etc
[13:40] <jrwren> I don't understand that. If you write it to a file, it will work.
[13:42] <amitprakash> jrwren, let me rephrase, in the content section for write_files, how do I generate such values on the fly?
[13:44] <amitprakash> Because from what I am reading content can contain static strings
[13:47] <jrwren> You do not, out of the box.
[13:47] <jrwren> I have, in the past, made my own template system to generate the cloud config and launch instances.
[13:48] <amitprakash> jrwren, any documentation against how I can do the same?
[13:48] <amitprakash> Or if you can share your work instead?
[13:50] <jrwren> amitprakash: the work i did was not opensource, but it was only python Template strings.
[13:51] <amitprakash> aight, thanks. I'll google around for similar approaches :)
[13:52] <rharper> amitprakash: you can always write a shell script to do what you want, (fetch nprocs and write out your conf files) and then inject the script via write-files and call it via runcmd
[13:54] <rharper> smoser: when you get a change, I'd like to discuss https://bugs.launchpad.net/cloud-init/+bug/1619423 re: Ubuntu-core
[14:02] <smoser> rharper, yeah.
[14:05] <rharper> *chance*
[14:05]  * rharper drinks more coffee
[14:07] <smoser> rharper, https://hangouts.google.com/hangouts/_/canonical.com/hangout-smoser
[14:07] <rharper> k
[14:22] <smoser> http://paste.ubuntu.com/23338848/
[14:23] <smoser> http://paste.ubuntu.com/23338850/
[14:24] <smoser> http://paste.ubuntu.com/23338852/