16:01:01 #startmeeting openstack-chef 16:01:01 Meeting started Mon Mar 14 16:01:01 2016 UTC and is due to finish in 60 minutes. The chair is sc`. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:05 The meeting name has been set to 'openstack_chef' 16:01:11 ohai 16:01:59 o/ 16:02:17 moin calbers 16:03:05 #chair jklare 16:03:06 Current chairs: jklare sc` 16:04:05 since the bulk of the refactoring is merged, i think there are just a couple of topics: austin and clearing the queue 16:04:12 hey 16:04:25 moin jklare 16:04:50 i think we should start looking at our bugs/blueprints page 16:05:14 there is a lot of stuff targeted for liberty 16:05:25 i started removing some things this morning 16:06:05 i'm bad at checking lp. it's in a pinned tab now, so i'll check it more often 16:06:08 but we should try to figure out what we want to finish or include in our mitaka release 16:06:13 :D 16:06:46 i targeted the rc1 of mitaka for the 31.3 and the stable one for the 30.4 16:06:53 which will be directly after the summit 16:07:04 i think this should be doable, as long as we have the packages 16:07:27 i've been trying to bump the centos packages to a newer build, but it doesn't seem to be building in integration 16:07:28 took a quick look at the mitaka packages for ubuntu on xenial today and they seem to work mostly :D 16:07:41 that said, i just spun a march 9 rdo build on my laptop 16:08:03 so its working locally, but not on infra? 16:08:25 yeah. might be a bigger problem because integration flat out doesn't work for centos without several hacks 16:08:33 ... 16:08:38 not good 16:08:41 it passes the rake gate 16:08:46 :D 16:08:47 so that might be good enough 16:08:51 its something ;) 16:09:09 i think we should get the integration testing working if we want to support it 16:09:11 friday and saturday i spent some time trying to make c7 integration work 16:09:14 i'm close 16:09:23 otherwise we will constantly break it without even knowing 16:09:30 it fails at starting apache, which is odd because the same build works locally 16:09:40 i'll have to spend some time with infra i think debugging the vm 16:09:52 sounds like a plan 16:10:04 usually infra is very helpful with that stuff 16:10:26 ahh btw 16:10:29 yeah. it was friday and i was working on it late 16:10:38 nobody wants to debug jenkins failures on friday :D 16:10:42 i closed all the open/unreleased milestones before mitaka 16:10:55 right on 16:11:09 so i "released" liberty and kilo rc1/stable with the dates from the corresponding commits 16:11:23 not sure if thats ideal, but since we missed doing that while actually releasing 16:11:35 its better they are closed now than let them stay open forever 16:11:42 yeah. better late than not at all 16:11:58 plus it cleans things up 16:11:58 so the only open milestones are on the mitaka stream 16:12:01 rc1 and stable 16:12:23 but this also means we need to retarget most of our bugs and blueprints as said above 16:12:37 markvan did a lot of comments in them 16:12:57 hoped he could take another swing at it and move some things around 16:14:10 any fixed plans for austin yet? 16:14:35 i still haven't registered, though i'm said a large portion of my team is going 16:14:41 i'm told 16:14:43 E_COFFEE 16:15:26 i think as the new ptl you should try to be there too :D 16:15:33 i'll do what i can 16:16:06 i know, was just joking 16:16:31 :D 16:17:20 no response yet if we get these working and fishbowl sessions for our projekt 16:17:24 project 16:17:36 not sure how the process works 16:18:05 j^2 might remember 16:18:15 :-O 16:18:20 :o 16:18:30 oh! 16:18:45 ha, yeah so ttx emailed all the PTLs 16:18:52 asked for everyone to say what they wanted 16:18:55 speaking of the devil :D 16:19:03 so ideally jklare you got an email? 16:19:15 otherwise i’d contact tom and ask him 16:19:18 yeah, i answered it and am waiting for the response now 16:19:31 nice 16:19:58 if all else fails we can always go to a bar or whatnot in Austin ;) 16:20:09 ahhh i have another quick and ugly topic 16:20:14 j^2 sounds good 16:20:16 i mean... there /is/ 6th street 16:21:02 ba! 16:21:04 bah! 16:21:11 i have much MUCH better places 16:21:31 i've been away from austin for a few years. cut me some slack :D 16:22:00 hi 16:22:15 hey markvan 16:22:41 hi markvan 16:23:04 jklare: we should have the allocation ready on Wednesday 16:23:22 ttx oh cool 16:23:27 ttx thanks for the quick update 16:23:41 as a spoiler, you should get what you asked for :) 16:23:47 :D 16:23:56 ttx amazing :D 16:23:58 you were pretty reasonable 16:24:10 :D 16:24:23 but shh, I didn't say anything 16:24:56 * j^2 looks around, checks the door 16:25:12 :) 16:25:20 the coast is clear! 16:27:26 repo with chefdk 0.11.2 is all kinds of busted on my mac 16:27:37 > 0.9.0 it seems 16:27:43 yeah, i went also back to 0.9.0 16:27:56 0.11.2 has too many changes and breaks too much stuff 16:28:56 :( 16:29:03 ideally, i'd like to get a working repo with newer chefdk before shipping mitaka, but that may be something that slips if the changes are too significant 16:29:04 yeah we’re pushing a lot of fixes recently 16:29:22 I’d wait for 0.12.0 and ship with that 16:29:29 i think we do not need a newer chefdk version 16:29:30 shouldn’t be _too_ long 16:29:44 and upgrading will be a lot of additional work 16:29:49 we don't /need/ one, but release cadence suggests we /should/ 16:30:17 again, nice to have on my part 16:30:35 i would rather release a working set of cookbooks with good documentation and an old chefdk version, than skip parts of the documentation and bury our whole work in fixing rubocop and foodcritic issues 16:31:18 jklare: yup, need to doc this new stuff, +1 16:31:28 i see where you're coming from. like i said, it doesn't have to block shipping mitaka, imo 16:31:51 0.9.0 is new 'enough' for most downstream users 16:32:59 we also need to remove the ec2 api stuff in our cookbooks for mitaka 16:33:20 and maybe point to this external ec2 cookbook 16:34:20 yup. makes sense. if we have support in the newton cycle, i'd like to get that under the umbrella of the project 16:34:37 +1 16:37:34 if i have some time this week, i can take a crack at removing the ec2 api stuff. depends on how busy i am this week 16:44:39 sounds good 16:44:53 i will keep playing around with xenial and the mitaka packages 16:45:40 right on. i've got the centos side handled 16:46:41 great 16:48:48 i think that's everything i have 16:49:09 just a few minutes left if anyone has anything else 16:50:33 have a good one! see you next week 16:50:36 #endmeeting