09:00:00 <gmann> #startmeeting qa 09:00:01 <openstack> Meeting started Thu Jan 28 09:00:00 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:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:05 <openstack> The meeting name has been set to 'qa' 09:00:24 <gmann> Hi, Who all here today? 09:00:35 <dmellado> Hi gmann o&/ 09:00:41 <gmann> dmellado: hi 09:00:57 <gmann> masayukig: will join little bit late 09:01:25 <dmellado> no worries, it's only us then? maybe we should wait a bit 09:01:55 <gmann> dmellado: looks like only 2 of us, let's wait for some time to have others 09:01:59 <gmann> dmellado: yea 09:05:26 <gmann> dmellado: may be we can walk quickly and in between other join 09:05:46 <gmann> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_January_28st_2016_.280900_UTC.29 09:05:51 <dmellado> sure 09:05:54 <gmann> ^^^ today's agenda 09:06:09 <gmann> #topic QA Code Sprint 09:06:28 <gmann> Nothing more on this, please add your name in list if panning to join 09:06:40 <gmann> dmellado: anything you have on this? 09:06:53 <dmellado> gmann: this is about the mid-cycle, isn't it? 09:07:02 <gmann> dmellado: yes 09:07:14 <gmann> #link https://wiki.openstack.org/wiki/QA/CodeSprintMitakaBoston 09:07:22 <dmellado> is there any etherpad for this? maybe I can tackle some stuff 09:07:31 <dmellado> I'm still waiting for the ack but I'll check some stuff 09:07:33 <dmellado> let me open it 09:07:51 <gmann> dmellado: yea we have 09:08:05 <gmann> #link https://etherpad.openstack.org/p/mitaka-qa-code-sprint 09:08:19 <dmellado> gmann: just found it, I'll add my name to something ;) 09:08:22 <gmann> all items for code sprint will be on this^^ 09:08:39 <gmann> dmellado: ok 09:08:40 <dmellado> maybe we can migrate the keystone v2 client to tempest-lib, now that the split is dnoe 09:08:59 <gmann> dmellado: yea but we need more i think on v3 also 09:09:27 <gmann> dmellado: i also feel some of them were code duplication but i need to check 09:09:28 <jordanP> O/ 09:09:29 <dmellado> gmann: then I can re-do for v3, as well as clean up the duplicated options that was waiting for v3 to be done 09:09:34 <gmann> if we can optimize more 09:09:36 <gmann> johi 09:09:41 <gmann> jordanP: hi 09:09:42 <dmellado> hi jordanP 09:09:46 <jordanP> hi guys 09:10:02 <gmann> jordanP: we just talking about Code Sprint 09:10:19 <gmann> I think on that, thats all 09:10:21 <masayukig_mob> o/ w/ mobile device, though 09:10:28 <dmellado> hi masayukig_mob ;) 09:10:31 <gmann> #topic Specs Reviews 09:10:35 <gmann> masayukig_mob: hi 09:10:41 <masayukig_mob> Hi all :) 09:11:00 <gmann> #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 09:11:44 <gmann> anyone has any spec to discuss 09:13:03 <gmann> ok let's move on 09:13:04 <masayukig_mob> How about DDT one? 09:13:11 <dmellado> DDT? 09:13:28 <gmann> masayukig_mob: ahh i see, 09:13:30 <masayukig_mob> Yeah, removing the spec 09:13:34 <jordanP> #link https://review.openstack.org/#/c/271149/ 09:13:40 <gmann> #link https://review.openstack.org/#/c/271149/ 09:13:43 <gmann> jordanP: Thanks 09:13:54 <dmellado> thanks jordanP 09:14:09 <gmann> so i think it was concluded not to implement that because of test renaming thing 09:14:25 <jordanP> do you have the policy that only PTL can merge/+A a spec ? 09:14:31 <gmann> masayukig_mob: in that case, we should remove spec. 09:14:45 <gmann> jordanP: no :) 09:15:04 <gmann> jordanP: you can do or i will do. 09:15:05 <masayukig_mob> yeah, true. so if you have an opinion, please put your comment 09:15:21 <gmann> masayukig_mob: yea that will be nice 09:16:19 <masayukig_mob> That's it from me 09:16:31 <dmellado> should we move to the next topic 09:16:37 <gmann> let's move on 09:16:38 <gmann> yea 09:16:43 <gmann> #topic Priority Items 09:16:53 <gmann> #link https://etherpad.openstack.org/p/mitaka-qa-priorities 09:17:13 <gmann> first i want to discuss about M-1 which is microversion testing support 09:17:28 <gmann> now all framewrok and nova v2.2 patches are merged 09:17:52 <gmann> i will start migration to lib so that other project can use like Ironic is waiting for this 09:18:21 <gmann> next one Service Client Migrations 09:18:37 <gmann> so not all the clients migration is done in M-2 and its going on 09:18:44 <dmellado> I'll track keystonev3 split too so we can migrate it asap 09:18:47 <gmann> main concentrate for neutron and keystone 09:18:53 <gmann> dmellado: Thanks 09:19:04 <dmellado> I've seen that oomichi was also working on neutron/routers 09:19:07 <gmann> after microversion migration i can also help on those 09:19:12 <dmellado> but it hsa been stalled for a while 09:19:23 <gmann> dmellado: yea he is doing on neutron clients currently 09:19:28 <dmellado> I could get it if he's not going to work on that anymore 09:20:11 <gmann> dmellado: this one ? https://review.openstack.org/#/c/260319/ 09:20:31 <dmellado> oh, I see, he was doing some work this morning 09:20:33 <dmellado> grat 09:20:35 <dmellado> great 09:20:37 <gmann> dmellado: he is doing that, i saw patch update today 09:20:39 <dmellado> I saw that stalled for a while 09:20:47 <dmellado> checked before jan 26 09:20:48 <dmellado> ;) 09:21:09 <gmann> dmellado: ok 09:21:14 <gmann> next is Tempest Lib Migrations 09:21:24 <gmann> jordanP: saw you need volunteer on this? 09:21:41 <gmann> jordanP: what all was there on this? 09:21:49 <gmann> other than cred and ssh 09:21:59 <jordanP> yes, I am quite busy and have no so much time for other stuff dans reviews 09:22:04 <jordanP> cred is done 09:22:15 <jordanP> ssh almost we need https://review.openstack.org/#/c/264323 09:22:15 <gmann> jordanP: i see, no issue we will help 09:22:21 <dmellado> jordanP: maybe I can get you one xD, what would be the topics? 09:22:21 <gmann> joyea 09:22:30 <dmellado> let's talk after the meeting 09:22:53 <gmann> jordanP: cred are still pending right, we have in tempest itself 09:23:09 <gmann> jordanP: but andreaf has removed almost conf dependency 09:23:13 * masayukig is at home now 09:23:16 <jordanP> the idea is to move evrything that is in tempest/common to tempest-lib 09:23:28 <gmann> jordanP: i see 09:23:32 <jordanP> yes, cred is not done but it has been "decoupled" 09:24:32 <gmann> jordanP: ok, i will check later if i can take any or find volunteer 09:24:40 <jordanP> great 09:24:54 <jordanP> it's not super critical though, imo 09:25:10 <jordanP> service spliting and service migration is more important I think 09:25:12 <gmann> next is sshauth one which i think andreaf and jlanoux is working 09:25:15 <gmann> jordanP: yea 09:25:26 <gmann> jordanP: yea, that will be priority 09:25:33 <gmann> and next one is Tempest CLI Improvements 09:25:49 <gmann> masayukig: IT IS m-3 but anything you want to bring up? 09:26:39 <masayukig> #link https://etherpad.openstack.org/p/tempest-cli-improvements 09:26:40 <masayukig> so 09:27:08 <masayukig> not so much progress this time, I think. 09:27:29 <masayukig> legacy commands have been done. 09:28:05 <masayukig> but new commands seems not so good progress. 09:28:19 <gmann> masayukig: yea, list-plugin is helpful for debugging 09:28:46 <gmann> masayukig: ok, may be we will get fats progress in mid cycle :) 09:28:53 <gmann> masayukig: Thanks 09:29:07 <masayukig> gmann: hope so 09:29:16 <gmann> #topic Tempest 09:29:39 <gmann> one is from mtreinish about cleanup tempest 09:29:41 <gmann> #link https://etherpad.openstack.org/p/tempest-refactor-ideas 09:29:51 <gmann> i saw this just before 1 hour. 09:30:05 <gmann> so basically there are ideas about cleanup and refactor tempest 09:30:20 <gmann> which we can start discussing and adding our points/comments on etherpad 09:30:26 <dmellado> gmann: sounds like a nice idea 09:30:47 <gmann> dmellado: yea 09:30:49 <jordanP> +1 ! 09:31:00 <gmann> not sure about last one, stress removal? 09:31:11 <gmann> "The stress framework should be deprecated and then deleted" 09:31:25 <gmann> and other interesting one is move back all into tempest from lib 09:31:36 <dmellado> +1 for improving it 09:31:47 <dmellado> I've heard people saying 'don't use tempest stress' use rally 09:31:51 <jordanP> "The stress framework should be deprecated and then deleted" Who is using it ? 09:31:52 <masayukig> cool! 09:31:58 <gmann> anyways i do not have much on those but we will start discussing in etherpad and coming meetings 09:32:01 <jordanP> yes, Rally makes a better job at it 09:32:31 <gmann> jordanP: in gate it is being tested, why it would not add much value 09:32:37 <dmellado> we could discuss either to improve or deprecate it 09:32:46 <jordanP> gmann, which job ? 09:32:56 <gmann> jordanP: stress jobs 09:33:07 <gmann> jordanP: i hope this is that one only 09:33:20 <dmellado> but the migration back to tempest makes me wonder if we should stop the initial one to tempest-lib xD 09:33:23 <gmann> jordanP: those are experimental 09:33:51 <jordanP> dmellado, they obviously go together :) 09:33:59 <gmann> dmellado: humm, i think not stop. in any case those will be moved under folder "lib" 09:34:30 <dmellado> gmann: I see your point, valid to me 09:34:33 <dmellado> jordanP: xD 09:34:37 <masayukig> moving to lib is one of the refactoring, IMO. 09:34:40 <gmann> i think only issue we are trying to fix there is to avoid dependency and time for adding new stuff which is needed by new tests 09:34:50 <gmann> which takes time currently due to lib release 09:35:27 <gmann> masayukig: yea, those work still goes on as they makes common interfaces better 09:35:40 <gmann> and we need those in lib or on tempest for external usage 09:36:18 <gmann> I think its all not to have separate repo and keep in tempest for fast work 09:36:48 <gmann> anyways we let's start adding our point there 09:36:52 <gmann> Thanks for all nice inputs 09:37:00 <gmann> anything else on this 09:38:00 <gmann> ok, anything on Tempest side 09:38:17 <jordanP> yes 09:38:24 <gmann> jordanP: please go ahead 09:38:26 <dmellado> I was planning to do some work on the plugin interface for neutron too 09:38:36 <jordanP> some reviews here: https://review.openstack.org/#/q/owner:apetrov%2540mirantis.com+status:open 09:38:43 <gmann> dmellado: for lbaas or neutron repo? 09:38:54 <dmellado> for neutron, api tests and so on 09:39:10 <gmann> dmellado: cool 09:39:38 <dmellado> I'll try to do some draft using the cookiecutter and will follow-up on the channels with you 09:39:46 <gmann> jordanP: sure, i will take look tomorrow after migration of version stuff 09:40:03 <gmann> dmellado: sure. Thanks 09:40:08 <jordanP> thanks 09:40:16 <dmellado> also I'd appretiate some input on this patch 09:40:18 <dmellado> https://review.openstack.org/#/c/259746/ 09:40:29 <dmellado> we can't really get the issue on the failures :\ 09:40:56 <jordanP> dmellado, this test doesn't seem super useful 09:41:04 <jordanP> I think it's already tested 09:41:09 <dmellado> jordanP: where? 09:41:33 <jordanP> everywhere, we have several tests that test security group and communication between servers 09:41:41 <jordanP> and we have a multinode job 09:41:51 <jordanP> or several, thus the feature is already tested implicitely 09:42:04 <gmann> i have not checked that but if its kindda duplicate as per jordanP we should avoid that 09:42:09 <gmann> as that is one of the items for cleanup tempest 09:42:28 <dmellado> this tests covers the functionaly of checking traffic between vms on different hosts 09:42:34 <dmellado> afaik, it wasn't really covered 09:43:06 * andreaf sneaks in 09:43:14 <dmellado> hi andreaf ;) 09:43:23 <gmann> andreaf: hi 09:43:32 <masayukig> andreaf: o/ 09:43:32 <andreaf> hi all - sorry I'm late 09:43:39 <gmann> anyways lets check that on review 09:43:44 <gmann> andreaf: np :) 09:43:49 <dmellado> thanks gmann 09:43:55 <jordanP> dmellado, it is. The moment you have a test that boots 2 VMs, there's a chance these VMs are on different hosts and communication between VMs are already tested 09:44:00 <dmellado> jordanP: in any case let me get back to you after speaking with yfried 09:44:36 <dmellado> jordanP: hold on, he's joining ;) 09:44:37 <yfried_> dmellado: ping 09:44:49 <yfried_> dmellado: what did I miss 09:44:50 <gmann> we have recently added new tests to boot VMs on diff host with sch hint 09:44:52 <dmellado> hi yfried_ we were discussing your patch: https://review.openstack.org/#/c/259746/ 09:45:25 <dmellado> and jordanP claims that it's already being tested, at when you run any test that boots 2 VMs, there's the chance that they get spawned on different hosts 09:45:34 <dmellado> so I was wondering if you thought about that too 09:46:18 <yfried_> dmellado: there's a chance. I'm looking for an explicit testing of traffic between compute nodes 09:47:15 <dmellado> jordanP: would that be enough for you? I was also thinking of that, that it might get tested but unless it's specifically there we won't be able to track when it happens 09:47:15 <gmann> yfried_: your one is for multinode only right 09:47:16 <jordanP> yfried_, those kind of tests are super expensive like 2/3min and imo it's already tested (implicitely though) 09:47:39 <dmellado> gmann: yep 09:47:47 <andreaf> dmellado, jordanP: you can boot servers like http://git.openstack.org/cgit/openstack/tempest/tree/tempest/scenario/test_server_multinode.py#n70 to make sure they land on the right node 09:48:20 <gmann> jordanP: but if it explicitly runs for mutlinode then it is ok 09:48:31 <jordanP> yes, but the question is: should we duplicate each and every test to also test the "multinode" case ? 09:48:32 <gmann> as other tests we might not have boot on diff node 09:48:50 <yfried_> gmann: only tests for multiple VMs 09:48:54 <yfried_> jordanP: ^ 09:48:58 <andreaf> jordanP: not every test, but for things that are different on multiple VMs 09:49:01 <jordanP> imo the future of tempest is to have only multinode jobs 09:49:07 <andreaf> jordanP: I think there's value in yfried_ test 09:49:12 <gmann> jordanP: not each and every specific of multinode one 09:49:36 <jordanP> ok guys, you +2 that patch, I won"t :) but I understand you 100% 09:49:49 <andreaf> jordanP :D 09:49:53 <dmellado> xD 09:49:55 <gmann> jordanP: the traffic congestion is one of the key in case of diff host VMS 09:49:58 <jordanP> I am not opposed to it, it's okay 09:49:59 <yfried_> jordanP: I agree that in an avg MN env, the first segcroup test will duplicate the 2nd 09:50:14 <gmann> jordanP: ok :) 09:50:25 <andreaf> jordanP: the alternative could be to change existing SG tests to ensure the boot VMs on different nodes if multiple nodes are available 09:50:27 <gmann> ok lets put comments on that patch if any 09:51:17 <gmann> andreaf: yea or if we can merge those with multinode tests 09:51:26 <gmann> need to check on those 09:51:48 <jordanP> recheck experimental also 09:51:58 <gmann> where all key functionality can be tested in specific multinode tests 09:52:44 <gmann> ok. anything else on Tempest side 09:53:22 <gmann> let's move on 09:53:42 <gmann> skipping DevStack + Grenade if there is nothing on those ... 09:53:58 <gmann> #topic Critical Reviews 09:54:16 <gmann> one i have to unblock stress job - https://review.openstack.org/#/c/271195/ 09:54:37 <gmann> currently experimental stress jobs are failing due to legacy cred 09:55:14 <gmann> any others reviews? 09:56:15 <gmann> Let's move on 09:56:18 <gmann> #topic Open Discussion 09:56:29 <gmann> anything else to discuss. 4 min left 09:56:54 <masayukig> I just want let you know about openstack-health. Now, it has parameters for the resolution, search word, period. 09:57:08 <gmann> masayukig: cool 09:57:08 <masayukig> like this http://status.openstack.org/openstack-health/#/?groupKey=project&resolutionKey=day&searchProject=neutron 09:57:25 <jordanP> yes, it's crazy powerful 09:57:31 <andreaf> masayukig: oh I didn't realise 09:57:31 <andreaf> :) 09:57:42 <masayukig> jordanP: andreaf: yay :) 09:57:54 <andreaf> masayukig: there's another thing we were chatting about with mtreinish yesterday that would be cool to have 09:58:14 <andreaf> click on a point in a graph to open a table of the runs associated to that point, with links to logs 09:58:40 <masayukig> andreaf: yeah, there is a useless parameter, though :-P 09:58:50 <gmann> andreaf: currently link to logs there? 09:59:24 <andreaf> gmann: there is a table with links to the last few runs 09:59:51 <gmann> andreaf: yea, but log links also? 09:59:57 <gmann> i did not find those 10:00:01 <andreaf> yes 10:00:10 <masayukig> it's the time 10:00:11 <andreaf> http://status.openstack.org/openstack-health/#/g/project/openstack~2Fpython-neutronclient?groupKey=project&resolutionKey=day 10:00:12 <gmann> ok, time ups. lets discuss on qa channel 10:00:26 <gmann> #endmeeting