[09:10] <Odd_Bloke> smoser: I can't remember where we said it would make sense to put the certificates that WALinuxAgentShim spits out on disk.  Can you remind me?
[12:51] <smoser> htey're per-instance, right 
[12:52] <smoser> i think we just leave them where they were right now (/var/lib/walinux/ or whatever)
[12:52] <smoser> but i guess makes as much sense to move them to /var/lib/cloud/instance/data or something. 
[12:56] <Odd_Bloke> smoser: Yeah, I'd prefer not to write them out to the walinuxagent path because we aren't holding ourselves to the same disk format (e.g. we aren't writing out some files that walinuxagent does, because we're just using them in-memory).
[12:56] <Odd_Bloke> And not using a temporary directory makes life much easier, because then I don't have to care about clean-up.
[12:56] <Odd_Bloke> (Or carrying the location of the temporary directory around)
[12:56] <Odd_Bloke> smoser: Having said that, though, some of this happens before we have an instance-id; will /var/lib/cloud/instance even be in place during the data source run?
[12:57] <smoser> you're right. it wouldnt be ther.e
[12:57] <smoser> so what are you writing out ? i'm confused.
[12:58] <Odd_Bloke> smoser: All of the certificate stuff is too involved to do in-memory, so we shell out to openssl; at the moment we store the files it operates on and produces in a temporary directory.
[12:59] <Odd_Bloke> But it would be good to have them somewhere more permanent for (a) debugging/analysis, and (b) avoiding temporary file handling/cleanup in the code.
[13:00] <Odd_Bloke> If there isn't a good place to put them, I can stick with the tmpdir approach.
[13:03] <smoser> well, i htink that since you dont have a instance-dir yet, you dont have a good place for per-instance stuff. i tihnk tempdir seems the best path. 
[13:03] <Odd_Bloke> Cool.
[13:41] <Odd_Bloke> smoser: Can you remind me what the DHCP bounce in Azure is intended to achieve?  Is it to get the fabric to recognise the host?
[13:41] <Odd_Bloke> smoser: (I'm trying to work out if I've replaced what it does with the WALinuxAgentShim work)
[13:43] <smoser> Odd_Bloke, i think its to "publish" the hostname.
[15:21] <smoser> harlowja, https://etherpad.mozilla.org/cloud-init-roadmap
[15:22] <smoser> that was claudiopoppa and my work last week to try to get something down as targets
[17:57] <tmclaugh[work]> Hi, is bootcmd run before networking is fully setup?
[17:57] <tmclaugh[work]> Trying to ping a host in out environment before talking to Puppet
[18:10] <smoser> tmclaugh[work], not guaranteed to have network up
[18:10] <smoser> if you're using a local datasource
[18:10] <smoser> if you have a network datasource you will have network
[18:11] <smoser> (because thats how you found the datasource)
[18:14] <harlowja> smoser cool
[18:14] <harlowja> smoser i start to wonder how much of systemd is doing all this same stuff (configuring networks...)
[18:14]  * harlowja doesn't really know, i just thought it started to have similar stuff
[18:14] <harlowja> maybe we should rename this to cloud-init-systemF (F is after d)
[18:15] <harlowja> it freakin has a 'systemd-timesyncd' woah, lol
[18:15] <harlowja> https://wiki.archlinux.org/index.php/Systemd-networkd ( smoser ) ?
[18:15] <harlowja> so i am starting to wonder if cloudinitd just tells systemd to do things... ?
[18:17] <smoser> harlowja, that is 'networkd' which is part of systemd
[18:17] <smoser> cloud-init will just kick networkd into submission
[18:21] <smoser> harlowja, we're moving to networkd for ubuntu server in 15.10
[18:30] <harlowja> smoser cool beans
[18:30] <harlowja> ya, i guess everyone will be eventually
[18:30] <harlowja> *all linux variants
[18:30] <harlowja> although who knows maybe windows doing all that open source stuff it will also adopt systemd, lol
[18:30] <harlowja> *microsoft doing all that open source stuff (not windows)
[18:30] <smoser> :)
[18:30] <smoser> its gonna be great.
[18:30] <smoser> unicorns and rainbows everwhere.
[18:39] <tmclaugh[work]> smoser: sorry, was in a meeting.
[18:39] <tmclaugh[work]> This is an AWS host with te data attached to the magic URL
[18:42] <smoser> yeah. then network should be up at that point
[18:42] <smoser> all network interfaces desscribed as 'auto' in /etc/network/interfaces should be up
[18:48] <harlowja> smoser unicorns, woot!