22:00:42 <gmann> #startmeeting qa
22:00:42 <openstack> Meeting started Thu Jun 11 22:00:42 2015 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:00:46 <openstack> The meeting name has been set to 'qa'
22:00:55 <gmann> Hi, who all here today?
22:01:04 <hogepodge> o/
22:01:20 <dkranz> o/
22:01:52 <gmann> hi  hogepodge dkranz
22:01:52 <dpaterson> o/
22:01:57 <gmann> Let�s start meeting
22:02:13 <gmann> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_June_11th_2015_.282200_UTC.29
22:02:20 <gmann> ^^^ Today's agenda
22:03:22 <gmann> #topic Specs Reviews
22:03:33 <gmann> Let�s discuss spec reviews.
22:03:41 <gmann> Does anyone have any open spec review to discuss?
22:03:51 <dpaterson> #link https://review.openstack.org/#/c/138785/
22:04:37 <gmann> dpaterson: this is CLI one.. cool
22:04:52 <dpaterson> si,  need one more +2
22:05:18 <gmann> dpaterson: yes, looks in good shape
22:05:28 <gmann> dpaterson: i will review today
22:05:35 <gmann> dpaterson: Thanks
22:05:38 <dpaterson> gmann: thank you
22:06:38 <gmann> another spec is for external plugin from Matt
22:06:44 <gmann> #link https://review.openstack.org/#/c/184992/
22:07:10 <gmann> please review which might be very imp for other project too
22:07:28 <dpaterson> gmann: will review
22:07:52 <dkranz> gmann: I think Matt was planning to actual do the first cut at the plugin thing
22:07:58 <dkranz> gmann: but he is out next week also
22:08:10 <gmann> dpaterson: thanks
22:08:57 <gmann> dkranz: yes, he is in Tokyo till tomorrow then i think will be in Israel
22:09:54 <gmann> From ML, Ironic-Inspector needs to have their tests
22:10:11 <gmann> that might be useful for them
22:10:27 <dkranz> gmann: there is also this https://review.openstack.org/#/c/178607/
22:11:30 <gmann> dkranz: ya, but not sure we should keep adding tests for non core projects till we move them out in their tree
22:12:04 <dkranz> gmann: yes, I am not sure about that
22:12:31 <gmann> gmann: I will ask Matt about that direction. We planed dinner today :)
22:12:34 <dkranz> gmann: there was a lot of talk about "big-tent" but for many folks what it really means is "small-tent"
22:13:01 <gmann> dkranz: heh, yea
22:13:22 <dkranz> gmann: I am not sure ironic/heat/ceilometer understood the "big tent" meant kicking them out in this way...
22:13:36 <gmann> dkranz: IMO we should not stop till we are ready with plugin and and common stuff in lib
22:13:47 <dkranz> gmann: I agree
22:14:15 <gmann> dkranz: exactly, Ironic guys stated the same
22:14:49 <gmann> anything else on spec
22:15:13 <dkranz> no
22:15:22 <gmann> Let's move on then
22:15:34 <gmann> #topic Blueprints
22:15:48 <gmann> Any open blueprints that we need to discuss or any status updates?
22:16:38 <gmann> I have one
22:16:48 <dkranz> gmann: go ahead
22:16:50 <gmann> "Rearrange-nova-response-schemas" is completed
22:17:03 <gmann> I have marked it completed in LP and spec to Implemented dir
22:17:05 <gmann> #link https://review.openstack.org/#/c/190429/
22:17:09 <dkranz> gmann: great
22:17:33 <dkranz> I have one too
22:18:03 <dkranz> With my change to add networks to the account generator, we should be able to change the non-admin and non-isolated jobs to use test accounts
22:18:25 <dkranz> We just have to make the change in devstack and project-config. But I am not sure of the best way to make the change in devstack.
22:18:44 <gmann> dkranz: cool
22:18:49 <dkranz> The devstack code is not really modular around this aspect
22:19:16 <dkranz> It is easy to change the iniset parts for tempest conf but where to run the account generator is not clear
22:19:48 <gmann> dkranz: ohk
22:20:46 <dkranz> that's it
22:21:20 <gmann> dkranz: i see, may be while configuring tempest - configure_tempest()
22:21:43 <gmann> dkranz: because it is more like building up configure file
22:22:00 <dkranz> gmann: that is the easiest thing but not where the current account creation is
22:22:24 <dkranz> gmann: I guess I can push that up and see what folks say as the easiest way to get feedback
22:22:37 <gmann> dkranz: yea, that will be good
22:22:43 <gmann> dkranz: thanks
22:23:01 <gmann> anyone else from anyone on BP
22:23:44 <gmann> let�s move onto next topic.
22:23:50 <gmann> #topic Devstack
22:24:05 <gmann> sdague, dtroyer: you there?
22:24:11 <gmann> please go ahead on Devstack
22:25:01 <gmann> looks like they are away.
22:25:22 <gmann> anyone have anything on Devstack, otherwise let's move on next topic
22:26:11 <gmann> #topic Grenade
22:26:25 <gmann> jogo: you around?
22:27:24 <gmann> ok, let's move to next topic
22:27:27 <gmann> #topic Bugs
22:27:47 <gmann> #link https://etherpad.openstack.org/p/Tempest-bug-report
22:27:53 <gmann> ^^This week bug report
22:28:26 <gmann> I had triage rotation last to last week but did not get much time due to LinuxCon.
22:28:37 <gmann> dkranz has next week one.
22:28:43 <gmann> #link  https://etherpad.openstack.org/p/qa-bug-triage-rotation
22:28:54 <dkranz> gmann: yes, we need more volunteers
22:29:13 <dkranz> gmann: maybe Matt should send a message to the core team
22:29:17 <gmann> dkranz: yes, last week was empty
22:29:28 <gmann> dkranz: +1
22:29:39 <gmann> dkranz: will ask him.
22:29:55 <tongl_> hi
22:30:26 <gmann> #action Matt to send message to core team about more volunteer on bug triage rotation
22:30:31 <gmann> tongl_: hi
22:30:40 <gmann> anything else on bug
22:30:40 <tongl_> This is Tong Liu from VMware
22:31:29 <gmann> tongl_: please go ahead
22:32:38 <tongl_> I am a technical lead of OpenStack QA team and see if we can contribute to the upstream QA community
22:33:12 <gmann> tongl_: you are most welcome
22:33:46 <gmann> tongl_: please join #openstack-qa channel in case of any help
22:33:57 <tongl_> I found that the upstream tempest scenario is limited, and we are trying to contribute more scenario test
22:34:11 <dkranz> tongl_: excellent
22:34:18 <gmann> tongl_: great
22:35:07 <tongl_> Also, I looked over the tempest plugin extension. It is good idea to have such plugin support.
22:35:13 <gmann> tongl_: if you have bunch of them and need some feedback before starting implementation, you can put a qa-spec first
22:35:51 <gmann> tongl_: yes, that is much needed as project list growing in OpenStack
22:36:22 <tongl_> We found a few areas that are specific to NSX plugin but not common to other vendors. It is good place for this kind of tests
22:37:03 <dkranz> tongl_: I'm not sure what you mean.
22:37:27 <tongl_> for example, router-type, our plugin support three kinds of logical routers, exclusive, shared, distributed
22:38:03 <tongl_> the upstream router tests only test router with default arg
22:38:19 <dkranz> tongl_: I'm not sure if you are saying you want to contribute tests that will not run in the upstream environment?
22:38:44 <gmann> tongl_: you mean only vendor specific tests?
22:38:52 <tongl_> no, no
22:39:15 <tongl_> I mean some are vendor specific but can be skipped if the extension is not enabled.
22:39:35 <tongl_> we want to contributed tests that will run in upstream
22:39:43 <dkranz> tongl_: ok
22:40:07 <tongl_> like distributed router scenario test, that definitely will run in upstream env
22:40:07 <dkranz> tongl_: just was not sure what you meant by "areas that are specific to NSX plugin"
22:40:39 <dkranz> tongl_: ok, great
22:40:45 <tongl_> I mean that are some vendor plugin specific test
22:41:11 <tongl_> but can be skipped if the extension is not supported
22:41:17 <gmann> tongl_: ohk, till they are good to run for upstream and not only vendor specific, will be good in upstream
22:42:19 <gmann> tongl_: Thanks. qa-spec will be good to start if there is something out of scope from Tempest then we can decide there only
22:42:45 <gmann> let's move to next topic
22:42:46 <gmann> #topic Critical Reviews
22:42:57 <gmann> Does anyone have any critical reviews they'd like to bring up?
22:43:37 <tongl_> What's the process of proposing blueprints. We do have a blueprint to improve tempest framework. But we can discuss next meeting.
22:43:41 <dkranz> gmann: https://review.openstack.org/178607 has been sitting with +2 for a long time
22:44:37 <dkranz> tongl_: the easiest thing is to push some text to openstack/qa-specs
22:44:39 <gmann> dkranz: yes, will try to look today or monday
22:44:51 <dkranz> tongl_: https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z
22:45:08 <tongl_> thanks, let's move on to the next topic
22:45:49 <gmann> tongl_: #link http://specs.openstack.org/openstack/qa-specs/
22:46:12 <gmann> I have some reviews for tempest-lib
22:46:41 <gmann> #link https://review.openstack.org/#/c/189549/
22:46:52 <gmann> and its dependent patches
22:47:08 <dkranz> gmann: I will look tomorrow
22:47:12 <gmann> wanted to push those in next lib release
22:47:17 <gmann> dkranz: Thanks.
22:47:36 <gmann> any other reviews
22:48:17 <gmann> let's move on
22:48:26 <gmann> #topic open-discussion
22:48:44 <gmann> any other thing to discuss
22:49:26 <gmann> There is some patches need master tempest-lib to be release
22:49:40 <gmann> as Matt is on vacation and seems like oomichi has permission to release new tag
22:49:49 <dkranz> gmann: good
22:49:50 <gmann> i will ask oomichi to do so if he can
22:50:08 <dkranz> gmann: it would be good if we all had permission and instructions
22:50:51 <gmann> dkranz: yes, agree :)
22:51:07 <gmann> dkranz: let's Matt come back and we can ask him
22:51:35 <gmann> thats all from my side
22:51:41 <gmann> anything else from anyone
22:52:26 <gmann> ok, if there is nothing else, we'll end here
22:52:36 <gmann> Thanks everyone for joining the meeting.
22:52:44 <gmann> #endmeeting