09:00:02 <gmann> #startmeeting qa
09:00:03 <openstack> Meeting started Thu Oct 20 09:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:00:06 <openstack> The meeting name has been set to 'qa'
09:00:14 <gmann> hello, who are here today?
09:00:17 <dmellado> o/
09:00:38 <gmann> dmellado: hi
09:00:47 <gmann> let's wait for few more min
09:00:52 <dmellado> hi gmann, I hope that there would be more than just us
09:00:55 <dmellado> yes xD
09:00:58 * masayukig is read-only mode
09:01:06 * dmellado kinda like that
09:01:16 * dmellado needs to finish some slides for the summit too...
09:01:16 <gmann> hope so
09:01:27 <gmann> dmellado: nice
09:01:41 <dmellado> how're you doing gmann? all set for your trip?
09:01:49 <gmann> dmellado: yea
09:02:00 <jordanP> hi
09:03:05 <gmann> jordanP: hi
09:03:27 <tosky> hi
09:03:35 <gmann> let's start and we can wrap up fast
09:03:38 <gmann> tosky: hi
09:03:40 <dmellado> +1
09:03:42 <gmann> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_October_20th_2016_.280900_UTC.29
09:03:47 <gmann> ^^ today agenda
09:04:15 <gmann> #topic Next Summit
09:04:28 <gmann> #link http://lists.openstack.org/pipermail/openstack-dev/2016-September/103560.html
09:04:44 <gmann> as we know we have 3fb 4wr room
09:04:54 <gmann> and oomichi assigned the sessions also
09:05:05 <gmann> #link https://etherpad.openstack.org/p/ocata-qa-summit-topics
09:05:23 <gmann> we need to prepare each sessions etherpad for discussion
09:05:50 <gmann> I have to start mine, may be tomorrow
09:06:03 <gmann> so request all sessions leaders to fill those
09:06:15 <dmellado> yep, I spoke with oomichi about it yesterday, will fill asap
09:06:31 <gmann> dmellado: great
09:07:08 <gmann> anything else on this?
09:07:46 <dmellado> gmann: well, I guess I cc'ed all the interested guys
09:07:57 <dmellado> but I created a hangout group to keep track of this and the dinner
09:08:01 <gmann> you replied to oomichi mail ?
09:08:06 <dmellado> feel free to join if interested using this link
09:08:08 <dmellado> yes
09:08:11 <dmellado> https://hangouts.google.com/group/Nt2aSq1dzPvojrdY2
09:08:20 <gmann> dmellado: great, ll join
09:08:35 <gmann> but i did not get mail seems
09:08:43 <dmellado> let me recheck the CC
09:09:21 <dmellado> gmann: oh, it seems you weren't on CC
09:09:24 <dmellado> let me put you as well
09:09:34 <gmann> ok
09:09:52 <gmann> #topic Specs Reviews
09:10:05 <gmann> #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z
09:11:04 <gmann> so on spec we have mainly policy one and stable-fixtures and resource
09:11:17 <gmann> we will be discussing the policy testing in summit
09:11:42 <gmann> but feel free to add review comments on those which are always helpful before discussion
09:12:06 <gmann> tempest-resources seems in good shape
09:12:14 <gmann> although need to review the latest version
09:13:05 <gmann> let's move next
09:13:08 <gmann> #topic Tempest
09:13:22 <gmann> #link https://review.openstack.org/#/q/project:openstack/tempest+status:open
09:13:42 <gmann> unit tests was failing on gate due to testscenario removal
09:14:05 <gmann> jordanP: fixed is in now and gate should be fine
09:14:08 <gmann> #link https://review.openstack.org/#/c/389055/
09:14:45 <gmann> other review we can keep doing
09:14:53 * gmann need to spend more time on reviews
09:15:04 <gmann> Bug tracking -
09:15:06 <gmann> #link https://github.com/oomichi/bug-counter#current-graph
09:15:32 <gmann> this is something we need to cleanup and can decide in summit about bug triage strategy
09:15:49 <gmann> we defiantly need some/group ownership on those
09:15:56 <dmellado> +1, there are a few ones around, we can discuss that at the working sessions
09:15:57 <tosky> a steady number of inprogress does mean that they are not really in progress
09:16:07 <dmellado> and I think it'd be a good thing to tackle
09:16:24 <gmann> true
09:16:55 <gmann> tosky: many might be with abandon patch and we might need to remove in progress tag there
09:17:56 <gmann> anything else on bug things or tempest
09:18:47 <gmann> one I have is stress tests repo
09:19:02 <gmann> #link https://github.com/ghanshyammann/tempest_stress
09:19:26 <gmann> I am creating a separate repo for that but facing some issue on config options registration
09:19:49 <gmann> I do not want to use plugin in this to register only config so want separate registration for those
09:19:49 <dmellado> gmann: do you have any review or code around?
09:20:04 <gmann> but seems like it default all parsed tempest options
09:20:10 <gmann> dmellado: not yet
09:20:32 <gmann> plan is to make it run and give this as a alternate to tempest stress
09:20:44 <dmellado> cool, I see, maybe you can put it up even on its current state so we could all have a look and collaborate
09:20:49 <gmann> and depend of usage we can later add this into openstack repo
09:21:04 <dmellado> let's have a chat about this at the summit in any case
09:21:06 <gmann> dmellado: sure, that will be helpful
09:21:10 <gmann> yea
09:21:33 <gmann> and other imp thing going is running tempest run workflow  in gate
09:21:42 <gmann> there is patch for that
09:22:05 <gmann> #link https://review.openstack.org/#/c/355666/
09:22:16 <masayukig> (SUPER WIP)
09:22:18 <gmann> masayukig: is debugging the stable branch issue
09:22:23 <gmann> masayukig: yea :)
09:22:38 <dmellado> also,when the stress framework is moved we'll have to change the gate too
09:22:39 <gmann> after that it will be nice to run gate with recommended tempest workflow
09:22:47 <gmann> dmellado: yes
09:23:07 <gmann> dmellado: as of now we will remove from gate also and if that gets added in openstack repo then test in gate too
09:23:18 <dmellado> gmann: ack, sounds fine
09:23:45 <masayukig> one thing about bug tracking, we already can see daily json files. e.g. #link http://status.openstack.org/bugday/tempest-bug-stats-daily.json but graph UI is not landed yet.
09:24:06 <masayukig> I'm sorry for my interruption
09:24:18 <gmann> masayukig: please go ahead
09:24:33 <gmann> graph UI is landed means?
09:25:17 <masayukig> I mean like this page http://status.openstack.org/bugday/
09:25:19 <gmann> masayukig: so current one is not correct
09:25:22 <gmann> #link http://status.openstack.org/bugday/
09:26:06 <masayukig> Now, we just have json data files only.
09:26:50 <gmann> so number on graph is fake
09:27:08 <masayukig> fake?
09:27:22 <gmann> masayukig: i mean dummy
09:27:39 <gmann> like in tempest graph it shows ~50 new bug
09:28:06 <masayukig> yeah
09:28:40 <masayukig> it's not true?
09:29:17 <gmann> seems true
09:29:30 <gmann> so you mean there will be more enhancement in graph there
09:29:43 <masayukig> yeah,
09:29:44 <gmann> masayukig: sorry for hacking your read-only mode
09:29:48 <gmann> i see
09:30:06 <masayukig> there's a patch
09:30:14 <dmellado> heh
09:30:14 <masayukig> https://review.openstack.org/#/c/372581/
09:30:36 <masayukig> oh, you already reviewed gmann
09:30:39 <gmann> masayukig: ahh i +1 that. sorry forgot about that
09:30:41 <gmann> :)
09:30:46 <gmann> i thought that got landed
09:30:47 <masayukig> :)
09:30:50 <masayukig> heh
09:30:56 <gmann> masayukig: Thanks, thats really nice
09:30:57 <masayukig> no worries
09:31:21 <masayukig> thanks, go ahead
09:31:27 <gmann> any more on tempest or bugs ?
09:31:48 * masayukig is about to go
09:32:06 <gmann> pinged on infra for +A
09:32:12 <gmann> ok, let's move
09:32:27 <gmann> we will skip DevStack + Grenade if nothing
09:32:45 <masayukig> gmann: thanks :)
09:32:47 <gmann> openstack-health too if masayukig is already gone
09:32:55 <dmellado> masayukig: get some rest ;)
09:33:16 <gmann> #topic Critical Reviews
09:33:29 <gmann> any critical review to review on priority ?
09:34:08 <gmann> let's jump to open then
09:34:12 <gmann> #topic Open Discussion
09:34:26 <gmann> so next week we will be meeting at barcelona
09:34:41 <gmann> so all have a safe and nice journey
09:34:49 <gmann> anything else from anyone
09:34:54 <jordanP> I'd like to proceed with https://review.openstack.org/#/c/380988/ (remove stress framework) asap
09:35:07 <dmellado> same there, please do remind that there's a dinner scheduled on Thu at 20:30 if you're interested ;)
09:35:17 <gmann> jordanP: ok, i was thinking to mention about new repo
09:35:24 <gmann> but that is not in work state
09:35:40 <gmann> so i am thinking to merge your one and later to mention if needed
09:35:51 <dmellado> gmann: could you publish your work into some repo
09:35:57 <dmellado> and then we can drop stress on tempest
09:36:06 <masayukig> ah, one thing about o-h, we wrote a graph lib and started to use it now. But it's still rough. http://status.openstack.org/openstack-health/ If you find a bug, please report it to the launchpad.
09:36:08 <dmellado> I mean, even if it's not into working state yet
09:36:10 <gmann> dmellado: #link https://github.com/ghanshyammann/tempest_stress
09:36:12 <dmellado> we can at least point them to it
09:36:15 <jordanP> gmann, I don't see why you are creating that new repo. Stress tests has been abandonned for months or years so why keep it alive, even somewhere else ?
09:36:22 <masayukig> see you guys :)
09:36:27 <dmellado> bye masayukig
09:36:43 <dmellado> jordanP: IIRC mkoderer__ said that there were some people still using them
09:36:45 <gmann> jordanP: plan while doing abandon was to create new repo and if any user
09:36:50 <dmellado> and in any case it won't hurt to have them around
09:37:05 <gmann> yea and if user then we add that as separate repo under qa project
09:37:11 <jordanP> well, it's up to you guys, but if people are interested, let them do the work
09:37:21 <dmellado> but if gmann has the repo around I'd say +1 to deprecate now
09:37:21 <gmann> masayukig: see you
09:37:26 <jordanP> we can't carry around to the maintenance for everybody
09:37:27 <dmellado> and if anything is interested, have them join the effort
09:37:34 <dmellado> wdyt about this approach?
09:37:44 <dmellado> /s/anything/anyone
09:37:55 <jordanP> I don't care, I just want this to be gone :)
09:37:55 <gmann> yea but let's wait if anyone using that
09:38:08 <gmann> in that case we should have some alternate
09:38:14 <dmellado> jordanP: gmann
09:38:18 <gmann> if no one use then its all safe to remove
09:38:21 <dmellado> could you guys send an email to the ML about it?
09:38:23 <dmellado> just in case?
09:38:26 <jordanP> no need for alternative since nobody is using this
09:38:28 <jordanP> we already did !
09:38:30 <gmann> and no need to keep anywhere
09:38:30 <jordanP> in february
09:38:34 <dmellado> oh, true!
09:38:51 <gmann> well we do not know if no body use thats our assumption
09:39:08 <jordanP> tempest code base is too big, we have areas where no one is able to review stuff
09:39:23 <jordanP> if people want to help, find let them help
09:39:26 <gmann> anyways thats almost ready and i do not feel any harm to maintain for some time
09:39:29 <jordanP> *fine
09:39:39 <dmellado> sure
09:39:45 <gmann> jordanP: i am not saying to keep in tempest
09:39:56 <jordanP> it's up to you, if you find time to manage several repos and do tempest reviews, I am happy
09:40:04 <gmann> defiantly we will remove code from tempest
09:40:13 <gmann> jordanP: :), let's se3e
09:40:13 <jordanP> ok then
09:40:15 <gmann> see
09:40:43 <gmann> so how about mentioning that repo there in reno and readme ?
09:40:54 <gmann> i will work in parallel for its working
09:41:16 <gmann> so that people get to know from release note
09:41:23 <dmellado> gmann: cool
09:41:49 <jordanP> no, I am not mentionning this in reno
09:42:20 <jordanP> the reno will be there for months and the other project is not even there
09:42:24 <dmellado> jordanP: well, I think that dropping the stress framework is worth mentioning a reno
09:42:27 <gmann> then how we will publish that we maintain a separate repo in case anyone want to use ?
09:42:30 <dmellado> and IIRC you had that in your patch, didn't you?
09:42:35 <jordanP> it's already in the reno
09:42:40 <jordanP> but not the mention to the other repo
09:42:44 <dmellado> oh, I see
09:43:01 <jordanP> if there's interest in the other repo, then we will update the readme
09:43:14 <gmann> anyways let's review on patch
09:43:17 <gmann> sure
09:43:57 <gmann> anything else to discuss?
09:44:11 <gmann> or we can close meeting little bit early
09:44:33 <dmellado> I guess that'd be it for today, at least for me
09:44:43 <gmann> ok
09:44:44 <gmann> 3...
09:44:44 <dmellado> safe travels everybody! see you next week!
09:44:49 <gmann> 2..
09:44:52 <gmann> 1.
09:44:54 <gmann> see you
09:44:56 <gmann> Thanks all
09:44:59 <gmann> #endmeeting