18:00:48 <sarob> #startmeeting akanda
18:00:49 <openstack> Meeting started Mon Aug 17 18:00:48 2015 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:53 <openstack> The meeting name has been set to 'akanda'
18:01:03 <sarob> #link https://wiki.openstack.org/wiki/Meetings/akanda#Agenda
18:01:11 <sarob> roll call
18:01:22 <markmcclain> o/
18:01:49 <adam_g> o/
18:02:01 <puranamr> o/
18:02:45 <sarob> morning/afternoon
18:03:04 <davidlenwell> o/
18:03:18 <sarob> #topic outstanding actions
18:03:49 <sarob> get versioning sane across stable branches (#1481877
18:04:10 <sarob> #link https://bugs.launchpad.net/akanda/+bug/1481877
18:04:10 <openstack> Launchpad bug 1481877 in akanda "stable/juno branches are versioned incorrectly" [Undecided,New]
18:04:37 <sarob> looks like this is mine
18:05:27 <sarob> i will do a bit of research and update the bug
18:06:03 <sarob> looks like that was the only outstanding action from last week
18:06:11 <sarob> moving on
18:06:22 <sarob> #topic critical bugs
18:06:50 <sarob> #link https://bugs.launchpad.net/akanda/+bug/1470673
18:06:50 <openstack> Launchpad bug 1470673 in akanda "pbr version numbering doesn't match semantic versioning" [Critical,In progress] - Assigned to Sean Roberts (sarob)
18:06:56 <sarob> this is related to the other bug
18:07:51 <sarob> i will update this one based on the meeting notes from previous
18:08:15 <sarob> thats it for critical bugs
18:08:29 <adam_g> https://launchpad.net/bugs/1481463
18:08:29 <openstack> Launchpad bug 1481463 in akanda "cant delete akanda ports" [High,In progress]
18:08:54 <adam_g> addressed by https://review.openstack.org/#/c/209267/
18:09:12 <sarob> sure lets talk about that one
18:10:08 <markmcclain> it's all old dead code that we left around because we thought we might make it an active feature
18:10:24 <markmcclain> we're better off just removing it
18:10:36 <sarob> ill review to push through
18:11:07 <sarob> done
18:11:41 <adam_g> cool
18:13:04 <sarob> #topic progress on bp
18:13:50 <sarob> davidlenwell: you around?
18:13:56 <davidlenwell> yep
18:14:18 <sarob> update on https://blueprints.launchpad.net/akanda/+spec/appliance-provisioning-driver
18:14:51 <davidlenwell> markmcclain and I are going to work today to break down the remaining work into smaller pieces
18:16:13 <sarob> the results partly going into the spec?
18:16:15 <davidlenwell> a patch for generic drivers support is in flight.. but there are some unanswered questions that we will work through today.
18:16:35 <davidlenwell> sarob: yes.. I'll update the "work items" in the spec to match what we break down today.
18:16:42 <sarob> davidlenwell: right on
18:16:51 <davidlenwell> so that spec is still not ready to merge .. don't merge it please
18:17:05 <sarob> davidlenwell: hands off here
18:17:20 <davidlenwell> 
18:17:21 <davidlenwell> k
18:17:49 <sarob> you and markmcclain make some good progress
18:17:56 <davidlenwell> yessier
18:18:08 <sarob> davidlenwell: ;)
18:18:28 <sarob> adam_g: update on https://blueprints.launchpad.net/akanda/+spec/rug-scaling
18:19:01 <adam_g> https://review.openstack.org/#/c/195366/ is the main patch for that, ready to review
18:19:13 <adam_g> ive been piling on some improvement / fixes on top of that
18:19:20 <adam_g> probably some more this week
18:19:34 <sarob> adam_g: sounds good
18:20:18 <markmcclain> in that series it would help if some others reviewed: https://review.openstack.org/#/c/198176/12
18:20:24 <sarob> markmcclain: update on https://blueprints.launchpad.net/akanda/+spec/appliance-ha
18:20:45 <markmcclain> no progress due to some other stuff
18:21:25 <sarob> markmcclain: should we plan on pushing this to the next release?
18:21:50 <markmcclain> possibly.. the driver work will impact this as well
18:22:10 <sarob> okay, i will go ahead and do that for now
18:23:06 <sarob> adam_g: update on https://blueprints.launchpad.net/akanda/+spec/nodepool-support
18:23:15 <adam_g> spec is still up awaiting review
18:23:48 <markmcclain> adam_g: sorry that one slipped through.. I'll go back and read it
18:23:56 <sarob> can i friend get an review on https://review.openstack.org/#/c/194882/
18:23:57 <adam_g> np
18:23:59 <sarob> cool
18:25:26 <sarob> i believe https://blueprints.launchpad.net/akanda/+spec/lbaas-v2-support and https://blueprints.launchpad.net/akanda/+spec/octavia-integration are blocked
18:26:01 <sarob> markmcclain: and davidlenwell breaking up the driver bp should help unblock
18:26:47 <markmcclain> they are
18:27:11 <sarob> puranamr: update on https://blueprints.launchpad.net/akanda/+spec/reduce-vm-footprint
18:27:53 <sarob> puranamr: you are still planning on adding performance details to this?
18:28:05 <puranamr> sarob: planning to break the content into two parts
18:28:33 <sarob> puranamr: two different bp or sections in the bp
18:28:34 <puranamr> one which captures the possible identified performance bottle necks and later supported with actual results
18:28:47 <puranamr> may be two bp would make sense
18:28:48 <markmcclain> I think this should be delayed
18:29:11 <sarob> markmcclain: which what?
18:29:27 <markmcclain> the reduce vm footprint
18:29:55 <puranamr> markmcclain: we thought of using this bp to add the performance activity too
18:30:16 <sarob> markmcclain: or you favor creating a separate bp?
18:30:17 <puranamr> the reduce vm footprint would be of lower prio though at this point
18:30:40 <markmcclain> the size of the vm image and tweaking the running configuration are independent of each other
18:30:55 <markmcclain> so should be distinct blueprints
18:31:05 <sarob> sounds good to me
18:31:11 <sarob> puranamr: you good with that?
18:31:14 <markmcclain> or realistically if the perf improvements are likely more bug sized
18:31:34 <markmcclain> vs having a super heavy weight write up
18:31:39 <sarob> markmcclain: we should start with a plan
18:31:47 <puranamr> sarob: ok with splitting
18:32:16 <puranamr> markmcclain: it is not heavy writeup, but spelling out identified areas for further focus
18:32:28 <sarob> markmcclain: it doesnt need to be a huge deal, just a plan that others will know where puranamr is going
18:32:39 <sarob> puranamr: what you said
18:32:42 <markmcclain> right.. realistically those are bugs with tags
18:33:01 <markmcclain> tag = vm-performance-improvement
18:33:11 <markmcclain> or something like that
18:33:15 <puranamr> sarob: markmcclain: sounds ok to me
18:34:17 <sarob> puranamr: if you can identify a group of performance improvements as bugs, it works for me
18:34:46 <puranamr> sarob: ok to call them out in the bp and then split as bugs?
18:35:26 <sarob> i think markmcclain was suggesting bugs instead of bp
18:35:50 <sarob> bp is generally for new features
18:35:57 <puranamr> sarob: ok
18:36:00 <sarob> bugs to fix whats broke
18:36:57 <sarob> was that what you were saying markmcclain?
18:37:46 <markmcclain> yeah.. and we can tag the bugs
18:38:01 <markmcclain> so that we can follow the series of performance improvements
18:39:13 <sarob> moving on
18:39:20 <sarob> #topic any other business
18:40:32 <adam_g> sarob, whats the plan for getting the liberty-2 milestone tagged?
18:41:50 <sarob> adam_g: im going to do bit of doubling the state of the repos
18:42:28 <sarob> adam_g: as we discussed if the repo hasnt got a patch since 2015.2.0b1, i will
18:42:37 <sarob> adam_g: push a dummy patch to move the head
18:42:53 <sarob> akanda-horizon is one for sure
18:43:07 <adam_g> sarob, im more curious about what schedule we're following. we set the release of liberty milestone-2 as 07-30 but we're still tracking in progress blueprints as if that date is still a month way
18:43:26 <adam_g> is it safe to say we're following our own schedule this cycle?
18:43:36 <sarob> adam_g: ah,
18:43:54 <sarob> adam_g: we hadnt formally discussed,
18:44:03 <markmcclain> yeah.. and we're only 2 weeks from the traditional milestone-3
18:44:45 <sarob> adam_g: i am leaning towards cutting 2015.2.0b2 this week
18:44:55 <adam_g> should we stop and set some dates for our remaining milestones  and RCs?
18:45:10 <sarob> adam_g: lets
18:45:13 <markmcclain> yeah
18:45:14 <adam_g> i fear we'll still be spinning on the same blueprints when the rest of openstack is cutting their RCs
18:45:28 * adam_g pulls up release schedule
18:46:18 <adam_g> sarob, there are no complete liberty-2 blueprints
18:46:28 <sarob> adam_g: that is correct
18:46:29 <adam_g> https://launchpad.net/akanda/+milestone/liberty-2
18:47:09 <adam_g> ... so if you're cutting liberty-2 this week,  those should be retargetting to liberty-3, making liberty-2 mostly bug fixes only
18:47:21 <sarob> adam_g: that sounds right to me
18:47:23 <adam_g> if thast the plan, lets set a date for L3 and stick to it
18:47:33 <sarob> adam_g: id like that
18:48:08 <adam_g> RCs start sept 21
18:48:39 <markmcclain> I was thinking that week or 28th
18:48:45 <adam_g> general openstack liberty-3 is sep 1-3 according to https://wiki.openstack.org/wiki/Liberty_Release_Schedule
18:49:25 <sarob> the dates for https://launchpad.net/akanda/liberty
18:49:32 <sarob> are the official ones
18:50:12 <adam_g> sarob, those need to change, then
18:50:35 <markmcclain> are we really going to have an FF period? if not I think we can collapse l3 on rc1 and release it 9/21
18:51:16 <adam_g> markmcclain, release == rc1?
18:51:16 <sarob> markmcclain: that sounds about right to me
18:51:39 <markmcclain> yes
18:52:29 <adam_g> ok
18:52:31 <sarob> everyone else following this?
18:53:34 <adam_g> if sarob tags the late liberty-2 this week and we cut RC1 on 09/21.. where do we put liberty-3? do we realistically expect everyting currently in https://launchpad.net/akanda/+milestone/liberty-2 to be done for l3?
18:54:01 <sarob> one month for each of the bp
18:54:02 <adam_g> its currently targeted for 09/03
18:54:35 <markmcclain> I was thinking we could just skip liberty-3
18:54:49 <adam_g> im not opposed to that
18:54:58 <sarob> markmcclain: hmm, simplier
18:54:59 <adam_g> the milestones didnt really do much for us
18:55:07 <adam_g> (so far)
18:55:42 <markmcclain> right
18:55:43 <sarob> few bugs would be moved to longer l2
18:55:55 <sarob> no real impact other than that
18:56:55 <sarob> sounds like we are in agreement
18:56:56 <markmcclain> I'm advocating we just cut liberty-2 now-ish and then our next tag will be RC
18:57:05 <adam_g> markmcclain, +1
18:57:11 <sarob> markmcclain: +1
18:57:22 <sarob> any one else?
18:57:26 <puranamr> markmcclain: +1
18:57:40 <adam_g> thats roughly 5 weeks, ya?
18:57:45 <adam_g> everyhone get to work :)
18:57:56 <sarob> adam_g: yup, and yup
18:58:04 <adam_g> almost at time
18:58:04 <sarob> ill call it there
18:58:39 <sarob> #action l3 will be eliminated
18:59:04 <sarob> #action sarob check up on his critical versioning bugs
18:59:15 <sarob> thats all folks
18:59:34 <sarob> #endmeeting