=== paride0 is now known as paride
Smithx10Hmm  I am trying to debug a config-mount issue I'm seeing in centos-801:56
Smithx10hmmm  built centos8 and centos7 images with the mi-centos-hvm repos and for some reason (still hunting) cloud-init blame shows 15.08800s (modules-config/config-mounts) for centos8 and 00.49400s (modules-config/config-mounts) for centos7  they are on different cloud-init versions01:56
Smithx10Anyway to see where we spend most of our time in config-mounts?01:57
meenaSmithx10: other than the debug logs? i dunno06:07
=== hjensas|afk is now known as hjensas
=== hjensas is now known as hjensas|afk
Odd_Blokemeena: Yeah, I wasn't sure how to ask them either.13:59
=== ahosmanMSFT_ is now known as ahosmanMSFT
=== mskalka_ is now known as mskalka
=== andrein_ is now known as andrein
=== logan_ is now known as logan-
=== philroche_ is now known as philroche
=== jdoss_ is now known as jdoss
Odd_BlokeSmithx10: You can look in /var/log/cloud-init.log as meena suggested, search for "Running module mounts" in there.14:00
meenaOdd_Bloke: we could start with twitter, which is my first choice, when there's no other choice14:03
Odd_Blokemeena: I won't stop you. ;)14:07
otuboOdd_Bloke: would you ahve time to take a final look at my PR? https://github.com/canonical/cloud-init/pull/54114:10
otuboOdd_Bloke: I think it's all fixed by now :)14:10
Odd_Blokeotubo: Sure thing, looking now!14:10
Odd_Blokeotubo: Just one small thought left, thanks for all the back and forth!14:55
otuboOdd_Bloke: I think it's reasonable to change that to INFO. Just pushed the change. Thanks for the review! :-)15:22
=== hjensas|afk is now known as hjensas
Odd_Blokeotubo: Merged. \o/16:00
meenaOdd_Bloke: https://twitter.com/hirojin/status/130591461622935961917:03
Odd_BlokeNow we play the waiting game.17:10
meenaOdd_Bloke: isn't that all we ever do? (and then we die)18:48
Odd_Blokeotubo: I'm looking at https://bugs.launchpad.net/cloud-init/+bug/1894837 and it's not 100% clear to me what the path forward is.  In the Ubuntu world, we use NM for desktops, but not at all for servers, so I don't really have background on how its configured without nm-applet, let alone via sysconfig.  Do you think we should remove that defaulting?  What impact might that have?19:31
ubot5Ubuntu bug 1894837 in cloud-init "RHEL8 ipv4 IPs not coming up when NM_CONTROLLED=False" [Undecided,New]19:31
=== tds5 is now known as tds
flingWhat is needed for cloud-init to work for lxd profiles? runcmd and packages and other sub entries of user.user-data in container config/profile21:20
blackboxswfling: something like this https://discuss.linuxcontainers.org/t/running-virtual-machines-with-lxd-4-0/751921:20
blackboxswgenerally you can create a lxd profile locally .... mine currently looks like this21:21
flingIt is just unclear for me what steps need to be performed.21:24
flingFirst I install cloud-init on the same host where I have lxd running right?21:24
flingThen I just add specific entries under 'user.user-data: |' to the config?21:25
flingAre there any other steps?21:25
Odd_Blokefling: cloud-init runs within the container, not outside it; your container image will need to include cloud-init for it to run.21:26
blackboxswd'oh I misread lxd --vms in the request fling: https://paste.ubuntu.com/p/N8cDrVj9wq/21:27
Odd_BlokeNote that many (all?) of the images from the images: remote do not include cloud-init; if you're using Ubuntu then the images from the ubuntu: remote do.21:27
blackboxswthat's how I setup lxd vm enabled profiles and launch a vm (not lxc) container21:27
Odd_BlokeWell, it's true that VM images would need cloud-init inside them, it's just more unusual to exclude cloud-init from VM images.21:27
blackboxswright and to Odd_Bloke's point, standard/supports cloud-images are available with cloud-init baked into those images. they can be launched with lxc launch ubuntu-daily:<xenial|bionic|focal|etc>....   most images aliases that contain cloud-init would be presented here https://us.images.linuxcontainers.org/21:29
blackboxswsorry for not answering the actual question you had above21:29
Odd_BlokeSystem container images don't _need_ it because you don't need to configure anything inside the container to be able to gain access (because you generally have direct access to the "hypervisor").21:29
Odd_Blokeblackboxsw: The ubuntu: remote is preferred for production use cases; the ubuntu-daily: images don't receive any testing before publication.21:30
flingThen what is needed for cloud init to perform stuff from user.user-data: ?21:30
Odd_Blokefling: I believe user.user-data needs to be a string that starts with "#cloud-config", it's not just nested YAML; perhaps that's tripping you up?21:31
flingOk, fine.21:31
blackboxswcorrect fling. as long  as cloud-init package is living in the container21:31
blackboxswsudo cloud-init query userdata > ud.yaml; cloud-init devel schema -c ud.yaml --annotate;21:32
blackboxsw^ perform this cmd inside your container and it'll tell you whether the user-data you provided was valid for cloud-init21:32
Odd_BlokeWe should really just make that a command.21:32
blackboxswyeah totally21:32
Odd_Bloke`cloud-init devel schema --system` or somesuch.21:32
blackboxswmaybe just `cloud-init devel schema validate`?21:32
blackboxsweven better21:32
blackboxswthat's a couple liner at nest21:33
flingHow is 'user.user-data:' entry getting to cloud-init from a container config?21:33
Odd_Blokefling: lxd writes it into a seed file in the container filesystem before starting the container.21:33
blackboxswlxc dumps it in /var/lib/cloud/seed/nocloud-net/user-data21:33
blackboxswand cloud-init NoCloud datasource knows how to read that yaml file21:34
flingso user.user-data is some kind of a special name? :D21:34
blackboxswon most cloud platforms it's just user-data.... and each cloud (lxc included) provides that data in an unique location/format21:34
blackboxswuser-data meta-data and vendor-data are kindof cloud-init special names for different layers of configuration information21:35
blackboxswlxc let's you provide your own user.user-data and user.meta-data etc21:35
Odd_Blokeuser.meta-data is appended to the metadata that lxd needs to provide for things to work as it expects (e.g. hostname, instance-id).21:37
flingmeaning lxd just performs this dump when it finds user.user-data: in the config right?21:37
Odd_BlokeAnd by "e.g." I guess I mean "those are the two things". :p21:37
Odd_BlokeCorrect, it writes that string to that file; cloud-init runs inside the container, finds that seed and processes it.21:38
blackboxswmore info here too https://cloudinit.readthedocs.io/en/latest/topics/instancedata.html21:38
blackboxswjust on data types that cloud-init considers21:38
blackboxswok fine. lies about a couple liner https://paste.ubuntu.com/p/wYn369B9K5/ without unit test fixes.22:07
blackboxswbrain break over, I might put up that branch tomorrow22:07
blackboxswmeh couldn't help it https://github.com/canonical/cloud-init/pull/57522:43
blackboxswjohnsonshi: if you have time to resolve the minor comments on https://github.com/canonical/cloud-init/pull/549/files we can land that22:45
blackboxsw(like dropping the unit test and adding a comment about an example vm flavors that exemplifies mlx5_core vs mlx4_core driver22:46
johnsonshiblackboxsw: Sure! Thanks for the ping!22:46
blackboxswno worries22:46

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!