Tuesday, 2018-10-09

*** nguyenhai_ has quit IRC02:18
*** nehaalhat_ has joined #openstack-blazar02:51
*** tetsuro has joined #openstack-blazar02:52
*** nehaalhat_ has quit IRC02:52
*** tetsuro has quit IRC03:58
*** tetsuro has joined #openstack-blazar04:54
*** nehaalhat has quit IRC05:02
*** ShilpaSD has quit IRC05:04
*** ShilpaSD has joined #openstack-blazar05:06
*** masahito has joined #openstack-blazar05:09
*** tetsuro has quit IRC05:34
*** nehaalhat has joined #openstack-blazar05:38
nehaalhatmasahito: Hi05:42
nehaalhatmasahito: I want to know that which CI job will run tempest test cases return in  openstack/blazar-tempest-plugin against any changes made in openstack/blazar project05:43
nehaalhatmasahito:tempest test cases written*05:43
masahitonehaalhat: hi06:01
masahitoThe host reservation scenario tests and API tests are executed to the all patches.06:02
masahitoThe instance reservation scenario is now under implementing. https://review.openstack.org/#/q/status:open+project:openstack/blazar-tempest-plugin+branch:master+topic:bug/171443806:02
*** tetsuro has joined #openstack-blazar06:32
nehaalhatmasahito: ok.. I want to know how these tempest test cases will get run against the patches submitted under openstack/blazar? Is there a CI job?06:54
masahitonehaalhat: Yes, the CI is running under the zuulv3. Blazar uses general OpenStack CI mechanism, not Blazar specific one.07:13
nehaalhatmasahito: Is this the CI job: blazar-devstack-dsvm?07:16
nehaalhatwhich will run tempest test cases07:16
*** tetsuro has quit IRC07:39
*** priteau has joined #openstack-blazar07:48
*** priteau has quit IRC07:50
*** tetsuro has joined #openstack-blazar08:26
*** priteau has joined #openstack-blazar08:45
priteaumasahito: So you think the Tempest run would still succeed without the `self.reservation_client.delete_lease` call at the end, it's just an extra precaution?10:03
priteauWould you be OK with these patches without the lease delete? I think it's better to exercise the code as much as possible. If the presence of terminated leases triggers an issue, it's likely a bug and we would have to fix it10:06
masahitoIMO, both perspectives are important for scenario tests. First one is yours, the next test should work even though the previous lease still exists. Second one is mine, the scenario should be tested in clean environment.10:07
masahitoSure. Ok, I'll remove the codes in next patch set.10:08
priteauIf you really want all tests to be done in a clean environment, I would prefer if tearDown did the cleaning of all existing leases, as you suggested in the meeting10:11
priteauBut I think I prefer the no-cleaning approach, to potentially catch more bugs10:18
*** masahito has quit IRC10:30
*** tetsuro has quit IRC10:35
*** tetsuro has joined #openstack-blazar10:40
*** tetsuro has quit IRC12:07
openstackgerritPierre Riteau proposed openstack/blazar master: Allow terminating a lease in ERROR state  https://review.openstack.org/60415912:22
openstackgerritMerged openstack/blazar master: Handle requirements set to empty strings  https://review.openstack.org/60217318:40
*** priteau has quit IRC21:15

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