Friday, 2020-02-07

*** diablo_rojo has quit IRC00:05
*** diablo_rojo has joined #openstack-tc00:06
*** diablo_rojo has quit IRC01:13
*** gagehugo has quit IRC01:58
*** jamesmcarthur has joined #openstack-tc02:44
*** jamesmcarthur has quit IRC03:31
*** jamesmcarthur has joined #openstack-tc03:32
*** jamesmcarthur has quit IRC03:59
*** jamesmcarthur has joined #openstack-tc04:00
*** jamesmcarthur has quit IRC04:04
*** tetsuro has quit IRC04:13
*** tetsuro has joined #openstack-tc04:13
*** jamesmcarthur has joined #openstack-tc05:01
*** jamesmcarthur has quit IRC05:06
*** gmann has quit IRC05:27
*** evrardjp has quit IRC05:34
*** evrardjp has joined #openstack-tc05:34
*** jamesmcarthur has joined #openstack-tc06:52
*** jamesmcarthur has quit IRC06:54
*** ricolin has quit IRC07:11
*** lpetrut has joined #openstack-tc07:29
*** lpetrut has quit IRC07:30
*** lpetrut has joined #openstack-tc07:31
*** witek has joined #openstack-tc07:55
openstackgerritJean-Philippe Evrard proposed openstack/governance-website master: Introducing ideas on the governance website  https://review.opendev.org/70643907:56
openstackgerritJean-Philippe Evrard proposed openstack/governance-website master: Introducing ideas on the governance website  https://review.opendev.org/70643907:58
*** slaweq__ has joined #openstack-tc08:00
*** slaweq__ has quit IRC08:05
openstackgerritJean-Philippe Evrard proposed openstack/governance master: Add Ideas into the governance sidebar  https://review.opendev.org/70644008:08
*** slaweq__ has joined #openstack-tc08:08
openstackgerritJean-Philippe Evrard proposed openstack/governance-sigs master: Add Ideas into the governance sidebar  https://review.opendev.org/70644108:10
*** rpittau|afk is now known as rpittau08:10
openstackgerritJean-Philippe Evrard proposed openstack/governance-sigs master: Add Ideas into the governance sidebar  https://review.opendev.org/70644108:10
*** slaweq has joined #openstack-tc08:17
openstackgerritJean-Philippe Evrard proposed openstack/election master: Add Ideas into the top sidebar  https://review.opendev.org/70644408:18
*** iurygregory has joined #openstack-tc08:19
*** slaweq__ has quit IRC08:19
*** tetsuro has quit IRC08:46
*** tosky has joined #openstack-tc08:48
*** david-lyle has quit IRC09:16
*** david-lyle has joined #openstack-tc09:16
fricklerhi, I would like to know how the TC feels about continuing to claim RHEL8 support for Ussuri given that there is still no working devstack support (seems stalled on waiting for RDO to release things https://review.opendev.org/688614)10:03
*** e0ne has joined #openstack-tc10:08
*** slaweq has quit IRC10:13
*** slaweq has joined #openstack-tc10:15
*** purplerbot has quit IRC10:50
*** slaweq_ has joined #openstack-tc10:51
*** purplerbot has joined #openstack-tc10:51
*** slaweq has quit IRC10:53
*** bauzas has quit IRC10:57
*** bauzas has joined #openstack-tc10:57
*** rpittau is now known as rpittau|bbl11:18
evrardjpfrickler: good question. I think the idea behind the support of the distro is two ways: the infra & projects side, and the users side. On the users side, it's good to say that OpenStack has been tested for RHEL8. However, you are right, one can doubt this claim, if it's not even tested in devstack.11:56
evrardjpHowever (double combo!) devstack is not the only way to claim its tested though, therefore it might be not enough to remove it. Also, removing after the fact might be triggering discussions about _which python versions_ needed to be supported at all during the Ussuri cycle.11:58
evrardjpOn the infra & projects, I suppose that it's up to infra to decide to remove the image, and up to the the projects to not test with rhel/centos (AFAIK not many projects do, maybe swift does, but my memory could be wrong). However, I think we'll cross that bridge when we'll get to it, don't you think?11:59
evrardjpSo IMHO, we should think about helping them getting this achieved more than dropping them. It's probably better for OpenStack in general12:00
evrardjpOfc I can change my mind with new arguments12:01
*** gmann has joined #openstack-tc12:08
*** slaweq__ has joined #openstack-tc12:09
*** slaweq_ has quit IRC12:11
gmanno/12:12
fungi"Each project should run some functional tests on these platforms so we make sure OpenStack works with distros used in production. The scope of these functional tests are discussed for every project, and may adjust their coverage depending of resources and support investment. These tests are run by using existing tooling, which comes with a reasonable expectation that it’s viable on the indicated12:17
fungidistributions."12:17
fungiso it doesn't specifically say that the functional tests have to be devstack/tempest12:17
fricklerso you are saying each project should invent their own way to test on centos instead of being able to rely on devstack as we did up to now?12:23
funginope, just saying that the policy doesn't specifically require devstack (and some projects, for example deployment projects, already don't use it)12:28
evrardjpthat's exactly what I meant, thanks for clarifying fungi :)12:29
evrardjpfrickler: do you know what's going on, so that devstack is not progressing?12:29
fricklerevrardjp: I'm not sure, it's a mix of "lack of developer investment" and "waiting on RDO" I guess.12:31
fricklerso maybe also just misinterpreting the "should" in the first sentence of fungi's quote.12:31
fricklerlike would it be o.k. for a project (like designate) to say: we don't test anything on centos until devstack supports it, and still be in compliance with the PTI?12:32
fricklerwe also don't test on opensuse afaict, but that's a different issue12:32
* njohnston sees if he can find someone from RDO to make a comment12:40
njohnston^^ ianw12:48
gmannfrickler project should not need devstack for functional testing which is required criteria ti declare distro is tested and supported.12:50
gmannevrardjp helping them and support testing as much as possible is generally good and we should do that BUT QA team is shortage of man power. We are somehow managing the load till now but i am afraid we need to start cutting the things-to-support in near future.12:54
evrardjpfrickler: yeah a project can decide afaik12:54
evrardjpgmann: I think it's fair12:55
evrardjpI am all creating the idea framework to make sure we can rethink from the ground up everything if necessary.12:55
evrardjpgmann: I am looking forward to an idea of yours on how we could refactor this. I might have one on your direction :p12:56
gmannother thing to not here - nobody verify the all supported distro testing on project side , i am 100% sure majority of projects do not test centos or opensuse. so claiming their support in openstack need more mandatory functional jobs on all those distro.12:57
evrardjpgmann: I thought of that, when I brought the addition of the opensuse support in fact.12:59
gmannevrardjp: +1. "refactoring" need someone to distribute load which is difficult now a days. I still feel, this is what BoD should help at least on horizontal team resources.12:59
evrardjpand you're right, only a few test centos or opensuse12:59
fungiwe also went for years without devstack working on centos but still claimed openstack ran on it12:59
evrardjpbut for me if a deployment project test centos/opensuse, it's good enough for the users, as its what the users are doing12:59
njohnstongmann: Perhaps we should add an investment opportunity for QA team members?12:59
evrardjpnjohnston: I think it already is there13:00
evrardjpbut sure, I don't mind ensuring that for 2020, this is proposed.13:00
njohnstonevrardjp: I checked https://governance.openstack.org/tc/reference/upstream-investment-opportunities/ and did not see it13:00
gmannnjohnston yeah, that is good idea.13:00
gmannevrardjp not till now.13:00
evrardjpI thought it was, my bad.13:00
gmannevrardjp but PTI says every project need fucntional jobs for each distro13:00
evrardjpnjohnston: do you want to propose it?13:01
gmannnot only deployment projects13:01
evrardjpwas it every project?13:01
njohnstonevrardjp: Definitely.13:01
evrardjpdamn my memory is bad13:01
fungi"Each project should run some functional tests on these platforms..."13:01
fungihttps://governance.openstack.org/tc/reference/project-testing-interface.html#pti-linux-distros13:01
gmannyes13:01
fungi(one could argue that "should" is not the same as "must")13:02
gmannhum, that is good point.13:02
evrardjp"Each project should run some functional tests on these platforms so we make sure OpenStack works with distros used in production. " -> I think it was on purpose made vague13:02
evrardjpwell thanks fungi again :D13:03
evrardjpWith the explicit:13:03
evrardjp"The scope of these functional tests are discussed for every project, and may adjust their coverage depending of resources and support investment"13:03
fungiit was made vague, because we have a lot of different sorts of projects and not all of them can be tested in the same ways13:03
evrardjpyeah exactly13:03
evrardjpand as long as one could test _multiple_ projects for the distro, we were happy. We didn't want to multiply tests for no reason13:03
fungiin the past, when devstack wasn't working on centos yet, we argued that projects like tripleo exercising openstack on that platform was a means of providing coverage for the projects they integrate, even if not every project runs tripleo jobs on every proposed change13:05
evrardjpBut I think this was contentious in the past, and I would look forward a different wording and simplifications, assuming there are resources provided to qa to make things happen13:05
evrardjpfungi: yeah that's it!13:05
evrardjpfungi: thanks for being the smart living hard drive that you are :p13:06
*** slaweq has joined #openstack-tc13:13
gmanncoming back to frickler question, do we have functional tox jobs/template for centos/opensuse ? so that we can say project can still test their code on centos7/opensuse even devstack not supporting centos.13:14
*** rpittau|bbl is now known as rpittau13:14
*** slaweq__ has quit IRC13:15
*** Luzi has joined #openstack-tc13:16
evrardjpI suppose that OSA has for centos opensuse.13:17
evrardjpit's worth checking if it's still the case13:17
fungiit's also debatable how much unit tests for a lot of projects cross the boundary into functional testing territory (nova requiring a running mysql datavbase and libvirt, swift requiring a local xfs filesystem, and so on)13:20
fungithe "unit tests" in many projects are not very thoroughly mocked out where system resources are concerned13:21
njohnstonneutron has a neutron-centos-7-tripleo-standalone job that is currently on hold because of drop-py27 issues13:21
njohnstonthat is on centos 713:21
fungiyeah, i was going to say, it's probably not testing on centos 8 anyway if it's blocked on needing python 2.713:22
fungigetting devstack into working order on centos 8 is obviously preferable, but if we can't by ussuri release day for some reason or another then we probably have the ability to say we expect openstack to work on centos 8 based on other indicators13:26
fungiand i'm supposing the situation is similar for opensuse13:26
toskyafaik the RDO plan (and not only RDO) is to have everything in shape before the release13:29
*** jamesmcarthur has joined #openstack-tc13:31
toskyso I understand that this is a painful situation, but it should be solved before the release13:33
gmannfungi "say we expect openstack to work on centos 8 based on other indicators"  - 'other indicators' you mean with current testing on deployment projects or if each project start functional tests ?13:33
*** gmann_ has joined #openstack-tc13:40
*** gmann has quit IRC13:40
*** gmann_ is now known as gmann13:40
*** gmann has quit IRC13:40
*** gmann has joined #openstack-tc13:41
*** ijolliffe has joined #openstack-tc13:42
*** jamesmcarthur has quit IRC13:44
*** jamesmcarthur has joined #openstack-tc13:45
fungigmann: or by observing tripleo's jobs running successfully on centos-8 nodes (once they do)13:47
fungior if openstack-ansible is testing on centos-8 with a majority of popular services13:47
slaweqnjohnston: gmann I think that everything in TripleO is run on centos7 now13:47
fungiright, i believe they're held up by the same rdo delays as devstack is13:48
slaweqalso e.g networking-midonet was testing with tempest on centos7 but now those jobs are probably removed as they were broken for different reasons13:50
gmannok, and we need to change that 'should' to 'must in PTI' sometime. may be after ussuri as py2 drop is very noisy to do on testing side in this cycle.13:50
*** jamesmcarthur has quit IRC13:50
fungigmann: doing that might also depend on being more specific on what we mean by "project" in that case13:51
gmannslaweq: ok. i think midonet is something did not support bionic also ? that is what i remember when migratin to bionic in stein13:51
gmannfungi: every code repo ?13:51
*** jamesmcarthur has joined #openstack-tc13:52
fungigmann: tripleo must run functional tests on platforms they lack support for? and how about the repos for the i18n team? infrastructure team's repos? ...13:52
fungii have a feeling if we said tripleo must run functional tests on ubuntu and opensuse, they'd have to just cease being part of openstack instead13:53
fungii wonder similarly if openstack-charms would ever work on centos or opensuse13:54
fungirequiring functional tests of the packaging-rpm teams deliverables on ubuntu would be similarly weird13:55
gmannyeah13:55
fungifor that matter teams like qa and release management may have deliverables which make no sense to require testing on multiple platforms13:56
gmannsome qa tooling need like Tempest, patrole but not all13:57
fungiright, requiring cross-platform testing for openstack-health and coverage2sql, maybe eslint-config-openstack would seem like overkill13:58
slaweqgmann: correct13:59
fungiso yeah, i think "should" is better than "must" there unless we more tightly scope the term "projects"14:00
*** lbragstad has joined #openstack-tc14:19
*** Luzi has quit IRC14:45
cmurphyftr keystone tests on opensuse14:49
*** witek has quit IRC15:03
*** rpittau is now known as rpittau|brb15:04
*** lpetrut has quit IRC15:08
*** rpittau|brb is now known as rpittau15:20
fungivia devstack, or other means?15:32
cmurphyfungi: via devstack15:35
cmurphyhttps://opendev.org/openstack/keystone/src/branch/master/.zuul.yaml#L35-L6515:36
fungicool, so it's at least working there for some projects15:37
jrosseropenstack-ansible is reasonably close to having something on centos8 - getting some help to iron out non openstack related changes centos7<>8 would be super helpful there15:37
*** jamesmcarthur has quit IRC15:38
jrosserit's not really clear who to reach out to for that15:38
*** jamesmcarthur has joined #openstack-tc15:38
*** witek has joined #openstack-tc15:39
njohnstonjrosser: What kind of changes?15:41
njohnstonjrosser: You could talk with the tripleo guys, see how they're handling those issues15:42
jrosserone trivial example is i can't make repo priorities work15:42
*** david-lyle is now known as dklyle15:53
*** bnemec has quit IRC15:55
*** bnemec has joined #openstack-tc15:56
*** jamesmcarthur has quit IRC16:10
*** jamesmcarthur has joined #openstack-tc16:12
*** jamesmcarthur has quit IRC16:17
*** jamesmcarthur has joined #openstack-tc16:22
*** jamesmcarthur has quit IRC16:27
*** slaweq has quit IRC16:37
*** rpittau is now known as rpittau|afk17:02
*** jamesmcarthur has joined #openstack-tc17:07
*** e0ne has quit IRC17:08
*** jamesmcarthur has quit IRC17:20
*** jamesmcarthur has joined #openstack-tc17:21
*** jamesmcarthur has quit IRC17:27
*** jamesmcarthur has joined #openstack-tc17:29
*** jamesmcarthur has quit IRC17:33
*** jamesmcarthur has joined #openstack-tc17:33
*** evrardjp has quit IRC17:34
*** evrardjp has joined #openstack-tc17:34
*** witek has quit IRC17:38
*** jamesmcarthur has quit IRC17:38
*** tosky has quit IRC17:40
*** jamesmcarthur has joined #openstack-tc17:41
*** jamesmcarthur has quit IRC17:43
*** jamesmcarthur has joined #openstack-tc17:44
*** jamesmcarthur has quit IRC17:48
*** jamesmcarthur has joined #openstack-tc17:53
*** diablo_rojo has joined #openstack-tc17:55
*** jamesmcarthur has quit IRC18:02
*** jamesmcarthur has joined #openstack-tc18:04
*** e0ne has joined #openstack-tc18:10
*** e0ne_ has joined #openstack-tc18:13
*** e0ne has quit IRC18:13
*** jamesmcarthur has quit IRC18:27
*** jamesmcarthur has joined #openstack-tc18:33
*** jamesmcarthur has quit IRC18:44
*** e0ne_ has quit IRC19:12
*** lbragstad has quit IRC20:48
*** ijolliffe has quit IRC20:51
*** iurygregory has quit IRC22:29
*** tosky has joined #openstack-tc22:31
*** camelCaser has quit IRC22:57
*** camelCaser has joined #openstack-tc22:58
openstackgerritNate Johnston proposed openstack/governance master: Add QA upstream contribution opportunity  https://review.opendev.org/70663723:34

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