[09:29] <brtknr> what does it take to setup a dev environment for cloud init?
[09:30] <brtknr> i have just tried running tox on centos 7.5 and ubuntu 18.04 and both report plethora of error messages on the master branch
[09:30] <brtknr> centos: ERROR: InvocationError for command '/opt/bharat/cloud-init/.tox/py3/bin/python -m nose --with-timer --timer-top-n 10 --with-coverage --cover-erase --cover-branches --cover-inclusive --cover-package=cloudinit tests/unittests cloudinit' (exited with code 1)
[15:30] <blackboxsw> brtknr: as far as I recall we didn't touch tox support on centos:      try 'make ci-deps-centos; make tests'
[15:31] <smoser> brtknr: need more info on the error. full pastebin ?
[15:32] <blackboxsw> also on an ubuntu system w/ lxc one can run something like ./tools/run-container --package --source-package --unittest centos/6
[20:39] <blackboxsw> smoser: I'd like to take your suggestion to bubble up network setup into Azure.get_data as a tech-debt item, there's their poll_imds use-case  which wants to re-try dhcp attempts across IMDS metadata updates due to a user-triggered IP address change. I think this will need broader discussion with Azure and/or access to a test env that exhibits the imds metadata change to verify that a single dhcp. I'm not sure if we
[20:39] <blackboxsw> want to block  the Azure network-config-per-boot branch on that refactor or ot.
[20:40] <blackboxsw> what I'm asking is do you think https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/352660 can land as is if we have a card/topic/bug for summit next week to discuss this consolidation (and possible rework of EphemeralDCHPv4
[22:02] <smoser> blackboxsw: are you happy with branch as it is right now ?
[22:03] <smoser> i marked approve
[22:25] <blackboxsw> thanks smoser yeah, I was going to try a separate proposal for consolidation of EphemeralDHCPv4 uses for azure as the next branch so we can chat over it w/ Azure
[23:45] <smoser> blackboxsw: set 'approved'. it should land.