[13:39] <dmsimard> Hi ! I was looking to get an OpenStack environment going with CentOS guests with config-drive provided network configuration. It looks like I would need the RHEL version of http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/1189?start_revid=1189
[13:40] <dmsimard> harlowja: ^ I was told you might be able to help ?
[14:56] <smoser> harlowja, ^
[16:32] <harlowja> sup
[16:56] <smoser> harlowja, dmsimard wants you to fix centos for network config
[16:56] <smoser> and config drive :)
[16:56] <harlowja> :-P
[16:56] <harlowja> ya, damn
[16:56] <harlowja> lol
[16:56] <harlowja> i knew it, ha
[16:56] <dmsimard> oh hai
[16:56] <dmsimard> well, I'm willing to help and all
[16:57] <dmsimard> friend here mgagne pointed me to an (older?) iteration of that implementation I guess, https://github.com/mgagne/cloud-init-fedora-pkg/blob/epel7/cloud-init-0.7.5-network-info-support.patch
[16:58] <dmsimard> But the way it was just merged (three weeks ago, talk about timing) looks similar yet different
[16:58] <mgagne> harlowja: original version here: https://github.com/racker/cloud-init-fedora-pkg
[16:59] <dmsimard> cloud-init will be in core OS packages in RHEL 7.3 and CentOS 7.3 this year so it'd be great to have a version cut with that support baked in
[17:01] <harlowja> mgagne dmsimard ya, i'd like to have that in also
[17:01] <harlowja> do u guys want to work on that, or should i?
[17:01] <harlowja> i moved companies recently, so i might have to do some of the legal CCLA crap again smoser
[17:01] <harlowja> i gotta aks on that
[17:01] <harlowja> *ask
[17:02] <larsks> harlowja: which goes back to my question yesterday asking about a 0.7.7 release... :)
[17:02] <dmsimard> I can help testing but I'm not knowledgeable enough about those bits to do it myself
[17:02] <harlowja> smoser is mr.release ;)
[17:02] <harlowja> he's gonna do git soon also
[17:02] <harlowja> lol
[17:02] <harlowja> i just know it
[17:02] <harlowja> i believe
[17:02] <harlowja> i'll send smoser a cookie if he does git
[17:02] <harlowja> lol
[17:03] <larsks> I would contribute to that cookie fund.
[17:04] <harlowja> :)
[17:07] <smoser> harlowja, git will come
[17:07] <smoser> git willi come
[17:07] <harlowja> smoser tommorow?
[17:07] <harlowja> lol
[17:07] <harlowja> today?
[17:07] <smoser> after 16.04 releases (next thursday)... not before.
[17:07] <harlowja> 16.04
[17:07] <harlowja> damn it
[17:08] <harlowja> another LTS
[17:08] <harlowja> i just reinstalled 14.04
[17:08] <harlowja> lol
[17:08] <smoser> if spandhe joins maybe we can convince her to do it.
[17:08] <smoser> she's still yahoo, right ?
[17:08] <harlowja> ya
[17:09] <harlowja> dmsimard mgagne if u guys want to get a patch working
[17:09] <harlowja>  https://github.com/mgagne/cloud-init-fedora-pkg/blob/epel7/cloud-init-0.7.5-network-info-support.patch i guess ?
[17:09] <harlowja> just maybe a few more tests ?
[17:09] <harlowja> cause that patch doesn't seem to have to many
[17:10] <harlowja> then maybe by the time those tests happen, smoser will have git
[17:10] <harlowja> and we can all have cookies
[17:11] <harlowja> i believe!
[17:11] <harlowja> lol
[17:13] <mgagne> harlowja: let me check if have a more up2date version
[17:13] <harlowja> mgagne  np
[17:13] <mgagne> because we are reading network_info.json now, not vendor_data.json
[17:13] <harlowja> right
[17:14] <harlowja> that's fine, some network_info.json test cases, that give a sample network_info.json in and check the output would be cool
[17:14] <harlowja> *and/or multiple sample inputs ---> check the outputs
[17:15] <mgagne> that's scary, I think I fixed it for debian but not rhel
[17:17] <mgagne> harlowja: for trusty, for what it's worth: https://gist.github.com/mgagne/46748012efa1ff3389b380a25bedb14d
[17:17] <harlowja> cool, ya, tests for these would be nice ;)
[17:17] <harlowja> like a bunch of input data files and expected output files
[17:18] <harlowja> for debian and ubuntu and redhat and ...
[17:18] <harlowja> maybe to far-fetched, butttt
[17:18] <mgagne> I might not be the right person to ask to invest time on it atm ^^'
[17:18] <harlowja> kk
[17:18] <harlowja> dmsimard ?
[17:19] <mgagne> don't know, doesn't work with us anymore =)
[17:19] <harlowja> delegation not working
[17:19] <mgagne> should patch be targeted for v2 or 0.7.x is fine?
[17:19] <harlowja> must delegate harder, lol
[17:19] <mgagne> still waiting for my clone to arrive from mail
[17:20] <harlowja> UPS lose it?
[17:20] <harlowja> lol
[17:20] <mgagne> unfortunate yes =( they also say we can't ship bio stuff :P
[17:20] <harlowja> ah
[17:20] <harlowja> good point
[17:23] <klindgren> I hear fedex or DHL is looser on the restrictions
[17:23] <harlowja> nice nice
[17:24] <harlowja> dmsimard let me know if u have time for those kinds of tests
[17:24] <harlowja> if not, i can try, but no guarantees on time for that :-P
[17:24] <harlowja> or smoser can get git and then we can accept patch, and i can start adding tests
[17:24] <harlowja> and cookies
[17:31] <larsks> Out of curiousity, what is the effort involved in moving to git?  Is it more than just import-from-bzr-export-to-github?
[17:31] <harlowja> larsks we already have that
[17:31] <harlowja> but its not in sync with bzr
[17:31] <harlowja> larsks https://github.com/openstack/cloud-init is that (export from bzr, import to github)
[17:31] <larsks> Right, I have noted that :).  Is the goal to maintain the bzr repo and keep it in sync automatically?
[17:31] <harlowja> but bzr has a native mode
[17:32] <larsks> Or why not just perform the manual sync once, then kill the bzr repo and go on our merry way?
[17:32] <harlowja> i delegate question to smoser
[17:32] <harlowja> :)
[17:33] <larsks> I am using git locally (via git-remote-bzr), which works great for me but confused the heck out of dmsimard yesterday when I forgot and gave him a git commit id from my local repo...
[17:34] <harlowja> i think the idea was to keep 0.7.x on bzr (and bzr-git) and anything new using that git above
[17:35] <larsks> That seems clunky, because people are going to continue to make patches against the 0.7.x code for packages, and it would be nice to have it in the same repo as newer stuff for ease for cherry-picking, etc.
[17:36] <harlowja> larsks  i know, its either that or we talk about killing bzr again :-P
[17:37] <smoser> larsks, it would be git on launchpad.
[17:38] <larsks> smoser: yeah, that's fine.
[17:38] <harlowja> but only for 0.7.x
[17:38] <harlowja> and then i think i'd ask the openstack-infra guys to kill the 0.7.x branch on  https://github.com/openstack/cloud-init version
[17:38] <smoser> right.
[17:38] <harlowja> which hopefully they would do
[17:38] <smoser> the other thing that is needed is the revision number thing...
[17:39] <larsks> Which revision number thing?
[17:39] <dmsimard> Sorry was afk getting food, reading backlog
[17:39] <smoser> harlowja, had something there. but basically i quite often make use of the bzr revision number for things (snapshots) and want some equivalent
[17:39] <smoser> i forget what it is... theres a apython module that gives snapsthos numbers.
[17:39] <harlowja> there's a few
[17:39] <harlowja> pbr
[17:39] <harlowja> a few others
[17:40] <harlowja> https://github.com/habnabit/vcversioner (another one)
[17:40] <harlowja> and i'm sure a few more
[17:41] <smoser> that wasnt it i dont htink
[17:41] <larsks> Or just use short git commit ids (which are nice because they can be used directly in git commands, etc)
[17:41] <smoser> yeah, but they dont increase.
[17:41] <dmsimard> ok, I read all that
[17:41] <larsks> True.
[17:41] <dmsimard> I definitely can't write python tests to save my life, sorry :p
[17:42] <larsks> That would be a great movie.  "Do you expect me to write a unit test? No, Mr. Bond; I expect you to die."
[17:43] <harlowja> lol
[17:49]  * smoser writes down not to trusty larsks's movie recommendations
[17:49] <smoser> s/trusty/trust/
[17:49] <smoser> (fingers type a y if i type trust)
[17:49] <larsks> Yeah, Trusty is old news.
[18:10] <dmsimard> harlowja: so was that patch a good fit for what landed in trunk, then ?
[18:10] <dmsimard> minus the debian bits
[18:10]  * harlowja hasn't looked over to much yet
[18:10] <harlowja> lol
[18:11] <harlowja> dmsimard i'll get into looking at it more
[18:12] <dmsimard> no emergencies or anything, I resorted to using dhcp for the time being :(
[18:12] <harlowja> k
[18:13] <dmsimard> Do let me know if you'd like to test anything though, this is something I can help with.
[18:13] <harlowja> k
[18:13] <harlowja> thx