Monday, 2018-06-04

*** xinliang has quit IRC01:14
*** xinliang has joined #refstack01:30
*** lifeless_ has joined #refstack03:08
*** lifeless has quit IRC03:09
*** lifeless has joined #refstack03:29
*** lifeless_ has quit IRC03:29
*** kopecmartin has joined #refstack06:16
*** tosky has joined #refstack07:29
arxcruz|rucktosky: https://review.openstack.org/#/c/566537/08:41
arxcruz|ruckgood morning :)08:41
toskyarxcruz|ruck: I'm behind with the reviews, catching up after 2 days of PTO08:48
arxcruz|rucktosky: how you dare to take 2 days of pto?08:49
arxcruz|ruckshame on you08:49
*** openstackgerrit has joined #refstack09:35
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: List and create swift roles  https://review.openstack.org/57198109:35
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Move configuring of services to services class  https://review.openstack.org/57087609:38
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: List and create swift roles  https://review.openstack.org/57198109:40
arxcruz|rucktosky: regarding https://review.openstack.org/#/c/570876/09:52
arxcruz|rucki don't remember a irc discussion as well, but i remember talking about have a method set_tempest_defaults or something like that being called to all the services to set the defaults09:53
arxcruz|ruckbecause today we are setting it in several places, it would be nice to have it in one single place for each service09:53
arxcruz|rucktosky: which i did in https://review.openstack.org/#/c/570157/6/config_tempest/services/base.py09:53
arxcruz|ruckhttps://review.openstack.org/#/c/570157/6/config_tempest/services/services.py09:54
toskyarxcruz|ruck: sure, and that's in fact what I was asking09:57
toskywhy it is not done in that review?09:57
toskywhat are the methods which can't be changed to use set_default_tempest_options?09:57
toskyif it's not done in that review, it should be planned for another review before the new release - this is what I remember from the discussion and the IRC logs seems to match09:58
arxcruz|rucktosky: no idea, but you can have a set_default_tempest_options for each service and call the other methods from there09:58
toskyI know!09:58
toskythat's what I was advocating09:58
toskythe point of the review is that it was not done09:58
kopecmartintosky, arxcruz|ruck check my comment there https://review.openstack.org/#/c/570876/310:05
toskykopecmartin: sure, and those are not reasons to not do the change IMHO10:05
toskylet me answer to each point10:05
chkumar246markvoelker: thanks10:13
kopecmartintosky, i didn't say we should not refactor it, I agree it needs some changes but not as part of that change10:16
toskykopecmartin: sure, fine; but that's different from what you wrote in the comment today (pointing to technical issues)10:18
*** eglute_s has joined #refstack10:19
toskyif you answered "the unification of other methods may take more time and refactoring and will follow up on it" I would not said anything :)10:20
*** eglute has quit IRC10:20
kopecmartintosky, I'm sorry it sounded differently than I thought, it was just summarizing the facts why i didn't do "quick" refactoring (renaming to set_default_tempest_options)10:20
kopecmartintosky, yeah, i should have added a note under the comment, that the idea of refactoring needs to be done, but not in that review, because it needs more, bigger changes unrelated to that review :)10:21
toskynp :)10:22
toskyok, oki10:22
toskykopecmartin: now, before approving that review we need https://review.openstack.org/#/c/570799/ and I was rechecking reno documentation10:24
toskynamely https://docs.openstack.org/reno/latest/user/usage.html#editing-a-release-note10:24
toskyand deprecation does not seem to fit the case10:27
toskyI was checking other repositories and it seems maybe for "upgrade"10:27
toskybut that's seems a bit a stretch too10:27
toskyin this specific case at least10:28
chkumar246kopecmartin: one little improvement https://review.openstack.org/571981 since you created the role, you need to the role to that project10:47
chkumar246*to assign the role10:47
*** lifeless_ has joined #refstack11:21
*** lifeless has quit IRC11:22
kopecmartintosky, we can use other section :D11:27
openstackgerritMerged openstack/python-tempestconf master: Don't expose user credentials  https://review.openstack.org/57074911:51
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Validation support  https://review.openstack.org/57079911:54
openstackgerritMerged openstack/python-tempestconf master: Load deployer input file automatically  https://review.openstack.org/56653712:04
openstackgerritMartin Kopec proposed openstack/python-tempestconf master: Generate accounts.yaml  https://review.openstack.org/57078112:14
chkumar246tosky: I am going to unpin the tempestconf from master in RDO12:14
toskyand master only12:19
chkumar246tosky: https://review.rdoproject.org/r/#/c/14023/12:23
*** openstackgerrit has quit IRC12:34
*** beisner is now known as beisner-sick13:22
kopecmartinchkumar246, why do we need to assign the role to a project? actually why do we need to create a role at all?13:28
kopecmartinif we want to assign a role, we need to know the project which the role will be assigned to .. but how to choose that project? what if that doesn't exists? ..13:28
chkumar246kopecmartin: we need a role so that while running swift tests it can be used14:14
chkumar246kopecmartin: but I think when a user creates a role that is already gets associated with it14:15
chkumar246kopecmartin: so i think that assigning is not needed14:15
kopecmartinchkumar246, the role created by tempestconf is not listed in `openstack role assignment list` , is that a problem?14:16
toskychkumar246: are you sure that the automatic assignment happens?14:19
chkumar246kopecmartin: tosky I need to check that14:19
kopecmartintosky, chkumar246 any idea when admin_* were moved from identity to auth section? https://github.com/openstack/python-tempestconf/blob/master/etc/default-overrides.conf#L6614:35
chkumar246kopecmartin: https://review.gerrithub.io/c/redhat-openstack/python-tempestconf/+/357879 made that change14:39
toskyif the memory helps me, following some tempest change14:41
kopecmartinchkumar246, yes, on python-tempestconf side, but i mean since when (which version) tempest uses auth.admin_* and not identity.admin_* ..14:41
chkumar246tosky: kopecmartin https://github.com/openstack/tempest/commit/ed6e586b9f8f0ada10af7711f297afa01b2b775414:44
chkumar246tempest-12.0.014:44
chkumar246from newton we are on 1314:45
kopecmartinchkumar246, great, so it means, we can remove it14:48
chkumar246kopecmartin: yup sire14:51
chkumar246kopecmartin: remove from TQE also14:56
*** lifeless_ has quit IRC15:08
*** openstackgerrit has joined #refstack15:16
openstackgerritChandan Kumar proposed openstack/python-tempestconf master: [DNM] patch to test backward compatibilty/ container check  https://review.openstack.org/57052415:16
chkumar246kopecmartin: in devstack Member role is assigned to user and project15:23
chkumar246against which we are testing15:24
chkumar246in pythontempestconf jobs swift is disabled15:24
kopecmartinchkumar246, i have a patch which should enable swift for testing purposes https://review.openstack.org/#/c/571985/15:26
chkumar246kopecmartin: ack I will rebase it with my patch15:58
*** chkumar246 is now known as chandankumar16:24
*** tosky has quit IRC16:47
openstackgerritMerged openstack/python-tempestconf master: Validation support  https://review.openstack.org/57079916:52
*** kopecmartin has quit IRC17:00
*** markvoelker has quit IRC17:59
*** markvoelker has joined #refstack18:00
*** lifeless has joined #refstack19:34
*** lifeless_ has joined #refstack20:49
*** lifeless has quit IRC20:50
*** lifeless has joined #refstack22:31
*** lifeless_ has quit IRC22:31

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