Thursday, 2018-05-17

*** markvoelker_ has quit IRC01:34
*** markvoelker has joined #refstack01:38
openstackgerritmegan guiney proposed openstack/refstack master: Subunit Data upload API  https://review.openstack.org/53068101:55
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Increase  compute.build_timeout 600  https://review.openstack.org/56903406:40
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Allow non admin users to upload image to glance  https://review.openstack.org/56825206:41
*** kopecmartin has joined #refstack07:06
*** tosky has joined #refstack07:55
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Allow non admin users to upload image to glance  https://review.openstack.org/56825208:32
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Allow non admin users to upload image to glance  https://review.openstack.org/56825208:32
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Allow non admin users to upload image to glance  https://review.openstack.org/56825208:35
chandankumartosky: kopecmartin arxcruz ^^ exception updated08:36
toskychandankumar: with unit test?08:36
chandankumartosky: oh shit, I need to add unit test, I will do that08:36
toskyeh, I know, but it's for your own safety08:37
kopecmartintosky, chandankumar arxcruz , it passed \o/ , please have a look https://review.openstack.org/#/c/562672/08:41
chandankumarkopecmartin: I should have improve the unit test also for the same to consume it08:43
chandankumarinstead of dependent on main method08:43
toskykopecmartin: uhm, uhm, can't we really avoid a duplication of parsing cloud data?08:44
toskythe value returned by get_arg_parser, which means the value returned by parse_argument, already knows the cloud data08:46
kopecmartintosky are you saying about this call: os_client_config.OpenStackConfig(), which is there twice?08:48
kopecmartinit's just an object instantiation , not parsing of a cloud08:49
chandankumarkopecmartin: is this https://github.com/openstack/python-tempestconf/blob/master/etc/default-overrides.conf#L117 taken care by tempestconf?08:54
chandankumarbootable=true08:54
chandankumarvolume_services=true08:54
kopecmartinchandankumar, AFAIK no08:55
chandankumarkopecmartin: if it is possible by some magic then we can get it done08:56
toskykopecmartin: I remember that you documented the way to use this new public API, was it in this review or just on IRC or I just dreamt about it?08:56
toskylike: call get_cloud_config, call config_tempest, etc08:57
toskyI'm still not totally convinced that another instance of os_client_config is needed; I thought that parsing the parameters could be isolated completely08:58
kopecmartintosky, i get it this way, parse_arguments deals with CLI  only .. get_cloud_creds needs arguments for querying the cloud in order to obtain its credentials08:59
kopecmartinthe object is needed twice, because it's two scopes, and we need two independent  methods from that library09:00
kopecmartintosky, which new public API? :D09:00
toskykopecmartin: this API :)09:02
toskytempestconf for any user (starting with refstack)09:03
kopecmartintosky, i have a coffee now :D, let's go one by one09:15
kopecmartinok, so this patch https://review.openstack.org/#/c/562672/09:15
kopecmartinas i explained above, i think those two methods have totally different usage, but both of them needs some method from os-.. * library, I think it's ok this way09:16
toskyok, fine, I won't block that09:18
kopecmartinI'm still gonna need to edit the commit message there, because we don't have to be dependent on the turning the ceilometer off09:18
kopecmartintosky, btw, do we still want to do it?09:19
kopecmartinturn the ceilometer off on packstack?09:19
toskykopecmartin: I was hoping that it could save resources, but if it does not do anything, it's pointless09:19
kopecmartintosky, it didn't solve the timeout issues, so there is enough resources which are allocated either way09:20
kopecmartinok, I'll edit the commit message09:20
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Make tempestconf easier to use as an library  https://review.openstack.org/56267209:21
kopecmartinarxcruz, thanks for review, I've just edited the commit message only, so you can +2 again :) https://review.openstack.org/#/c/562672/09:22
arxcruzkopecmartin: second +2 in the same patch it's 2 beers09:22
arxcruzkrusovice09:22
toskyeven the choice!09:22
kopecmartinarxcruz, :D done09:23
arxcruz;)09:23
kopecmartinbut you have to call me out too, when you are in Brno next time09:23
kopecmartinarxcruz, fhubik says, that only u suka ;)09:24
arxcruzkopecmartin: done09:24
kopecmartintosky, ok, this patch now https://review.openstack.org/#/c/568695/09:28
kopecmartinyou're saying it's fine, but we need to figure out a generic way, how to deal with multiple versions in the future (if we will have multiple versions for a service again)09:29
kopecmartinis that correct?09:29
toskykopecmartin: yes; it works now, but it removes some more general code which could be improved for sure, but it may be needed (for example, I would split SERVICE_VERSIONS so that each service provides all the versions supported)09:32
kopecmartinok, agree09:33
kopecmartintosky, we can still have the SERVICE_VERSIONS containing only one version for a service right now09:34
kopecmartinbut I'm thinking if there is a nicer way, how to do it09:34
toskydo you mean keep SERVICE_VERSIONS for now, but empty (as there are no more multiple versions), while thinking about a better solution?09:35
kopecmartinyes09:36
toskythat's a possibility to not block the rest of the content of the review (the code which checks for deprecated versions, which is good)09:37
toskymaybe a TODO near the definition of SERVICE_VERSIONS could help09:37
kopecmartinok, I'll add it there, we will create a task for another sprint which will be dealing with this, i have a few ideas, but it requires more time09:38
toskysure09:38
kopecmartintosky, chandankumar one big question, which is blocking my mind, where/ how /what are we gonna backport? for which versions of openstack?09:39
kopecmartinwe made a huge amount of changes09:39
kopecmartinare they gonna be packaged for older versions?09:39
toskykopecmartin: if we are going to have this working as refstack-client, we will need to support at least the same version of openstack supported at the time of the integration09:42
toskywhich may be a problem with the removal of old versions09:42
toskychecking for deprecated is fine, because that is discovered, but totally removing cinder v2, or identity v2, at this time, not so much09:44
kopecmartintosky, this removing of old version is applicable only since 13 and higher09:44
toskykopecmartin: s/13/queens/ :)09:44
toskyI think that refstack-client supports more than that09:45
kopecmartintosky, 13  is consists of two characters, it's faster :D09:45
kopecmartinyes, and here I'm not sure, how it works for older versions , can we just backport only some of the commits? if yes, it's fine09:46
*** xinliang has quit IRC09:46
toskybackports which commits to which version of what?09:47
toskyat the time when refstack-client starts using tempestconf, that version of tempestconf (so future one) should support all versions of openstack that refstack-client supports (so likely older)09:48
kopecmartincommits of python-tempestconf, which i want to rpm packages for older versions of OpenStack09:49
kopecmartinoh, i see, so i can't chose which commits from the history I will backport, i can backport all commits , before a certain commit, or none09:49
toskyif you are talking about "which version of tempestconf can I use with RDO", we may decide (I think we discussed it with chandankumar) to still pin to 1.1 and create a 1.1 branch for bugfixes there, if the changes are too invasive09:51
chandankumarkopecmartin: tosky currently for ocata-1.1.3 and pike, queens - 1.1.4 is working09:55
chandankumartosky: kopecmartin if we want to support older releases i mean pike, queens also we need to find what is broken and fix it09:56
chandankumarit might needs to keep hardcoded stuff to support previous releases09:56
toskywell, if we don't drop for old versions, as needed by refstack-client, it would help for using tempestconf directly on older versions09:57
*** xinliang has joined #refstack09:58
chandankumarkopecmartin: tempestconf is branchless, we donot suppport backport for that, a particular tag should satisy the need, but we can work on supporting older release also but we need to find out what is getting broken for previous releases09:59
toskychandankumar: again, my question is: you wrote "we can work", but I think it is more "we must work", if refstack-client needs to support more releases10:00
toskymy point, more than my question10:00
chandankumartosky: yup we must work but let me get some rdoci jobs to find the breakage from pike release onwards as ocata support is getting EOL soon10:01
toskychandankumar: also for refstack-client?10:02
toskychandankumar: if you can execute the last guidelines with the last refstack-client, even Newton is supported: https://refstack.openstack.org/#/guidelines10:03
chandankumartosky: for refstack-client we can just run the tempest provided refstack tests for each release and find out what is broken10:03
chandankumartill newton? It would be too much costlier10:04
toskychandankumar: well, then wait for mergining until the next version of the guidelines are released10:06
toskyif you select version "Next", it starts from Ocata10:07
toskybut again, is it true that you can run refstack-client/master and expect to execute all those tests? If it is, yes, we need to keep the compatibility10:07
*** kopecmartin is now known as mkopec|lunch10:22
*** mkopec|lunch is now known as mkopec11:21
*** mkopec has quit IRC11:21
*** kopecmartin has joined #refstack11:22
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Filter deprecated versions out  https://review.openstack.org/56869511:32
kopecmartintosky, chandankumar this way it shouldn't break anything ^^11:33
chandankumarkopecmartin: you can proactively verify it https://trello.com/c/sOUB7PeX/749-enable-logging-for-tempest-container11:42
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Allow non admin users to upload image to glance  https://review.openstack.org/56825212:10
*** tosky has quit IRC12:32
*** tosky has joined #refstack12:36
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Store volumev2 and v3 extensions as well  https://review.openstack.org/56887612:57
kopecmartintosky, this is longer, but more generic solution .. would it be better this way? ^^12:58
toskykopecmartin: commented :)12:59
toskythanks for working on it12:59
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Store volumev2 and v3 extensions as well  https://review.openstack.org/56887613:12
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: Allow non admin users to upload image to glance  https://review.openstack.org/56825213:49
*** kopecmartin_ has joined #refstack13:57
*** kopecmartin has quit IRC14:00
*** kopecmartin_ has quit IRC14:20
*** kopecmartin_ has joined #refstack14:33
*** kopecmartin_ has quit IRC16:26
*** eglute has quit IRC22:48
*** eglute has joined #refstack22:49
*** tosky has quit IRC23:36

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