[20:16] <rharper> powersj: can I run ci against a cloud-init in a PPA  easily ?
[20:37] <powersj> Uhh no
[20:38] <rharper> bummer
[20:38] <powersj> Add a card ;)
[20:38] <rharper> hehe
[20:38] <powersj> I'm sure it wouldn't take much
[20:39] <rharper> k
[20:39] <powersj> Basically pull source for it and go
[20:39]  * rharper is now upgrading from azure panel to cli now; since you can;t multi-nic in the portal 
[21:08] <dpb1> rharper: so you can do two nics, but not sriov ones
[21:09] <rharper> yeah, panel still shows nothing advanced, but I'm testing dual nics in any case
[21:09]  * dpb1 nods
[21:15] <Majost> I am seeing an unexpected behavior for the chef  cloud-config where it installs chef correctly, but doesn't appear to run the chef-client
[21:16] <Majost> All the docs I have seen suggest that adding a runcmd to do this is not needed
[21:23] <rharper> Majost: if you can, getting /var/log/cloud-init* and your user-data together; we can look at what's going on
[21:25] <rharper> dpb1: unexpectedly, adding a second nic and starting the VM back up changes the public ip the instance had ;   going to wipe cloud-init data and see what a firstboot on a dual nic setup does (not sure how they handle the double dhclient route issue)
[21:26] <dpb1> rharper: but you aren't bonding
[21:26] <rharper> no, just testing normal things in azure with the new code
[21:26] <dpb1> k
[21:27] <dpb1> that's odd indeed
[21:27] <dpb1> though admitedly, I'm not sure what I have tested in azure wrt two nics before this
[21:27] <rharper> testing the "don't break existing networking"