Tuesday, 2018-07-10

*** kopecmartin has joined #refstack07:38
*** tosky has joined #refstack07:39
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Document installation process  https://review.openstack.org/58019108:10
*** rmart04 has joined #refstack08:32
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Document installation process  https://review.openstack.org/58019108:41
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Fix http_image uploading to glance  https://review.openstack.org/58134412:07
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Fix http_image uploading to glance  https://review.openstack.org/58134412:07
openstackgerritMerged openstack/python-tempestconf master: Fix documentation structure  https://review.openstack.org/58017212:09
*** markvoelker has quit IRC12:18
*** markvoelker has joined #refstack12:21
*** markvoelker has quit IRC12:31
*** markvoelker has joined #refstack12:35
chkumar|ruckkopecmartin: is the http image issue only coming in RHOS-14 only?12:46
toskyahem, Rocky12:52
kopecmartinchkumar|ruck, yes13:04
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Document CLI options  https://review.openstack.org/58098113:22
kopecmartinchkumar|ruck, well not .. the package for queens is without the refactoring changes, however the package for Rocky contains the changes, which means that we broke it by refactoring13:41
kopecmartinand by "we" i mean "me" because i didn't understand the image.http_image option  correctly :)13:42
tosky"we" because we reviewed and approved it13:42
toskyand having just one relevant breakage so far is not bad; it could have been much more complicated :)13:43
kopecmartintosky, regarding to the comment on line 79 https://review.openstack.org/#/c/58105814:09
kopecmartincan you please write me the whole sentence?14:10
toskygood point, let me rephrase the sentence (or sentences?) properly14:10
toskycomment added14:16
kopecmartintosky, thanks, what about the sentence on line 79?14:31
kopecmartinshould i just append "using the Story and Task footer respectively." ?14:31
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Fix http_image uploading to glance  https://review.openstack.org/58134415:03
toskykopecmartin: yes, sorry, that was the idea, but I'm not sure now if's really needed, or that's implicit if you know how contribution works, or we can just reference the storyboard documentation15:06
kopecmartintosky, I'd say it's implicit15:08
toskyoki, so no need to add it15:09
toskyif we say someone referencing the story and the task in a freeform way, after the -1 we add it15:10
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Add Contributor Guide  https://review.openstack.org/58105815:10
toskykopecmartin: about the CLI options change: is that automatically generated with some command?15:33
kopecmartintosky, no, i copy pasted it15:34
toskykopecmartin: did you check the autoprogram-cliff directive for sphinx?15:35
toskykopecmartin: https://docs.openstack.org/cliff/2.8.0/user/sphinxext.html15:36
toskyit should avoid the problem of keeping the documentation synchronized with the program15:36
kopecmartini saw it, but it wasn't very self-explained :D15:37
toskyyou can steal the example of other programs who migrated to it, like this change: https://github.com/openstack/python-neutronclient/commit/423890a4950a725d6b493304d7b933d5b7c090d715:37
kopecmartinI was looking for something more copy-pastable solution15:40
kopecmartinin any case, we would still need to write the description somewhere15:40
toskyyes, but no need to manually document the options15:41
kopecmartini can try to check some blogs on how to implement it15:43
kopecmartinbecause i don't like the documentation much15:44
toskyuhm, then maybe it's better to rebase "Add Contributor Guide", which is more ready, directly on top of "Document installation process", which is more ready15:51
*** rmart04 has quit IRC15:52
toskyoh, about the question on the integration with refstack and what to do with the flavor: finding a flavor is fine by me15:54
toskyif no flavors exist, and the user can't create them, well, it means that it's not possible to run (various) tests anyway, not our fault15:54
kopecmartintosky, do we want to create a new argument for that?16:01
kopecmartinor maybe add the implementation of the smallest available flavor here https://github.com/openstack/python-tempestconf/blob/master/config_tempest/flavors.py#L7716:03
kopecmartinit would be done automatically16:03
toskykopecmartin: yeah, we already have the argument16:04
toskyso, if refstack does not want/can't do the autodetection, we can try it, and if we fail, well, no much to do16:04
toskythat said, it may be tricky to find a flavor small enough that can be used properly, but again, if we explain this properly, it should work16:05
toskywith a big warning (at least info log entry) when the flavor is autodetected16:05
chkumar|rucktosky: kopecmartin we need to find two smallest flavor if not found flag the msg of using overrides?16:06
toskychkumar|ruck: ehm, can you please rephrase the final part of the sentence?16:07
chkumar|rucktosky: flag the msg as pass arguments compute.flavor and compute.flavor_alt with the cli16:08
chkumar|rucktosky: I am introducing --overrides in refstack-client to pass all extras params which needs to be overridden16:08
chkumar|ruckin tempest.conf16:08
kopecmartinso when create is not allowed and micro and nano are not found, the tool will try to find the smallest flavor available (with a info msg that it's doing so), and then if not found, big message for a user, that some flavors need to be created and for example specified via overrides (so that the tool doesn't have to autodetect them)16:09
toskychkumar|ruck: if I get it correctly, no: the other way; if you pass a flavor use it; autodetect as last resource16:09
chkumar|rucktosky: pass a flavor means? passing as a extra overrides?16:11
toskychkumar|ruck: yes, specified as user input16:11
toskyif you specify the flavors with overrides, that's what the user wants16:12
chkumar|ruckkopecmartin: tosky so the implementation would be if extra overrides is passed use it, if not then look for nano and macro, if not found, detect the lowest possible flavor if all the above is false, flash the big mesg?16:13
kopecmartinyes16:15
toskyalmost16:15
chkumar|rucklet's move it to storyboard16:15
toskyafter nano and macro, if not found detect the lower possible flavor AND send a warning, but continue; if detection fails, exit16:16
kopecmartinyes, agree16:17
kopecmartingreat, I'll have a look later, now I'm going for a run, see ya16:17
toskyo/16:17
chkumar|rucktosky: kopecmartin https://storyboard.openstack.org/#!/story/200293216:21
toskychkumar|ruck: I would replace, in the first point, "it will look for it" with "it will use it"16:22
chkumar|rucktosky: done ,t hanks :-)16:23
* chkumar|ruck headed out16:24
openstackgerritwes hayutin proposed openstack/python-tempestconf master: add jobs for python-tempestconf only  https://review.openstack.org/58108416:55
*** kopecmartin has quit IRC18:14
*** rmart04 has joined #refstack19:25
*** rmart04 has quit IRC19:38
*** rmart04 has joined #refstack20:02
*** rmart04 has quit IRC20:18
*** tosky has quit IRC23:08

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