Friday, 2019-01-04

*** markvoelker has quit IRC00:54
*** markvoelker has joined #refstack00:54
*** markvoelker has quit IRC00:59
*** tosky has quit IRC01:17
*** markvoelker has joined #refstack01:55
*** markvoelker has quit IRC02:46
*** markvoelker has joined #refstack02:46
*** lifeless has joined #refstack03:10
*** markvoelker has quit IRC08:08
*** markvoelker has joined #refstack08:08
*** markvoelker has quit IRC08:13
*** kopecmartin|off is now known as kopecmartin08:28
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Added python-tempestconf-tempest-devstack-py3  https://review.openstack.org/62286508:39
*** tosky has joined #refstack08:47
toskykopecmartin: in https://review.openstack.org/#/c/627722/, did you mean "Why should *not* we use the older version?"09:22
kopecmartintosky, yes, your question means the same but from the other point of view .. the thing is, there is no description, no explanation of why the change is needed ..09:24
kopecmartinoh wait, there is an answer, a moment09:24
kopecmartinI see, i misunderstood the signs (< > =) :D so the change is updating to the new version09:26
tosky:)09:27
kopecmartintosky, btw, do we need to have a top limit there? <1.2.009:27
toskyit seems that RDO rocky has 1.1.0: https://cbs.centos.org/koji/buildinfo?buildID=23649 and Queens has 1.0.0+: https://cbs.centos.org/koji/buildinfo?buildID=2155309:27
toskykopecmartin: I fear yes, because a new version may introduce stricter rule and introduce sudden failures09:28
toskywhich is not necessarily a bad thing, but I think that normally people are limiting the version of hacking09:28
kopecmartinok, makes sense09:28
toskyfor example, I had to apply some fixes and blacklist few parsing rules when I tried to bump the version on hacking in sahara recently: https://review.openstack.org/#/c/567164/09:30
openstackgerritMerged openstack/python-tempestconf master: Replace tripleo-scenario002-multinode with scenario002-standalone  https://review.openstack.org/62825810:05
*** markvoelker has joined #refstack10:09
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Fix diff in gates  https://review.openstack.org/62818010:09
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Added python-tempestconf-tempest-devstack-admin-py3  https://review.openstack.org/62286510:09
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Added python-tempestconf-tempest-devstack-admin/demo-py3  https://review.openstack.org/62286510:22
kopecmartinarxcruz, chandankumar tosky about the functional tests https://review.openstack.org/#/c/626539/ do we want to have it?10:30
kopecmartinI created tests for --append and --remove based on chandankumar request, suddenly, it turned out to be a role :D10:30
arxcruzi have no idea10:31
kopecmartindo you see benefits in having the role and the job?10:31
arxcruzif we plan to have other tests, yes10:31
arxcruzisn't py2/py3 jobs already cover it ?10:31
toskyas I mentioned: IMHO it must be a separate role10:31
toskywe can discuss whether using on the existing jobs or not10:31
kopecmartinarxcruz, --remove and --append are not  covered in the existing jobs10:32
kopecmartintosky, makes sense having it in a separate role10:33
kopecmartinso maybe we could include the role in our existing jobs and in future if the role becomes bigger we can move it to a separate job?10:33
toskyis there anything else that we test in the main job but where we don't touch all the use cases? Or is it anything else that we don't test of the public CLI (because the internal API should be covered also by unit tests) and that we should?10:35
kopecmartinthere are a few arguments which are not used in our jobs, e.g. --generate-profile, --image-disk-format, --network-id ..10:41
kopecmartinbut i have no idea if it's worth to test them too10:42
openstackgerritMerged openstack/python-tempestconf master: Update hacking version  https://review.openstack.org/62772210:47
toskymaybe --generate-profile - at least we need some unit tests (there are for read)10:48
toskyand what about the existing parameters? Are there combinations of parameters that we don't check?10:49
kopecmartintosky, i don't think more unit tests for generate-profile are needed, the functions which made sense to be tested by unit tests are already tested11:00
kopecmartintosky, which parameters you mean?11:00
toskythe ones we already had11:00
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Added python-tempestconf-tempest-devstack-admin/demo-py3  https://review.openstack.org/62286511:02
kopecmartintosky, CLI arguments? there are a few which are not tested, but they basically sets a value, nothing complicated11:02
kopecmartinnot tested by gates11:03
toskyuhm11:06
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: [DNM] testing os_tempest  https://review.openstack.org/62748211:31
arxcruzchandankumar: tosky regarding https://review.openstack.org/#/c/622865/ we should create story to remove py2 job in near future12:39
arxcruzor will have support unofficial to python 2 in openstack?12:39
*** lifeless has quit IRC12:42
chandankumararxcruz: we donot know when upstream is going to remove python2 support but a story would be ok to create for tracking12:44
arxcruzchandankumar: https://pythonclock.org/ is my guess12:45
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: [DNM] testing os_tempest  https://review.openstack.org/62748212:46
openstackgerritMerged openstack/python-tempestconf master: Fix diff in gates  https://review.openstack.org/62818013:03
chandankumararxcruz: kopecmartin tosky https://review.openstack.org/#/c/622865/ can we merge py3 stuff?13:04
*** markvoelker has quit IRC13:33
*** markvoelker has joined #refstack13:33
openstackgerritMartin Kopec proposed openstack/refstack-client master: Fix generate-tempestconf-file role  https://review.openstack.org/62844614:30
openstackgerritMerged openstack/python-tempestconf master: Added python-tempestconf-tempest-devstack-admin/demo-py3  https://review.openstack.org/62286514:52
chandankumar\o/14:54
*** arxcruz is now known as arxcruz|brb16:11
openstackgerritMartin Kopec proposed openstack/refstack-client master: Fix generate-tempestconf-file role  https://review.openstack.org/62844616:13
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: DNM - Testing refstack gate  https://review.openstack.org/62863917:25
chandankumarkopecmartin: Hey17:31
kopecmartinchandankumar, what's up?17:31
chandankumarkopecmartin: We are seeing a lot of repeatition in our python-temepstconf roles17:32
chandankumarkopecmartin: the install parts are copied everywhere17:32
chandankumarkopecmartin: I think we can move it to a single role17:32
kopecmartinwhat were? do you have any example?17:32
chandankumarkopecmartin: one min17:33
chandankumarkopecmartin: https://github.com/openstack/python-tempestconf/blob/master/roles/generate-tempestconf-file-cloud/tasks/main.yaml#L2 to l2617:33
chandankumarkopecmartin: https://github.com/openstack/python-tempestconf/blob/master/roles/generate-tempestconf-file/tasks/main.yaml#L5 to l2917:34
chandankumarkopecmartin: did you get that?17:34
kopecmartinyes , but is it worth it to create a new role for only these two cases?17:35
chandankumarkopecmartin: https://review.openstack.org/#/c/626539/7/roles/functional-tests/tasks/main.yaml17:36
toskydo you mean a new job?17:36
chandankumarkopecmartin: what do you think repeating same code at three places17:36
chandankumartosky: nope17:37
chandankumartosky: just moving the install part in a single role17:37
toskyok, but then why are those role different?17:37
toskyif they do almost the same thing?17:38
kopecmartinchandankumar, three places if we merge that patch :D but i see your point17:38
chandankumartosky: because they do some different stuff while testing python tempestconf named args17:38
toskyok, I agree that the common parts deserves a role17:39
chandankumarkopecmartin: hehe17:40
kopecmartinlet's create a storyboard for that17:40
kopecmartin*a story in our storyboard17:40
chandankumarkopecmartin: will create a tomorrow17:40
kopecmartinok17:40
chandankumarkopecmartin: one more thing with whom you are talking with redhat certification work?17:42
chandankumarkopecmartin: generally I go to office, I will catch them to understand their problem17:42
chandankumarkopecmartin: is it Anshul or somebody else?17:42
toskychandankumar, kopecmartin maybe in private?17:46
chandankumartosky: yes done!17:46
*** kopecmartin is now known as kopecmartin|off17:58
*** tosky has quit IRC18:09
*** lifeless has joined #refstack20:12
*** openstack has joined #refstack23:46
*** ChanServ sets mode: +o openstack23:46

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