Tuesday, 2018-07-03

hogepodgefungi: ugh, I never maintain wikis and our meeting agendas have been a set of linked etherpads going back a long while01:42
hogepodgethere will be a meeting tomorrow at 10 am01:42
fungicool, that's all i really needed to know--thanks!02:08
fungiwas just having a tough time figuring it out from the available clues02:10
*** openstackgerrit has quit IRC06:49
*** kopecmartin has joined #refstack08:15
*** tosky has joined #refstack08:20
arxcruztosky: ping08:48
toskyarxcruz: I know that I need to review the job change08:48
toskyarxcruz: hi! Anything else?08:48
tosky:)08:48
arxcruztosky: that's it08:48
arxcruzit's working08:49
arxcruzcommit message updated08:49
arxcruztask/story created08:49
arxcruzetc, etc08:49
toskyand bug too08:49
tosky(I subscribed)08:49
toskythanks, let me check it08:49
toskyarxcruz: added few notes09:30
arxcruztosky: jesus christ!09:33
toskyI think I already mentioned two of them in past reviews :)09:36
*** openstackgerrit has joined #refstack09:48
openstackgerritArx Cruz proposed openstack/python-tempestconf master: Collecting tempest files  https://review.openstack.org/57644409:48
arxcruztosky: dne09:48
arxcruzdone09:48
toskythanks09:53
*** rmart04 has joined #refstack09:55
kopecmartintosky, arxcruz, chandankumar I took pto for tomorrow, I broke my OS by an update and I'm in Slovakia (i wanted to take advantage of public holidays on Thursday and Friday), I'll reinstall it after I'm back in Brno10:45
kopecmartina lot of things don't work :D, so my work performance can be affected10:46
kopecmartinbut I'll be around a few hours tomorrow, so chandankumar, we can write and review cards for the next sprint10:46
chandankumarkopecmartin: ack sir, enjoy, yup sprint planning tomorrow10:46
toskykopecmartin: oook12:10
arxcruzkopecmartin: chandankumar https://review.openstack.org/#/c/576444/12:56
kopecmartinarxcruz, just one question, where can i find the collected logs in devstack jobs?12:57
arxcruzkopecmartin: did you read the commit? ;)12:58
arxcruzkopecmartin: http://logs.openstack.org/44/576444/29/check/python-tempestconf-tempest-devstack-admin/0b6cf0f/controller/logs/12:58
arxcruzthere's a tempest.conf tempest.log and on -demo the accounts.yaml12:58
kopecmartinarxcruz, oh i see, i didn't find it because they are renamed like tempest_conf.txt ..12:59
arxcruzkopecmartin: this is the devstack upload log thing, there's nothing i can do13:00
arxcruzand NO, I'll not override that upload logs13:00
arxcruz:)13:00
kopecmartinarxcruz, it's fine, i was just confused because i couldn't ctrl+F them :D13:00
*** kopecmartin has quit IRC13:06
*** kopecmartin has joined #refstack13:06
*** kopecmartin has quit IRC13:10
*** kopecmartin has joined #refstack13:10
kopecmartinarxcruz, https://review.openstack.org/#/c/579838/ looks like, the default-overrides.conf removal haven't broken anything13:45
arxcruzkopecmartin: in meeting, i'll check later13:45
*** rmart04_ has joined #refstack14:48
*** rmart04 has quit IRC14:50
*** rmart04_ is now known as rmart0414:50
*** rmart04 has quit IRC15:07
*** kopecmartin has quit IRC15:20
*** chandankumar is now known as chkumar|ruck15:29
openstackgerritMerged openstack/python-tempestconf master: Collecting tempest files  https://review.openstack.org/57644415:57
mguineymeeting today?17:05
hogepodgeI’m running late at a physician appointment. If folks can check in on their work here that would be helpful.17:10
* mguiney nod17:10
hogepodgeTwo big things are close to landing. Subunit upload and tempest auto config. Drop links here so they can be reviewed17:10
mguineyi'm still in the middle of a big refactor. i saw the new comments you dropped, and will address those in the code as soon as I finish the initial code restructure, as the tests themselves will need to be heavily modified as a result of the updates17:12
mguineyi appreciate the feedback that went into those, and hope to have that new patch up soon. in the meantime, the current patch can be found at: https://review.openstack.org/#/c/530681/2117:13
fungiahh, i was looking in #openstack-meeting-alt and missed the discussion starting up in here17:18
mguineyi did that the other day17:20
mguineyare there new updates from infra-land?17:20
toskyon the tempestconf side, a lot of patches landed; the refactor is still ongoing, we have two issues to fix (clean up the internal code and more documentation)17:21
toskybut the API should be stable for refstack-client17:22
tosky(also, we have py3 unit tests now)17:22
toskya lot of work thanks to arxcruz, chkumar|ruck and kopecmartin17:22
fungiahh, not infra, just wanted to mention that the tc is taking a more active role in tracking overall health of the openstack community and reaching out to project teams, sigs and working groups with assigned liaisons to get feedback on what issues you're facing and how we might help: https://wiki.openstack.org/wiki/OpenStack_health_tracker17:22
fungiTheJulia and i volunteered to be liaisons to the refstack team, and dims and i volunteered to be liaisons to the interop wg17:23
* mguiney nod17:28
fungilooks like most of the dev work on the refstack repo is being propped up by foundation staff/contractors at the moment, would that be a fair assessment?17:31
fungialso it doesn't look like there's a lot of reviewing happening from other members of https://review.openstack.org/#/admin/groups/refstack-core17:32
fungilooks like refstack-client has gotten a little more in the way of outside patch contribution than refstack has, but which core reviewers are active there seems to be roughly the same state as for the refstack repo17:33
hogepodgefungi: yes, turns out I was at the doctor, and missed starting the meeting.17:39
hogepodgefungi: on the whole. refstack is being wound down17:39
hogepodgeOnce we land a set of patches, we're going to do some testing, update the deployment tooling, and officially put the project into maintenance mode17:40
funginot enough interest in what it provides, or its purpose is being fulfilled in other ways?17:40
hogepodgefungi: it is feature complete17:40
fungiwoo!!!17:41
* fungi cheers17:41
fungijob well done17:41
fungior, at least soon anyway17:41
hogepodgeIf there was interest in extending its capabilities, that would be welcome, but it does its job (almost) :-)17:41
mguineyhopefully soon17:41
hogepodgealso, lack of developers. One interesting thing is the active development that's coming out of RedHat on Tempest Auto Conf. That project is part of RefStack, and will likely remain active. I expect the contributors to that project may carry on, or may look for a new home. It's up in the air.17:42
fungido you think it should continue to have a designated team after that point in case future issues crop up which need addressing, or that it might be a candidate for adoption into another existing team or the interop wg?17:43
hogepodgeThey added an extremely valuable component to refstack-client, which is why they fell under the refstack project (tosky and chkumar|ruck can elaborate)17:43
hogepodgefungi: I'll remain on point for it, since it's directly related to my work as running the interop and trademark program for the Foundation17:43
toskyat least one our side we plan to keep maintaining tempestconf17:44
mguineywould it perhaps just fall under the interop-wg umbrella, after refstack goes into maintenance?17:44
hogepodgeyeah, having iterop-wg be the owners seems like the best idea, just need to balance it with the autoconf team17:45
fungiis tempest autoconf work more closely affiliated with other qa team activities that it might make sense for autoconf to be a qa deliverable at some point?17:46
fungii haven't looked at the overlap in folks involved there yet17:46
toskyI think that the QA team is generally not keen on the autoconfiguration (for reasons)17:46
toskyautodiscovery, that is17:46
fungigot it. makes sense for it to be a separate effort in that case17:47
fungiand yeah, from a qa perspective i can understand the reasons17:48
fungiwe certainly wouldn't want ci jobs to suddenly stop testing features which were accidentally disabled17:48
* mguiney nod17:48
mguineymakes sense17:48
hogepodgeyeah, the qa team has been supportive of the effort, but resistant to it being under their umbrella17:48
fungicool, so does the autoconfiguration/autodiscovery work stay joined to the refstack effort if it moves under the interop wg, do you think, or would it get spub off as a separate team entirely even?17:49
fungis/spub/spun/17:50
hogepodgefungi: I think that is a topic for discussion17:50
fungicertainly doesn't need to be decided now17:50
fungijust didn't know if ideas had already been floated17:50
hogepodgeno, not yet17:51
hogepodgeProbably a discussion to have in August once we've cleared the US holidays and OSF staff meeting17:51
hogepodgeno harm in starting to think about it now, though.17:52
fungicool, well i'm curious to see how it all unfolds, and happy to help out from a tc perspective on whatever help you need for any of it17:52
hogepodgeUltimately I want to support tosky's team in the best way to keep them successful. They've been doing long-needed and difficult work.17:52
hogepodgefungi: thank you. :-)17:53
fungiany time!17:53
chkumar|ruckhogepodge: fungi from the openstack summit openstack-qa feedback some has asked from auto tempest conf genrator17:54
* fungi bringing you "a kinder, gentler openstack technical committee"17:54
chkumar|ruckhogepodge: fungi http://osdir.com/openstack-developers/msg125483.html17:56
fungichkumar|ruck: a great reference--thanks!17:57
*** tosky has quit IRC18:14
openstackgerritmegan guiney proposed openstack/refstack master: Subunit Data upload API  https://review.openstack.org/53068121:02

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