Tuesday, 2021-02-02

airship-irc-bot1<kk6740> @craig.anderson could you help me with couple of things related to image builder?00:53
airship-irc-bot1<kk6740> 1. does it use bundle in any way build from documentEntrypoint in phase?00:54
-openstackstatus- NOTICE: The Gerrit service on review.opendev.org is being quickly restarted to apply a new security patch00:55
*** uzumaki has quit IRC02:32
airship-irc-bot1<craig.anderson> @kk6740 no03:09
*** irclogbot_2 has quit IRC03:27
*** uzumaki has joined #airshipit03:28
*** irclogbot_2 has joined #airshipit04:14
*** irclogbot_2 has quit IRC04:20
*** lemko2 has joined #airshipit04:28
*** lemko2 has quit IRC04:29
*** lemko0 has joined #airshipit04:29
airship-irc-bot1<kk6740> @craig.anderson Can we have a sync tomorrow, I can show you how to do all this without requiring almost no changes to airshipctl, only manifests need to be changed.  However i will need some input from you on how image builder container should be run.04:30
*** lemko has quit IRC04:30
*** lemko0 is now known as lemko04:30
airship-irc-bot1<craig.anderson> @kk6740 k, sure04:39
airship-irc-bot1<craig.anderson> also the pipeline is failing but I think that's due to another patchset merged today04:40
*** irclogbot_1 has joined #airshipit04:40
airship-irc-bot1<kk6740> that is because we disabled gate tests :slightly_smiling_face:04:40
airship-irc-bot1<kk6740> and manifests got broken04:40
airship-irc-bot1<kk6740> i’ve prepared a fix for this, however, it seems like there is another issue related to tigera and calico as well.04:41
airship-irc-bot1<craig.anderson> ahh04:41
airship-irc-bot1<craig.anderson> I see04:41
*** irclogbot_1 has quit IRC04:54
*** irclogbot_2 has joined #airshipit04:57
airship-irc-bot1<aodinokov> @craig.anderson you can try to rebase on top of https://review.opendev.org/c/airship/airshipctl/+/772467 this patchset seems like passing05:57
*** uzumaki has quit IRC08:09
*** muhaha has joined #airshipit09:08
*** uzumaki has joined #airshipit11:32
airship-irc-bot1<rp2723> Folks there is no topic in the design call hackmd page for today, I checked and there is also no issue needing design we should discuss today. Last call for topics before I send a cancellation notice for the Design Call today .12:23
*** sreejithp has joined #airshipit14:14
airship-irc-bot1<alexander.hughes> hello team, IRC meeting is in ~30 minutes with 1 agenda item. please add any items you'd like to discuss, or patches you'd like reviewed14:27
airship-irc-bot1<alexander.hughes> #link https://etherpad.opendev.org/p/airship-team-meeting14:27
*** uzumaki has quit IRC14:36
mattmceuen#startmeeting airship15:00
openstackMeeting started Tue Feb  2 15:00:28 2021 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: airship)"15:00
openstackThe meeting name has been set to 'airship'15:00
mattmceuen#topic Rollcall15:00
*** openstack changes topic to "Rollcall (Meeting topic: airship)"15:00
airship-irc-bot1<ih616h> o/15:00
mattmceuenGood morning/evening everybody!15:00
airship-irc-bot1<alexander.hughes> o/15:00
airship-irc-bot1<sirajudeen.yasin> o/15:00
airship-irc-bot1<j_t_williams> o/15:01
airship-irc-bot1<ak3216> o/15:01
mattmceuenLet's give it just a couple minutes for folks to join - here's our agenda:  https://etherpad.opendev.org/p/airship-team-meeting15:01
airship-irc-bot1<mb551n> o/15:01
*** dwalt has joined #airshipit15:01
dwalto/15:01
jemangso/15:02
airship-irc-bot1<james.gu> o/15:04
mattmceuenOk, let's get started15:04
mattmceuenShort agenda today --15:04
mattmceuen#topic OpenSUSE builds15:04
*** openstack changes topic to "OpenSUSE builds (Meeting topic: airship)"15:04
mattmceuenThe background for anyone not familiar with it is that we have a collection of builds in our Airship 1 gates to test ingration of Airship 1 components on OpenSUSE images15:05
airship-irc-bot1<alexander.hughes> That one's mine :slightly_smiling_face: just wanted to have a quick discussion on the state of Airship1 image build pipelines - which image builds do we want to support? Most (all?) projects currently build an Ubuntu Xenial, Ubuntu Bionic, and an OpenSUSE image15:05
mattmceuenAre the SUSE jobs currently failing or passing?15:06
airship-irc-bot1<alexander.hughes> SUSE is passing currently, Xenial just recently started failing with pip errors and needed some updates to keep building images15:06
mattmceuenSo I think the key word you have in your original question is "support"15:07
airship-irc-bot1<alexander.hughes> But the question to me is, as a community, how much effort do we put into these images that are seemingly unused - our reference configuration in Treasuremap isn't being updated and certainly isn't using SUSE.  I believe (correct me if I'm wrong) that the images in TM are all Bionic15:07
mattmceuenAfter the folks who were working on the opensuse integration shifted their focus away, I think we left the gates in place because they did more good than harm - no harm in letting them continue to run green15:08
mattmceuenI think the question is, what happens if they break?  And other things that would take active work15:08
airship-irc-bot1<alexander.hughes> yep, I don't mind to leave them in place as they run, but the xenial failures last week prompted a thought exercise on what we do with the less popular image build pipelines as they begin to fail15:09
portdirectosa faced this challenge15:09
portdirectonce the gates broke, they moved them to non-voting, and put a message out to the ml15:10
portdirectAFAIK after two-three weeks, they ere then removed15:10
portdirect*were15:10
mattmceuenThat makes a lot of sense.  Gives anyone with an interest in opensuse support a chance to fix them if they want15:10
mattmceuenSound reasonable to you too @alexander.hughes?15:11
airship-irc-bot1<jb2592> I'd say remove support for ubuntu xenial, but we should add for ubuntu focal15:11
airship-irc-bot1<alexander.hughes> yes, but should we limit the scope of this approach to OpenSUSE or should we include xenial as well?15:12
portdirectI'd two them in two seperate actions15:12
airship-irc-bot1<alexander.hughes> and to Jim's point, should we add newer Ubuntu image distros to the image build pipelines15:12
portdirectif suse's not broken atm - leave it for now15:12
mattmceuen+115:12
portdirectbut its high time airship2 supported focal - and i dont thing anyones doing net-new 16.04 deployments15:13
mattmceuenAgree, I'll get that added to our backlog if it's not already there15:13
airship-irc-bot1<alexander.hughes> agree but we're straying from the original question - Airship2 should definitely support focal, but Airship1 ?15:13
portdirectare people using xenial in production with as1?15:14
portdirectif so - id keep xenial builds working until their sites migrate to newer distro15:15
portdirectmay save some weekend work if a hotfix is needed ;)15:15
mattmceuenYeah, there are still some production deployments I know of using 1604, so it would be worth a bit of effort to keep those gates running15:17
airship-irc-bot1<j_t_williams> IMO, there needs to be a commitment within the community to support previous Airship versions N-months beyond the release of a newer version, unless the community falls in line with dropping support.15:17
airship-irc-bot1<alexander.hughes> so to make sure I understand your position - for Airship 1: support images that are still used in prod deployments, 2: leave in place image build pipelines that are not used in prod deployments until they begin to fail on their own - at which point, change to non-voting and communicate to community that support is ending unless someone wants to begin maintaining, 3: no new image build pipelines (e.g., focal for Airship 115:18
airship-irc-bot1projects)15:18
mattmceuenAgree that community needs are paramount.  There can be a long tail on production deployments, so the "is anyone still using this" question is important15:18
airship-irc-bot1<j_t_williams> @alexander.hughes I agree with your comment.15:19
portdirectalexanderhughes: ++15:20
mattmceuenI'm not sure if we should take a "# of months" approach, at least for airship1, since it has only a handful of operators.  If all those operators have moved on from a version, then there's no need to support15:20
airship-irc-bot1<alexander.hughes> so on (1) supporting what's in prod, perhaps a survey to the community is in order so we can understand what's being used and start setting tentative dates on ending support for old images15:20
portdirectmattmceuen: agreed - i think we should however give ax month period for a as yet unknown user to step up15:20
mattmceuenthat makes sense15:21
airship-irc-bot1<alexander.hughes> and with airship2 around the corner, that survey could provide an update on airship2 status and steps on getting started for new deployments15:21
mattmceuenshould we add that to our current (ongoing) survey and then blast it out?15:21
airship-irc-bot1<j_t_williams> I think so15:21
mattmceuenok cool, I'll sync w/ Ashlee on that15:22
airship-irc-bot1<alexander.hughes> I think that could be a separate item as part of Airship2 GA announcement personally - communicate GA, and get a sense of who is using A1 and if they plan to move to A2 and how long they plan to keep their A1 deployments15:22
airship-irc-bot1<alexander.hughes> could alternatively update the existing survey, and include as part of the GA announcement when it occurs15:23
airship-irc-bot1<j_t_williams> The only reason for a N month or some deadline is to prod the community to look beyond the current version.15:23
portdirectit would be really nice to see that data by industry alexanderhughes15:23
airship-irc-bot1<alexander.hughes> agreed, our engagement on the surveys has been low, I'd like to take that to one of the committee meetings and review current responses and our approach to socializing the survey15:24
mattmceuenSounds good - we can carry that one forward to our next WC or TC meeting, we have some time15:25
airship-irc-bot1<alexander.hughes> +115:25
airship-irc-bot1<j_t_williams> +1, I'm Ok with that but there no harm to adding it to the survey.  Feedback in any for is good.15:26
mattmceuenyeah, not mutually exclusive15:26
mattmceuenAlright, anything else on this one alexander.hughes?15:26
airship-irc-bot1<alexander.hughes> yep, so recap real quick -- airship2: Matt will add Focal support to backlog if not already present // airship1: survey when airship2 GA releases to discuss support of airship1 projects going forward, we will not be adding any new image build pipelines, and existing pipelines will be maintained as long as their is prod use of the images generated by them - if there is not they will be moved to non-voting for a period of15:27
airship-irc-bot1time before being disabled (with communication sent to community to verify that image is no longer being used)15:27
airship-irc-bot1<alexander.hughes> there*15:27
mattmceuenSounds good!  That is copy-paste-save worthy, thanks for the summary15:28
airship-irc-bot1<alexander.hughes> thanks :slightly_smiling_face:15:28
airship-irc-bot1<alexander.hughes> that's all from me15:28
mattmceuen#topic Review Requests & Roundtable15:28
*** openstack changes topic to "Review Requests & Roundtable (Meeting topic: airship)"15:28
mattmceuenOne request this morning:  https://review.opendev.org/c/airship/airshipctl/+/77308415:28
airship-irc-bot1<alexander.hughes> 2 liner ^ updating the linter to include newer version of gosec15:29
mattmceuenit's a tiny one, let's try to get it reviewed today15:29
mattmceuenAny other patchsets folks would appreciate timely reviews on?15:29
mattmceuenAlright, then we can have a half hour back - thanks everybody for your time today15:31
mattmceuenhave a good one15:31
airship-irc-bot1<alexander.hughes> thanks all!15:31
mattmceuen#endmeeting15:31
*** openstack changes topic to "https://opendev.org/airship || https://wiki.openstack.org/wiki/Airship || https://review.opendev.org/#/q/projects:airship+status:open+NOT+label:Verified%253D-1+NOT+label:Workflow%253D-1+NOT+message:DNM+NOT+message:WIP"15:31
openstackMeeting ended Tue Feb  2 15:31:36 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2021/airship.2021-02-02-15.00.html15:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2021/airship.2021-02-02-15.00.txt15:31
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2021/airship.2021-02-02-15.00.log.html15:31
airship-irc-bot1<mf4716> thanks folks - make it a great day15:31
*** uzumaki has joined #airshipit15:38
airship-irc-bot1<ih616h> Is anyone seeing new issues with the `25_deploy_ephemeral_node.sh` script? I'm seeing this, which wasn't happening yesterday  ```loading generator plugins: 2 errors occurred:         * accumulateFile error: "accumulating resources from 'hostgenerator': '/tmp/airship/airshipctl/manifests/site/test-site/host-inventory/hostgenerator' must resolve to a file"         * accumulateDirector error: "recursed accumulation of path15:39
airship-irc-bot1'/tmp/airship/airshipctl/manifests/site/test-site/host-inventory/hostgenerator': no matches for OriginalId airshipit.org_v1alpha1_VariableCatalogue|~X|password-secret; no matches for CurrentId airshipit.org_v1alpha1_VariableCatalogue|~X|password-secret; failed to find unique target for patch airshipit.org_v1alpha1_VariableCatalogue|password-secret"```15:39
airship-irc-bot1<kk6740> yes15:39
airship-irc-bot1<kk6740> WIP15:40
airship-irc-bot1<ih616h> eta? or should I target an older commit15:40
airship-irc-bot1<kk6740> u can help :slightly_smiling_face:15:40
airship-irc-bot1<kk6740> one second15:41
airship-irc-bot1<kk6740> it is done, just need to wait for merge15:41
airship-irc-bot1<kk6740> https://review.opendev.org/c/airship/airshipctl/+/77357915:41
airship-irc-bot1<ih616h> nice, thanks @kk674015:42
airship-irc-bot1<ih616h> looks like that's already got approvals15:42
airship-irc-bot1<ih616h> commit message say it fixes toos/deployment/30_*scripts?15:43
airship-irc-bot1<kk6740> yes, i wrote it because at the moment i had fix for 25_  localy15:44
airship-irc-bot1<kk6740> but it fixes it15:44
airship-irc-bot1<ih616h> ah, makes sense15:44
*** uzumaki has quit IRC15:55
*** uzumaki has joined #airshipit15:57
*** muhaha has quit IRC17:42
airship-irc-bot1<steven.fitzpatrick> FWIW, re: supporting ubuntu 20.04 (Focal) - I was able to get things working with just a couple of small modifications to the libvirt install. I left notes here in this PS. I marked it DNM, since I am really not too familiar with libvirt and what unintended consequences this change could have. But hey, 'it works on my machine' :)   https://review.opendev.org/c/airship/airshipctl/+/768572  I'm happy to revisit this PS if17:43
airship-irc-bot1there is interest.17:43
airship-irc-bot1<rishabh.k.jain> Hi Team,  I need some core reviews on these 2 baby patch sets :) https://review.opendev.org/c/airship/airshipctl/+/772425 https://review.opendev.org/c/airship/airshipctl/+/77183918:59
*** muhaha has joined #airshipit19:13
*** dwalt has quit IRC21:21
*** uzumaki has quit IRC22:58
*** muhaha has quit IRC23:54

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