Tuesday, 2020-11-10

airship-irc-bot<mattmceuen> Hey @sreejith.punnapuzha, re: what we talked about this morning, where the deployment scripts remove the master taint to allow scheduling, and we want to do something smarter00:02
airship-irc-bot<mattmceuen> Looking at the functions, it appears that the CAPI components (and HelmOperator) should already have tolerations for the master taint00:03
airship-irc-bot<mattmceuen> So let me know what your experiment uncovers, now I think I understand the problem less than before :slightly_smiling_face:00:03
*** rezroo has joined #airshipit03:21
*** evrardjp has quit IRC05:33
*** evrardjp has joined #airshipit05:33
*** awander has quit IRC07:33
*** roman_g has joined #airshipit08:03
*** rezroo has quit IRC08:14
airship-irc-bot<victor.melin> document pull10:59
airship-irc-bot<craig.anderson> image-builder patchset could use some reviews still. thanks. https://review.opendev.org/#/c/730777/12:58
roman_gAdded ^^^ to requests for review https://etherpad.opendev.org/p/airship-meeting-2020-11-1013:15
airship-irc-bot<craig.anderson> thx13:44
*** awander has joined #airshipit13:56
mattmceuenHi all, our team meeting will begin in ~1hr.  Agenda:  https://etherpad.opendev.org/p/airship-team-meeting14:03
mattmceuen@roman_g we're using a rolling agenda etherpad now, would you mind copying your item to this one^?14:03
roman_gmattmceuen OK. Wiki needs to be updated14:04
mattmceuenthanks14:04
*** SRao has joined #airshipit14:04
roman_gWiki is updated14:12
*** dwalt has joined #airshipit14:25
mattmceuenty!15:00
dwalt#startmeeting airship15:00
openstackMeeting started Tue Nov 10 15:00:51 2020 UTC and is due to finish in 60 minutes.  The chair is dwalt. 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
mattmceueno/15:01
dwaltHey everyone, we'll get started in a few minutes. The design call is still wrapping up15:01
airship-irc-bot<ih616h> o/15:04
airship-irc-bot<mf4716> o/15:04
airship-irc-bot<james.gu> o/15:04
airship-irc-bot<ak3216> o/15:04
roman_go/15:04
dwaltWelcome to everyone filtering in from the design call. Here is our agenda today15:04
dwalt#link https://etherpad.opendev.org/p/airship-team-meeting15:04
*** sreejithp has joined #airshipit15:05
airship-irc-bot<j_t_williams> o/15:06
dwaltAlrighty, let's get things started15:06
dwalt#topic Zuul gate problems15:06
airship-irc-bot<sean.eagan> o/15:06
*** openstack changes topic to "Zuul gate problems (Meeting topic: airship)"15:06
mattmceuenFolks have probably noticed, we have a pair of unrelated but brutal issues with our gates at the moment15:06
jemangso/15:07
mattmceuenFirst: infrastructure availability for our 16gb VMs15:07
mattmceuenOf the two providers that supply them, we're back down to one working at the moment -- resulting in a lot of NODE_FAILURE type errors15:07
airship-irc-bot<lb4368> o/15:07
airship-irc-bot<mb551n> o/15:07
sreejithpo/15:07
jemangs(The same problem as earlier?)15:08
mattmceuenArijit has been working to get 3rd-party gating going per patchset15:08
mattmceuensimilar @jemangs15:08
mattmceuenI think this may be a networking problem, previously a cooling problem, or something15:08
mattmceuenCurrently the 3rd party gates are non-voting, and not (yet) reporting status up to patchsets -- that's a work in progress15:08
roman_gjemangs, similar. Previously that was AC failure, now – router malfunction.15:09
mattmceuenhttps://jenkins.nc.opensource.att.com15:09
mattmceuenWhile we get status reporiting to patchsets working, developers can manually check for their job's status in that UI^15:09
mattmceuenAnd we'd like to switch (when ready) to making the 3rd party deployment gate our voting gate, instead of the zuul deployment gate15:10
mattmceuento be clear:  all the things that can be done in "normal size" VMs -- linting, image build, etc -- would still be run via zuul15:11
mattmceuenI would propose that for the time being, we make the zuul deployment gate *on-merge only*, and then check in jenkins for per-patch testing status15:11
mattmceuenThis will get us unblocked15:12
mattmceuenThoughts/concerns?15:12
dwaltThis is great, thanks mattmceuen and sreejithp15:12
airship-irc-bot<ih616h> +115:12
dwaltDoes that mean the job would be disabled for check, and enabled voting for gate?15:12
mattmceuenyes, disabled for check -- leaving more of our limited capacity available for the merge job15:13
roman_gdwalt , Yes, but you can trigger job manually by leaving "check experimental" comment to the patch set in Gerrit15:13
airship-irc-bot<mf4716> Did we hear any more about resolution to the router malfunction?15:13
mattmceuen+115:13
dwaltThat makes a lot of sense. More reliable than relying on the cores to verify that the job passed. +1 from me15:13
mattmceuenThe longer-term (but hopefully still soon) idea would be to make the 3rd party gating Voting, and make the zuul gate non-voting15:14
mattmceuenWe should pull the trigger on that once we have status reporting back to the PS in place, and are comfortable with it15:14
roman_gmf4716 no. It's non-commercial cloud provider (basically home-based servers farm).15:15
mattmceuenAny other thoughts/comments before we move on to the other terrible gate issue? :)15:15
mattmceuenyeah - really useful from a community perspective, but can be problematic when we're relying on it for our day jobs15:15
airship-irc-bot<mf4716> any ETA roman?15:15
mattmceuenat least, when the third party gates break, it's our job to fix them :)15:15
roman_gmf4716 no ETA.15:16
mattmceuenSo issue #2:15:16
mattmceuenAnd this one may be more challenging to work around.15:17
mattmceuendockerhub has instituted rate limiting on image pulls, limiting to 100 pulls per-IP per month15:17
mattmceuenI believe we thought we'd been using some kind of image caching, but weren't, and now we've exausted our quota for the month from some of the open infra IPs15:18
mattmceuenA few ways we could potentially approach this:15:18
mattmceuen1. migrate to using the 3rd party gates as Voting ASAP, and make sure they have caching enabled -- they'll have different IPs and so won't be hurt by the quota15:18
mattmceuen2. migrate to a non-dockerhub mirror for all images hosted in dockerhub15:19
mattmceuen3. upgrade to a paid plan15:19
dwaltDo we have an estimate on the number of images impacted?15:19
mattmceuenThis is a promising (incomplete) list:15:21
mattmceuen[madgin@leviathan:~/airship2/airshipctl]$ grep -r "image: docker" manifests15:21
mattmceuenmanifests/function/helm-operator/deployment.yaml:        image: docker.io/fluxcd/helm-operator:1.2.015:21
mattmceuen[madgin@leviathan:~/airship2/airshipctl]$15:21
airship-irc-bot<rp2723> Can we put the point in time images we care about in quay and use that instead15:21
dwaltlol. That is indeed promising15:21
dwaltIf it's one image, migrating it to Quay seems like it would be feasible15:22
airship-irc-bot<rp2723> It’s a single image ?? The word list is rhetorical15:22
mattmceuenlol I should have googled earlier, mea culpa15:23
mattmceuenthere could be other images in other projects though15:23
mattmceuenbut getting airshipctl unblocked would be great15:23
airship-irc-bot<sean.eagan> helm-controller/source-controller are now in github container registry15:23
dwalt\o/15:23
airship-irc-bot<sean.eagan> (the replacements for helm operator)15:23
airship-irc-bot<sean.eagan> https://github.com/orgs/fluxcd/packages/container/package/helm-controller15:24
mattmceuenwhat about helm-operator?  We're not quite ready to switch to the helm-controller yet, are we @sean.eagan?15:24
dwaltSo is it fair to say that we can push the operator image to quay, since we are moving away from it?15:24
mattmceuenyes15:24
airship-irc-bot<sean.eagan> https://review.opendev.org/#/c/758615/15:24
mattmceuen+115:24
airship-irc-bot<sean.eagan> ^ it's merged15:24
sreejithpmattmceuen, we also need the go docker image "docker.io/golang:1.13.1-stretch"15:25
sreejithpwe use this for building airshipctl binary15:25
*** SRao has quit IRC15:26
mattmceuenahh you're right15:26
mattmceuendo we even still need helm-operator now that we have the helm-controller merged Sean?15:26
mattmceuenif we simply switch the test-site to use helm-controller, -operator wouldn't get run by the tests15:27
airship-irc-bot<sean.eagan> the function for helm-operator is still in place (for a short migration period), but it's not actually used by the default phases included in airshipctl15:27
mattmceuenthen it must only be the golang image that's hurting the gates, right?15:28
dwaltIs the gate runner failing in the pre-run playbooks or later on?15:28
dwaltI think that's when we run `make images`15:29
mattmceuen(treasuremap is using the helm-operator, so we'll need to handle that)15:29
airship-irc-bot<sean.eagan> https://review.opendev.org/#/c/761666/15:29
airship-irc-bot<sean.eagan> ^ treasuremap migration15:29
mattmceuennice!15:30
dwaltThat's great sean.eagan. Between pushing those two images to quay and finishing the helm controller migration, it sounds like this is largely under control15:32
mattmceuenI'm trying to find a failed job example and am not quickly... was seeing a few yesterday, so that's interesting15:33
airship-irc-bot<ih616h> Here's one that failed on the golang image https://zuul.opendev.org/t/openstack/build/36ce6912b90b45378d246273d193ebb615:33
dwaltYeah. Mostly seeing the node failures on the front page15:33
airship-irc-bot<ih616h> (if that's what you're looking for)15:33
mattmceuenahh yep, it's for the golang15:34
airship-irc-bot<ih616h> which makes sense - that image is pulled for even the linting jobs15:34
roman_ghttps://review.opendev.org/#/c/755456 Docker cache for airship/airshipctl Zuul jobs15:34
mattmceuenso migrating to an alternate source for that is a top priority, any volunteers?15:34
dwaltIf we're just going to do a quick push, probably needs to be one of us from the wc :)15:35
dwaltI can do it15:35
mattmceuenoh I figured there might already be a golang image in gcr land :)15:35
mattmceuenthey share a "g"15:35
dwaltoh that's a better idea15:36
roman_gThere are also a few images which are pulled from inside of nested VMs. Those also need to be verified on where do they get pulled from.15:37
roman_gPS above is a solution to enable cacheing of container images on OpenDev infrastructure servers.15:38
mattmceuenawesome ty roman_g15:38
mattmceuendwalt thank you for volunteering for that one, yeah I'd say just spend a few minutes searching for prior work before pushing to quay.io/airshipit as a Plan B15:39
dwaltI'll post to #airshipit if I find one15:39
mattmceuenGood news -- just learned from Arijit that the 3rd-party gates are now reporting back to gerrit!15:39
dwaltnice!15:40
mattmceuenCan I ask for a volunteer to put in a change to make the deployment zuul job on-merge only?15:40
mattmceuenI'd do it but need to step away for a couple hours15:40
roman_gmattmceuen Make airshipctl gate runner script run only on request and on Zuul gate (pre-merge) to reduce workload onto community CI15:40
roman_ghttps://review.opendev.itorg/76213615:40
roman_gIt's all in meeting Etherpad https://etherpad.opendev.org/p/airship-team-meeting15:41
mattmceuenThat's perfect, +2 - ty Roman15:41
dwaltthanks roman_g15:41
dwaltAnything else we need to hash out?15:41
mattmceuenok dwalt that all I have for our gate shenanigans, THANKS ALL for the working session15:41
dwaltgreat!15:42
dwalt#topic release tagging15:42
*** openstack changes topic to "release tagging (Meeting topic: airship)"15:42
roman_gImages pulled from inside of nested VMs are not covered.15:42
dwaltI think you're back in the spotlight mattmceuen15:42
dwaltroman_g: do you know those atm? We may need to let the gates run to see15:42
mattmceuen@roman_g agree we need to follow up on that; hopefully the golang change will give us a little bit of respite, esp will switching most of the VM load to 3rd party gates15:43
roman_gdwalt not atm, need to grep code a bit15:43
dwaltSounds good. Let's go ahead and cover our last agenda item and circle back if we have some remaining time15:43
mattmceuenTagging:  so we'd decided when we cut our Beta release that we'd tag the quay.io image, but not the repo15:44
mattmceuenFor the life of me, I don't recall why we thought that was a good idea -- seems like we should be doing both; @sean.eagan brought up yesterday wanting to do git diffs and needing to dig for commit hashes15:44
mattmceuenIn addition, we're not actually labelling our tagged quay.io images with their git hash, so it's not easy to trace from "v2.0.0-beta.1" tag to commit hash in quay15:45
mattmceuenAre their any concerns with additionally labelling the airshipctl repo (and others in the future) with release tags which match the built quay images?15:45
dwaltI can't think of any, but I missed Sean's concern the other day15:47
airship-irc-bot<sean.eagan> use case is starting to explore publishing actual github releases with release notes etc: https://github.com/airshipit/airshipctl/issues/39015:47
dwaltDo we need to start publishing our images with the commit sha mattmceuen?15:47
mattmceuenI think that would be a good thing to do additionally as well dwalt15:47
mattmceuenCool, I will tag the repo later today then unless anyone objects.15:48
mattmceuenall from me dwalt :)15:48
dwaltSound good. Thanks mattmceuen15:48
dwaltI'll create an issue for the image publishing. We can discuss on the flight plan call15:48
dwalt#topic roundtable15:48
*** openstack changes topic to "roundtable (Meeting topic: airship)"15:48
dwaltOkay folks, 10 mins left. Anything else we need to discuss?15:49
dwalt#topic reviews15:50
*** openstack changes topic to "reviews (Meeting topic: airship)"15:50
dwalt#link https://review.opendev.org/#/c/730777/15:50
dwaltJust one review for today. And with that, we can adjourn. Thanks, everyone! Have a great day15:51
dwalt#endmeeting15:51
*** 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:51
openstackMeeting ended Tue Nov 10 15:51:16 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-11-10-15.00.html15:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-11-10-15.00.txt15:51
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-11-10-15.00.log.html15:51
mattmceuenty @dwalt!15:51
airship-irc-bot<mf4716> ty all - make it a great day!15:53
airship-irc-bot<kk6740> @mattmceuen do u know by any chance where did `dev` tag for templater plugin docker image go? trying to find it in the repository seems to be missing https://quay.io/repository/airshipit/templater?tab=tags15:55
airship-irc-bot<kk6740> at the same time, we have it in our manifests https://github.com/airshipit/airshipctl/blob/master/manifests/function/airshipctl-base-catalogues/env-vars-template.yaml#L1015:56
roman_gAdd commit and other labels to the airshipctl container image https://review.opendev.org/76216415:58
airship-irc-bot<victor.melin> Hi, is it normal that the docker image "quay.io/airshipit/templater:dev" is still referenced in the Airshipctl functions while it does not exist in the docker registry?16:05
airship-irc-bot<kk6740> @victor.melin That is what i am working on currently16:06
airship-irc-bot<kk6740> @victor.melin, @sidney.shiba I have added correct tag, can u try now ?16:11
airship-irc-bot<dwalt> `gcr.io/gcp-runtimes/go1-builder ` is a potential candidate for go. 8 MB smaller :)16:13
airship-irc-bot<victor.melin> oh sorry, I did not see your message..16:29
airship-irc-bot<victor.melin> yes it works thanks !16:30
airship-irc-bot<sb464f> is there a way to login to ephemeral node if cloud init is not ran and no user got created ..?17:01
airship-irc-bot<craig.anderson> with image-builder, yes17:06
airship-irc-bot<sb464f> the current airshipctl using image builder ..?17:21
airship-irc-bot<sb464f> I mean the latest.17:21
*** muhaha has joined #airshipit17:24
airship-irc-bot<craig.anderson> the one we integrated together17:52
*** muhaha has quit IRC18:03
*** roman_g has quit IRC18:10
*** roman_g has joined #airshipit18:11
*** roman_g has quit IRC18:12
*** uzumaki has joined #airshipit20:00
uzumakihey mattmceuen , you there?20:00
uzumakineed to lend your thoughts for a couple minutes20:01
*** GoldenBear_ has joined #airshipit20:05
*** GoldenBear has quit IRC20:05
*** dwalt has quit IRC20:05
airship-irc-bot<mattmceuen> hey @uzumaki yep I'm here20:19
uzumakihow've you been?20:19
uzumakimattmceuen,20:19
airship-irc-bot<mattmceuen> Can't complain :)20:19
airship-irc-bot<mattmceuen> you???20:19
uzumakiI'm well, thanks.20:20
uzumakiI'm sure everybody's occupied with the airship 2.0 release coming up, I'm just wondering, what are some of the "should haves" or "good to haves" for airship in the coming months?20:21
uzumakiI know it's a very vague question, but I'm just curious, since we plan to make more contributions mattmceuen20:22
airship-irc-bot<mattmceuen> Hey that's awesome and I'm happy to hear that.  One thing I'll offer is taking a look at the notes from the PTG for anything that aligns with what you guys would benefit from:  https://etherpad.opendev.org/p/wallaby-ptg-airship20:25
airship-irc-bot<mattmceuen> We talked a lot about post-2.0 scope (sometimes in vague terms, with more detailed design to follow)20:25
uzumakiOh, that's great!20:25
airship-irc-bot<mattmceuen> But multi-cluster management, airshipui, out-of-box-user-experience, disaster recovery and others20:26
airship-irc-bot<mattmceuen> More notes from the post-2.0 scope were captured here: https://hackmd.io/9eXSGC2WQOOFiVMrAocB3Q?both20:27
airship-irc-bot<mattmceuen> If any of those things sound like fun, we could start deeper discussion in the design call with you20:27
uzumakiThat sounds GREAT! Unfotunately I missed this PTG and I'd be catching up with the recordings and it'll be awesome to catch up on the design call, sounds prefect!20:28
uzumakiBoth the sources are very helpful, merci beaucoup!20:28
airship-irc-bot<mattmceuen> oh fantastic :slightly_smiling_face:  yeah let me know what you think!  de rien mon ami!20:29
uzumakiau revoir! o/ merci encore!20:29
*** sreejithp has quit IRC22:24
*** ianychoi has quit IRC22:52
*** ianychoi has joined #airshipit22:52
*** uzumaki has quit IRC23:19

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