23:59:55 #startmeeting congressteammeeting 23:59:56 Meeting started Wed Jan 11 23:59:55 2017 UTC and is due to finish in 60 minutes. The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:59:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 23:59:59 The meeting name has been set to 'congressteammeeting' 00:00:07 Hi 00:00:25 hi ramineni_ ! 00:00:30 hi 00:00:49 hi everyone. hope all is well! 00:01:12 thinrichs won’t be here today due to travels. 00:01:42 just a couple items from me today. 00:01:43 Pike PTL 00:01:44 Ocata-3 patches 00:01:44 Ocata-3 QA 00:01:46 anything else? 00:02:02 sounds good 00:02:33 ok then let’s dive right ahead. 00:02:43 #topic Pike PTL 00:03:00 Quick item: 00:03:00 Pike PTL nomination week is Jan 23. Feel free to talk to thinrichs or I if you have any questions about that. 00:04:12 moving on then. 00:04:19 #topic Ocata-3 patches 00:04:26 Any patches to discuss for Ocata-3? 00:05:27 oh and good work everyone for getting ocata-3 patches in! 00:06:15 Here are some patches that seem ready to merge. any thoughts on them? 00:06:27 #link https://review.openstack.org/#/c/401960/ 00:06:37 #link https://review.openstack.org/#/c/399124/ 00:07:01 #link https://review.openstack.org/#/c/404478/ 00:07:19 sorry, slow responses for some patches. I'll check it in today. 00:07:27 #link https://review.openstack.org/#/c/416814/ 00:07:55 np masahito 00:08:15 For reference, here is the list of open patches on congress: https://review.openstack.org/#/q/project:openstack/congress+status:open 00:09:04 ekcs: I'll also check today .. 00:09:23 ekcs: ocata 3 is Jan 23 right 00:09:40 awesome. 00:11:10 I want to complete one more patch also for ocata 00:11:14 ramineni_: yes. jan 23. but since the time between ocata-3 and RC1 is so short (and also because many things become hard to change after O3), we’re aiming to merge everything by Jan 16 to have a full week of testing and fixing. 00:11:50 based on lessons learnt from last cycle’s madness at the end. 00:11:57 hmm 00:12:45 Ok .. 00:14:07 it’s not set in stone of course. let’s talk more about it either here or later if we need to adjust = ) 00:14:34 Sure .. Thanks 00:14:49 one patch I want to bring up. #link https://review.openstack.org/#/c/410705/ 00:16:03 I haven’t been following closely, but is this something we can discuss and reach consensus on ramineni_ and masahito ? 00:17:53 My comment on this patch is a question. 00:19:01 Couldn't get time to look into how to do it ..I think if heartbeat has subscription info I can use to list all subscribers right 00:19:14 It seems to work well if Congress is deployed in one node. 00:20:36 Yes ... I'll look into how to implement masahito comment 00:20:51 I'll update the patch this week 00:21:22 ok. I’ll take a look too. 00:22:46 ok let’s move on then if there’s nothing else to discuss here. 00:23:17 #action review open patches for Ocata-3 aiming to merge by Jan 16 00:23:47 #topic Ocata-3 QA 00:25:07 Like we’ve discussed, we’d like to do more testing on Ocata-3 than last cycle, both because it’s a very short time between O3 and RC1, and because we want to avoid repeating all the difficulty we had in fixing late breaking bugs late in the cycle. 00:26:27 To help us on that front, I setup some QA tasks here: https://bugs.launchpad.net/congress/+bugs?field.tag=qa 00:27:48 The idea is to start manually and aim to automate as much as possible based on the manual work. 00:28:39 It’ll help us have a much more rigorous testing process for future releases. 00:29:16 so feel free to sign up for tasks. (the time frame for these tasks is between Jan 16 and Jan 23). 00:29:41 masahito: I remember you mentioning another QA task we should do, but I forgot what it was. 00:29:53 pulling up notes from last meeting. 00:30:25 ekcs: it's about fail over of datasource service 00:31:13 ekcs: Should I report it as bug report to track the status? 00:32:03 sure go for it. thanks! and please tag it with qa so we can easily find it. 00:32:20 got it. 00:32:30 oh and thanks aimeeu for volunteering for the standalone install task! 00:32:51 you're welcome. I should be committing a script early next week. 00:33:03 thanks aimeeu 00:33:03 for single-node install at least 00:33:04 any questions or comments or thoughts around QA for ocata? 00:33:22 aimeeu: and dashboard part ..Are we targeting for ocata? 00:34:00 I thought ekcs was concerned about time to test so I am targeting Pike 00:34:23 you mean moving to a new repo? 00:34:26 yes 00:34:30 aimeeu: oohok 00:35:18 my workload in OPNFV is pretty heavy right now so limited time 00:35:29 so my thinking was if we can create the new repo without disturbing the current way it works, then we can try to do it for O if there is time. 00:36:02 creating the repo and replicating code I think is the easiest part 00:36:13 that way it’s available, but the old one is also available so we don’t need to thoroughly test the new one. 00:36:39 making sure both projects deploy correctly and dashboard is registered with Horizon is more time consuming 00:36:54 and if so, the new repo and progress at basically any schedule we find convenient without us depending on it to be ready at any particular time. 00:37:33 I agree. I keep thinking of more deployment scenarios that would need to be tested 00:37:40 so my main concern is keeping the existing thing working in the mean time. 00:37:57 ekcs: +1 00:38:52 ekcs : if we split the repo .. we have to do all the release work by Jan end for the new repo too? 00:39:52 ramineni_: I’m not sure. My guess would be we can start the new repo without being forced to include it in the release right away. 00:40:10 ekcs: yes 00:40:22 ekcs : ok ..Then should be fine 00:41:03 one more thing on Ocata. please go ahead and target things for Ocata in launchpad for the things you want in ocata. that way we can all get a big picture of what is left to be done. very helpful in planning. 00:41:37 and feel free to ask me to make those changes for those who don’t have permissions on launchpad. 00:42:52 ok then. let’s move on to open discussion. 00:42:56 #topic open discussion 00:44:51 I reported a couple bugs on postgres deployment. #link https://bugs.launchpad.net/congress/+bugs?field.tag=postgres 00:45:46 both seem to boil down to a mysterious 401 error when contacting datasource. I’m going to look into it some more, but throwing it out here too to see if someone happens to have a clue. 00:47:58 ekcs: do you know how to deploy openstack with mysql? I've not tried it. 00:48:24 masahito: you mean using devstack or not? 00:48:31 using devstack. 00:48:34 by default devstack uses mysql. 00:48:51 oops, sorry. s/mysql/postgresql/ 00:49:09 to change to postgres you add the following to local.conf 00:49:11 disable_service mysql 00:49:11 enable_service postgresql 00:49:24 before stacking. 00:49:34 good to know. thanks! 00:51:13 ok if there’s nothing more to discuss, shall we end early? 00:51:27 I’ll wait a couple minutes = ) 00:52:48 ok have a great rest of the week, and see you all later! 00:52:55 #endmeeting