=== hjensas_ is now known as hjensas
[10:23] <JohnDohh> Hi all
[10:24] <JohnDohh> i m totally new in cloud init
[10:25] <JohnDohh> is it possible in cloud-config file to have both autoinstall section and user-data section ?
[10:26] <JohnDohh> when i supply user-data section i got a jsonschema.exceptions.ValidationError
[10:27] <JohnDohh> but when i test it with "cloud-init devel schema --config-file myfile" it is valid cloud-config file
[10:27] <JohnDohh> i am a bit lost
[10:38] <meena> JohnDohh: is your user-data a template?
[10:39] <JohnDohh> yes
[10:39] <meena> JohnDohh: so the template is valid, but what it generates isn't?
[10:40] <JohnDohh> exactly
[10:40] <JohnDohh> when i use only few settings as identity in autoinstall section it work well
[10:42] <meena> JohnDohh: when you retrieve the file from the server in question, how does it look there?
[10:43] <JohnDohh> with only identity datas in autoinstall section ?
[10:46] <meena> JohnDohh: well, so, cloud-init query should retrieve it from the metadata service (and fail?)
[10:47] <meena> JohnDohh: but it might be persisted as file somewhere in /var/lib/cloud-init
[10:47] <meena> or was it /var/run?
[10:47] <JohnDohh> ok let me look at it
[10:59] <JohnDohh> meena: i got files both in /var/run/cloud-init/ and /var/lib/cloud-init/
[10:59] <meena> JohnDohh: is any of them user-data.txt(i) ?
[10:59] <JohnDohh> meena: no
[10:59] <meena> well that's suspicious / sad
[11:00] <meena> i would've hoped for: yes this is broken, but here's what it actually is: 0xBAD
[11:01] <JohnDohh> my user-data file is actually sourced on cdrom/autoinstall/ dir
[11:02] <JohnDohh> some parts are read by the installation process because i can log in with the user provided in identity
[11:37] <skd> Hi, I wonder what is the status of LVM support in cloud-init? Can't find any mention of it.
[11:46] <JohnDohh> meena: btw, thanks for your help/time
[11:47] <JohnDohh> i m trying to bypass some blocking parts
[12:06] <meena> skd: define LVM support
=== vrubiolo1 is now known as vrubiolo
[19:49] <Krikke> is it possible to include files rather than specifying the content in write_files ?
[20:12] <Odd_Bloke> Krikke: Can you expand on what you mean by "include" a little?
[20:13] <Krikke> like instead of writing the content of the file into the cloud-init config file like a hobo I would just have the file there in the filesystem and would say something like `include_file(./htoprc)`
[20:15] <Odd_Bloke> Krikke: Which filesystem?  Your local filesystem, or the filesystem which cloud-init is running on?
[20:15] <Krikke> and it would parse it on it's own and the cloud init config file would look much cleaner
[20:15] <Krikke> the local filesystem
[20:15] <Krikke> before creating the image
[20:17] <Odd_Bloke> You generally pass user-data as either a string or a file to your cloud's CLI when creating an instance.  For an include like that to work, each of those clients would have to understand what it meant and how to perform the substitution correctly.
[20:17] <Odd_Bloke> Which isn't really practical, as you might imagine.
[20:18] <Odd_Bloke> What you could do, though, is use a templating language to generate your cloud-config before passing it into whichever tool you're using.
[20:18] <Krikke> that would work yeah
[20:19] <Odd_Bloke> Then it'd be `aws ec2 run-instances ... --user-data "$(my-template-thing cloud.cfg.tmpl)"` or similar.
[20:19] <Krikke> yeah I have a terraform template which sets up a kvm virtual machine and uses cloud init to configure it
[20:21] <Odd_Bloke> falcojr: Just posted my review of the integration testing stuff; FYI, that's just based on examination of the code, so I may have further comments once I've written a test with it.