*** ianychoi_ has joined #airshipit | 01:03 | |
*** lemko5 has joined #airshipit | 01:04 | |
*** lemko has quit IRC | 01:12 | |
*** ianychoi has quit IRC | 01:12 | |
*** lemko5 is now known as lemko | 01:13 | |
*** uzumaki has joined #airshipit | 02:38 | |
*** uzumaki has quit IRC | 04:50 | |
airship-irc-bot1 | <alexander.hughes> hello team! IRC team meeting starting in a little over an hour. currently 1 agenda item, please add any others you'd like to discuss here https://etherpad.opendev.org/p/airship-team-meeting | 12:43 |
---|---|---|
airship-irc-bot1 | <dwalt> I also don't mind sending an email for that announcement if nothing else gets added. Just dates to add to your calendar :slightly_smiling_face: | 13:01 |
airship-irc-bot1 | <sreejith.punnapuzha> Team, can i get a review on this commit? https://review.opendev.org/c/airship/airshipctl/+/780297 -> this is to move capm3 ipam deployment from url so that deployment works behind proxy | 13:02 |
airship-irc-bot1 | <kalpgiorgos> Hi everyone!! im new here . trying to install airship in a bottle but having issues with open particular pod on ucp namespace ( mariadb-server) . Should I go for Airskiff or troubleshoot the situation?Thanks | 13:15 |
airship-irc-bot1 | <mattmceuen> Hey @kalpgiorgos - welcome :slightly_smiling_face: FYI, airship in a bottle is an all-in-one environment for our Airship 1 platform; if you're just getting started you may be more interested in Airship 2 | 13:34 |
airship-irc-bot1 | <mattmceuen> We still plan to at least tag airship-in-a-bottle so that it can have a stable reference, so if Airship 1 is what you need, we can try to figure that one out | 13:34 |
airship-irc-bot1 | <alexander.hughes> anyone trying to access the design call, please use the updated link for today please: https://attcorp.webex.com/join/rp2723 | 13:35 |
airship-irc-bot1 | <mattmceuen> @kalpgiorgos we're going to have our IRC/Slack team meeting in this channel in ~25 minutes, if you'd like more information feel free to drop a topic in here: https://etherpad.opendev.org/p/airship-team-meeting | 13:37 |
airship-irc-bot1 | <mattmceuen> If you decide on Airship 2, the airship-in-a-bottle type thing is here: https://github.com/airshipit/airshipctl/tree/master/tools/airship-in-a-pod | 13:38 |
airship-irc-bot1 | Action: outbackdingo thinks he needs a irc meeting to get an all-in-one deployed on bare metal... this is much harder then it needs to be, and not having any success | 13:38 |
airship-irc-bot1 | <kalpgiorgos> @mattmceuen Thanks for your info ! I was not aware about airship in a pod. I ll give a try first and report back , I saw that aiab is marked deprecated. My primary goal is to evaluate it as a MEC framework in combination with other tools like ETSI MANO compliant ( management & orchestration) , ONAP or openstack TACKER as NFV orchestrators. | 13:51 |
airship-irc-bot1 | <mattmceuen> That sounds great - yeah please let us know how it works out for you @kalpgiorgos. FYI @james.gu so you're aware of this too | 13:53 |
airship-irc-bot1 | <kalpgiorgos> Great guys Thanks again !!! | 13:54 |
airship-irc-bot1 | <mattmceuen> Hey @dwalt @alexander.hughes The meetingbot can't be driven through the slack mirroring, right? If not could one of you guys please kick off the meetingbot, I'm having IRC issues this morning | 14:01 |
airship-irc-bot1 | <dwalt> yep, it's IRC. Sure, no problem | 14:01 |
airship-irc-bot1 | <mattmceuen> awesome, thanks much! | 14:01 |
*** alexanderhughes has joined #airshipit | 14:02 | |
*** dwalt has joined #airshipit | 14:02 | |
alexanderhughes | #startmeeting airship | 14:02 |
openstack | Meeting started Tue Mar 16 14:02:21 2021 UTC and is due to finish in 60 minutes. The chair is alexanderhughes. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
*** openstack changes topic to " (Meeting topic: airship)" | 14:02 | |
openstack | The meeting name has been set to 'airship' | 14:02 |
alexanderhughes | #topic Rollcall | 14:02 |
dwalt | oh you beat me by a hair | 14:02 |
*** openstack changes topic to "Rollcall (Meeting topic: airship)" | 14:02 | |
airship-irc-bot1 | <alexander.hughes> o/ | 14:02 |
airship-irc-bot1 | <mattmceuen> haha | 14:02 |
airship-irc-bot1 | <mattmceuen> Hello everyone! Here's our agenda for today: https://etherpad.opendev.org/p/airship-team-meeting | 14:02 |
airship-irc-bot1 | <mf4716> o/ | 14:02 |
airship-irc-bot1 | <james.gu> o/ | 14:02 |
airship-irc-bot1 | <mattmceuen> Please add on any additional topics you'd like to discuss today, we have a couple so far | 14:03 |
airship-irc-bot1 | <j_t_williams> o/ | 14:03 |
airship-irc-bot1 | <mattmceuen> Hope some of you are having a less rainy day than we're having in Saint Louis :slightly_smiling_face: | 14:03 |
*** sreejithp has joined #airshipit | 14:04 | |
airship-irc-bot1 | <mattmceuen> Alright, let's get it started: | 14:04 |
alexanderhughes | #topic Mark your calendars! The April 2021 Airship vPTG sessions are scheduled | 14:04 |
*** openstack changes topic to "Mark your calendars! The April 2021 Airship vPTG sessions are scheduled (Meeting topic: airship)" | 14:04 | |
airship-irc-bot1 | <mattmceuen> Right on cue @alexander.hughes! | 14:05 |
alexanderhughes | :) | 14:05 |
alexanderhughes | Drew and Matt this one is yours! | 14:05 |
airship-irc-bot1 | <mattmceuen> The dates & times can be found in the agenda, a couple 4-hour blocks on Apr22/23 | 14:05 |
airship-irc-bot1 | <mattmceuen> Hopefully those times work well for folks | 14:05 |
airship-irc-bot1 | <mattmceuen> (they're basically the same times we did last time I believe) | 14:06 |
airship-irc-bot1 | <ak3216> o/ | 14:06 |
airship-irc-bot1 | <mattmceuen> We have an etherpad to start adding agenda items in: https://etherpad.opendev.org/p/xena-ptg-airship | 14:06 |
airship-irc-bot1 | <mattmceuen> I encourage y'all to add in things to discuss. This will be a particularly good opportunity to dig into post-2.0/2.1 plans for Airship, and to take a step back | 14:07 |
airship-irc-bot1 | <mattmceuen> Is (free) registration open yet, does anyone know? | 14:08 |
alexanderhughes | yes | 14:08 |
alexanderhughes | #link https://april2021-ptg.eventbrite.com | 14:08 |
airship-irc-bot1 | <mattmceuen> perfect | 14:08 |
alexanderhughes | as for the times, need to double check they're accurate in UTC since we just changed from CST to CDT | 14:09 |
airship-irc-bot1 | <mattmceuen> Great point | 14:09 |
alexanderhughes | but these are the same central times that we used in October | 14:09 |
airship-irc-bot1 | <mattmceuen> I think we need to do it the other way -- dwalt can correct me if I"m wrong, but I think the UTC times are set in stone and the C?T ones need to be adjusted to match | 14:10 |
airship-irc-bot1 | <mattmceuen> Any other ideas/questions/thoughts around the PTG next month? | 14:10 |
airship-irc-bot1 | <dwalt> I did calculate it with CDT time in mind | 14:11 |
airship-irc-bot1 | <dwalt> It should be 8 AM CDT - noon | 14:11 |
airship-irc-bot1 | <mattmceuen> brilliant | 14:11 |
alexanderhughes | excellent :) | 14:11 |
alexanderhughes | If there's nothing else on this then, moving on to | 14:11 |
alexanderhughes | #topic Periodic patchset abandoning | 14:11 |
*** openstack changes topic to "Periodic patchset abandoning (Meeting topic: airship)" | 14:11 | |
alexanderhughes | Mike and Matt, all yours | 14:11 |
airship-irc-bot1 | <mattmceuen> Next up: we talked about this, but I think it was quite some time ago | 14:12 |
airship-irc-bot1 | <mattmceuen> We have some number of old, old patchsets that haven't been updated in a long time | 14:12 |
airship-irc-bot1 | <mattmceuen> Gerrit supports the "abandon" function to archive a patchset in a way that can be easily un-archived if ever needed, but which takes the patchset "off the radar" of the team | 14:12 |
airship-irc-bot1 | <mattmceuen> normally we rely on folks to abandon their own patchsets when appropriate | 14:13 |
airship-irc-bot1 | <mf4716> The thought here was to implement a retention practice, or policy, to minimize tech debt, and hedge our position if we need to bring back an old(er) PS | 14:13 |
airship-irc-bot1 | <mattmceuen> +1 | 14:13 |
airship-irc-bot1 | <mattmceuen> The proposal is to have some kind of periodic review, where any patchsets that haven't been updated in the last "time period X" are abandoned | 14:14 |
airship-irc-bot1 | <mattmceuen> There are other open source communities that do similar things | 14:14 |
airship-irc-bot1 | <mattmceuen> e.g. "stale issues expire after 90 days" etc | 14:14 |
airship-irc-bot1 | <ak3216> +1 are we thinking 90 days? | 14:14 |
airship-irc-bot1 | <mattmceuen> I think 90 days makes a good strawman? Seems reasonable at least | 14:15 |
alexanderhughes | I'd propose this review process also encompass open issues, perhaps during flight plan. Run through the issues say quarterly to see what still makes sense, and then run a job to clean up any old patches. Before running the job we could add a comment/rebase any patches in question to get some attention back on them in cases where developers have been reassigned to other work or have left the project | 14:15 |
airship-irc-bot1 | <pb269f> if we do this - can one person produce a script that is run on a cron to do this (@mattmceuen) | 14:15 |
airship-irc-bot1 | <ak3216> Especially right now given the amount of change that has come through since the beginning of the year | 14:15 |
airship-irc-bot1 | <mf4716> +1 - yes re: 90 days.. several have leaned in to more closely monitor Github issues; in theory, if the Issues are managed via Flight Plan, PS mgmt will follow | 14:16 |
airship-irc-bot1 | <pb269f> other times we have done this in airship and osh in the past - without that automation its: a) fallen apart, b) been performed sporadically | 14:16 |
airship-irc-bot1 | <j_t_williams> I agree. Is there any mechanism to reach out to the submitters with information that the patchset will be abandoned in X days as a freindly reminder? | 14:16 |
airship-irc-bot1 | <mattmceuen> @pb269f @j_t_williams I think a bot-based approach would lend itself to friendly reminders and/or "FYI your PS is abandoned" emails | 14:17 |
alexanderhughes | if we're scripting it I don't see why we couldn't obtain the author's email from patch on a similar schedule. we'd want to consider where we're sending these notifications from to avoid emails getting lost in outlook rules that filter gerrit activity | 14:18 |
airship-irc-bot1 | <pb269f> it has to be a bot if its gonna work | 14:18 |
airship-irc-bot1 | <j_t_williams> Sounds good then. | 14:18 |
airship-irc-bot1 | <mattmceuen> It has to be a bot if this is gonna work repeatably and reliably :slightly_smiling_face: in the meantime I think clicking the abandon button a couple dozen times right now will at least help folks in the short term | 14:19 |
airship-irc-bot1 | <pb269f> im less worried about the 'reminder email' esp if its not a human clciking abondon - its easy for people to unabandon. | 14:19 |
airship-irc-bot1 | <mattmceuen> I will create an issue where we can start collecting requirements for the bot | 14:19 |
airship-irc-bot1 | <mattmceuen> yeah, agree @pb269f | 14:19 |
airship-irc-bot1 | Action: pb269f looks forward to three pages of abandoned ps's ;) | 14:19 |
airship-irc-bot1 | <mattmceuen> hahah | 14:19 |
airship-irc-bot1 | <mattmceuen> are there any Nay's? | 14:19 |
airship-irc-bot1 | <mattmceuen> We have a number of Yea's | 14:20 |
airship-irc-bot1 | Action: mattmceuen bangs his gavel, tap tap | 14:20 |
airship-irc-bot1 | <pb269f> i support - if automated | 14:20 |
alexanderhughes | no objection, but would like to segue into reviewing open issues periodically. some of these have been open over a year | 14:20 |
airship-irc-bot1 | <mattmceuen> yeah. we could potentially share the retention process/bot/schedule with issues while we're at it | 14:21 |
airship-irc-bot1 | <mattmceuen> our gerrit/github bot already has its fingers in github issues & gerrit PSs; we could consider enhancing that | 14:21 |
alexanderhughes | right, maybe look for an abandoned by <job> tag in gerrit - and then if no activity on issue in X days, move it to an archived status | 14:22 |
airship-irc-bot1 | <mattmceuen> Although auto-closing github issues already has other ways to do it, so probably better to use what already works | 14:22 |
airship-irc-bot1 | <pb269f> ++ | 14:22 |
alexanderhughes | alright, moving on | 14:23 |
alexanderhughes | #topic Daylight saving time | 14:23 |
*** openstack changes topic to "Daylight saving time (Meeting topic: airship)" | 14:23 | |
airship-irc-bot1 | <mattmceuen> I move that we abolish it | 14:23 |
alexanderhughes | it's that cursed time of year where we lost an hour of sleep to Daylight Saving Time. please send petitions to your elected leaders to abolish it | 14:24 |
airship-irc-bot1 | <mattmceuen> Does the OIF grant us that kind of authority? | 14:24 |
airship-irc-bot1 | <mattmceuen> lol | 14:24 |
alexanderhughes | in the mean time, be advised that most of our meetings are scheduled in US central time, with the change if you do not observe DST the meetings have changed by 1 hour for you | 14:24 |
airship-irc-bot1 | <mattmceuen> I suppose folks that are here have figured this out | 14:24 |
airship-irc-bot1 | <mattmceuen> Anyone catching up on IRC logs: sorry :slightly_smiling_face: | 14:24 |
airship-irc-bot1 | <mattmceuen> That's all we have on the agenda, any other topics team? | 14:25 |
alexanderhughes | I'll take an action item to review the wiki for meeting times and make sure they're all updated for UTC, and send out a note in the TC newsletter | 14:25 |
airship-irc-bot1 | <mattmceuen> ah ty alex | 14:25 |
alexanderhughes | before we open it up for round table, checking if anyone has any patches that need reviews | 14:25 |
alexanderhughes | #topic Call for reviews | 14:26 |
*** openstack changes topic to "Call for reviews (Meeting topic: airship)" | 14:26 | |
alexanderhughes | none listed on the agenda, please let us know in Slack/IRC if you have any that need reviews throughout the day | 14:27 |
alexanderhughes | #topic Roundtable | 14:27 |
*** openstack changes topic to "Roundtable (Meeting topic: airship)" | 14:27 | |
airship-irc-bot1 | <mattmceuen> Alright - then I think we can call it a day. | 14:27 |
alexanderhughes | #endmeeting | 14:27 |
*** 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:27 | |
openstack | Meeting ended Tue Mar 16 14:27:43 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:27 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/airship/2021/airship.2021-03-16-14.02.html | 14:27 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/airship/2021/airship.2021-03-16-14.02.txt | 14:27 |
openstack | Log: http://eavesdrop.openstack.org/meetings/airship/2021/airship.2021-03-16-14.02.log.html | 14:27 |
airship-irc-bot1 | <mattmceuen> Thanks everyone! & thanks @alexander.hughes for driving | 14:27 |
airship-irc-bot1 | <alexander.hughes> my pleasure, have a great day all | 14:28 |
*** uzumaki has joined #airshipit | 15:51 | |
airship-irc-bot1 | <sean.eagan> fyi image publishing for airshipctl and krm functions has been broken for ~2 weeks, since the cloud-init krm function was added, since the corresponding quay repo was never created, and so we were failing to push to it. I went ahead and created the repo, so hopefully should be fixed now | 15:57 |
airship-irc-bot1 | <sean.eagan> https://quay.io/repository/airshipit/cloud-init | 15:58 |
airship-irc-bot1 | <sean.eagan> maybe we should add some notifications somewhere for post job failures so we can catch them quicker | 15:59 |
airship-irc-bot1 | <sean.eagan> https://zuul.opendev.org/t/openstack/builds?job_name=airship-airshipctl-publish-image | 16:02 |
*** alexanderhughes has quit IRC | 16:31 | |
*** dwalt has quit IRC | 16:42 | |
*** roman_g has joined #airshipit | 17:20 | |
*** roman_g has quit IRC | 17:36 | |
airship-irc-bot1 | <ih616h> Hey team, could I get some reviews on the following PSs? https://review.opendev.org/c/airship/sip/+/780120 - Label vBMHs with SIP name along with namespace https://review.opendev.org/c/airship/sip/+/780610 - Light refactoring | 19:18 |
airship-irc-bot1 | <ih616h> and this one from airshipctl: https://review.opendev.org/c/airship/airshipctl/+/771662 - Suppress the "go command not found" message | 19:19 |
airship-irc-bot1 | <sean.eagan> Hey all, could I get some reviews on these small fixes to wrap up the release automation flow? https://review.opendev.org/c/airship/airshipctl/+/780940 https://review.opendev.org/c/airship/airshipctl/+/780875 https://review.opendev.org/c/airship/airshipctl/+/780972 | 20:47 |
*** sreejithp has quit IRC | 21:14 | |
airship-irc-bot1 | <sidney.shiba> Hi team, could you please review the following patchsets related to Helm Chart Collator? • Dex Chart Collator - Quay.io Docker image | https://review.opendev.org/c/airship/images/+/774028 • Helm Chart Collator (airship-core) - Treasure Map | https://review.opendev.org/c/airship/treasuremap/+/779413 | 21:52 |
airship-irc-bot1 | <ratnopam.chakrabarti> Hi Team, can I get some reviews on below patches https://review.opendev.org/c/airship/treasuremap/+/776840 - This needs another +2 to get merged https://review.opendev.org/c/airship/treasuremap/+/778359 https://review.opendev.org/c/airship/treasuremap/+/779889 Thanks! | 23:06 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!