=== cpaelzer__ is now known as cpaelzer
=== vrubiolo1 is now known as vrubiolo
otuboGuys, I'm leaving for my vacation, my PR will probably get stale, but I'll work on that when I'm back (which will be Jan/4th).16:04
otuboHappy holidays to the cloud-init family. Thanks for all the reviews :) Hope we can have fun again next year.16:05
* rharper waves 16:11
blackboxswotubo: take care!17:09
* blackboxsw wonders about turning off our stale PR checker for the Holiday at end of next week :) should be pretty quiet around here17:09
powersjland everything then leave :P17:10
blackboxswgood point. I'll have falcojr do that with his new commit rights :)17:10
blackboxsw.... and have him plan to spend just a bit of time during his vacation fixing things :)17:11
blackboxswfalcojr:  landed https://github.com/canonical/pycloudlib/pull/7717:11
falcojrpush a huge change right as I leave on Friday...what could go wrong?17:41
=== ijohnson is now known as ijohnson|lunch
AU-S2SI'm working on a cloud-config to launch the stock Debian ami-070f235fd371de8e4, but I need to add a key to the admin user.18:45
AU-S2SThe admin user pre-exists in the image. Would the proper syntax/yaml be:18:45
AU-S2S  - name: admin18:45
AU-S2S    ssh_authorized_keys:18:45
AU-S2S       - < key >18:45
AU-S2SWould this then just UPDATE the user?18:45
AU-S2SSorry - This is on EC2...18:46
meenai would say: yes18:46
AU-S2S:) TY!18:47
AU-S2SCloud-init is different than ignition which is what were were using for CoreOS.  Which there was a delta document.18:49
AU-S2S^^ word - Wish.18:49
=== ijohnson|lunch is now known as ijohnson
stephan48hi, before i am searching for another hour... is there a solution for nocloud-net to pass in network config? i only see the ENI format22:05
rharperstephan48: are you attempting to pull config from remote or can you supply the nocloud datasource in the target filesystem or iso ?22:56
rharperif you are creating a nocloud iso datasource, you can put in a network-config file where you put user-data/meta-data files ... and you can use network-config v1 or v2;  note that you just need to omit the top-level 'network' key; network-config file is expected to22:58
rharperstephan48: I believe if you put up a network-config file where you're hosting your user-data/meta-data files it should fetch that as well23:00
stephan48 https://github.com/number5/cloud-init/blob/master/cloudinit/sources/DataSourceNoCloud.py#L161 and https://github.com/number5/cloud-init/blob/00dbc1447bbf8ecf611653a1af50af958ac5aeb4/cloudinit/util.py#L81423:01
stephan48sry should have mentioned that i looked into the code already and just wanted confirmation that i am not blind23:02
stephan48in the debian buster version the vendor-data is not even in(did not check backports yet)23:02
rharperoh, usually talking upstream here ...  what version is present ?23:03
stephan4820.2-2~deb10u1 in buster and buster-backports23:03
stephan48strange that its the same in both dists23:04
stephan48according to code the only source can be indeed files23:05
stephan48but mh.23:05
stephan48thinking about this I can integrate it23:05
stephan48if i ditch the nocloud for local sourcing23:06
stephan48i control the image installation after all... i am launching a debian-installer in which i do an automated full disk encrypted install23:06
stephan48i was just hoping to run the cloud-init handling inside the running os... for no apparrent reason23:07
rharpernetwork-config typically is provided at local time, to configure the networking; in some cases (datasources) we bring up ephemeral networking (ie, dhcp on an interface and attempt to fetch network config);  I thought we had discussed/worked on NoCloud doing this; but I don't see that in the code though23:07
stephan48for Hetzner its in the code23:07
stephan48with an Ephemeral APIPA23:07
stephan48cloud-init is a fascinating piece of software :)23:07
rharperhehe, indeed23:08
stephan48learned a shit ton the past week. i went the long way around... injecting cloud-init user data into hetzner which downloads a ipxe, that bootstraps the debian-installer for preparing the disks, all with a bit of pingpong between the Hetzner API, a small App on my side. still needs to bring up the vpn automatically throu23:10
stephan48so technically i could make the preseed generate a small partition with the cloud-init files for the finished VM and populate it at the end of setup from my API, but then i could aswell drop the required config directly into /etc/cloud/cloud.cfg.d/ as far as i understand23:12
stephan48theres no real benefit from nocloud at that point, or am I missing something?23:12
rharperif you can modify the target filesystem, there's no need for the partition , no23:13
rharperfor NoCloud, putting things at /var/lib/cloud/seed/nocloud-net/{user-data,meta-data,network-config}  will do the trick;23:13
stephan48ah nice23:14
rharperfor some cases where the rootfs is meant to be pristine; then storing the cloudconfig on secondary filesystem or partition is helpful23:14
stephan48usually if you restore/clone from an image23:14
stephan48you can just inject a second disk easily23:14
stephan48but then... i don't control the hypervisor... took me some time to figure out how to tell cloud-init to ignore Hetzner23:15
stephan48if not for the encrypted disk, i could go said cloning route here too23:16
stephan48but i don't like having multiple VMs with the same master keys23:16
stephan48and lets start another full reimaging run... see if i got all the last kinks out23:17
stephan48thanks! you gave me a lot of food for my thoughts, indeed the route with populating /var/lib/cloud/seed/nocloud-net/* will probably be the easiest one23:18
rharperstephan48: cool23:20
stephan48its quite fun seeing so many different software packages interacting23:20

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