15:59:19 #startmeeting Kolla 15:59:20 Meeting started Wed Aug 30 15:59:19 2017 UTC and is due to finish in 60 minutes. The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:59:23 The meeting name has been set to 'kolla' 15:59:38 #topic w00t for Kolla, cheer for release 15:59:43 o/ 16:00:01 w00t 16:00:22 o/ 16:00:40 o/ 16:00:41 o/ 16:00:56 w00t! 16:01:00 w00t 16:01:13 w00t 16:01:23 wo/o/T 16:01:27 oh, inc0 o/ 16:01:29 \o o/ 16:01:30 -o- 16:01:58 /o\ 16:02:11 \o\ /o/ 16:02:30 o/ 16:02:30 let's start because we'll be busy today:) 16:02:30 wish that was enough to make me thin ;) 16:02:40 #topic announcements 16:03:11 o/ 16:03:12 1. RC-1 week, that means creation of stable/pile 16:03:14 pike 16:03:49 if you need definetly something merged, now's the time to speak up 16:04:09 2. PTG is in 2 weeks 16:04:20 Kolla sessions are last 3 days (Wed-Fri) 16:04:26 hope to see you there! 16:04:58 3. Let's cancel next weeks meeting 16:05:13 since lots of people (myself included) will be traveling for PTG 16:05:29 any community announcements? 16:05:57 #topic PTG schedule (https://etherpad.openstack.org/p/kolla-queens-ptg-schedule) 16:06:11 I've scheduled sessions 16:06:17 changed form a bit this time 16:06:42 instead of putting hours to topics, let's try to have block of time about given field 16:06:52 and discussion inside will be more free-form 16:07:01 just noted talking points 16:07:45 if anyone have any comments about schedule, feel free to make note in etherpad 16:07:49 or tell me 16:08:22 #topic Testing Pike release (https://ethercalc.openstack.org/wdu4nu1hsd4o) (egonzalez) 16:08:27 inc0: do you recommend any cross-projects meetings the kolla team needs to attend/organize Monday and Tuesday? 16:08:29 egonzalez: go ahead 16:08:42 vhosakot: I'll leave it for everyone to decide 16:08:46 inc0: cool 16:08:48 i've created a chart with services we currently deploy 16:08:56 I'll need to prep my own schedule, I'll be happy to share it 16:09:06 please, pick one or various and test them 16:09:14 I am thinking about interop and refstack 16:09:17 inc0, so, 11-12h of Wed is cross-projects between us and TrileO or just us? 16:09:37 duonghq: just tripleo 16:09:55 we'll have some more across the week and I leave Friday unscheduled if we need something 16:10:43 I don't get your point, is it cross-project session? or session of whom? 16:11:20 duonghq: let's talk after Eduardo's topic, I'll restart schedule one 16:11:21 vhosakot, I'll be in the doc cross section with my Kolla hat on 16:11:56 egonzalez: where is this chart? 16:11:58 egonzalez, looks good, very organized 16:11:59 egonzalez: I had similar idea and made note in schedule 16:12:04 i've created a chart with services we currently deploy with ansible 16:12:08 put it in schedule* 16:12:08 #link https://ethercalc.openstack.org/wdu4nu1hsd4o 16:12:13 krtaylor: yeah, I know, will try to attend it. I have a list of cross-project stuff I'll probably attend that helps kolla. 16:12:34 egonzalez, want to have a mention of arm and ppc64le verification? 16:12:40 would be awesome if we have all the services in green 16:12:40 planning to sit with the neutron cats. 16:12:51 I'd add upgrade tested to this too 16:13:10 krtaylor, non x86 are not implemented in ansible yet (AFIK) 16:13:26 egonzalez: not sure it has to 16:13:33 it's just different image to use 16:13:40 yep 16:13:43 we can test 16:13:47 nothing need to be done in ansible 16:13:50 and even if things don't look rosy, it's useful 16:14:05 or green, rather 16:14:24 ah, ansible, got it 16:14:42 krtaylor: you cannot deploy with kolla-ansible? 16:14:47 wanna arm or ppc64le too? 16:15:02 inc0: I'd like to have it there, and ask my team to test and see what comes of it 16:15:09 it is not in our plan to have everything working 16:15:12 already added arm 16:15:14 but I'd like to know how broken it is 16:15:19 thanks 16:15:35 gema, ansible is not a problem, but I have not verified, just not a priority ...yet 16:15:49 krtaylor: understood 16:15:51 yeah, is useful to track what's the current status on the services 16:16:02 if found some service is hard to configure due many dependencies or manual steps, please add documentation if not present 16:16:07 krtaylor: my team has been verifying in a more unstructured way than this sheet, so I'd like to ask them to fill in 16:16:09 egonzalez: we'll need to add Q->P upgrade too 16:16:11 and see what we get 16:16:17 egonzalez: good work 16:16:47 gema, almost the same here 16:17:02 inc0, sure 16:18:02 i'll be working for queens adding a release testing doc, examples, use cases, so we can share to community with easy steps to follow 16:18:15 +1 16:18:34 egonzalez: are you coming to PTG? 16:18:40 inc0, yep 16:18:47 great! let's discuss there 16:18:52 and prepare process for it 16:19:21 can we move on egonzalez ? 16:19:26 sure 16:19:37 #topic PTG schedule (https://etherpad.openstack.org/p/kolla-queens-ptg-schedule) 16:19:46 I'll restart this one as there were questions 16:19:59 duonghq: so Mon and Tue are mostly for cross-project work 16:20:56 besides deployment teams, tripleo+k8s and cinder/ironic on Mon we don't have anything else planned 16:21:14 but I believe we might once we get there, everyone is in release mode now 16:21:44 I saw TripleO + kolla-k8s session is put in Wed schedule? 16:21:55 that's why I also left Friday unscheduled, we'll have room then but that's where we can plan any discussions that came up over the week 16:21:57 right 16:23:45 if we'll run out of time during any discussion or came up with new ideas to discuss, Friday will be bucket for them too 16:25:53 any more questions regarding schedule? 16:27:22 inc0: any way to attend remotely ? 16:27:42 we don't plan anything as it was full of issues last time 16:27:51 also hours will be horrible 16:28:04 keep an eye on etherpads tho 16:28:19 yeah, sure 16:28:40 #topic Release notes check 16:28:56 I'd like if we all would do reno list 16:29:10 and see if any feature is missing from 5.0 release notes 16:29:31 krtaylor: we've added a note about the new archs, you may want to read it 16:29:47 krtaylor: and see if we are missing anything 16:30:35 gema, will do 16:33:53 check both kolla and kolla-ansible 16:34:07 and publish new note if anything is missing 16:34:21 Jeffrey4l: when do we tag pike? 16:34:33 tomorrow i think. 16:34:54 ok, let's make sure to publish missing notes then 16:34:57 before Friday. 16:35:45 rdo pike repos are not ready yet, need to pin pike for binary images, we tag and backport when available or wait? 16:36:05 tag and backport 16:36:09 we can't miss this deadline 16:36:10 egonzalez, we can pin pike after pike branch is created. 16:36:18 sure 16:36:18 we will have rc2 tag. 16:36:40 is there an rc1 tag already we can build from? 16:36:52 Friday is the dead line for tail cycle project in openstack's scheduler. 16:37:17 gema, no. we are going to create rc1 tag tomorrow. 16:37:23 Jeffrey4l: great, thanks 16:38:44 gema: but current master will be almost the same 16:38:54 inc0: yep 16:38:56 so don't let that stop you from testing:) 16:39:08 inc0: I have hrw off tomorrow, so he will build on Friday 16:39:20 cool 16:40:39 allright 16:40:44 #topic open discussion 16:40:48 anything? 16:43:44 guess not 16:43:57 see you in denver, folks 16:43:59 we'll cancel next meeting and PTG comes afterwards 16:44:13 roger 16:44:15 so next meeting will be at 20th 16:44:31 see you in Denver! 16:44:37 #endmeeting kolla