Tuesday, 2020-04-14

*** openstack has joined #airshipit09:52
*** ChanServ sets mode: +o openstack09:52
*** dpawlik has quit IRC09:55
*** dpawlik has joined #airshipit09:56
openstackgerritMerged airship/airshipctl master: Update Kustomize integration to api/v0.3.1  https://review.opendev.org/71557111:36
openstackgerritVladislav Kuzmin proposed airship/airshipctl master: Make Redfish parameters configurable  https://review.opendev.org/71781212:20
openstackgerritDmitry Ukov proposed airship/airshipctl master: [WIP] Introduce document plugin subcommand  https://review.opendev.org/71993112:23
openstackgerritDmitry Ukov proposed airship/airshipctl master: [WIP] Introduce document plugin subcommand  https://review.opendev.org/71993112:54
*** SRao has joined #airshipit12:59
mattmceuenGM all!  Here's the agenda for our IRC meeting in about an hour:  https://etherpad.opendev.org/p/airship-meeting-2020-04-1413:07
mattmceuenNo topics yet, so feel free to add any topics or patchset review requests to it13:08
*** diga_ has joined #airshipit13:23
*** diga_ has quit IRC13:24
*** diga has joined #airshipit13:25
openstackgerritVamsi Savaram proposed airship/airshipctl master: Gather container logs in check pipeline  https://review.opendev.org/71752213:36
*** evgenyl has quit IRC13:50
*** vdrok has quit IRC13:50
*** vdrok has joined #airshipit13:51
*** evgenyl has joined #airshipit13:51
*** ak3216 has joined #airshipit13:52
*** ak3216 is now known as andrewkarandjeff13:56
*** raymonddeng has joined #airshipit13:57
openstackgerritDrew Walters proposed airship/airshipctl master: Add Dell Redfish client  https://review.opendev.org/71712313:59
openstackgerritDrew Walters proposed airship/airshipctl master: Add iDRAC ephemeral boot media support  https://review.opendev.org/71371113:59
*** ab2434_ has joined #airshipit13:59
*** alhatneha has joined #airshipit13:59
mattmceuen#startmeeting airship14:00
openstackMeeting started Tue Apr 14 14:00:12 2020 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: airship)"14:00
openstackThe meeting name has been set to 'airship'14:00
mattmceuen#topic Rollcall14:00
*** openstack changes topic to "Rollcall (Meeting topic: airship)"14:00
mattmceuenGood morning/evening everyone!14:00
airship-irc-bot1<alexander.hughes> o/14:00
mattmceuenHere's our agenda for today: https://etherpad.opendev.org/p/airship-meeting-2020-04-1414:00
airship-irc-bot1<dwalt> o/14:00
airship-irc-bot1<ih616h> o/14:00
ian-pittwoodo/14:01
mattmceuenplease add any review requests or topics that you'd like to discuss today14:01
*** roman_g has joined #airshipit14:01
airship-irc-bot1<mb551n> o/14:01
*** jtwill98 has joined #airshipit14:02
mattmceuenwe have folks coming in from the design call now; we'll give it just another minute...14:02
*** raymonddeng has left #airshipit14:02
*** raymonddeng has joined #airshipit14:02
mattmceuenAlrighty:14:03
mattmceuen#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: airship)"14:03
mattmceuenalexander.hughes, take it away sir14:03
airship-irc-bot1<alexander.hughes> hello all!  it's been a fantastic 10 months since Airship introduced it's formal governance paving the way to be confirmed as a top level OSF project14:04
airship-irc-bot1<alexander.hughes> in June, 2 months from now we'll hold our next committee election, for the TC.  the responsibilities and eligibility is defined here: https://opendev.org/airship/governance#user-content-technical-committee14:04
*** mfixtex has joined #airshipit14:04
airship-irc-bot1<alexander.hughes> something to ponder for those looking to get more involved in the community14:05
mattmceuenthe year has flown by quickly :)14:05
mattmceuenthe working committee elections will follow quickly about a month later as well14:05
mattmceuenThanks for the heads up alex.  Any other thoughts/questions on this one?14:06
mattmceuen#topic irc-slack bot14:06
*** openstack changes topic to "irc-slack bot (Meeting topic: airship)"14:06
mattmceuenportdirect:  thanks for bringing this one up, go for it14:06
portdirectnothing really to add14:06
portdirectnot sure who is looking after the bot14:07
mattmceuenbots taking over the world14:07
openstackgerritIan Howell proposed airship/airshipctl master: Uplift go-git  https://review.opendev.org/71785614:07
mattmceuenjbryce fyi:  this is how bot-copied text looks if you're using an alternate client to slack -- https://usercontent.irccloud-cdn.com/file/5LDRdjJK/Screen%20Shot%202020-04-14%20at%208.11.21%20AM.png14:07
mattmceuennot sure if there's a config for that or not14:07
mattmceuenReminder for folks using slack in general:  your underlying slack ID (typically your email address minus the domain) is reported in IRC by the bot14:08
mattmceuenThis is changeable if you choose to change it (deep in some config item in slack).  E.g. michael beaver, you're showing up as the vanilla:14:09
mattmceuen<mb551n> o/14:09
mattmceuenAnyway, if anyone has experience with resolving the bot-identity problem in other slack/irc clients, please let portdirect and us know14:10
mattmceuenmoving on in the meantime:14:11
mattmceuen#topic Airship blog calls for content14:12
*** openstack changes topic to "Airship blog calls for content (Meeting topic: airship)"14:12
mattmceuengo for it alexander.hughes14:12
airship-irc-bot1<alexander.hughes> thanks Matt, we mentioned this during the virtual meetup that we've got content on the airship blog here https://www.airshipit.org/blog/ but we've had a lot of great work lately from contributors that deserve to be showcased.  things that have gone above and beyond plain documentation where we've had demos of new features being worked and detailed discussions on challenges and victories with these features14:13
airship-irc-bot1<alexander.hughes> if you'd like to showcase any of that work, it's as simple as contributing in markdown to https://github.com/AirshipWeb/airship-website/ if you'd like to get involved or need direction don't hesitate to reach out to me14:13
*** mfixtex is now known as mikefix14:14
mattmceuensharing accomplishments and informing the community - sounds like a win win14:14
mattmceuenPlease chew on that and come up with some good things to share, team.  We can also enlist extra hands to help with writing tasks; step 1 is "good ideas"14:15
mattmceuenNext topic:14:16
mattmceuen#topic Consolidate common Zuul jobs into aiship-zuul-xxx repo14:16
*** openstack changes topic to "Consolidate common Zuul jobs into aiship-zuul-xxx repo (Meeting topic: airship)"14:16
mattmceuenNot sure who added this one?14:16
roman_gHi. It's mine.14:16
mattmceuenah thanks roman_g, go for it14:16
roman_gJust wanted to ask if it's a good time to move common jobs to separate repo and then import them from it.14:16
roman_gOpinions?14:17
mattmceuenGood question.  We'd started out developing common jobs in airshipctl directly to allow them to stabilize, but originally with the plan to move them back to the zuul job repo when stable14:17
*** uzumaki has joined #airshipit14:17
roman_gWe have this zuul-airship-something repo already14:17
mattmceuenroman_g just curious, are you aware of other projects that could reuse any jobs yet?14:18
roman_gAirship/images and airship/airshipctl may be.14:18
roman_gAre we interested in improving airship 1.x jobs/gates?14:19
airship-irc-bot1<aodinokov> due to the fact that images is a separate directory, we can't test images :slightly_smiling_face:14:19
airship-irc-bot1<aodinokov> in the job :slightly_smiling_face:14:19
roman_ghttp://opendev.org/airship/images - I meant this repo14:20
mattmceuenI think we're always interested in proving airship 1.x jobs/gates.  I'm not sure whether it makes sense to share jobs between A1 and A2, but I think putting common A1 jobs in the zuul repo might be good if we see a good opportunity for it14:20
airship-irc-bot1<dwalt> I think we recently tried to do this with one of the jobs, but we ended up breaking the developer gate scripts, which are not aware of the ways we can indicate role dependencies in Zuul. I think we need to develop an offline dependency strategy first.14:20
uzumaki+114:20
airship-irc-bot1<dwalt> With that being said, there are a lot of opportunities to reuse our roles, especially in Airship 114:21
mattmceuendwalt: putting you on the spot, are you able to walk us through the dependency issue we ran into?14:21
airship-irc-bot1<dwalt> Anything that does publishing or mirroring would be great to have consistent across all ~20 repos or however many variations we maintain now14:21
airship-irc-bot1<dwalt> I'll do my best :slightly_smiling_face:14:21
roman_gthanks. publishin14:22
roman_gPublishing and mirroring seem to be good targets14:22
mattmceuenyeah, agree roman_g14:23
roman_gWhat is good is that is independent of devs, and would not break anything.14:23
roman_g*it is independent of devs14:23
airship-irc-bot1<dwalt> We moved a docker role out of airship/airshipctl and into airship/images recently. I can't remember which one. When we did so, we "imported" that role into airshipctl using a feature in zuul that allows you to use roles in other repositories. This left our upstream CI green, but downstream, the dependent roles were missing, as zuul was not there to pull them in. Our downstream strategy could be as simple as cloning airship/images.14:23
uzumakire the mirroring topic, there's also a script in the zuul.d I suppose, which does Github comment posting, using Gerrit events. This is the single script in the scripts directory. I noticed it's not being used anymore, and has been succeeded by the airshipbot. Do we still want to keep that? And the Zuul job it corresponds to?14:24
airship-irc-bot1<dwalt> +1 to testing with those jobs first roman_g uzumaki14:24
airship-irc-bot1<dwalt> s/downstream/locally14:25
roman_gOK, thanks. I'm done.14:25
roman_gDownstream/locally - devs should ideally install and use ansible ;)14:26
uzumaki<dwalt> agree on testing those first14:26
roman_gThis way we wold not duplicate work, by writing 1) ansible code and then 2) bash code.14:26
airship-irc-bot1<dwalt> The scripts I'm referring to are just dev friendly wrappers on the ansible: https://github.com/airshipit/airshipctl/tree/master/tools/gate14:27
mattmceuenone approach is to put content into shell scripts, and then invoke those within zuul via shallow ansible playbooks14:27
mattmceuenportdirect did some great things with that approach in openstack-helm14:27
mattmceuenAnd asking developers to run bash locally on their laptops seems more reasonable to me than ansible, but that's only an opinion14:28
mattmceuenbut I also agree roman_g that it would be nice from a CI perspective to use "zuul everywhere" and not juggle different CI systems14:29
airship-irc-bot1<dwalt> +1 for the OSH approach. That was always helpful when getting started in OSH14:29
jtwill98+1 bash is locally available14:29
airship-irc-bot1<pb269f> I've got a poc of the bash approach for airshipctl that i could push up this week if there is interest?14:30
airship-irc-bot1<pb269f> it would need some cleanup, but is what ive been using in my home lab for a couple of weeks14:30
mattmceuenoh yeah, that would be cool to see14:30
howell+1 for the poc14:30
airship-irc-bot1<dwalt> I'd love to give that a try14:30
airship-irc-bot1<dwalt> +114:31
airship-irc-bot1<alexander.hughes> +114:31
portdirectok - will do :)14:31
mattmceuenthanks portdirect14:31
mattmceuenand roman_g, dwalt14:31
mattmceuenok!  I think we can move on:14:31
mattmceuen#topic     Reminder for new contributors - GitHub issues https://github.com/airshipit/airshipctl/issues14:31
*** openstack changes topic to "Reminder for new contributors - GitHub issues https://github.com/airshipit/airshipctl/issues (Meeting topic: airship)"14:31
airship-irc-bot1<dwalt> as for the original question, are we safe to test those mirroring jobs in airship/zuul-jobs?14:32
mattmceuenoops sorry to cut you off dwalt14:32
airship-irc-bot1<dwalt> since they should have no impact locally14:32
airship-irc-bot1<dwalt> no worries :slightly_smiling_face:14:32
mattmceuenI think that makes a good first target, yeah - and can go ahead14:32
airship-irc-bot1<dwalt> great! Thanks for bringing this up roman_g14:33
airship-irc-bot1<dwalt> and volunteering ;)14:33
mattmceuenhahahah14:33
mattmceuenalright, lemme try a fresh segue:14:34
mattmceuen#topic     Reminder for new contributors - GitHub issues https://github.com/airshipit/airshipctl/issues14:34
*** openstack changes topic to "Reminder for new contributors - GitHub issues https://github.com/airshipit/airshipctl/issues (Meeting topic: airship)"14:34
mattmceuengo for it alexander.hughes14:34
* uzumaki is wondering if that :slightly_smiling_face: can be tab-completed. Or if <dwalt> is determined enough to type the whole thing14:34
airship-irc-bot1<alexander.hughes> I got a message from a new community member a few minutes ago asking on how to get involved in airship development, so first I'd like to welcome all of the new community members that are lurking in chat14:34
mattmceueno/ welcome!14:35
* uzumaki keeps lurking about, sneaking, prowling14:35
raymonddengHi, that was me! Thanks for the warm welcome ^^14:35
airship-irc-bot1<alexander.hughes> and to answer the question again publicly, the best way to jump in with issues is by heading over to https://github.com/airshipit/airshipctl/issues and browsing through the list.  I highly encourage you all to make use of the new labels, such as "good first issue" or "documentation" etc. to find an issue that interests you14:35
airship-irc-bot1<alexander.hughes> welcome Raymond :slightly_smiling_face:14:35
uzumakiwelcome aboard raymonddeng ! o/14:35
mattmceuen+1 welcome Raymond, feel free to reach out here any time if you'd like some help getting started14:36
mattmceuenAnd now, I pass the baton back to you roman_g:14:36
mattmceuen#topic Copyright line in file headers14:37
*** openstack changes topic to "Copyright line in file headers (Meeting topic: airship)"14:37
roman_gApache 2.0 license application example says that there should be a copyright line14:37
roman_gWe don't have it in airshipctl at the moment.14:38
roman_gHas there been a discussion in WC/TC what should be put there? Who is copyright owner?14:38
roman_gLawers have been contacted, may be?14:38
roman_ghttps://www.apache.org/licenses/LICENSE-2.0#apply14:39
mattmceuenwe've discussed somewhere, forget which forum exactly14:39
mattmceuencheck out kubernetes' license: https://github.com/kubernetes/kubernetes/blob/master/LICENSE14:39
mattmceuenit is one of many many examples that simply leave the Copyright template as-is14:39
roman_ghttps://github.com/kubernetes/kubernetes/blob/master/cmd/kubectl/kubectl.go#L214:40
mattmceuenI believe that's what we followed, trusting in the cumulative lawyer wisdom of the open source community at large14:40
airship-irc-bot1<alexander.hughes> but the headers in files has been a subject of debate lately, looking at k8s again https://github.com/kubernetes/kubernetes/blob/master/pkg/api/endpoints/util.go14:40
airship-irc-bot1<alexander.hughes> lists copyright kubernetes authors14:40
mattmceuenalexander.hughes, can you share a link to the debate if you can find it again?14:40
roman_gKubernetes community adds copyright line in every file, as it is recommended https://www.apache.org/licenses/LICENSE-2.0#apply14:41
mattmceuenWe have erred away from e.g. "Airship Authors" copyrighting to date, as it is not a legal entity (neither is Kubernetes Authors as far as I know)14:41
portdirectcopywrite in the files means very little14:41
portdirectwhat matters is the copywrite of the commit14:41
mattmceuen+114:42
portdirectother than being a topic of endless debate of course ;)14:42
mattmceuenwhich is a cumulative thing -- can have multiple copyrights on a per-file basis up top14:42
portdirectplease no14:42
portdirectwe can, and theres nothing wrong with it14:42
portdirectbut the one thing that really matters at the end of the day is git log14:42
mattmceuenah, I see what you mean14:43
portdirectit just makes things super complex, and frankly hard to approach14:43
portdirectits why the `Kubernetes Authors` approach is used14:43
uzumakihow do we ensure copyrighting in commits? the signed-off-by thing? or the CLA?14:43
portdirectit just heads off this thing14:43
portdirectand gently directs people to make use of the version control history for the authorship14:44
portdirectotherwise, in the case of both k8s and the linux kernel14:44
portdirectyour (c) headers would be hundreds if not thousands of lines long14:44
uzumakioh I see!14:45
mattmceuenthe joys of open source14:45
mattmceuenanything else on this topic folks?14:46
uzumakiwell, how does this entity get defined then?14:46
roman_gNo14:46
uzumakithe "Kubernetes Authors"14:46
uzumakiit's implied that it includes all the committers?14:46
mattmceuenThat's why we don't have an "Airship Authors" defined - because that's not a legal entity14:46
portdirectthey are the authors of kubernetes14:46
uzumakiso, like the OWNERS file people?14:47
mattmceuenI think there is a healthy dose of "it doesn't matter" when it comes to this stuff -- the license guarantees it's open source, the git history shows who the authors are14:47
portdirectno - to use a book/adademic paper analogy, they are the 'editors'14:48
portdirectmattmceuen: +++14:48
uzumakiah! I get it now. That's what I was thinking as well, got it14:48
mattmceuenand theres a lot of examples of big projects /not/ defining a copyright in the Authors file14:48
uzumakiportdirect, I see, thanks!14:48
mattmceuenyou are not the first person to be confused by this stuff uzumaki :D14:48
*** rezroo has joined #airshipit14:48
* mattmceuen was at least earlier in the confusion chain14:49
mattmceuenok!  moving on!14:49
uzumakiI see, well, open source has its own joys, like you said mattmceuen14:49
mattmceuen#topic Review Requests14:49
*** openstack changes topic to "Review Requests (Meeting topic: airship)"14:49
mattmceuen    https://review.opendev.org/#/c/717856/ - uplift go-git14:49
mattmceuen    https://review.opendev.org/#/c/718532/ - Add APIExtensions ClientSet to airship Client14:49
mattmceuen    https://review.opendev.org/#/c/717844/ - Remove deprecated `interfacer` linter14:49
mattmceuenLet's please get some solid reviews on these ones today.  Any additional patchsets that y'all would like to put forward today?14:50
mattmceuenas you do, feel free to drop a note in the IRC channel anytime14:51
mattmceuen#topic Roundtable14:51
*** openstack changes topic to "Roundtable (Meeting topic: airship)"14:51
mattmceuenAny additional topics, or community feedback this morning?14:51
uzumakimattmceuen, a small nit. Can we somehow embed the agenda etherpad link with the topics? That way, if sbd joins in later, they can quickly come upto speed with the etherpad14:51
*** francisy has joined #airshipit14:51
mattmceuenwould definitely be interested in making that easier14:51
uzumakithat'll be great14:52
mattmceuenfor the most part I think they're aligned already (I for one tend to copy and paste out of the agenda)14:52
mattmceuenare you thinking more like, dropping the verbatim topic name into the etherpad after its kicked off?14:52
uzumakino, I mean, the etherpad URL, part of the topic string14:52
mattmceuenohhhhhhhh14:52
mattmceuenI see14:52
airship-irc-bot1<alexander.hughes> For the new community members I forgot to mention another good set of resources for getting engaged with the day to day of Airship development https://wiki.openstack.org/wiki/Airship lists all our community meetings, how to subscribe to the mailing list, etc.14:53
uzumakiAnd we can keep the topic name bunch of identifying keywords, not to make the topic stirng too long14:53
mattmceuenI'll take an action item to look into the meeting bot documentation, and see what I can do uzumaki14:53
uzumakimattmceuen, that sounds great!14:53
mattmceuenif this is something we could automate somehow, would make it super easy14:53
uzumakiyes14:54
mattmceuenthanks for sharing that alexander.hughes14:54
* mattmceuen also, etherpad :) https://etherpad.opendev.org/p/airship-meeting-2020-04-1414:54
uzumakimerci!14:55
mattmceuende rien14:55
mattmceuenany other topics team?14:55
uzumakinope14:55
mattmceuenalright - thanks for a productive meeting; hope you all enjoy the rest of your Tuesday14:55
mattmceuenSee you next week if not before :)14:56
mattmceuen#endmeeting14:56
*** 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:56
openstackMeeting ended Tue Apr 14 14:56:09 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-04-14-14.00.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-04-14-14.00.txt14:56
uzumakisee you! \o14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-04-14-14.00.log.html14:56
openstackgerritDmitry Ukov proposed airship/airshipctl master: [WIP] Introduce document plugin subcommand  https://review.opendev.org/71993114:57
*** raymonddeng has left #airshipit14:57
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add pipeline factory and pipeline helpers  https://review.opendev.org/71910815:11
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add kubernetes pipeline implementation  https://review.opendev.org/71911315:11
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add pipeline Run command  https://review.opendev.org/71966615:11
*** alhatneha has quit IRC15:12
*** jtwill98 has quit IRC15:12
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add pipeline Run command  https://review.opendev.org/71966615:21
openstackgerritVamsi Savaram proposed airship/images master: Gather container logs in check pipeline  https://review.opendev.org/71373315:21
openstackgerritDrew Walters proposed airship/airshipctl master: Add iDRAC ephemeral boot media support  https://review.opendev.org/71371115:21
openstackgerritDrew Walters proposed airship/airshipctl master: Move bootstrap cmd functionality to baremetal cmd  https://review.opendev.org/71910315:30
openstackgerritDrew Walters proposed airship/airshipctl master: Move remote cmd functionality to baremetal cmd  https://review.opendev.org/71910915:30
openstackgerritDrew Walters proposed airship/airshipctl master: Add ephemeral host power on command  https://review.opendev.org/71674415:30
openstackgerritDrew Walters proposed airship/airshipctl master: WIP: Add baremetal ephemeral ejectmedia command  https://review.opendev.org/71911115:30
airship-irc-bot1<james.gu> a quick question for folks that are familiar with update-golden. The gate appears to run update-golden then run the unit test. What is the purpose of always running update-golden in the gate? Would that step virtually guarantee the pass of unit tests?15:39
airship-irc-bot1<ih616h> @james.gu it's a bit convoluted but...15:40
airship-irc-bot1<ih616h> the unit tests are run first15:40
airship-irc-bot1<ih616h> then update-golden is run15:40
openstackgerritAlexey Odinokov proposed airship/airshipctl master: Substituting ad-hoc sushy-emulator and apache reverse-proxy with apache with sushy-emulator attached via wsgi  https://review.opendev.org/71932015:40
airship-irc-bot1<ih616h> (update-golden actually reruns the unit tests)15:40
*** uzumaki has quit IRC15:40
airship-irc-bot1<ih616h> then there's a git-diff which verifies that there's no new golden files15:41
airship-irc-bot1<alexander.hughes> basically we're testing to make sure current tests work  then making sure that the tests themselves are valid (no tests are missing, no unused tests are present)  when we update the tests, we test again to make sure they still pass15:41
airship-irc-bot1<james.gu> ah it is the "(update-golden actually reruns the unit tests)" that caught me15:41
airship-irc-bot1<ih616h> on that note - `update-golden` only runs the code in the `./cmd` package15:42
airship-irc-bot1<ih616h> and it only partially runs tests - there's no assertions being made15:42
airship-irc-bot1<james.gu> just curious, since the unit test has already passed in the previous step, is there a need for update-golden (golden data has to be identical to what the cmd class output)?15:44
airship-irc-bot1<ih616h> yes - if a developer deletes a unit test in `./cmd`, it's possible that they forget to delete its associated golden file15:45
airship-irc-bot1<ih616h> basically, it verifies that developers are properly cleaning up after themselves :slightly_smiling_face:15:45
airship-irc-bot1<james.gu> from that purpose, it makes sense. I thought the purpose was broader, to match/update golden data to the actual cmd output.15:46
airship-irc-bot1<james.gu> thanks for the explanation howell15:47
*** uzumaki has joined #airshipit15:50
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add PhaseSelector and PhaseLabel  https://review.opendev.org/71886915:52
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add CurrentContextCluster Type and Name methods  https://review.opendev.org/71881415:52
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add pipeline factory and pipeline helpers  https://review.opendev.org/71910815:52
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add kubernetes pipeline implementation  https://review.opendev.org/71911315:52
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add pipeline Run command  https://review.opendev.org/71966615:52
*** avolkov has quit IRC15:57
*** ab2434_ has quit IRC16:00
*** diga has quit IRC16:03
openstackgerritDmitry Ukov proposed airship/airshipctl master: [WIP] Introduce document plugin subcommand  https://review.opendev.org/71993116:19
openstackgerritVamsi Savaram proposed airship/images master: Gather container logs in check pipeline  https://review.opendev.org/71373316:23
openstackgerritPrateek Dodda proposed airship/shipyard master: Implement Security Context for Airflow_Scheduler  https://review.opendev.org/71951916:27
openstackgerritRodolfo Pacheco proposed airship/airshipctl master: Implements airshipctl config --import <from kubeconfig>  https://review.opendev.org/71763016:35
*** evrardjp has quit IRC16:37
*** evrardjp has joined #airshipit16:37
*** SRao has quit IRC16:52
*** mikefix has quit IRC17:04
openstackgerritRodolfo Pacheco proposed airship/airshipctl master: Implements airshipctl config --import <from kubeconfig>  https://review.opendev.org/71763017:11
openstackgerritStas Egorov proposed airship/airshipctl master: removed Modules from Config  https://review.opendev.org/71856717:14
*** roman_g has quit IRC17:19
*** roman_g has joined #airshipit17:19
*** roman_g has quit IRC17:20
*** roman_g has joined #airshipit17:20
*** roman_g has quit IRC17:20
*** roman_g has joined #airshipit17:21
*** roman_g has quit IRC17:21
*** roman_g has joined #airshipit17:22
*** roman_g has quit IRC17:22
*** roman_g has joined #airshipit17:22
*** roman_g has quit IRC17:23
*** roman_g has joined #airshipit17:23
*** roman_g has quit IRC17:24
*** uzumaki has quit IRC18:02
*** dpawlik has quit IRC18:02
openstackgerritMatthew Fuller proposed airship/airshipui master: [WIP] Add plugin to show database status to Airship UI  https://review.opendev.org/71641418:11
openstackgerritAlexander Hughes proposed airship/airshipctl master: [WIP] Refactor of codebase addressing IDE errors  https://review.opendev.org/72004718:14
*** andrewkarandjeff has quit IRC18:43
openstackgerritAlexander Hughes proposed airship/airshipctl master: Refactor of codebase addressing IDE errors  https://review.opendev.org/72004719:15
openstackgerritAndrew Schiefelbein proposed airship/airshipui master: [WIP] transform airship ui into a standalone electron app  https://review.opendev.org/71784819:39
openstackgerritAlexander Hughes proposed airship/airshipctl master: Refactor of codebase addressing IDE errors  https://review.opendev.org/72004719:43
*** vamsisavaram has quit IRC19:54
openstackgerritAlexander Hughes proposed airship/airshipctl master: Refactor of codebase addressing IDE errors  https://review.opendev.org/72004719:56
openstackgerritIan Howell proposed airship/airshipctl master: Implements airshipctl config --import <from kubeconfig>  https://review.opendev.org/71763019:56
*** mikefix has joined #airshipit20:03
openstackgerriteric welch proposed airship/deckhand master: WIP password rotation for deckhand, testing first helm install  https://review.opendev.org/71216220:16
*** georgk has quit IRC20:19
*** georgk has joined #airshipit20:20
*** georgk has quit IRC20:20
*** georgk has joined #airshipit20:21
*** georgk has quit IRC20:23
openstackgerritAlexey Odinokov proposed airship/airshipctl master: Substituting ad-hoc sushy-emulator and apache reverse-proxy with apache with sushy-emulator attached via wsgi  https://review.opendev.org/71932021:00
*** KeithMnemonic has joined #airshipit21:08
*** roman_g has joined #airshipit21:08
*** KeithMnemonic has quit IRC21:16
openstackgerritMatthew Fuller proposed airship/airshipui master: Add plugin to show database status to Airship UI  https://review.opendev.org/71641421:16
*** KeithMnemonic has joined #airshipit21:17
openstackgerritAndrew Schiefelbein proposed airship/airshipui master: [WIP] transform airship ui into a standalone electron app  https://review.opendev.org/71784821:25
*** roman_g has quit IRC21:53
airship-irc-bot1<sirajudeen.yasin> Code review pls, https://review.opendev.org/#/c/713755/12 , just updated some commit msg per review comment21:58
openstackgerritRahul Khiyani proposed airship/armada master: Tiller: Add apparmor profile to tiller container  https://review.opendev.org/71952821:59
openstackgerritSirajudeen proposed airship/airshipctl master: Organize CLI helper functions  https://review.opendev.org/71375522:03
openstackgerritSirajudeen proposed airship/airshipctl master: Organize CLI helper functions  https://review.opendev.org/71375522:08
openstackgerritSirajudeen proposed airship/airshipctl master: Fix for Lint warnings  https://review.opendev.org/71828922:18
*** mikefix has quit IRC22:21
*** born2bake has quit IRC22:46

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