Tuesday, 2017-07-18

*** amalagon has joined #openstack-outreachy01:16
*** amalagon has quit IRC01:20
*** nikhil_ has joined #openstack-outreachy02:06
*** samueldmq_ has joined #openstack-outreachy02:06
*** nikhil_ is now known as Guest7866902:06
*** samueldmq has quit IRC02:13
*** nikhil has quit IRC02:13
*** samueldmq_ is now known as samueldmq02:14
*** Guest78669 is now known as nikhil02:14
*** amalagon has joined #openstack-outreachy02:17
*** amalagon has quit IRC02:21
*** rodrigods has quit IRC02:43
*** rodrigods has joined #openstack-outreachy02:55
*** amalagon has joined #openstack-outreachy03:47
*** amalagon has quit IRC04:27
*** amalagon has joined #openstack-outreachy05:39
*** amalagon has quit IRC05:43
*** amalagon has joined #openstack-outreachy07:27
*** amalagon has quit IRC07:32
*** rossella_s has quit IRC08:36
*** rossella_s has joined #openstack-outreachy08:39
*** amalagon has joined #openstack-outreachy09:15
*** amalagon has quit IRC09:20
*** Eva-i has quit IRC09:32
*** raildo has joined #openstack-outreachy11:03
*** amalagon has joined #openstack-outreachy11:03
*** amalagon has quit IRC11:08
*** mine0901 has joined #openstack-outreachy11:56
*** amalagon has joined #openstack-outreachy12:51
*** amalagon has quit IRC12:56
*** rossella_s has quit IRC14:20
*** rossella_s has joined #openstack-outreachy14:22
*** amalagon has joined #openstack-outreachy14:40
*** amalagon_ has joined #openstack-outreachy14:41
*** amalagon has quit IRC14:44
*** mine0901 has quit IRC14:57
*** lwanderley has joined #openstack-outreachy16:23
raildoping rodrigods lwanderley17:30
lwanderleyhi o/17:31
raildojust wait for a few minutes to see if rodrigo can join us today :)17:32
lwanderleycool17:32
raildo#link https://etherpad.openstack.org/p/outreachy-leticia17:33
raildook, so we can start17:34
raildo#topic project progress17:34
raildolwanderley, I saw that you sent the patch for the CI job17:35
raildorodrigods, give a great feedback on it17:35
lwanderleyyeah, i did17:35
lwanderleyyeah, i saw that, could you clarify that feedback?17:35
raildosure17:36
lwanderleyi was trying to find an example of CI job running tempest but i could not find any17:36
raildoso, we have to approaches for this case, we can have this job running only the keystone tests on tempest,  track this behavior to see if everything is ok for now17:37
raildoand then, later send a change to extend to the job run all the tempest tests for all the services and coverage the use case that he mentioned in your patch17:38
raildoso would, we can decide to have a "checkpoint" that all keystone tests are running ok, and then go to all the tempest tests17:39
raildoor, just run the whole bunch of tests on tempest17:39
raildoand see the result17:39
lwanderleyok, so that we are going to test running all the tempest tests is if all the services can authenticate with each other?17:40
raildolwanderley, is it more clear for your?17:40
raildokind of, the main gap that rodrigo mentioned was the user/group tests, looks like this tests are not inside the keystone repo17:41
raildoand we have ldap involved on this tests17:41
lwanderleyyeah they aren't17:42
raildoso, we need to cover this tests on this job17:43
lwanderleyright now i am trying to run all tempest tests that use keystone and the user/group tests are actually inside tempest17:43
lwanderleyas rodrigods said17:43
lwanderleyok, it's a lot clearer now17:43
raildoactually you're running the keystone plugin, not all tempest tests17:44
raildoit's more a design question than a right/wrong question17:45
lwanderleyok17:45
lwanderleyi meant that right now on my vm, haha17:46
lwanderleythe CI job is running the keystone plugin only17:46
raildo++17:46
raildoI believe that a good test for you will be execute all the tempest tests on your env17:47
raildoand see if everything is ok (this could take a while)17:47
raildoif we verified that all the tempest tests are ok with this change, makes sense test the whole tempest on this job right now17:47
lwanderleyi am trying to do that, just having a bit of trouble with tempest configuration17:48
raildoif we have some issue, we can keep on this way and work to fix the other issues17:48
raildothe tempests tests take more than 1 hour17:48
raildoso I suggest do this later :P17:48
lwanderleyhahha ok17:48
raildook so, the next steps that I see will be run this tempest tests so we can decide which decision we will take17:50
raildobesides that, we have to ask for review on the devstack plugin17:51
raildoso I was thinking on be present in the next qa meeting17:51
raildohttps://wiki.openstack.org/wiki/Meetings/QATeamMeeting17:51
raildonext thursday17:51
raildoso, we can ping the qa community to take a look on this patch17:51
lwanderleycool17:52
raildolwanderley, if you have some free time to attend this meeting would be great17:52
lwanderleyThursday at 17:00UTC?17:53
raildoyeap17:53
raildo14:00 local time17:53
lwanderleycool, i will be there17:53
raildogreat17:54
raildolwanderley, anything else that you want to discuss?17:54
lwanderleyso i should keep trying to run tempest tests?17:55
raildoyeap, if you keep having issues with this, ping us on irc17:55
lwanderleyok, thanks!17:55
lwanderleyi think that's all, for now17:56
raildobut before take a moment to see the tempests docs about it, tempest it's not a trivial case sometimes :)17:56
lwanderleygood, thanks, i will17:56
raildolwanderley, ok, so great progress at this moment, good luck and a great week17:57
lwanderleyraildo thanks, a great week for you too!17:57
*** lwanderley has quit IRC18:13
*** deep-book-gk_ has joined #openstack-outreachy19:19
*** deep-book-gk_ has left #openstack-outreachy19:21
*** raildo has quit IRC20:48

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!