18:01:29 #startmeeting akanda 18:01:30 Meeting started Mon Sep 14 18:01:29 2015 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:34 o/ 18:01:34 The meeting name has been set to 'akanda' 18:01:38 o/ 18:02:54 o/ 18:03:24 good morning 18:03:26 everyone 18:03:43 hello 18:03:58 elo: hey eric 18:04:03 agenda 18:04:12 #link https://wiki.openstack.org/wiki/Meetings/akanda 18:04:19 first item 18:04:48 electing a project PTL in preparation for mitaka 18:05:01 #topic electing a project PTL in preparation for mitaka 18:05:04 better 18:05:19 i put it out there that 18:05:33 i have enjoying running the dev meetings 18:05:48 but its time to elect a technical leader 18:06:22 adam gandelman has shown his technical leadership in the project 18:06:48 so i lean toward him, but 18:07:02 this is a public project so we need to discuss it 18:07:23 +1 to adam_g 18:07:36 also +1 to adam_g 18:07:39 open for discussion on the topic 18:07:57 ryanpetrello: you around? 18:08:02 but it wouldn't hurt to discuss the alternitive of markmcclain taking that roll would it? 18:08:14 certainly not 18:08:43 its all up for discussion 18:08:44 im fine with takin over if its me 18:08:59 markmcclain: what are your thoughts? 18:10:20 i didnt see any responses when I put the PTL discussion out on the ML 18:10:31 so i thought we should open discuss here 18:10:56 I've kicked around the different scenarios while I be happy to serve as PTL 18:11:32 but from a project community and community perspective I think would be a better fit for the next cycle 18:11:48 *I think adam_g would be a better fit for the next cycle 18:12:16 * markmcclain fingers aren't typing fast enough today 18:13:05 I'm too new to project to contribute 18:13:20 markmcclain: so if i understand correctly, you are offering to be PTL for mitaka cycle? 18:13:36 markmcclain: or for the remainder of liberty? 18:13:53 he's saying he'd be happy to do it but he thinks adam_g is a better fit for next cycle 18:13:56 sarob: quite the opposite.. I think adam_g would be good PTL 18:14:30 and selecting a ptl for remainder of L and all of M makes sense since the other projects are going through the same process currently 18:16:23 markmcclain: got it same PTL for the rest of L and M 18:16:31 right 18:18:07 okay if no more discussion then lets vote 18:19:09 #startvote adam gandelman as PTL for the remainder of L cycle and all of M cycle 18:19:10 Unable to parse vote topic and options. 18:19:21 #startvote adam gandelman as PTL for the remainder of L cycle and all of M cycle? 18:19:22 Begin voting on: adam gandelman as PTL for the remainder of L cycle and all of M cycle? Valid vote options are Yes, No. 18:19:23 Vote using '#vote OPTION'. Only your last vote counts. 18:19:32 #vote yes 18:19:35 #vote yes 18:19:41 #vote yes 18:20:05 * adam_g abstains 18:20:05 ryanpetrello: ? 18:20:20 i guess thats majority 18:20:34 #showvote 18:20:55 #endvote 18:20:56 ryanpetrello is off today 18:20:56 Voted on "adam gandelman as PTL for the remainder of L cycle and all of M cycle?" Results are 18:21:18 3 yes 18:21:25 1 abstain 18:21:28 1 not present 18:21:36 congrats adam_g 18:21:49 w00t thanks guys 18:22:18 moving on 18:22:36 #topic akanda F2F hack 18:23:01 we had discussed a few different times 18:23:27 28-29 september seems to be the best dates 18:23:33 in portland 18:23:49 are we in agreement still that is the right place and time? 18:24:02 works for me 18:24:16 elo? 18:24:30 yes. I'm in town that week already 18:25:01 davidlenwell, adam_g? 18:25:03 +1 18:25:56 im pretty sure davidlenwell is good as well 18:26:34 yea 18:26:43 sorry .. i knew you knew that so I didn't speak up 18:27:04 so we need to start prepping for mitaka and get a some work prepped for the f2f 18:27:35 i think we should first worry about getting our liberty release in order 18:28:09 adam_g: what do you think the f2f focus should be? 18:28:31 adam_g: like scheduled work that is 18:29:07 sarob, oh right, yes. we can discuss future M development in portland. 18:29:15 well, assuming we get our L released next week :) 18:30:10 adam_g: yeah, so we should organize the f2f schedule very soon 18:31:09 yup 18:31:11 i was thinking we can schedule a 30 minutes or so over irc sometime this week 18:31:24 we can just create an etherpad people can dump ideas into as they get htem? 18:31:33 adam_g: sounds good 18:31:50 lets share over ML then? 18:32:03 https://etherpad.openstack.org/p/akanda-mitaka-planning 18:32:07 #link https://etherpad.openstack.org/p/akanda-mitaka-planning 18:32:16 #action everyone start dumping ideas for M planning into https://etherpad.openstack.org/p/akanda-mitaka-planning 18:33:07 #action everyone start dumping ideas for M planning into https://etherpad.openstack.org/p/akanda-mitaka-planning 18:33:21 moving on 18:33:34 #topic critical bugs 18:33:49 #link https://bugs.launchpad.net/akanda/+bug/1481877 18:33:50 Launchpad bug 1481877 in akanda "stable/juno branches are versioned incorrectly" [Critical,In progress] - Assigned to Sean Roberts (sarob) 18:34:17 #link https://review.openstack.org/217814 18:34:28 #link https://review.openstack.org/217808 18:34:38 #link https://review.openstack.org/217812 18:34:46 should all be ready to merge 18:34:57 i had a typo in the commit msg 18:35:14 thx markmcclain 18:35:16 cool 18:35:23 #link https://bugs.launchpad.net/akanda/+bug/1491593 18:35:24 Launchpad bug 1491593 in akanda "tenant created networks cannot be deleted by the tenant" [High,In progress] 18:35:29 #link https://bugs.launchpad.net/akanda/+bug/1491593 18:35:37 i have patches up for those two 18:36:02 oops 18:36:14 #link https://bugs.launchpad.net/akanda/+bug/1492056 18:36:14 Launchpad bug 1492056 in akanda "A missing appliance instance is caught by alive check, not the missing instance" [High,In progress] 18:36:59 sarob, can you create an rc1 release milestone so i can start targeting bugs accordingly? 18:37:21 also, FYI we decided a couple of weeks ago that our rc1 would go out next week with the rest of em 18:37:29 #link https://launchpad.net/akanda/+milestone/liberty-rc1 18:37:32 adam_g: good catch 18:37:58 sarob, ah cool 18:38:14 adam_g: need to change the date though 18:38:57 #action sarob update rc1 release to match neutron 18:39:41 looks like 18:39:43 #link https://bugs.launchpad.net/akanda/+bug/1490331 18:39:44 Launchpad bug 1490331 in akanda "akanda-appliance stable/juno test.unit.drivers.test_hostname.HostnameTestCase test is failing" [Critical,In progress] - Assigned to Ryan Petrello (ryan-petrello) 18:39:55 was already merged, just not updated 18:40:02 thats a stable/juno bug 18:40:14 * adam_g untargets 18:40:37 adam_g: yup 18:41:13 so we need some reviews on your bug patches adam_g 18:41:39 anything else before bp update? 18:42:09 markmcclain, maybe you know if this is a bug or expected https://bugs.launchpad.net/akanda/+bug/1491673 18:42:10 Launchpad bug 1491673 in akanda "newly created router briefly reports as ACTIVE before it is built" [Undecided,New] 18:42:41 we can chat about that after 18:42:43 sarob, okay to move on 18:42:50 #topic progress on liberty rc1 18:43:10 adam_g: yeah.. it's a quirk we've tolerated for a bit 18:43:19 markmcclain, ah ok 18:43:25 #info appliance provisioning driver 18:43:27 #link https://blueprints.launchpad.net/akanda/+spec/appliance-provisioning-driver 18:43:33 davidlenwell: update 18:44:14 in the process of fixing all the tests that fail in https://review.openstack.org/#/c/215227/9 18:46:57 anything else? 18:47:11 base driver patch 18:47:20 #link https://review.openstack.org/#/c/215226/12 18:47:32 and driver ffactory patch 18:47:34 #link https://review.openstack.org/#/c/215220/16 18:47:50 should be ready to merge after those tests are landed? 18:48:32 Thre will be new patches on the driver factory that includes tests 18:48:45 okay good 18:49:00 but the base driver patch will likely stay as is 18:49:26 got it 18:49:29 moving on then 18:50:02 #info LBaaSv2 18:50:26 #link https://blueprints.launchpad.net/akanda/+spec/lbaas-v2-support 18:50:41 i believe you plan on starting tomorrow 18:50:53 work on that blue print will start tomorrow.. plan to get it finished in a few days 18:51:01 cool 18:51:03 moving on 18:51:10 #link rug scaling 18:51:14 #link https://blueprints.launchpad.net/akanda/+spec/rug-scaling 18:51:25 adam_g: your patches are out there 18:51:31 yep 18:51:47 we as a team need to review 18:52:18 #action team needs to review rug scaling patches pending 18:52:42 #info nodepool/pez 18:52:52 #link https://blueprints.launchpad.net/akanda/+spec/nodepool-support 18:53:09 just fished up a working POC on friday 18:53:09 adam_g: how is that coming? 18:53:22 i'll clean that stuff up and hopefully have it in a state others can start banging on it this week 18:53:36 cool 18:53:44 anything else? 18:53:48 good thing is that pez is its own standalone service and default/existing behavior will be preserved 18:54:04 so we shouldn tneed to block release if its still in an experimental state 18:54:14 got it 18:54:34 #info docs updates 18:54:53 #link https://blueprints.launchpad.net/akanda/+spec/liberty-doc-updates 18:55:08 first quarter of this is merged 18:55:25 ill get more pushed up this week 18:55:36 #topic any other business 18:56:19 none from me 18:57:32 anyone else? 18:57:42 sarob, shall i plan on chairing the meeting next week? 18:57:51 yes, plz 18:58:02 10-4 18:58:08 roger roger 18:58:18 i guess that is it 18:58:25 cheers everyone! 18:58:42 #endmeeting