17:02:08 #startmeeting Designate 17:02:08 Meeting started Wed Apr 23 17:02:08 2014 UTC and is due to finish in 60 minutes. The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:09 thanks 17:02:11 The meeting name has been set to 'designate' 17:02:18 Heya :) 17:02:21 hey - whos here? 17:02:23 hee 17:02:26 here 17:02:26 heya :-) 17:02:28 hey 17:02:29 here 17:02:29 here 17:02:38 cool 17:02:38 here 17:02:47 #topic Review action items from last week 17:02:57 Joe Work with mugsie to get an application in for https://www.openstack.org/blog/2014/03/call-for-proposals-open-source-openstack-summit/ 17:03:00 that was done 17:03:08 hopefully should hear back soon 17:03:31 #topic DNSpy update 17:03:43 Who added this? 17:03:49 Making good progress 17:03:59 cool - anything of note to report? 17:04:00 I have committed sample code 17:04:15 to poc code base for 17:04:17 eankutse1: cool - where? 17:04:20 notify 17:04:29 #link https://github.com/designate-dns/minidns-poc 17:04:31 and axfr_from a server 17:04:33 ah 17:04:38 mugsie: thx 17:04:41 np 17:04:53 next step is axfr from NS 17:04:57 nameserver 17:04:59 should we make it an action for people to have a look at ^ 17:05:00 ? 17:05:14 Not sure that needs to be an action ;) But I know I will 17:05:15 Yes. 17:05:31 It's still very basic but good to look at 17:05:37 #action everyone - review eankutse's MiniDNS POC 17:05:59 eankutse1: cool - thanks 17:06:15 np 17:06:21 we ok to move on, or do people have questions? 17:06:27 I do 17:06:35 eankutse1: overall, are you thinking it will do everything we need? 17:06:42 kiall: you have the floor 17:06:48 already asked ;) 17:06:55 yes. I think dnspython is capable 17:07:08 I'll be more firm when I complete axfr 17:07:44 eankutse1: Okay, cool.. I'll have a read of your code so-far after the meet 17:07:52 thx 17:07:58 ok to move on? 17:08:31 yes 17:08:53 the agenda on the wiki looks like last weeks one - vinod do you want to talk about rrdata again? 17:09:02 or shall we move to open disccussion? 17:09:38 nothing more about rrdata - i talked to kiall yesterday 17:09:44 #topic Open Discussion 17:09:45 and updated the code 17:09:55 cool - anyone have anything they want to talk about? 17:09:57 vinod: I gave the patchset a quick review earlier today, it looks good 17:10:20 kiall did you get a chance to further investigate the object transmission bug across rpc 17:10:23 Wanted to come back to it again before commenting etc.. But I didn't notice anything with a quick read 17:10:53 vinod: yes, I'm eyeing up this as the cause: https://github.com/stackforge/designate/blob/master/designate/rpc.py#L107 17:11:27 But, I can't see where it's coming into play 17:11:54 i noticed the Fixed IP PTR API code i submitted is now failing. i'll review the problem and update accordingly. can it get reviewed shortly after to avoid this problem? 17:12:04 rjrjr_: no problem 17:12:16 it most likely just needs to be rebased 17:12:23 rjrjr_: was that not still marked as a WIP? Apologies if it wasn't 17:12:52 it is, but 4+ weeks later, other changes came in and broke the code. 17:13:34 rjrjr_: ah.. Well, once rebased, well give it a final round of reviews 17:13:41 great! 17:14:04 cool - anythign else? 17:14:16 Kiall: regarding summit 17:14:24 is this ready to use: https://github.com/designate-dns/designate-workshop-packer? 17:14:26 info on using the VM for Atlanta? 17:14:29 vinod: re the messaging bug, I have setup, but not had a chance to test out, a copy of the old pre-o.m code 17:14:55 eankutsel, exactly what i was thinking. 17:14:56 (Just to verify the pre-o.m code does what I expected) 17:15:24 thanks kiall 17:15:36 eankutse1: yes, it should be ready to use with everything pre-installed etc.. There's some quick+dirty docs on setting the build off, and adding anything needed for the other parts 17:15:59 (I asked mugsie for everyones emails yesterday afternoon, and we both promptly forgot) 17:16:01 I'll be using RH OS1 for my VMs 17:16:09 Kiall: thx. I'll check it out 17:16:10 :-) 17:16:26 richm: makes sense :) 17:16:53 eankutse1: 1 tip for running the build.. keep your hands OFF THE KEYBOARD until it's well underway ;) 17:17:07 ok. I will :-) 17:17:11 (You'll understand why when you run the build...) 17:17:12 no interruptions 17:17:13 yep - I found that out the hard way 17:17:25 thx :-) 17:17:33 mugsie, anything catastrophic? 17:17:45 it just totally breaks the build bit 17:17:46 rjrjr_: wasted 30 mins from memory ;) 17:17:53 yeah ^ 17:18:06 :) 17:18:17 for the design summit - our session has been schedualed - http://sched.co/1eJqs6h 17:18:30 Tuesday 12-12.45 17:18:35 It takes a while to build (30-60 mins, depending on your laptop) but it's repeatable in a way that doing it by hand just isnt 17:18:42 Great! Thx mugsie 17:19:03 it is only 40 mins - so we will have to be clear about what we will be talking about 17:19:13 but that will be done closer to the time 17:19:31 Kiall: thx for the headsup on the build 17:19:34 + 17:20:00 ok - anyone have anything else? 17:20:14 So moving on (again) if people don't mind :) I've had a few people from inside and outside HP ping me re Designate Incubation 17:20:48 ok 17:21:07 Where do people stand on getting the application re-written before the Summit, and "working the room" while we're there with the TC etc? 17:21:39 If I remember we had a list 17:21:42 of what to complete 17:21:48 before we apply again 17:22:02 I wonder how much of that list we've completed so far 17:22:16 I believe we meet all (at the least most) the tickboxes, but we'd need to dig out the list and recheck 17:22:30 we only have 3 weeks 17:22:59 Yep - Not huge amounts of time left before the summit 17:23:14 will the TC entertain incubation requests at the summit? 17:23:19 #link http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements 17:23:23 #link http://git.openstack.org/cgit/openstack/governance/tree/reference/new-programs-requirements.rst 17:23:31 vinod: no - but it doesnt hurt to talk to them 17:23:51 there will be new members on the TC in atlanta 17:23:52 vinod: Honestly, no idea. But having it ready + in hand while face to face can't hurt 17:24:06 kiall, what can we do to help? 17:24:38 rjrjr_: look over those 2 docs and figure out where we'll get -1's :) 17:24:55 kiall: Are you thinking Designate will be a new program or part of an existing one? 17:25:02 betsy: new 17:25:06 (hopefully) 17:25:26 betsy: Not sure, I'd prefer not to be under Neutron, as I don't see enough overlap... 17:25:39 mugsie: okay. I’ll look at the new program req. doc. Haven’t looked at that yet 17:26:00 kiall do you have a link to the TC meeting minutes - i wanted to look at how the recent incubation requests went 17:26:20 vinod: they should be in the same place as our minitues 17:26:29 ok will look there 17:26:32 so action item for everyone to review incubation documents. 17:26:37 #link http://eavesdrop.openstack.org/meetings/tc/ 17:26:38 I think 17:26:54 #action everyone - review incubationn requirments 17:27:31 Anyway - If we think we hit all the marks (or enough/the important marks), we should use the next meet to write out the application 17:27:40 (Switch the next meet to a hangout?) 17:28:02 that suits me - how do other people feel? 17:28:07 sounds good 17:28:11 works for me 17:28:20 works for me too 17:28:33 cool. Same time same place - on a hangout? 17:28:41 1 item agenda - Incubation 17:28:43 yes 17:28:49 Yea, easiest for everyone I reckon 17:28:52 grand 17:28:59 Mark M. says that it is preferred that Designate _not_ be part of an existing program/project 17:29:02 +1 17:29:16 richm: Any reasoning given? 17:29:28 (Not that I disagree, just wondering what the reasoning us) 17:29:29 is* 17:29:40 (Also - Apologies for missing the HO on Monday, was a holiday here and I was out with family..) 17:29:46 He doesn't think any of the existing projects will want to take us (people, code) on board 17:30:01 By the way, any advantages or disadvantages either way? ( program/project…)? 17:30:01 they are too busy to worry about integrating another big pile of code 17:30:34 richm: sounds like a good reason 17:30:43 Mark M. also said the biggest problem with the first round was that there were too few contributors, which shouldn't be a problem now 17:31:07 richm: you talking to him now? (Say "Hi" for me..) 17:31:55 no, not right now 17:32:05 this was a while ago, after our meeting in Austin 17:32:34 Okay - Anyway, let's circle back to this next week once we're re-read the linked docs 17:32:43 yup. 17:32:49 moving on - anything else? 17:32:52 cool 17:33:25 fyi - just sent out the invite for next week 17:33:50 ok - we good to say we are done for this week? 17:34:04 yep 17:34:09 yes 17:34:10 I’m good 17:34:17 good 17:34:22 Yep :) 17:34:25 ok 17:34:28 #endmeeting