[01:38] <smoser> blackboxsw, if you're still around, we missed a template on bug 1701097
[01:38] <smoser> i'll get it tomorrow if not
[01:38] <smoser> :-(
[01:38] <smoser> later
[09:19] <mbwe> thanks smoser well overhere its now morning
[09:19] <mbwe> Europe overhere
[13:09] <smoser> mbwe, you all keep funny time.
[15:18] <rharper> powersj: how were you getting that negative value in the cloud-init analyze lxc run?  I'm trying to reproduce here
[15:19] <powersj> rharper: let me look
[15:21] <rharper> I just forgot that cloud-init.log has subsecond timestamps now, so it's easier to just cat cloud-init.log | cloudinit-analyze show -i -     versus those journalctl ones
[15:21] <powersj> rharper: Ah! It was when I was doing my demo script, which uses the following user data: https://github.com/powersj/debconf17/blob/master/demo/user_data.yaml which is setting the timezone to something that isn't correct.
[15:21] <rharper> oh!
[15:21] <rharper> yes
[15:21] <powersj> it will be correct in couple days ;)
[15:22] <rharper> lol
[15:27] <smoser> powersj, rharper well, analize is doing bda math then
[15:27] <smoser> or ignoring time zone
[15:27] <smoser> er... *not* ignoring time zeon.
[15:27] <smoser> zeon!
[15:27] <smoser> it should be doing any time operations on utc.
[15:27] <smoser> or some constant
[15:28] <rharper> smoser: we get timestamps from python logging in cloud-init.log
[15:28] <rharper> when you modify the timezone; logging doesn't know that
[15:31] <smoser> hm...
[15:32] <smoser> we'd then need to chage theoutput to log with timezone information. i can't imagine that python logging is simply broken across time zone changes
[15:32] <smoser> surely it can detect that
[15:39] <rharper> looks like we;'d need to force logging to use gmt
[18:07] <blackboxsw> rharper: smoser https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/328241 all comments addressed. performing one more test run on aws now
[18:13] <blackboxsw> validatred on aws
[18:16] <smoser> blackboxsw, your comment
[18:16] <smoser> "Perform dhcp discovery on nic if it is not already up."
[18:16] <smoser> i dont think that is true
[18:16] <smoser> "if the nic is down, run dhclient"
[18:16] <smoser> where is "if" ?
[18:16] <smoser> i think it just runs dhclient
[18:17] <blackboxsw> ahh fixing that
[18:18] <blackboxsw> right that was an earlier iteration on this branch
[18:21] <smoser> blackboxsw, the other comment is the bit in DataSourceEc2.py
[18:21] <smoser> dhcp_leases = dhcp.maybe_perform_dhcp_discovery()
[18:22] <smoser> move that out to anoterh method maybe ?
[18:23] <smoser> ipv4_info = dhcp.maybe_dhcp_and_get_ipv4_info()
[18:23] <smoser> if not ipv4_info:
[18:23] <smoser>   return False
[18:24] <smoser> with net.EphemeralIPv4Network(**ipv4_info):
[18:24] <smoser>   ...
[18:30] <blackboxsw> :w
[18:30] <blackboxsw> whoops mid-fixing it
[18:49] <smoser> blackboxsw, have a minute ?
[18:49] <smoser> http://c.brickies.net/hangout
[18:49] <blackboxsw> sure, pushed latest changes so we are talking about the same thing
[20:12] <blackboxsw> smoser: fixes pushed testing on aws now
[20:24] <smoser> there are merge conflicts tehre.
[20:24] <smoser> you should rebase
[20:24] <smoser> other than that i think its probably sane
[21:33] <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+ref/feature/analyze
[21:34] <smoser> and i gots to go. ^ that is the analyze work that i did, thats all though.
[21:34] <blackboxsw> ok will shepherd it in next week
[21:34] <blackboxsw> have a good one
[21:35] <rharper> thanks
[21:37] <powersj> thanks smoser
[21:38] <smoser> its no where near done.. just initil thing.