Friday, 2016-07-15

*** markvoelker has quit IRC00:48
*** markvoelker has joined #refstack02:48
*** markvoelker has quit IRC05:43
*** markvoelker has joined #refstack06:30
*** openstackgerrit has quit IRC06:33
*** openstackgerrit has joined #refstack06:34
*** markvoelker has quit IRC06:39
*** markvoelker has joined #refstack08:23
*** markvoelker has quit IRC08:27
*** markvoelker has joined #refstack09:17
*** markvoelker has quit IRC09:21
*** markvoelker has joined #refstack10:11
*** markvoelker has quit IRC10:16
*** markvoelker has joined #refstack11:05
*** markvoelker has quit IRC11:10
*** markvoelker has joined #refstack11:59
*** markvoelker has quit IRC12:03
*** cjvolzka has joined #refstack12:54
*** cjvolzka has quit IRC12:55
*** markvoelker has joined #refstack13:03
*** edmondsw has joined #refstack14:02
*** markvoelker has quit IRC14:13
*** markvoelker has joined #refstack14:16
*** markvoelker has quit IRC14:16
-openstackstatus- NOTICE: Gerrit is restarting to correct memory/performance issues.14:19
*** markvoelker has joined #refstack14:37
hogepodgeluzC: hi15:31
luzChello hogepodge15:42
luzChad some connection issues, earlier...15:42
hogepodgeno problem15:43
luzCso, refstack-client waiver implementation...15:45
hogepodgeWhat we need is a script that takes a list of API calls in some format, and generates a patch that removes strict checking from the appropriate jsonschema in this directory http://git.openstack.org/cgit/openstack/tempest/tree/tempest/lib/api_schema/response/compute15:45
hogepodgeOne thing I'm trying to wrap my head around is how to best build that list, and map it back to the actual API calls15:49
luzCI was thinking on adding an optional argument for refstack run... so that it run the suite as it is, then run matt's script to see if strict checking cause the problems, if so then patch refstack tempest repo and then run the failed test cases...15:50
hogepodgeluzC: I like that15:50
hogepodgeluzC: would you feel comfortable writing up a blueprint for it?15:51
luzCyes15:51
hogepodgeluzC: The procedure for writing up the spec/blueprint is to create a new entry here: https://blueprints.launchpad.net/refstack/+addspec15:53
luzCyes, I'll do, let you know when I have the draft...15:54
hogepodgeluzC: then send up a patch to this directory http://git.openstack.org/cgit/openstack/refstack/tree/specs15:54
hogepodgeluzC: thanks for taking this15:54
luzCNP :)15:54
hogepodgeLet me know if you need help with anything15:54
luzCyes, I'll :)15:54
luzCAlso I yesterday I run matt's script (piping ostestr output)... and it is not working, I changed line 48 from "returnmime" to "return"... I guess it was a typo... after that it worked ok15:59
hogepodgeluzC: thanks16:05
luzChogepodge BP at https://blueprints.launchpad.net/refstack/+spec/refstack-waiver16:32
luzCabout the spec... is it needed even if it is for refstack-client instead of refstack ??16:33
hogepodgeluzC: ask catherineD about it. I think that refstack is where the specs for both projects land16:50
catherineDluzC: yes  please we use the same one for both...16:52
catherineDsame for bug filling16:53
*** pvaneck has joined #refstack18:14
*** davidlenwell has quit IRC18:23
openstackgerritLuz Cazares proposed openstack/refstack: Implement additional properties Defcore waiver  https://review.openstack.org/34302218:32
luzC@hogepodge @catherineD spec is here https://review.openstack.org/#/c/343022/18:34
*** davidlenwell has joined #refstack20:34
*** ChanServ sets mode: +o davidlenwell20:34
*** catherineD has quit IRC20:57
*** edmondsw has quit IRC20:58
*** edmondsw has joined #refstack21:02
*** edmondsw has quit IRC21:02
*** catherineD has joined #refstack21:02
*** edmondsw has joined #refstack21:03
*** edmondsw has quit IRC21:04
*** edmondsw has joined #refstack22:40
*** edmondsw has quit IRC22:45
*** pvaneck has quit IRC23:56

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