09:00:14 #startmeeting qa 09:00:15 Meeting started Thu Feb 9 09:00:14 2017 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:18 The meeting name has been set to 'qa' 09:00:28 o/ 09:00:35 hello, who all here today ? 09:00:37 masayukig: hi 09:00:45 hi 09:01:20 zhufl: hi, nice to see you in meeting 09:01:43 gmann:^-^ 09:01:57 let's wait for few more min to have more people 09:02:09 o/ good morning 09:02:18 DavidPurcell: morning 09:02:59 dmellado chandankumar .. 09:03:14 o/ 09:03:29 tosky: hi 09:03:30 o/ 09:03:36 blancos: hi 09:03:44 let's start as we enough people now 09:03:47 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_February_9th_2017_.280900_UTC.29 09:03:55 ^^ today agenda 09:04:10 dmellado: gmann \o/ 09:04:53 I really want to track ocata cycle items more precisely to avoid missing priority items after good plan 09:04:57 chandankumar: hi 09:05:15 but let's do it from next meeting onwards as we have to plan for PTG 09:05:20 #topic PTG 09:05:30 #link https://etherpad.openstack.org/p/qa-ptg-pike 09:05:40 etherpad link 09:05:52 we have lot of ideas which is nice thing 09:06:22 we still waiting for what all room(with capacity ) we will be allocated 09:06:45 and depending on that we can plan each sessions 09:07:09 but i think we should keep dividing the sessions with time slot based on priority 09:07:35 i will check with andreaf how he want to process each sessions. 09:07:45 time + parallel allocation of sessions 09:08:04 #action gmann to check with andreaf about time allocation of PTG sessions 09:08:22 any feedback ideas about sessions discussions in PTG ? 09:08:27 gmann : yeah, and I think we have some interactive sessions with the other projects 09:08:56 I think we( andreaf? ) need to coordinate for it. 09:09:03 masayukig: yea honestly saying i see very challenges in such sessions 09:09:15 not sure how much people from required projects we will have there 09:09:23 +1 09:09:28 heh, yea 09:10:08 so we have interactive projects section in each one and let's take those and coordinate with other projects via ML or their PTL etc 09:10:30 +1 09:10:33 +1 09:11:04 #action andreaf to send notification/request to ask required projects representative from their PTL/Cores in cross project sessions 09:11:37 i am putting AI for andreaf but all team is there to help and he can divide the resp in case of overloaded :) 09:11:46 gmann: o/ 09:11:52 dmellado: hi 09:12:08 hope you all join PTG 09:12:22 zhufl: hope you get the visa things before PTG dates 09:12:28 gmann: yep, I'll be there. We couldn't get chandankumar visa in time, sadly 09:12:35 oh 09:12:38 dmellado: thanks 09:12:47 oh.. :( 09:12:58 gmann: masayukig 09:12:59 gmann:me may not:( 09:13:00 that said 09:13:04 I can't, but other AT&T folks will be there :( 09:13:10 I'll be trying to put all things in etherpad/irc 09:13:13 chandankumar: even lot of rejection from my india team but fortunately one member for in a week 09:13:16 so he can join online 09:13:30 and hopefully more folks would be able to, too 09:13:30 chandankumar: you applying from channai or delhi ? 09:13:53 DavidPurcell: oh, yea nice to have people 09:14:48 chandankumar: let us know if we can help anything on visa things 09:15:22 another things if you have any other topic to discus feel free to add on etherpad 09:15:31 * dmellado thought that India nationals could apply to ESTA 09:15:43 tbh I was quite surprised when I found out all this visa stuff... 09:16:10 dmellado: yea, its all complicated for me too 09:16:28 zhufl: i added topic of coordinating company owned tests to upstream as you mentioned in mail 09:16:43 and let's try to find the best way to do that 09:16:48 gmann: I'll try to join that discussion too 09:16:50 gmann: yes I see it ,thank you:) 09:17:00 we really encourage people to upstream their tests/ideas 09:17:10 gmann: i was going through mumbai 09:17:11 dmellado: cool 09:17:12 there are quite a few folks working with me who I'm really trying to push upstream 09:17:27 chandankumar: ohk, and they takes time or it is not approved ? 09:17:43 dmellado: great, that is good news 09:17:51 gmann: chandankumar told me it'd just take too long to get it done 09:17:56 gmann: the queue was very long. 09:17:57 and internally we were also a li'l bit late 09:18:00 hummm 09:18:29 anything else to discuss for PTG ? 09:18:46 gmann: I guess also for the PTG 09:18:54 we could try to do a bug smash session 09:19:16 till next meeting at 17UTC we should be ready with all PTG preparation. mainly sessions allocation 09:19:39 dmellado: nice idea, we can try that if we or some people have time 09:19:59 may be worth to have a group working on that and people can join that 09:20:06 that's what I think too 09:20:10 cool. 09:20:33 dmellado: out that idea on etherpad till we just forget after meeting 09:20:41 * dmellado typing as we speak 09:21:00 #action dmellado to add bug smash sessions on etherpad 09:21:09 #topic Specs Reviews 09:21:19 #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 09:21:57 i can see new spec on grenade - 09:21:59 #link https://review.openstack.org/#/c/422170/ 09:22:08 check this out if get time 09:22:22 (o/ Sorry I am late) 09:22:34 jordanP: hi 09:22:56 anyone want to discuss anything specific to current specs 09:23:38 we should start spec writing for PTG sessions where ever applicable 09:23:55 it will utilize our time in PTG more efficiently 09:24:11 yeah, good idea 09:24:18 even etherpad preapration etc can be done as early as possible 09:24:29 yeah, if the "session owners" could fill the etherpad a much as possible that would be great 09:24:38 jordanP: +1 09:24:47 * masayukig nods 09:24:48 so that we know what we want to achieve 09:25:23 so let's iterate the eptherpad may be next early and start finishing all these TODO for each sessions 09:25:48 yeah 09:27:15 +1 09:27:25 sorry guys nework issue 09:27:30 np gmann 09:27:34 :) 09:27:42 can you go ahead with the meeting? if you can't we can handle it ;) 09:27:45 i will be able to spend more time this weekend as no cricket match for me 09:27:59 let's move 09:28:07 #topic Tempest 09:28:29 can we come to an agreement on when to use Nova's security group and when to use Neutron's security group in testcases? 09:28:36 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 09:28:38 In ScenarioTest, create_server uses Neutron's security group, while _create_security_group uses Nova's, that will cause trouble 09:28:54 zhufl: neutron one always for new tests 09:29:08 new tests? 09:29:10 zhufl: we have deprecated security group and all kind of proxy in Nova 09:29:12 yeah, nova one is really legacy 09:29:34 yeah, new tests should use Neutron API for security grouos 09:29:44 old tests should be kept as is 09:29:45 zhufl: we do not want to completely remove from existing tests as those are deprecated not removed yet 09:30:11 even for image volume things also new tests should use direct API not nova proxy 09:30:27 oh, and if neutron's security group is not enabled? 09:30:43 if neutron's security group ext is not enabled 09:30:55 zhufl: it means skip the tests as cloud is what with no sec group 09:31:05 and on gate we make sure we have those enabled 09:31:11 yeah, probably skip the tests 09:31:37 ok, I see. that will be simple then 09:31:43 but test should have logic to skip if required extension is not there 09:31:50 yes 09:31:58 so that tempest can be able to run on a type of cloud 09:32:12 yep, that should be dealt with a skip decorator 09:32:22 and shall we change using Nova' security group to using Neutron's in old testtests? 09:32:40 yea or in skip method if it depends on all tests in that class 09:33:18 I see 09:33:23 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 09:33:34 these are open reviews in tempest ^^ 09:33:59 keep the good work as we are doing and keeping review frequency in good pace 09:34:53 anything on tempest side before moving to bug things 09:35:39 nope from me 09:35:46 ok let's move then 09:35:49 Bug Triage. 09:36:03 #link https://etherpad.openstack.org/p/ocata-qa-bug-triage 09:36:28 #link https://etherpad.openstack.org/p/tempest-weekly-bug-report 09:36:28 #topic Bug Triage 09:36:38 seems like andreaf had this week 09:36:42 masayukig: thanks 09:36:54 gmann : but it doesn't work.. :-o 09:37:11 heh 09:37:25 #topic Bug Triage 09:37:29 :) 09:37:36 :) 09:37:41 seems like we have 4 new bugs 09:37:51 ll check those 09:37:59 chandankumar: seems you have next week one ? 09:38:28 the last rotation for Ocata 09:38:48 and we will try to make NEW as 0 before we release Ocata 09:39:24 masayukig: whats the deal with this - https://github.com/oomichi/bug-counter#current-graph 09:39:42 i feel we should start a bug dashbaord like other team. 09:39:48 what you guys thinks ? 09:40:12 gmann : bug dashboard? 09:40:13 I think it'd be a nice addition 09:40:23 on top of openstack-helath, of course ;) 09:40:28 masayukig: like review dashboard kindda 09:40:59 btw, masayukig if you get the time at the PTG I'd like to talk with you about some possible enhancements :D 09:41:00 what's a bug dashboard ? 09:41:08 dmellado: not o-h, i was thinking which tells us weekly progress and critical bugs and imp one very clearly 09:41:09 a link ? 09:41:11 gmann: could you post an example of an existing one? 09:41:26 let me check 09:41:27 like this http://status.openstack.org/bugday/ ? 09:42:35 we are at the bottom of the page already 09:42:41 humm 09:43:09 this is graph one, i was talking about other one 09:43:23 but ll take time to have example link 09:43:37 i will search and let you all know later 09:43:40 gmann: maybe we can follow up on this on the m-l? 09:43:45 yea 09:43:53 ok 09:44:02 #action gmann to check and ask bug dashboard feedback in team 09:44:14 #topic DevStack + Grenade 09:44:21 anything on devstack and grenade ? 09:44:47 seems nothing 09:44:49 #topic openstack-health 09:44:54 masayukig: please go ahead 09:45:14 the angular1.6 issue was resolved, so, 09:45:27 I asked myself yesterday 'when was the last devstack failure I faced on my laptop ?' And i can't remember, devstack is way more stable than 2 years ago 09:45:27 the gate is now healthy :) 09:45:51 jordanP : yeah 09:45:52 jordanP: cool. 09:46:09 masayukig: thanks for fixing and making gate good 09:46:21 masayukig: we have session on o-h feedback for PTG ? 09:46:30 i forgot if we have in list on etherpad 09:46:39 gmann : heh, I did nothing, though. ah, yeah, 09:46:58 gmann : looks good to me 09:47:09 may be quick sessions will be good to see what extra people expect from o-h 09:47:15 jordanP: on devstack I guess there's more issue on the plugins than on the main devstack 09:47:18 ;) 09:47:26 I had an issue while using devstack + manila + sahara 09:47:36 but only if I had the two plugins 09:47:44 erf, yeah, I can imagine 09:47:52 dmellado: plugins never be perfect :) 09:47:57 we know tempest one also 09:48:07 ok, anything else masayukig ? 09:48:17 nope, thanks :) 09:48:22 * gmann reminds 12 min left 09:48:27 masayukig: thanks 09:48:30 #topic Patrole 09:48:39 DavidPurcell: your turn.. 09:49:05 anything you want to discuss or highlight on Patrole 09:49:06 I'm actually handing the reins to blancos. I'm moving to a less active role in Patrole and she's taking over :) 09:49:24 cool 09:49:32 blancos: thanks 09:50:02 i will also start reviewing those as in Nova we are discussing about providing more roles on policy side 09:50:03 Glad to help contribute :) 09:50:25 so that operator need not to have their own written roles 09:50:34 and that will be good to tests in Patrole 09:51:14 You can use Patrole with default roles or custom ones. 09:51:20 * dmellado needs to leave early today, looking forward to meeting you guys soon! 09:51:32 hehe 09:51:46 trye 09:51:49 true 09:52:00 dmellado: thanks see u soon 09:52:08 * masayukig is waving to dmellado 09:52:15 I really want to add HA project status here for fast progress 09:52:29 and think many people on production testing want that 09:53:02 HA is hard to test.. 09:53:26 yea, but let's see how much we can failure scenario we can cover 09:53:29 many people are testing that, good for them, if they want to start a new project upstream, good. But not in Tempest 09:53:52 yea that we already decided not in tempest and new project got go ahead in barcelona 09:54:06 but seems not much progress after that 09:54:07 yeah 09:54:28 ok let's move as 5 min left 09:54:34 sure 09:54:34 #topic Critical Reviews 09:54:46 any critical imp review from anyone 09:55:55 ok let's move on open discussion 09:55:57 #topic Open Discussion 09:56:12 anything else people want to discuss 09:56:16 hi! o/ I'd like to raise awareness of this bug https://bugs.launchpad.net/tempest/+bug/1592345 09:56:16 Launchpad bug 1592345 in tempest "Import of tempest.test has side-effect that config is parsed" [Undecided,Confirmed] - Assigned to chandan kumar (chkumar246) 09:56:21 I was happy to have 2 strong candidates for the PTL position 09:56:29 long time, valuable contributors 09:56:35 jordanP: :) thanks 09:56:49 jlibosva: sure i will check tomorrow for sure 09:56:53 jordanP : +++++++++ 09:57:00 basically it seems that importing tempest module parses CLI arguments and it blocks development of some in-tree tempest tests in Neutorn 09:57:01 jordanP: agreed! 09:57:08 gmann: thanks! it's been there for a while 09:57:41 jlibosva: this seems confirmed ? any thing to discuss on this ? 09:58:11 gmann: I just wanted to raise it here as it seems to lack attention :) 09:58:29 discussion can happen on the launchpad I guess 09:58:49 jlibosva: i see, ll check tomorrow and reply accordingly if anything needed otherwise push patch 09:59:00 gmann: thanks 09:59:02 we have 2 min left... 09:59:06 1 09:59:23 jlibosva, I've just commented on the bug report 09:59:37 let's meet at Atlanta and all have safe flight. 09:59:50 3... 09:59:55 yep, see you there 09:59:57 2.. 10:00:03 1. 10:00:04 thanks all 10:00:15 * gmann #endmeeting 10:00:23 #endmeeting