Wednesday, 2020-05-13

*** tetsuro has joined #openstack-tc00:30
*** tetsuro_ has joined #openstack-tc00:40
*** tetsuro has quit IRC00:43
mnaserclarkb, fungi: given your intimate knowledge of our infra, do you know how much 'extra load' we would add if projects actually tested for 1 or 2 more distros (say debian and centos) -- and probably one job only.  is the impact big enough or it won't really be noticed?00:52
clarkbmnaser: its been a while since I ran the generation of those stats but they are in graphite now so anyone should be able to look at them I think01:02
clarkbin general ot seems that the job cost itself is a major factor which is why tripleo has been a major consumer01:02
clarkblong running jobs with multiple nodes consume a lot relatove to other jobs01:03
clarkball that to say it really depends on the type of jobs you want to run01:03
mnaserclarkb: right, there seems to be a lot of discussion with the "Remove centos 8 from the list" but in reality we don't really test any of the othrs so they're not more deserving to be there than the others01:03
mnaserso wondering how much extra work we might end up needing if we were to implement something so all projects run at least a _single_ devstack based job on all the supported platforms01:04
clarkba single node devstack probably wouldnt be too bad. You'd need people to keep devstack running on those platforms though01:05
clarkbalso note fungi pointed out earlier the docs dont actually say w e must test thoseplatofrms01:06
clarkbjust that those platforms are common and projects should test them if they can01:06
mnaseryeah, i agree.  it just seems like it's a big point of contention right now amongst people that consider those platforms "untestable"01:06
mnaseri'm almost tempted to rip out that entire document in that case because we just ship a bunch of python code.  the fact we test it on ubuntu validates that it works, but not that specific operating systems are supported01:07
gmannalso stability of job will be more important, we need to check it would not slow down the development01:07
clarkbreally itslong running multinode jobs that have the biggest impact01:08
clarkbsingle node devstack is probably fine but we can run actual numbers and quantify it (just not this moment as it is dinner time)01:08
mnasergmann: yeah i imagine from a qa perspective we probably have the whole ubuntu platform nailed down01:22
mnaseras someone whos done a lot of deployment across different os, generally, platforms are pretty stable01:22
gmannmnaser: 1 idea is to add periodic jobs on each project that can test each distro daily basis and would not have much impact on current gate situation.01:25
gmannlike we do for oslo master testing in "tempest-full-oslo-master"01:25
mnasergmann: true but in my experience no one ends up paying attention to periodic jobs :X01:26
gmannthat depends on team to team but for majority i agree those are not actively monitored .01:27
mnaseryeah i generally feel like those go usually unnoticed01:29
gmannso how much testing we want to cover ? per services only or per repo (mean all the code changes including for client, lib etc ) and functional tests only or integration tests too01:29
gmannintegration tests might question on stability of job (like ubuntu based are also not 100% stable) as functional testing is much stable.01:31
mnasergmann: i think you'd probably be the best domain expert in that (or maybe we should stop promising "supported operating systems" because the list doesn't really mean much)01:34
gmannmy initial plan/arguments was always to tests all listed distro but it was our doc which was/is confusing for me on tested vs supported vs list to decide the testing runtime.01:37
gmannmnaser: let me try out some devstack jobs with some other services than what we have on devstack and get some stat. and then we can decide if to test those distro or stop promising their support.01:38
mnaserperhaps.  i mean, if we drop the OS, we should drop all operating systems as "tested" and make no promises about the OS that we test on01:39
mnaserit's a little unfair for other distros just because ubuntu was the day 1 resident that we test on (i.e. i'd personally have preferred it to be debian but it is what it is!)01:40
gmannthat's fair point.01:40
*** tetsuro has joined #openstack-tc01:44
*** tetsuro_ has quit IRC01:47
*** tetsuro_ has joined #openstack-tc02:12
*** tetsuro has quit IRC02:15
fungiback to my earlier point, we need some way of deciding when we can drop support for specific versions of some dependencies02:24
fungihow we've been deciding that is by looking at what's shipped in lts server distros on which our users commonly deploy our software02:25
fungikeeping a list of the distros we use in that calculation is the main benefit i see to that bit of the document02:25
fungiotherwise how do we determine, for example, when it's safe to start releasing code which can no longer run under python 3.6?02:26
fungithat's what the list of distros is there for, and when that section was added we made a careful attempt to avoid saying they were "supported" or that all our software was "tested" on them02:27
fungiit was taken as an aspirational goal to suggest that projects should run functional tests on those platforms, that was acknowledged in the review comments as well, and as was observed at the time could form the basis of some cycle goals around increased testing02:30
fungibut given that most projects haven't added their own functional tests on additional platforms, four years later, it seems like we're better off removing that suggestion02:31
*** tetsuro has joined #openstack-tc03:06
*** tetsuro_ has quit IRC03:09
*** tetsuro_ has joined #openstack-tc04:06
*** tetsuro has quit IRC04:09
*** evrardjp has quit IRC04:36
*** evrardjp has joined #openstack-tc04:36
*** diablo_rojo has quit IRC04:44
*** dmellado has quit IRC04:45
*** dklyle has quit IRC05:01
*** tetsuro has joined #openstack-tc05:43
*** tetsuro_ has quit IRC05:47
*** njohnston has quit IRC06:05
*** tetsuro_ has joined #openstack-tc06:23
*** belmoreira has joined #openstack-tc06:24
*** tetsuro has quit IRC06:26
*** tetsuro has joined #openstack-tc06:29
*** tetsuro_ has quit IRC06:32
*** lpetrut has joined #openstack-tc06:42
*** slaweq has joined #openstack-tc06:51
*** witek_ has joined #openstack-tc06:59
*** tetsuro_ has joined #openstack-tc07:24
*** tetsuro has quit IRC07:27
*** rpittau|afk is now known as rpittau07:29
*** tosky has joined #openstack-tc07:35
*** dmellado has joined #openstack-tc07:37
*** e0ne has joined #openstack-tc08:05
*** tetsuro_ has quit IRC08:47
*** tetsuro has joined #openstack-tc09:07
*** tetsuro has quit IRC09:23
openstackgerritGraham Hayes proposed openstack/governance master: Require PTL signoff for project-update changes  https://review.opendev.org/72770410:41
*** njohnston has joined #openstack-tc11:01
*** rpittau is now known as rpittau|bbl11:04
*** rpittau|bbl is now known as rpittau12:19
*** tkajinam has quit IRC12:24
*** lpetrut has quit IRC12:46
*** ianychoi has quit IRC12:55
jungleboyjo/13:06
njohnstono/13:09
belmoreirao/13:34
mnaserexcellent patch mugsie13:38
gmanno/13:50
*** lpetrut has joined #openstack-tc14:29
knikollao/14:31
*** dklyle has joined #openstack-tc14:42
gmannnjohnston: on V cycle goal selection,  its time to do now. I will say we(tc) decide on IRC instead of gerrit vote what yo say? or any better and fast idea14:45
cloudnullo/14:56
evrardjpgmann: WFM14:58
gmannevrardjp: cool14:59
gmanntc-members: let's discuss V cycle goal selection and finalise it tomorrow office hour15:00
gmannor in meeting, mnaser when is our meeting next week?15:01
mnasergmann: i say lets do it for office hours, i will need to figure out meeting logistics.  the whole end of cycle thing + getting back to chair duties is slowly getting us started15:02
gmannmnaser: ok15:02
mnasergmann: i feel like this needs a non-async discussion too15:03
mnaserit'll stall out for too long otherwise15:03
mnasertc-members: who is able to attend tomorrows office hours for ^ ?  can we get quorum?15:03
knikollai will attend.15:03
gmannmnaser: yeah, as ussuri is released officially we need to final it now.15:03
gmanni will be there.15:04
*** lpetrut has quit IRC15:08
* njohnston will be there15:08
*** belmoreira has quit IRC15:24
jungleboyjI will be in office hours tomorrow.  Have another call at the same time but should still be relatively dialed in.  :-)15:24
*** witek_ has quit IRC16:15
*** rpittau is now known as rpittau|afk16:21
*** camelCaser has quit IRC16:22
*** ccamel has joined #openstack-tc16:22
*** witek_ has joined #openstack-tc16:26
*** evrardjp has quit IRC16:36
*** evrardjp has joined #openstack-tc16:36
diablo_rojo_phonI can be there if you need me for quorum.17:11
*** ijolliffe has quit IRC17:36
*** e0ne has quit IRC17:55
*** belmoreira has joined #openstack-tc19:05
*** dklyle has quit IRC19:38
*** dklyle has joined #openstack-tc19:46
*** belmoreira has quit IRC20:07
*** slaweq has quit IRC21:57
*** slaweq has joined #openstack-tc22:08
*** slaweq has quit IRC22:13
*** slaweq has joined #openstack-tc22:23
*** slaweq has quit IRC22:28
*** tkajinam has joined #openstack-tc22:46
*** tosky has quit IRC23:06

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!