Tuesday, 2020-09-29

*** evrardjp has quit IRC04:33
*** evrardjp has joined #airshipit04:33
*** uzumaki has joined #airshipit06:04
*** airship-irc-bot1 has joined #airshipit09:20
*** airship-irc-bot has quit IRC09:21
*** SRao has joined #airshipit13:00
mattmceuenHi all, our team meeting will start in 20 minutes - here's the agenda:  https://etherpad.opendev.org/p/airship-team-meeting13:40
mattmceuenPlease add anything you'd like to discuss today into the agenda13:40
*** sreejithp has joined #airshipit13:55
mattmceuen#startmeeting airship13:59
openstackMeeting started Tue Sep 29 13:59:50 2020 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: airship)"13:59
mattmceuen#link https://etherpad.opendev.org/p/airship-team-meeting13:59
openstackThe meeting name has been set to 'airship'13:59
mattmceuen#topic Rollcall14:00
*** openstack changes topic to "Rollcall (Meeting topic: airship)"14:00
airship-irc-bot1<alexander.hughes> \o/14:00
airship-irc-bot1<ih616h> o/14:00
mattmceuenGood morning, evening everyone - let's give it just a minute or two, the design call is still winding down :)14:00
*** roman_g has joined #airshipit14:00
mattmceuenplease add any additional topics you'd like to the agenda above^14:01
airship-irc-bot1<mf4716> o/14:01
sreejithpo/14:02
airship-irc-bot1<mb551n> o/14:02
roman_go/14:02
airship-irc-bot1<dwalt> o/14:02
mattmceuenOk, let's get started14:02
mattmceuen#topic New gerritbot channels14:02
*** openstack changes topic to "New gerritbot channels (Meeting topic: airship)"14:02
airship-irc-bot1<sirajudeen.yasin> o/14:02
airship-irc-bot1<ak3216> o/14:03
mattmceuenYou all may have noticed less chatter in this channel :)  we have moved the gerrit bot updates to a separate channel, for clarity14:03
airship-irc-bot1<ih616h> this is much cleaner now14:03
airship-irc-bot1<mf4716> very nice14:03
mattmceuenIn IRC the channel is #airshipit-gerritbot, and in Slack it's #airship-gerritbot -- please re-subscribe if you got value out of that14:03
mattmceuen+114:03
mattmceuenty to ashferg and jbryce for their help getting that in place too14:03
mattmceuen#topic Reminder: Open Infra Summit Oct 19-2314:04
*** openstack changes topic to "Reminder: Open Infra Summit Oct 19-23 (Meeting topic: airship)"14:04
airship-irc-bot1<alexander.hughes> best part about this change is being able to set up notifications for "every new message"  so you're always in the loop14:04
mattmceuenYes!14:04
mattmceuenThe Summit is quickly approaching14:04
mattmceuenNB: Thursday is the last day to submit a recording, if you have a talk14:05
mattmceuenalexander.hughes put together a list of Airship talks:  https://www.airshipit.org/blog/airship-featured-at-virtual-open-infrastructure-summit-in-october/14:05
mattmceuenWe will additionally have an Airship 101 overview session, and a short update in the keynotes14:05
mattmceuenDon't forget to register (free!)14:06
mattmceuen#link https://openinfrasummit2020.eventbrite.com/14:06
mattmceuenAnd by the same token...14:06
airship-irc-bot1<alexander.hughes> OSF actually beat me to publishing the list on the blog :slightly_smiling_face:14:06
mattmceuen#topic Open Infra PTG Oct 26-3014:06
*** openstack changes topic to "Open Infra PTG Oct 26-30 (Meeting topic: airship)"14:06
mattmceuenHaha, I just assumed it was yours Alex ;-)14:06
mattmceuenThe PTG is following the Summit by a week14:06
mattmceuenWe'll have an etherpad soon for Airship topics.  Airship is later in the week (Wednesday and Thursday)14:07
mattmceuenMore info can be found in the etherpad agenda14:07
mattmceuenPlease register for that one as well, so that the OSF can plan accordingly14:07
mattmceuen#link https://october2020ptg.eventbrite.com14:07
mattmceuenOne point of discussion for today:  this time we will be incorporateing New Developer Onboarding into the PTG itself, instead of the Summit14:08
mattmceuenWe can do that whenever we want during our time slots, but we should figure it out ahead of time so that the OSF can advertise it14:08
mattmceuenAnyone care whether we e.g. lead with new user onboarding on Wednesday morning, or would prefer to e.g. end with it later on Thursday?\14:09
airship-irc-bot1<alexander.hughes> prefer new user up front, serves as a path to the more advanced topics if they're really interested14:09
mattmceuenThat's what I was thinking too14:10
mattmceuenand then y'all don't have to join at 8am central on Wednesday if you don't want to participate in the onboarding -- but you are certainly encouraged to :)14:10
mattmceuenI think an hour would be a good amount of time to set aside, do you agree?14:11
airship-irc-bot1<ashlee> I’d agree with that too since it’s a more global friendly time14:11
mattmceuenCool -- I'll communicate that out then14:12
airship-irc-bot1<alexander.hughes> agree on 1 hour, objective is to get a new user's feet wet not feed them with a fire hose14:12
mattmceuenyeah14:12
*** uzumaki has quit IRC14:13
mattmceuenAlright - any questions / thoughts on the Summit or PTG before we move on?14:14
airship-irc-bot1<alexander.hughes> how are we looking on airship 101 presentation?  do we need more help from other contributors to shore that up?14:14
mattmceuenI think it's ready to go!  Andrew K and dwalt volunteered to give that talk, and they have the slides well hashed-out14:15
airship-irc-bot1<dwalt> @ak3216 and I are recording today :slightly_smiling_face:14:15
mattmceuennice14:15
airship-irc-bot1<alexander.hughes> awesome! :slightly_smiling_face:14:15
airship-irc-bot1<dwalt> thanks for offering to help @alexander.hughes14:15
mattmceuen+114:15
mattmceuenOK, next topic:14:15
mattmceuen#topic Airship UI meetings14:15
*** openstack changes topic to "Airship UI meetings (Meeting topic: airship)"14:15
mattmceuenAlex, I think this one's yours?14:15
airship-irc-bot1<alexander.hughes> yep!  Rodolfo sent out an e-mail announcement a few weeks ago, just want to make sure everyone is aware14:16
airship-irc-bot1<alexander.hughes> #link http://lists.airshipit.org/pipermail/airship-discuss/2020-September/001085.html14:16
airship-irc-bot1<alexander.hughes> the UI SIG has been cancelled, so the UI grooming and design topics will be moving to the flight plan and open design calls respectively14:16
mattmceuenthanks for socializing @alexander.hughes14:16
mattmceuenThe next topic is yours as well:14:17
mattmceuen#topic Contributing to the blog14:17
*** openstack changes topic to "Contributing to the blog (Meeting topic: airship)"14:17
airship-irc-bot1<alexander.hughes> the Airship blog right now seems to be just TC newsletter updates, big project announcements, and OSF announcements.  I'd encourage all of you to submit your own contributions to help make the blog more organic and cover a wider set of topics and content styles14:18
mattmceuenThe Summit & PTG are going to be good opportunities to let the wider community know what we've been up to14:19
mattmceuenI think additional blog posts timed around then would be really good14:19
airship-irc-bot1<alexander.hughes> it's just a github project, where you submit your contribution in markdown https://github.com/AirshipWeb/airship-website/14:19
mattmceuenThinks like:  AIrship in a Pod14:19
mattmceuenAirship UI14:19
airship-irc-bot1<alexander.hughes> yep!  airship in a pod, airshipui, kustomize work we've been doing14:19
mattmceuenMulti-provider support14:19
mattmceuenI will volunteer to put together a Multi-Provider Support blog post; if anyone would like to contribute to that please let me know14:20
mattmceuenAnything else on this topic team?14:21
mattmceuen#topic Roundtable & Review Requests14:21
*** openstack changes topic to "Roundtable & Review Requests (Meeting topic: airship)"14:21
mattmceuenAny other topics, or changesets to get on our review radar for the day?14:22
mattmceuenAlright - feel free to drop any topics or patchsets into the channel any time; we'll all see them now that gerritbot is in the next room :)14:23
mattmceuenOur next meeting will be October 13th14:23
mattmceuenThanks everyone!14:23
mattmceuen#endmeeting14:23
*** 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"14:23
openstackMeeting ended Tue Sep 29 14:23:43 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-09-29-13.59.html14:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-09-29-13.59.txt14:23
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-09-29-13.59.log.html14:23
airship-irc-bot1<mf4716> team, a quick comment on the Airship UI meetings topic, any assistance during design & flight plans calls to promote the discussion of the UI would be appreciated; been a recurring agenda topic, just been bumped a few times in priority14:24
mattmceuenIt came up in today's design call, but I don't think we had any UI team members present to drive the discussion this time14:24
mattmceuenDesign call topics taking longer than expected - and getting bumped to next time - unfortunately occurs a lot14:25
mattmceuenAlthough the PTG is still weeks away, it'll help get us work through our design backlog14:26
roman_gJFYI, #airship channel could also be used if anyone wants to occupy a nice-looking channel name14:27
mattmceuenoh, someone had been camping in it before! is it free now? :)14:28
mattmceuennice, roman_g14:28
airship-irc-bot1<mf4716> yeah @mattmceuen, the UI team member dropped, just before the topic was announced; I'll provide a reminder in our DSU today requesting folks to remain engaged on the calls14:29
mattmceuenfolks know the #airshipit channel at this point, but now that you are the op, roman_g, we can at least hold on to it and come up with a good use14:30
mattmceuenthanks @mf4716.  It happens :)14:30
airship-irc-bot1<mf4716> no worries @mattmceuen - there was ack. on the call that the discussion was needed, so, it's all folks' radars, which is all that is important14:32
*** uzumaki has joined #airshipit15:03
airship-irc-bot1<sirajudeen.yasin> Team, I am trying to add some level of zuul job dependencies to skip running "gate runner job" when there is any lint issue with PS, this way we can save some zuul resource.  Let me know if someone thinks different15:56
airship-irc-bot1<sirajudeen.yasin>15:57
airship-irc-bot1<alexander.hughes> how are zuul resources looking now?  frankly as a developer if I submit a patch and it fails one gate, I fix it then submit and a new gate fails that I could have resolved in first patch it's really inconvenient15:57
airship-irc-bot1<alexander.hughes> and the other side of the equation - can the gate runner script ever pass if there is a linting failure?15:58
airship-irc-bot1<sirajudeen.yasin> i assume gate runner can pass even if there is a lint failure, i can double check15:59
airship-irc-bot1<alexander.hughes> if gate runner always fails if there's a linting error I'm all for just skipping gate running if lint fails.  if not I think running both so long as resource usage isn't an issue right now is more convenient16:00
airship-irc-bot1<sirajudeen.yasin> thanks @alexander.hughes, i will try to check on the resource usage16:02
clarkbthe reason we run and report all jobs by default is that we've found that there appears to be more human overhead necessary when you short circuit. The reason for this is you end up with more code review round trips.16:03
clarkbthis was differ between different code bases though and our original observations were with openstack a number of years ago16:04
clarkb*this may differ16:04
clarkbalso running linters tends to be very easy to do locally, we've tried to encourage developers run them before pushing. I'm sure a majority still don't :) but cleaning up lint errors early is the ideal here I expect16:08
roman_galexander.hughes, There is technical possibility to start that long-running (1h+) job only after all shorter jobs have succeeded. This is something project committees could decide upon. I can work on implementation if this is considered needed.16:09
roman_gWe have 4 custom jobs which run in around 5-10 mins, one common job we don't have control on runs for 5min, and our champion - airship-airshipctl-gate-script-runner - over 1h, closer to 1,5h.16:12
airship-irc-bot1<alexander.hughes> WC meeting is coming up before the next TC meeting, can add it to their agenda16:16
airship-irc-bot1<alexander.hughes> https://etherpad.opendev.org/p/airship-wc-meeting-2020-10-0516:17
roman_gDelay we would introduce by running airship-airshipctl-gate-script-runner only after all other jobs complete with SUCCESS would be around 5-10+ minutes.16:19
roman_g+ 5-10+ minutes16:19
roman_galexander.hughes, thanks for the link16:21
airship-irc-bot1<alexander.hughes> no problem :slightly_smiling_face:  @dwalt https://wiki.openstack.org/wiki/Airship/Airship-WC looks out of date, want me to fix real quick or you got it?16:22
roman_ghttps://review.opendev.org/#/c/754999/ - airshipctl gates - Reduce Zuul CI pool workload - please, review. Thanks.16:22
airship-irc-bot1<dwalt> oops. Can you fix it? Thanks @alexander.hughes16:23
airship-irc-bot1<alexander.hughes> sure16:23
roman_gSuper fast reaction. Thank you, team.16:24
airship-irc-bot1<dwalt> @raliev does this env variable change the way that airshipctl looks for phase entrypoints? I don't see it used in the script anywhere, but I've seen some comments that suggest it's used somewhere https://github.com/airshipit/airshipctl/blob/d8a6139e8156eb049c650a012a7c4eab76bbc7a7/tools/deployment/22_test_configs.sh#L3816:26
airship-irc-bot1<raliev> @dwalt there was a plan to use it just for some debugging commands, like to go to `$targetPath/$repoName` and perform some commands inside, but for now it’s not used anywhere, it’s safe to remove if needed. this variable does not change way of looking for phase entrypoints16:30
airship-irc-bot1<dwalt> Ah, that clears it up. Thanks @raliev.16:32
airship-irc-bot1<dwalt> The strange behavior I am seeing is that [this](https://zuul.opendev.org/t/openstack/build/d31688dd7837408e86d7ee37673865a1/log/primary/.airship/config) config file results in airshipctl looking in `/home/zuul/src/opendev.org/airship/treasuremap/airshipctl/manifests/site/test-site/ephemeral/bootstrap`16:33
airship-irc-bot1<dwalt> I was expecting `/home/zuul/src/opendev.org/airship/treasuremap/manifests/site/test-site/ephemeral/bootstrap`16:34
airship-irc-bot1<kk6740> @dwalt from what i see that you have: `targetPath: /home/zuul/src/opendev.org/airship/treasuremap`16:36
airship-irc-bot1<kk6740> when you do document pull, it goes to target path and clone all repositories defined in manifests16:37
airship-irc-bot1<dwalt> It's not defined in the manifest, right? This is also without document pull16:38
airship-irc-bot1<dwalt> The only repository defined should be treasuremap16:38
airship-irc-bot1<kk6740> yes, so in your case, would would get it cloned  to ```/home/zuul/src/opendev.org/airship/treasuremap/treasuremap```16:39
airship-irc-bot1<dwalt> That makes sense. But where is the airshipctl coming from?16:40
airship-irc-bot1<dwalt> Adding document pull to treasuremap will be a follow-on to this. Just focusing on the phases for now16:40
airship-irc-bot1<kk6740> can u give link to patchset16:41
airship-irc-bot1<dwalt> https://review.opendev.org/754789 https://review.opendev.org/75471616:41
airship-irc-bot1<raliev> likely from here https://review.opendev.org/#/c/752595/27/manifests/phases/phases.yaml16:41
airship-irc-bot1<dwalt> That's definitely it16:42
airship-irc-bot1<kk6740> :slightly_smiling_face:16:42
airship-irc-bot1<kk6740> but you mean they come in treasuremap16:43
airship-irc-bot1<dwalt> I can just plan on redefining those in Treasuremap. It was sort of a temporary shortcut16:43
airship-irc-bot1<dwalt> thanks @kk6740 and @raliev :slightly_smiling_face:16:43
airship-irc-bot1<kk6740> @dwalt so you got the root cause? i feel like i didn’t completely follow how that got into treasuremap :slightly_smiling_face:16:46
airship-irc-bot1<kk6740> @dwalt here is ur problem i thnk16:48
airship-irc-bot1<kk6740> ```    metadataPath: manifests/site/test-site/metadata.yam```16:48
airship-irc-bot1<kk6740> in here https://zuul.opendev.org/t/openstack/build/d31688dd7837408e86d7ee37673865a1/log/primary/.airship/config16:48
airship-irc-bot1<kk6740> it should be `manifests/type/network-cloud/metadata.yaml` intead ?16:49
airship-irc-bot1<dwalt> @kk6740 The link that Ruslan posted, https://review.opendev.org/#/c/752595/27/manifests/phases/phases.yaml , links to the phases defined in airshipctl. Those phases are all pre-pended with airshipctl now16:54
airship-irc-bot1<dwalt> That still needs to be fixed too. But I think that's not what's causing it16:55
*** uzumaki has quit IRC17:03
*** ianychoi_ has joined #airshipit17:17
*** ianychoi has quit IRC17:20
*** iamweswilson has quit IRC17:37
*** portdirect has quit IRC17:37
*** alexanderhughes has quit IRC17:37
*** mnaser has quit IRC17:37
*** v1k0d3n has quit IRC17:37
*** francisy has quit IRC17:37
*** donnyd has quit IRC17:37
*** megheisler has quit IRC17:37
*** jemangs has quit IRC17:37
*** seaneagan has quit IRC17:38
*** ildikov has quit IRC17:38
*** alanmeadows has quit IRC17:38
*** lamt has quit IRC17:38
*** mattmceuen has quit IRC17:38
*** jayahn has quit IRC17:38
*** aprice has quit IRC17:38
*** jbryce has quit IRC17:38
*** ian-pittwood has quit IRC17:38
*** phrobb has quit IRC17:38
*** srwilkers has quit IRC17:38
*** rpioso has quit IRC17:38
*** gagehugo has quit IRC17:39
*** howell has quit IRC17:39
*** alexanderhughes has joined #airshipit17:48
*** mattmceuen has joined #airshipit17:49
*** megheisler has joined #airshipit17:50
*** jemangs has joined #airshipit17:54
*** aprice has joined #airshipit17:54
*** gagehugo has joined #airshipit17:54
*** phrobb has joined #airshipit17:54
*** seaneagan has joined #airshipit17:54
*** donnyd has joined #airshipit17:54
*** mnaser has joined #airshipit17:55
*** jayahn has joined #airshipit17:58
*** jbryce has joined #airshipit17:59
*** portdirect has joined #airshipit17:59
*** alanmeadows has joined #airshipit17:59
*** srwilkers has joined #airshipit17:59
*** francisy has joined #airshipit18:00
*** ian-pittwood has joined #airshipit18:00
*** ildikov has joined #airshipit18:05
*** v1k0d3n has joined #airshipit18:05
*** iamweswilson has joined #airshipit18:10
*** roman_g has quit IRC18:14
*** SRao has quit IRC18:15
*** howell has joined #airshipit18:15
*** rpioso has joined #airshipit18:15
*** sreejithp has quit IRC18:55
*** sreejithp has joined #airshipit18:59
*** aprice has quit IRC19:05
*** rpioso has quit IRC19:05
*** aprice has joined #airshipit19:06
*** rpioso has joined #airshipit19:06
*** howell_ has joined #airshipit19:07
*** ildikov has quit IRC19:07
*** howell has quit IRC19:08
*** howell_ is now known as howell19:08
*** ildikov has joined #airshipit19:08
*** sreejithp has quit IRC19:33
*** sreejithp has joined #airshipit19:34
*** sreejithp has quit IRC19:34
*** sreejithp has joined #airshipit19:35
*** sreejithp has quit IRC19:37
*** sreejithp has joined #airshipit19:38
*** ildikov has quit IRC20:16
*** ildikov has joined #airshipit20:17
airship-irc-bot1<james.gu> Hello, could I send another review request for treasuremap 1.8 branch patchsets: https://review.opendev.org/#/c/753864/ (needs a 2nd +2/WF) and https://review.opendev.org/#/c/755079 (simple one liner). TIA !!!20:33
*** sreejithp has quit IRC21:35
*** rpioso has quit IRC21:52
*** alanmeadows has quit IRC21:52
*** ian-pittwood has quit IRC21:52
*** howell has quit IRC21:52
*** portdirect has quit IRC21:52
*** jbryce has quit IRC21:53
*** iamweswilson has quit IRC21:53
*** srwilkers has quit IRC21:53
*** ildikov has quit IRC21:53
*** mattmceuen has quit IRC21:53
*** francisy has quit IRC21:53
*** megheisler has quit IRC21:54
*** aprice has quit IRC21:54
*** jayahn has quit IRC21:54
*** ian-pittwood has joined #airshipit21:54
*** alanmeadows has joined #airshipit21:54
*** aprice has joined #airshipit21:55
*** jbryce has joined #airshipit21:55
*** mattmceuen has joined #airshipit21:55
*** rpioso has joined #airshipit21:56
*** jayahn has joined #airshipit21:56
*** megheisler has joined #airshipit21:56
*** portdirect has joined #airshipit21:56
*** ildikov has joined #airshipit21:57
*** francisy has joined #airshipit21:57
*** howell has joined #airshipit21:57
*** iamweswilson has joined #airshipit21:58
*** srwilkers has joined #airshipit22:03
*** ianychoi_ is now known as ianychoi23:00
*** kklimonda has left #airshipit23:29

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