15:04:31 #startmeeting akanda 15:04:32 Meeting started Mon May 4 15:04:31 2015 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:36 The meeting name has been set to 'akanda' 15:04:48 o/ 15:05:19 Agenda 15:05:27 #link https://wiki.openstack.org/wiki/Meetings/akanda 15:06:24 Specs got merged 15:06:34 So that was completed 15:06:54 sweet 15:07:05 Next was to update the existing bp with details 15:07:14 I did some of that 15:07:28 Y'all have a pass at that 15:07:39 its on my list for early this week 15:07:54 might fit in a little .. however monday is meeting day.. so.. 15:08:55 Adam_g how about you? 15:09:11 i can do the same with the spec i had written last week 15:09:49 Cool 15:10:50 #topic workflow 15:11:43 Adam_g and I were discussing launchpad workflow 15:12:29 I'm thinking of running this closer to neutron style 15:12:42 Many repos 15:12:51 Single launchpad 15:13:04 Using bug tags 15:13:36 Loading up all the tarballs in one place 15:14:23 Tracking the releases in one place 15:14:49 As opposed to one launchpad project per repo 15:15:00 all of that sounds good.. 15:15:04 That's my preference 15:15:10 Which one? 15:15:33 single launchpad / many repos 15:15:39 im fine iwth the single meta-project approach 15:15:41 Okay 15:15:58 Markmcclain join us ? 15:16:01 keep it simple .. 15:16:25 Yeah, that was my objective 15:17:05 Anything else on this? 15:17:31 How about multi project bugs Adam_g 15:18:01 sarob, you'd have to just use bug tags to designate a bug affects multiple projects 15:18:17 er, sub-projects 15:18:34 was that multi release too your sample bug 15:19:55 sarob, you can still target bugs to the 'akanda' project and target it specific a series (ie, juno) 15:20:38 Okay 15:20:39 but its not going to be as fine grained as having multiple LP projects, ie able to say "this bug affects akanda-XXX kilo and liberty AND akanda-YYY juno + kilo) 15:20:52 should be okay though 15:21:07 i can't imagine that ever needing that 15:21:15 Alright, let's move on then 15:21:30 #topic kilo release 15:21:55 We set this Friday as the the kilo branch date 15:22:28 I have not had enough time to test our kilo code to know if we can hit that 15:22:29 We get in docs 15:23:07 theres one patch from markmcclain up that should land, but its unit tests need fixing 15:23:38 the devstack plugin code in the akanda-rug repo should work now 15:24:10 So we have this week 15:24:11 ive pushed https://review.openstack.org/#/c/179434/to build images during devstack deployment. enabling the plugin and running should stand up an akanda environment tho im still having some trouble with networking 15:26:17 Dropped off there 15:27:45 it happens you only missed one message 15:28:11 So 15:28:30 5 days 15:30:36 Let's get the basics going 15:30:57 it aligns with several other goals.. I think we can do it 15:32:28 I'll may need a little help with the mechanics this first go around 15:32:53 I will reach out as necessary 15:33:54 I don't know the state of lbaas v2 API 15:34:18 Anyone know where markmcclain is on that one? 15:34:21 does anytone? 15:34:24 anyone 15:34:39 sorry .. this is no place for sarcasm 15:35:05 sarob_, nothing up on gerrit yet 15:35:12 It hard to read through your char 15:36:05 did see a patch on cloud-init support 15:36:52 rug-scaling and lbaasv2 api look likely to push then 15:38:09 oh, question about versioning.. is this 1.0 or 2015.1.0 ? 15:38:21 follow openstack convention 15:38:34 2015.1.0 right? 15:38:47 ya 15:38:52 yep 15:39:03 no new wheels invented 15:39:09 +1 15:39:40 im thinking we need to vote as a group when we think akanda 2015.1.0 is stable 15:39:44 after branching 15:40:16 bugfixing and test tweaking should be our focus for next week 15:40:20 sound right? 15:40:43 sounds good to me 15:44:27 cool 15:44:32 adam_g 15:44:37 sound good to you? 15:44:45 i think so 15:45:11 bug fixes will either be batched up for a 2015.1.1 or 2015.2.0 ? 15:45:25 #action kilo release 2015.1.0 for 08may15 15:45:51 adam_g: whats your preference? 15:46:21 sarob, i guess it depends on how many bugs are being identified and fixed 15:46:31 and how fast trunk moves after friday 15:46:40 adam_g: sounds about right to me 15:46:42 should be okay 15:46:51 to keep moving on 2015.2 and backport anything critical 15:47:12 or were you suggesting we push 2015.1.0, and continue to work there to stabalize? 15:47:41 i thought both 15:47:44 okay 15:47:45 cool 15:47:54 2015.1.0 this fri 15:48:15 i just dont want to get stuck working on kilo for too long while the liberty ship is sailing, and then spend the first half of M trying to catch up to liberty 15:48:31 yeah.. its a viscious cycle 15:48:37 minor bugs mean we tag 2015.1.1 following frid 15:48:54 bigins mean 2015.2.0 15:49:10 adam_g: i agree 15:49:33 excellent segway 15:49:41 #topic liberty blueprints 15:50:30 i propose we find a slot of time on tuesday 15:50:34 of summit 15:50:39 for our design session 15:51:02 i have a slew of bp 15:51:05 #link https://blueprints.launchpad.net/akanda 15:51:13 +1 15:51:33 and an etherpad teed up 15:51:38 #link https://etherpad.openstack.org/p/liberty-akanda-design 15:52:00 soo, in our spare time this week 15:52:30 lets organize the pushed bp and new bp 15:52:37 into a liberty release plan 15:53:18 #action sarob rough version of liberty release plan in etherpad by end of this week 15:53:54 ill take responsibility for it 15:54:23 but y'all need to weigh in with what you want to see in this next 6 months 15:55:02 thats all i got 15:55:37 #topic any other business 15:55:53 got 5 minutes 15:56:10 I don't have anything to add 15:56:39 adam_g: ? 15:56:43 only thing 15:56:59 hit me 15:57:00 if anyone is planning on doing some devstack work this week, please iterate on the devstack plugin hosted in the akanda-rug repo 15:57:13 instead of the akanda-devstack repo, lets make that go away 15:57:29 +! 15:57:38 yes 15:57:51 its super easy to enable: https://github.com/stackforge/akanda-rug/blob/master/devstack/README.md 15:57:51 thats all from me 15:57:55 cool 15:58:04 so lets break 15:58:17 #endmeeting