Wednesday, 2019-10-09

*** markvoelker has quit IRC00:05
*** markvoelker has joined #openstack-tc00:07
*** markvoelker has quit IRC00:14
*** markvoelker has joined #openstack-tc00:19
*** diablo_rojo has joined #openstack-tc00:37
*** ijolliffe has quit IRC00:37
zanebo/01:00
*** njohnston_ has joined #openstack-tc01:09
njohnston_o/01:10
*** njohnsto_ has joined #openstack-tc01:11
*** njohnston_ has quit IRC01:14
*** njohnsto_ has quit IRC01:18
*** ricolin has joined #openstack-tc02:21
*** markvoelker has quit IRC03:09
*** markvoelker has joined #openstack-tc03:10
*** markvoelker has quit IRC03:23
*** markvoelker has joined #openstack-tc03:24
*** diablo_rojo has quit IRC03:40
*** markvoelker has quit IRC04:35
*** markvoelker has joined #openstack-tc04:35
openstackgerritMerged openstack/governance-sigs master: New UC Rep  https://review.opendev.org/68739205:13
*** jaosorior has quit IRC06:33
*** jaosorior has joined #openstack-tc07:04
evrardjpo/07:08
*** tosky has joined #openstack-tc07:14
*** iurygregory has joined #openstack-tc07:21
evrardjpAs a reminder, I am out for holidays tomorrow afternoon.07:27
*** tosky has quit IRC07:58
*** tosky has joined #openstack-tc07:59
*** e0ne has joined #openstack-tc08:39
asettleo/08:52
*** jaosorior has quit IRC08:53
*** jaosorior has joined #openstack-tc09:31
*** jamesmcarthur has joined #openstack-tc10:15
*** jamesmcarthur has quit IRC10:19
ricolino/10:27
*** lpetrut has joined #openstack-tc10:39
njohnstono/11:08
mugsieo/11:25
*** nicolasbock has joined #openstack-tc11:28
mnaserhttps://www.suse.com/c/suse-doubles-down-on-application-delivery-to-meet-customer-needs/11:35
mnaser:/11:35
*** nicolasbock has quit IRC11:39
*** nicolasbock has joined #openstack-tc11:39
jroll:(11:42
asettleYisss if you have any questions, will do my best to answer them11:49
*** jaosorior has quit IRC11:58
cmurphyit's official i guess12:17
asettleAye12:26
*** jaosorior has joined #openstack-tc12:28
mnaserwhat does that mean for those who are working on openstack right now?12:28
cmurphyunclear12:30
mnasercmurphy: i hope it all clears out for you (and others) in the .. best way possible :(12:33
cmurphythanks mnaser12:34
*** zhipeng has quit IRC12:35
*** mriedem has joined #openstack-tc12:44
*** ijolliffe has joined #openstack-tc12:49
jungleboyjA sad morning.12:53
jungleboyjo/12:54
jungleboyjevrardjp: You around?12:56
*** markvoelker has quit IRC13:10
*** markvoelker has joined #openstack-tc13:11
*** markvoelker has quit IRC13:11
*** markvoelker has joined #openstack-tc13:11
*** AlanClark has joined #openstack-tc13:21
*** bnemec has quit IRC13:29
*** bnemec has joined #openstack-tc13:31
*** jaosorior has quit IRC13:33
evrardjpI am.13:35
*** ianychoi has quit IRC13:41
gmanno/13:43
gmannoh, that's surprising news.13:43
*** AlanClark has quit IRC13:51
*** sapd1_ has joined #openstack-tc13:53
*** gagehugo has quit IRC13:56
*** tonyb has quit IRC13:56
*** scas has quit IRC13:56
*** sapd1 has quit IRC13:56
*** openstackstatus has quit IRC13:58
jungleboyjevrardjp:  Hey.  I responded to the mailing list.  I thought I had sent an e-mail volunteering to look at the User Survey.14:01
*** jaosorior has joined #openstack-tc14:03
*** lpetrut has quit IRC14:09
*** jamesmcarthur has joined #openstack-tc14:19
mnaserhm14:29
mnaserare we meeting?14:29
mnaseri got sucked into things but i was waiting for the expected usual ping14:29
mnaserafaik 1430 utc14:30
jungleboyjmnaser:  I had that the meeting time was last hour, but I could be wrong.14:30
mnaserno, that is the right time14:30
jungleboyjOk, Phew.14:30
mnaser1400 utc is the meeting, 1500 utc is office hours afterwards.14:30
jungleboyjOh, the meeting isn't until tomorrow though  At this time.14:31
mnaseroh shit14:31
mnaserwe'14:31
mnaserwe're not thursday14:31
mnaserwtf14:31
mnaserwhy did i-14:31
mnaseroh well14:31
jungleboyjEveryone is off this week.14:31
jungleboyjOff as in thrown off.14:32
jungleboyjAnyway, the only question I had is when people needed me to have looked through the User Feedback if I am taking that work item.14:32
ttxmnaser: the good side is.. you just won an extra day in the week!14:33
mnaserwoo?14:34
ttxheh14:34
jungleboyjI feel like it should be Thursday too.14:34
gmannjungleboyj: thanks for taking user feedback work.14:41
asettleDefinitely has a Thursday feel14:41
asettleBut no, not meeting today :D14:41
jungleboyjgmann:  Welcome.  I have always enjoyed understanding it for Ciner.14:41
jungleboyj*Cinder14:41
gmannI miss my FC SIG meeting due to those weekdays confusion :). meeting notes on board works much better than machinery calendars :)14:43
gmannjungleboyj: +1. this is first time for TC so new thing for us.14:43
jungleboyjgmann:  Ok.  So, it is mine to run with.  :-)14:44
jungleboyjgmann: I will scan over the data before our meeting tomorrow.  Won't have time to go through it in details but will try to have a plan to discuss at least.14:45
gmannjungleboyj: +1.14:46
jungleboyjgmann:  Cool.  Sorry, I had thought I responded to the mailing list about that last week.  :-)14:48
gmannjungleboyj: i think you did.14:49
jungleboyjOh good.  I am not crazy.  evrardjp  is.14:50
gmann:) he might have missed that.14:51
*** diablo_rojo has joined #openstack-tc15:06
evrardjpSorry I missed this. Will read asaic.15:10
*** jaosorior has quit IRC15:11
*** iurygregory has quit IRC15:20
*** lpetrut has joined #openstack-tc15:21
gmanntc-members: i would like to discuss the plan for the py2.7 drop. It need unit/functional tests jobs (this is going to be automatic bot work i think) and integration testing (tempest and other jobs which needs to be manually done).15:27
gmannwe can plan the ad-hoc meeting like we did for py3 plan.15:28
gmannpy2.7 Integration jobs are the big one which can speed up the projects gate. especially grenade, tempest and project specific job.15:30
fungiis there any reason to mass propose removal of py27 testing? can't projects just remove it at their own pace (or leave it if they want to keep testing py27 for a while, since there are some who surely will want that)15:34
fungiwe said it's acceptable for projects to drop py27 jobs from master after the train release, not that it's required15:35
*** lpetrut has quit IRC15:35
fungiit's not as if python 2.7 interpreters are going to suddenly disappear from the platforms we're doing testing on15:36
gmannyeah, if any project want they can keep but we have not said officially that other can drop py2.715:36
gmannit was plan to drop in start of U cycle i think but was not confirmed (if i did not miss)15:37
fungithe plan was that it was okay for projects to drop those jobs at the start of the u cycle if they want15:37
gmannthere were some patches of dropping the py2.7 integration jobs (grenade one) and I hold those till U15:38
funginow certainly if frameworks like devstack, tempest or grenade want to drop support for 2.7 in master, then projects will end up needing to drop any 2.7 variants of those jobs15:38
gmann+1, so we can communicate the same via ML and start the effort from integration-gate  template or new tempest template15:38
gmanndevstack and greande can as they are branched but Tempest have to keep for stable branch testing.15:39
fungibut also didn't train switch to running those on python 3 by default anyway?15:39
gmannyes but doing py2.7 + p3 both.15:39
fungiahh, yeah, tempest will need to support 2.7 for stable branches i guess, if we want to be able to run it on platforms which lack python315:40
fungithough it does seem like it might be possible to move tempest to python 3 for testing those branches if we want, since we install it into a virtualenv anyway15:41
fungithat could be a compromise down the line if 2.7 support in tempest becomes increasingly burdensome15:41
gmannwe can but we need to test py2.7 along with py3 as that is one of the official supported py version by openstack releases15:42
fungiright, but running tempest on 2.7 doesn't test openstack running on 2.7. tempest is in an isolated virtualenv15:42
fungiyou can run tempest from a python3 venv and test openstack deployed/running with 2.715:43
fungitempest has already been isolated from the rest of the devstack deployment for many cycles15:43
gmannyeah, if they have py3 env to run tempest.15:44
fungithe main reason to continue supporting 2.7 in tempest is if you want people to be able to run it on platforms where it's challenging to install a python3 interpreter to be able to create that venv, right15:45
fungiso, like, if we have any jobs which run tempest on centos-7 nodes (do we?)15:45
gmannyes. + if some users run Tempest directly on system pkg not venv.15:46
fungithough tempest may not support running coinstalled with old devstack these days... i don't think we test that's even possible without a separate virtualenv15:47
gmannyes, we have centos-7 jobs15:47
*** iurygregory has joined #openstack-tc15:47
fungiand we don't install tempest in a virtualenv on those?15:47
fungithe whole reason we started installing it into a virtualenv was that its dependency versions drifted from what stable branches need15:47
gmannit is running with old devstack at least tested for all supported stable.15:48
gmannand with master u-c15:48
fungiso a stable/rocky devstack+tempest job installs openstack projects system-wide with the rocky constraints list and builds the tempest virtualenv with the master constraints set15:48
fungithat job is not (as far as i know) installing tempest outside a virtualenv using the same dependencies as the stable branch, is it?15:49
fungithat's what i mean by them not being coinstallable anyway15:49
gmannyeah it is with venv not outside.15:50
*** openstackgerrit has quit IRC15:52
gmannasettle: evrardjp let me know if it is ok to add that in agenda for tomorrow meeting ? if its late now then we can discuss the same in office hour or ad-hoc meeting.15:56
evrardjpgmann: well I don't expect the community to be aware of the conversation above with magic, so it would be a little hard for anyone to know this has happened... Maybe we could say on the ML we'll be talking about that after the meeting?15:58
evrardjpthat was poorly worded, let me rephrase :)15:59
evrardjpI expect the people paying attention to this channel would be a subset or a different set that people who might want to attend your conversation. What do you think fo sending an ML email to warn about the topic happening? Or maybe I missed an email (totally plausible! :) )?16:01
fungii think the primary takeaway is that there should be an ml thread covering the timeline for devstack and grenade dropping python 2.7 support in master, as well as what to do about tempest in the near term and over time16:04
gmannevrardjp: I got it and make sense to me. It does not need to be in meeting as it can be detailed discussions. we can do in office hour after meeting. if looks ok then I can send email (not sent yet) to openstack-discuss that this is happening in tomorrow office hour if anyone want to join the discussion or want to get the final updates about the py2.7 drop plan.16:04
fungiand also of course reminding projects that they're free to drop whatever other 2.7 jobs they like from master now (or maybe not until after next week just in case they need to worry about backportability to stable/train in the interim)16:05
gmanndevstack and grenade will be part of same discussion. + Tempest plan also16:05
gmannfungi: +1.16:06
gmannwe can define the timeline about when it should happen like during summit (if many patches needed and not to load gate resources) or something.16:06
gmannthough CI  (zuul.yaml) update of dropping py2.7 jobs should be ok as they do not get back-ported.16:08
gmannor to avoid any confusion or extra work during train release, we can do after official release also something like 21st oct week..16:11
*** jamesmcarthur has quit IRC16:22
*** jamesmcarthur has joined #openstack-tc16:30
*** jamesmcarthur has quit IRC16:35
*** jamesmcarthur has joined #openstack-tc16:39
*** bnemec has quit IRC16:45
*** bnemec has joined #openstack-tc16:47
*** AlanClark has joined #openstack-tc16:51
gmanntc-members: please let me know if 24th office hour (Where most of the TC members are available) is ok to discuss the final plan for py2.7 drop. accordingly I will communicate the same in ML if other community members want to join/get update or so.16:52
*** markvoelker has quit IRC16:53
mnaserok for me, i block out office hours on my calendar16:53
jungleboyjYep.  Same here.16:54
evrardjpok16:54
*** markvoelker has joined #openstack-tc16:54
njohnstonme too16:57
*** mriedem is now known as mriedem_afk16:58
*** e0ne has quit IRC17:02
zaneb+117:03
*** ricolin has quit IRC17:41
*** gagehugo has joined #openstack-tc17:49
*** nicolasbock has quit IRC18:15
*** nicolasbock has joined #openstack-tc18:17
*** mriedem_afk is now known as mriedem18:18
*** openstackgerrit has joined #openstack-tc18:22
openstackgerritKendall Nelson proposed openstack/election master: Re-Add Kendall as Election Official  https://review.opendev.org/68764618:22
*** e0ne has joined #openstack-tc18:25
fungiwoo! someone new to review my endless patches18:25
fungitc-members: ^ that's technically a tc delegation so need some of you to give your blessing18:27
jungleboyjDone.18:29
fungithanks!18:39
*** jamesmcarthur has quit IRC18:45
gmannfinally got my passport and china visa with single entry tough.18:46
fungicongrats! i'm still waiting. they came back to me with a request for more paperwork, which i provided, but... you never know18:54
gmannohh, hope for best.18:55
*** e0ne has quit IRC19:00
fungiwith my background, i won't be too surprised if they deny me. i mean... ecuador is now jailing computer security researchers at random19:04
fungithere's a lot of governmental distrust of people with backgrounds in security and cryptography19:04
fungii don't *expect* a problem, but i always assume it's a possibility19:06
*** e0ne has joined #openstack-tc19:08
*** mgagne has quit IRC19:11
*** zaneb has quit IRC19:33
*** zbitter has joined #openstack-tc19:33
*** iurygregory has quit IRC19:37
*** e0ne has quit IRC19:56
*** lpetrut has joined #openstack-tc20:41
*** lpetrut has quit IRC20:52
*** AlanClark has quit IRC21:10
*** lpetrut has joined #openstack-tc21:13
*** lpetrut has quit IRC21:30
*** cloudnull is now known as cloudnull-afk21:42
*** diablo_rojo has quit IRC21:47
*** ijolliffe has quit IRC22:12
*** markvoelker has quit IRC22:28
*** mriedem has quit IRC22:30
*** jamesmcarthur has joined #openstack-tc22:42
*** openstackstatus has joined #openstack-tc23:19
*** ChanServ sets mode: +v openstackstatus23:19
*** tosky has quit IRC23:30
*** jamesmcarthur has quit IRC23:43
*** dklyle has quit IRC23:47
*** david-lyle has joined #openstack-tc23:47
*** markvoelker has joined #openstack-tc23:48
*** markvoelker has quit IRC23:59

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