17:01:16 #startmeeting designate 17:01:21 Meeting started Wed Jun 11 17:01:16 2014 UTC and is due to finish in 60 minutes. The chair is Kiall. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:25 The meeting name has been set to 'designate' 17:01:25 Hey Guys - Who's here today? 17:01:29 here 17:01:30 o/ 17:01:31 here 17:01:36 hello 17:01:37 here 17:01:44 mugsie is out today, so won't be here 17:02:03 #topic Review action items from last week (and the week before!) 17:02:08 o/ 17:02:37 first was mugsie to translate etherpads over to launchpad blueprints - he asked me to push this till next week 17:03:03 first from the week before was "eankutse to get initial answers to jbrattons questions" .. I just saw a draft of this from eankutse 17:03:15 yes. it's here #link http://paste.openstack.org/show/83671/ 17:03:21 #link http://paste.openstack.org/show/83671/ 17:03:26 but will put it in bp 17:03:29 beat me to it :) 17:03:33 :-) 17:04:05 Great - We'll be able to iterate on the answers once it's in there to get a good idea of what we need to allow for in mdns 17:04:12 sure 17:04:24 Next was "eankutse to pick Jbratton's brain on ops side of things for minidns/pools" .. Seems to me the previous item covered it 17:04:37 that;s the intent 17:05:28 Next two were "kiall to write our various initial load scenarios" and "kiall to file BP on exposing the NS (and SOA?) record in the V2 API" - And I've not had time this week :( Every spare minute was getting the devstack gate running right 17:05:50 #action kiall to file BP on exposing NS/SOA records in V2 API 17:06:00 saw all the commits you did :-) 17:06:09 #action kiall to write out mdns initial load scenarios and add to eankutse's BP 17:06:22 (I think your BP and those will be pretty related) 17:06:28 yes they are 17:06:42 Okay - That was all the actions we missed last week 17:06:55 #topic Mini DNS - is 'mdns-designate-mdns-functional' a place holder or explicit functionality? (eankutse) 17:07:06 (what a BP name, I apologize for that ;)) 17:07:16 1 sec 17:07:24 #link https://blueprints.launchpad.net/designate/+spec/mdns-designate-mdns-functional 17:07:31 yep 17:07:46 so 17:08:04 is this item standing on it's own? 17:08:12 or is it considered done when 17:08:15 So - My idea when I filed this BP was that, this would be where the skeleton designate-mdns service we now have turns from a skeleton to something useful - even if it's not all of mdns. 17:08:20 the items below it are done? 17:08:54 This would be where we actually get more than "SERVFAIL" and get real answers from mdns for simple queries - e.g. SOA lookups 17:09:10 (but not AXFR just yet, or TSIG sign requests) 17:09:20 ok. 17:09:45 so these would be things leading up to AXFR 17:09:48 If that doesn't make sense to anyone but me, we can add/remove BPs etc 17:09:50 and TSIG 17:10:02 ok. 17:10:03 kiall: makes sense to me 17:10:07 eankutse: yea - that was my thinking when I split mdns up into a pile of BPs 17:10:27 and leads to smaller patch submissions 17:10:33 makes reviewing easier 17:10:54 Ideally, once this happens, and mdns can answer a simple SOA query, we can fork and have 3 people working on different things.. 1 getting AXFR working, 1 adding TSIG support, 1 writing the supporting code to send DNS notifies 17:11:12 (fork != github style fork ;)) 17:11:26 cool 17:11:37 Oh .. There is 1 other BP blocking this one 17:11:42 #link https://blueprints.launchpad.net/designate/+spec/mdns-designate-mdns-dnspy-translations 17:12:24 That was intended to be where we would write out the "converter" methods to translate from our objects, over to dnspy's objects 17:12:27 i was thinking this would happen in pieces 17:12:34 as we implement the other functionality 17:12:39 eg NOTIFY, 17:12:41 SOA 17:12:43 AXFR 17:13:01 these would 'build up' this bp 17:13:07 as we go 17:13:24 e.g. translating an "A" designate.objects.Record to dns.rdata.a.A() (or w/e the dnspy class is called) 17:13:32 Is the blue print mdns-designate-mdns-dnspy-translations different from https://blueprints.launchpad.net/designate/+spec/mdns-designate-mdns-notify? 17:13:38 I would assume so 17:13:50 The description for blueprint mdns-designate-mdns-dnspy-translations talks about NOTIFY 17:13:56 vinod: dooh - description is wrong 17:13:58 title* 17:14:10 copy and paste fail while filing all them 17:14:44 refresh please :) 17:14:45 https://blueprints.launchpad.net/designate/+spec/mdns-designate-mdns-dnspy-translations 17:15:08 That was my original intent for that BP - does that change things? 17:15:50 (They're chatting) 17:16:09 lol - I was wondering ;) 17:16:41 so Kiall: what do you think about the piecemeal approach? 17:16:43 I would think that it would be easier to do the translations as we use dnspython objects 17:17:05 vinod / eankutse sure - we can cross that BP out and do it bit by bit 17:17:13 I like that 17:17:36 and .. marked as obsolete. 17:17:46 +1 on that 17:18:09 Anyone disagree before we move on? 17:18:42 i'm good. 17:18:45 kiall: I liked your approach better, but I’m not the one doing the code. 17:18:46 :) 17:18:49 lol 17:18:56 So, I’m good 17:19:04 +1 17:19:28 I think getting 1 done before the meat of the mdns-functional done would be a good idea, all is likely not necessary 17:19:41 getting all done is likely not necessary* 17:20:00 Okay .. Moving on so :) 17:20:03 #topic DevStack (kiall) 17:20:20 I think everyone noticed the binge of DevStack patches ;) 17:20:28 #action kiall Mark https://blueprints.launchpad.net/designate/+spec/mdns-designate-mdns-dnspy-translations as obsolete 17:20:31 :-) 17:20:32 3 cheers for Kiall! 17:20:51 it's not all cheers - I had to revert some stuff too :( 17:21:02 So is all the devstack stuff done now? 17:21:04 https://github.com/stackforge/designate/commit/f205633c6303dd209ece20237ed60fa5043689da 17:21:35 That added some nice functionality which, sadly, broke when ran in the gate. as does https://review.openstack.org/#/c/97628/ 17:22:18 We're going to have to figure out what exactly is breaking so we can get them merged.. I'm frankly stumped on the first one.. and just confused on why unbound is ending up installed, preventing the second one 17:22:50 richm: any chance you were able to identify how/why unbound was ending up installed? 17:24:14 Is it being installed by one of the other projects? 17:24:40 vinod: "unbound" is nowhere to be found in devstack, so it shouldn't be 17:25:04 And - When ran locally in vagrant - it's not there... 17:25:12 (even with the same set of services/devstack options etc) 17:25:37 I'm starting to wonder if the infra folks are pre-installing it on all the single use slaves 17:26:00 maybe fungi / clarkb know? 17:26:43 Kiall: no, I'm not an ubuntu guy - I'll need to install a vm and do some investigating 17:26:44 Kiall: yes, we install it because we need to cache local dns queries on job workers 17:27:18 ok - so looks like, for testing, we'll need to run the designate DNS server on another ip/port 17:27:25 fungi: ooo. Okay - I can chat with you after then.. We might be able to make them co-exist so long as neither bind to *:53 17:27:49 Kiall: perhaps, get up with us in #-infra when you're free 17:28:12 Kiall: importantly we do it because the cloud providers DNS servers don't work... 17:28:14 richm: or we pick another IP - 127.*.*.* is all "ours" .. just have to make sure we're doing it in a sane way 17:28:31 Kiall: if you happen to have any sway in how dns is run at one of them ;) 17:28:44 clarkb: lol - recursive dns is not my area ;) 17:28:50 That's a whole other team 17:29:00 thanks fungi / clarkb - at least that solves 1 mystery :) 17:29:32 Okay - Anyway - I just put that on the agenda so people could think about/come up with solutions ;) 17:30:34 Also - You may have noticed I added a Vagrantfile to the contrib/devstack folder which will spin up DevStack with out plugin in either ubuntu or fedora 17:30:54 richm: that would be the quickest + easiest way to get a ubuntu VM :) 17:31:48 Unless there's any Q's on all the Devstack changes / what's needed going forward we'll move on.. 17:31:52 So .. Any Q's? :) 17:32:02 Kiall: ok - will take a look 17:32:04 i'm good. 17:32:11 good work! 17:32:15 are there more devstack changes to be done? 17:32:43 vinod: richm has a patch up that's blocked on the unbound thing that extends the testing we do 17:33:19 and we'll want to try and write some tempest tests if we can figure out how to hook into that, as that's going to be expected of us once we incubate 17:33:34 did we incubate? 17:33:39 That's next ;) 17:33:40 Is this https://review.openstack.org/#/c/98968/ needed for incubation? 17:33:56 No - Nothing is blocking incubation anymore 17:34:03 #topic Incubation progress (kiall) 17:34:07 may as well ;) 17:34:16 #link https://review.openstack.org/#/c/97609/ 17:34:19 ^ the voting .. 17:34:31 6 Yay's, 0 Nay's 17:34:37 It’s looking good 17:34:45 :-0 17:34:48 :-) 17:34:53 There's also 3 others who voted +1 before the updated patchset 17:35:03 markmc asked us to update the mission statemen 17:35:04 t 17:35:05 So is somebody expected to do a +2 before we can get incubated? 17:35:36 myself and graham came up with an alternative wording which made people happy - https://review.openstack.org/#/c/97609/3/reference/programs.yaml 17:36:16 "Enable operators to meet their Domain Name System needs in a stable and scalable manner." <- original wording 17:36:16 That looks good! 17:36:26 Any concerns before it's too late to change it again? 17:36:50 As long as the TC is happy, I am happy 17:37:01 :) 17:37:02 in a* technology-agnostic? 17:37:13 tsimmons: NOOOOO 17:37:26 tsimmsons: +1 17:37:27 :O 17:37:36 * Kiall closes his eyes and pretends he didn't hear that 17:38:04 eyes or ears? 17:38:07 http://2.bp.blogspot.com/-UUBBVvfBUcM/T1t8Zi673mI/AAAAAAAAA0c/uEdZ-PA4IpI/s1600/homer-simpson-bush-gif.gif 17:38:09 both 17:38:15 ^ that 17:38:30 I'm sure it'll be fine. 17:38:47 :) 17:38:54 If Anne Gentle (technical writer) didn't care I don't think we have to ;) 17:38:58 Okay - Anyway, We'll be back on the agenda for the TC meet next week 17:39:03 Sweet 17:39:14 If there are no -1's, I believe that's the end of it 17:39:31 (or the start, whichever ;)) 17:40:06 So after incubation do we move to openstack from stackforge? 17:40:30 vinod: yes, usually during the next scheduled Gerrit downtime 17:40:40 (you can't rename gerrit projects without downtime) 17:41:04 kiall: oh, interesting. I thought it wasn’t until after integration 17:41:33 I don't think that's the case! 17:41:41 https://github.com/openstack/barbican suggests it's not :) 17:41:55 Fun. I'm sure that won't mess any scripts up :P 17:42:13 cool 17:42:16 tsimmons: you have no idea how much pain that's going to cause me ;) 17:43:25 Anyway - once accepted, we'll be expected to start doing things like A) submit our devstack plugin to devstack proper and fix all the issues they find, B) start writing tempest tests, C) start writing a horizon plugin etc 17:43:45 (HP has C covered, we have one we're happy to open source - when we can put it into openstack/horizon) 17:43:57 Cool. 17:44:31 We'll also have to deal with the fun (aka pain) of the "integrated gate" 17:45:00 Approved patches will take much longer than land, but, they'll still land :) 17:45:22 http://status.openstack.org/zuul/ the center column gives you an idea of the integrated gate queue times 17:45:56 I know. I’ve looked at that before and been glad we were in that queue 17:46:01 ;) 17:46:08 The price of incubation 17:46:20 we are cloud developers - we should just horizontally scale out the gate :-) 17:46:32 richm: lol .. that's exactly what happens ;) 17:46:47 there are currently 900 instances acting as test slaves 17:46:53 egads 17:46:58 ;) 17:47:10 The first graph at the very bottom of the page shows it 17:47:16 #topic Open Discussion 17:47:30 (Since we're basically onto the open discussion topic anyway) 17:47:37 I have a quick follow up 17:47:40 regarding #link http://paste.openstack.org/show/83671/ 17:47:49 Internal Server Error 17:47:49 The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application. 17:47:51 ;) 17:48:07 there we go - 3 refreshes later and it came up 17:48:25 Can I add it to the current bp where it is? 17:48:45 since it will all be moved to designate-spec? 17:48:46 rather than in designate-specs? yea, for existing BPs moving them over seems pointless 17:48:52 yea 17:49:00 ok 17:49:17 Any other topics? 17:50:24 Going once? 17:50:26 I have a quick question 17:50:52 That's probably not relevant to everyone :) So it can wait till after, just fyi 17:51:07 lol .. sure? 17:51:28 Alright, as far as extending the v2 api, should we use a similar method to v1, stevedore etc? 17:52:36 I just wanted to check which patches were still waiting for reviews? 17:52:37 Yea, i think the old pattern worked well - using stevedore (well, entry points i.e the stuff behind stevedore) let's you write out of tree API extensions 17:52:49 I mean you could just write more views/controllers and hack them into the root.py thing, but that seems messy. 17:52:57 I know we have some very HP-specific extensions for the V1 API 17:53:27 tsimmons: yea, hacking them in means forking when you want to add an private extension, and once you have a fork, things go wrong fast :) 17:53:49 (Just ask a certain cloud provider how that went down with Nova ;)) 17:54:07 Yeah that's no fun. So I guess I'll look at the other projects (none of which seem to use pecan in a similar way) and try and figure out an extension mechanism with pecan. 17:54:27 vinod: mugsie came up with this for review backlogs http://bit.ly/1u7Zvjy 17:54:36 very bad idea 17:55:10 vinod: It'll be tailored to you, showing you the patches which you should "probably" look at 17:55:44 Thanks kiall and musgsie for the link 17:56:19 tsimmons: yea, the others use WSME on top of Pecan - Which at the time, was simply not ready to be used in any way. 17:56:51 Kiall: Should we switch to that now? 17:57:26 It's still not ready for prime time 17:57:45 But - It is something we should consider at some point.. Just not this cycle. 17:57:56 Fine by me. I guess I'll just see what I can figure out with Stevedore 17:58:01 and the current state. 17:58:15 Okay - Anything else before we call it a day? 17:58:22 none 17:58:44 nothing else 17:58:58 Okay - Thanks all :) 17:59:00 and .. all yours SlickNik :) 17:59:01 #endmeeting