=== hjensas|afk is now known as hjensas
=== MAbeeTT2 is now known as MAbeeTT
[12:16] <holst> Hi guys! The top level document in a cloud-init file contains a lot of keys; a question I have is the order of execution of those blocks guaranteed to be done in sequence as I have defined them in the yaml?
[12:18] <holst> sorry, I am a bit new to the cloud-init terminology. What I am talking about is the "cloud-config" document type
[14:10] <falcojr> holst: no, they are not executing in the order you defined them in the cloud-config
[14:11] <falcojr> if you run `cloud-init analyze show` on your instance, that'll show the order things were executed. Order can be changed in /etc/cloud/cloud.cfg
[14:15] <falcojr> smoser: do you have a chance to take another look at https://github.com/canonical/cloud-init/pull/743 ? We still need an approval from you
[16:10] <chillysurfer> is there a command for cloud-init to output network config?
[16:18] <rharper> chillysurfer: do you mean what was found in IMDS? what it rendered?
[16:19] <chillysurfer> rharper: sorry, i should have clarified. i mean what is rendered
[16:19] <rharper> the short answer is no; we don't have such a sub-command;    I do think having it dump (what network config were you given) and show (what config did you write) would be useful
[16:20] <rharper> chillysurfer: the latter (given you have the former); is present but quite awkward to use;  cloud-init devel net-convert --help
[16:21] <rharper> used something like, devel net-convert --debug -p <input netconf file> -k <input type> -d <output directory> -D <distro> -O <renderer name>
[16:25] <chillysurfer> rharper: ok cool i'll check that out
[16:25] <chillysurfer> thanks!
[16:29] <rharper> chillysurfer: one big improvement would be for cloud-init to keep the original IMDS data in a file somewhere in /var/lib/cloud/instance/  ...  right now I don't think we log the original input in all cases;
[16:32] <chillysurfer> ah ok that makes sense
[17:03] <viks____> Odd_Bloke: sorry.. i saw your message nw... i have fixed config-drive issue in my setup and with that, cloud-init seems to be working fine..  thanks a lot for your inputs and suggestions..
[17:07] <Odd_Bloke> viks____: Great, glad to hear it!  Happy we could help. :)
[20:44] <Odd_Bloke> While working on the LXD VMs pycloudlib change, I got derailed by a test that was failing for another reason on LXD VMs: https://github.com/canonical/cloud-init/pull/801