Tuesday, 2020-03-10

*** AlexNoskov has quit IRC00:30
openstackgerritdiwakar thyagaraj proposed airship/maas master: [WIP]Enable Logs Output in Zuul for Deployment Scripts  https://review.opendev.org/70976300:35
*** segorov has joined #airshipit00:48
*** thansen has quit IRC01:00
*** thansen has joined #airshipit01:02
*** rezroo has quit IRC01:27
*** happyhemant has quit IRC02:05
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add repository to airship config template, ansible  https://review.opendev.org/71182202:12
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Split document model, add entrypoints for repos  https://review.opendev.org/71157102:12
*** mfuller has quit IRC02:52
*** mfuller has joined #airshipit02:53
*** mfuller has quit IRC02:53
openstackgerritVladimir Maliaev proposed airship/promenade master: Updated resiliency gate  https://review.opendev.org/70854503:09
*** airshipbot has quit IRC03:37
*** roman_g has quit IRC04:02
*** krishnaposa has quit IRC04:13
*** ianychoi has quit IRC04:39
*** ianychoi has joined #airshipit04:40
*** rezroo has joined #airshipit05:29
*** evrardjp has quit IRC05:35
*** evrardjp has joined #airshipit05:35
*** rezroo has quit IRC06:29
*** dpawlik has joined #airshipit07:21
*** ianychoi has quit IRC11:16
*** ianychoi has joined #airshipit11:16
openstackgerritDmitry Ukov proposed airship/airshipctl master: Fix go get for airshipctl module  https://review.opendev.org/71040011:58
openstackgerritNikolay Fedorov proposed airship/airshipctl master: Add Bare Metal Operator resources  https://review.opendev.org/70653312:00
openstackgerritNikolay Fedorov proposed airship/airshipctl master: Add Bare Metal Operator Ironic config files  https://review.opendev.org/70673612:01
openstackgerritNikolay Fedorov proposed airship/airshipctl master: Add Bare Metal Operator Ironic entrypoints  https://review.opendev.org/70673712:01
*** happyhemant has joined #airshipit12:40
*** ianychoi has quit IRC12:49
*** ianychoi has joined #airshipit12:50
*** SRao has joined #airshipit13:01
*** rezroo has joined #airshipit13:13
mattmceuenHey everyone, good morning/evening -- reminder that our team IRC meeting will be in 30min due to daylight savings time change13:28
mattmceuenThe agenda is wide open, so feel free to add anything you'd like to discuss today: https://etherpad.openstack.org/p/airship-meeting-2020-03-1013:28
*** nishantkr has joined #airshipit13:42
nishantkrHello everyone, Here is the meeting agenda for today - https://etherpad.openstack.org/p/airship-meeting-2020-03-1013:46
nishantkrwe will start the meeting in 15 mins13:46
*** LoicL35 has joined #airshipit13:48
*** ab2434_ has joined #airshipit13:48
*** uzumaki has joined #airshipit13:50
mattmceuenSince we have a light agenda today - please add any patchsets you'd either like review on or would like to discuss^^13:50
mattmceuenso that, if we give time back, we can spend it doing reviews :)13:51
*** zainub_wahid has joined #airshipit13:52
nishantkr#startmeeting airship14:00
openstackMeeting started Tue Mar 10 14:00:18 2020 UTC and is due to finish in 60 minutes.  The chair is nishantkr. 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
nishantkr#topic Rollcall14:00
*** openstack changes topic to "Rollcall (Meeting topic: airship)"14:00
ian-pittwoodo/14:00
alexanderhugheso/14:00
uzumakio/14:01
nishantkrHello guys, Here is the agenda for today's meeting - https://etherpad.openstack.org/p/airship-meeting-2020-03-1014:01
mattmceueno/14:01
nishantkrPlease add any topics you would like to discuss, we will get started in couple of minutes14:01
*** madhumati has joined #airshipit14:01
*** ashferg has joined #airshipit14:02
*** dwalt has joined #airshipit14:02
nishantkr#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: airship)"14:03
nishantkralexanderhughes: please go for it14:04
dwalto/14:04
*** kkalina has joined #airshipit14:04
nishantkro/ dwalt14:04
jamesguo/14:04
alexanderhugheshello, just a quick reminder we transitioned to github issues for scope tracking a couple weeks ago.  for those that are looking for something to work on there's a couple good starting points I'd recommend14:04
seaneagano/14:05
*** alhatneha has joined #airshipit14:05
alexanderhughes1. find something that has an issue and is assigned to a milestone.  this will help you identify issues that need to be worked in an ordered fashion https://github.com/airshipit/airshipctl/milestones14:05
alexanderhughesor 2. if you're new to the project and looking for something that might interest you check out the labels https://github.com/airshipit/airshipctl/issues things like "good first issue" or "component/documents" to help narrow down issues that align with your interests14:06
mattmceuen++14:06
alexanderhughesif there is something you think airshipctl needs but is not yet present on issues, please feel free to open an issue, and the project organizers will review and discuss it.  usually during the flight plan calls on wednesdays14:07
*** jtwill98 has joined #airshipit14:07
alexanderhughesthat's all from me :)14:07
nishantkrthanks for sharing that information alexanderhughes , This is really helpful14:08
nishantkr#topic Does the community see any obvious knowledge gaps14:09
*** openstack changes topic to "Does the community see any obvious knowledge gaps (Meeting topic: airship)"14:09
nishantkralexanderhughes: that's you again, please go for it :)14:09
*** ianychoi has quit IRC14:10
*** RaviWaghmare has joined #airshipit14:10
alexanderhughesthanks Matt.  so this is a little bit of a followup on the announcement, and comes from a conversation I had yesterday looking for an area in Airship2 development that had a need to develop more expertise.  the area called out that I want to start working on is provisioning - but I wonder if there are other areas that would benefit from more people focusing on them: documents, baremetal provisioning, cluster14:10
*** ianychoi has joined #airshipit14:11
alexanderhughesetc.  and this question serves 2 functions... 1: as we get new people contributing are they able to help fill in some gaps?  and 2: do we have people with expertise in some of these areas that can serve as "mentors" of sorts, to help the new contributors get up to speed quickly14:11
mattmceuenI feel like some "domains" of work have been shaping up for airship2, like UI, provisioning, YAML engineering, CI automation...14:12
*** pramchan has joined #airshipit14:13
mattmceuensome of those have SIG meetings, and some do not (but they could consider spinning them up if helpful)14:13
mattmceuenI'm trying to think of gaps14:13
portdirectprovisioning is a rather loaded term in the world of airship ;)14:13
portdirectfrom the call earlier today - i wonder how much we are looking at things like the kubeadm capi implementation?14:14
mattmceuento be specific, I meant "widget provisioning"14:14
portdirectesp for things like etcd14:14
mattmceuengood point, and kubeadm deep knowledge for both config and management would be uber helpful to grow on our team14:15
pramchanwell we can use pre-provisioning and post-provisionong wrt  BM and clusters to segregate the associated tasks14:15
portdirectthe other aspect i think that woudl be great to see - is real thought given to failure domain handling and labeling14:16
portdirectthis is less of a 'pure' airship2 issue, but one we also have in airship1 today14:16
portdirectis there a way we can expose failure domain info to workloads?14:16
mattmceuen+, I didn't call it out before but workload management is a domain of work, which spans argo things and helm/tiller things14:17
pramchanwell labels need to defined before we can use them and atleast we in community do not have a cluse what lables mean in Airship to use14:17
portdirectpramchan: but what should we define ;) also this goes beyond kust labeling14:17
portdirectthings like pod affinity, etc14:18
pramchansure but that's the architecture and design call to freez labels for different use as 10 use cases Rodolfo was mentioning14:19
portdirectpramchan: im reffering more to what runs ONTOP of airship itself14:19
portdirectone day we will have a working cluster, then the real work begins14:19
*** diga has joined #airshipit14:20
pramchanmy understanding till date has been we learn what cluster API or metal3.io can offer besides argo on top and then we borrow or adopt what works for airship, rather than define what we need and adjust later14:21
uzumakiI agree, portdirect things are really complicated in airship, and we're all just focussing on the infrastructure itself (which we used to call the UCP), not the workload yet, gosh14:21
*** kkalina has quit IRC14:21
pramchanyes UCP -undercloud platform still exists although we do not want to use that term.14:23
portdirectanyway - didnt mean to derail - but in answer to alexanderhughes's question i think documentation re target use cases, and workload management are some of the biggest gaps atm in the community14:23
uzumaki+114:24
portdirectand closing them may help make some of what we do simpler to conceptualizes, but also ensure that we are building a platform that supports them14:24
mattmceuenlol hopefully something in there piqued everyone's interest for digging into -- good topic alexanderhughes14:24
alexanderhugheswould you say these are gaps where we have no knowledge in the community - or do you know of people working these items currently to begin collaborating with to share some of that knowledge?14:24
pramchan+1 shoukd consider getting Treasuremp 2.0 and Readthedoc completed as we move14:25
*** kkalina has joined #airshipit14:25
portdirectalexanderhughes: for much of this is just not having looked out that far with airship214:26
portdirectsom of this is fairly high level - eg CNFs needx, AI needs y etc14:27
pramchanLets bring it to community gathering once MM anounces the dates and bridge and open topics to debate14:27
uzumakiportdirect, agree. I don't think the 2.0 community is thinking of these things14:27
mattmceuenalexanderhughes:  I think the kubeadm area (through CAPBK and otherwise), and failure domain stuff jump out at me as additional areas where more depth would be valuable14:27
portdirectbut can get reasonable granular - eg storage provisioning etc, and if we use somthing like say ceph via rook - how can we manage this - taking into account failure domains in a deployment etc14:28
portdirect100% agree with mattmceuen's comment above14:28
portdirectsimple things - eg whats going on with etcdadm, or was that effort abandonded?14:28
nishantkrIs there a good way we can document somewhere about these areas within airship2, keep a track of people who are working on it and see which area needs more attention?14:29
pramchanetcadm is trying to align with kubeadm as last i evesdropped to hear their take14:29
uzumakithat sounds like a good idea14:29
uzumakinishantkr, create a new etherpad and link it in the design one?14:30
pramchan+114:30
nishantkrYup that's always an option :)14:31
pramchancall it user stories plus use cases14:31
uzumakicool, what do you guys this? alexanderhughes mattmceuen portdirect14:31
alexanderhughesI'd like to see this as well.  a high level overview of what areas are being worked now - what we think is coming in the future, and who we have that generally works in which domains.  using a table like that would be easier to visualize where our gaps are, what needs future thought and who the "go to" person is for each area when trying to onboard new people or get status updates14:32
mattmceuenwe could consider using tags for different (coursegrained!) domains, and tagging work in github issues14:32
mattmceuenso we'd be maintaining all of that stuff in one place14:32
mattmceuenbut I don't have a strong opinion14:32
nishantkryeah even i was thinking if we could somehow track this in github14:32
mattmceuenthensomeone could search github issues for upcoming e.g. bare metal provisiong scope or what have you14:33
pramchanremember adding too many issues and backlogs to github will strain the githup pipeline , rather discuss agree and then add new issues to github14:34
uzumakiagree. that could become an addendum to what we're talking about, that whole etherpad thing, where like alexanderhughes says we could also have a table/list of who's doing what14:34
nishantkrThis is a good topic to revisit again with options on how we can maintain this in a common place like github or etherpad or something else?14:35
mattmceuenpramchan: good point; I was only talking about tagging issues that /already/ have anyway, as opposed to adding a lot of new ones w/o thinking them through14:35
uzumakiI'm thinking this, etherpad with overall view of this thing, with that list like alexanderhughes said. IN ADDITION, introduce extra labels in github like mattmceuen said, just as a value added thing, for people to browse the github to look at the work itself (or perhaps introduce new work under those domains)14:36
alexanderhughesI think for tracking work github, but an etherpad addendum could be a good way to summarize the work people have already done that was tracked in github.. using that plus YAML sig attendance we can start to get a better idea of who is working what and which areas are still light on contributors14:36
uzumakiexactly my though alexanderhughes14:36
pramchan+114:37
mattmceuenthe good thing about these SIG meetings is that they kinda start up when we need them, and then expire when they're not needed anymore14:37
pramchanwell that's case with Bootstrap SIG for now14:37
nishantkrok sounds good, is that something you would want to start up with alexanderhughes and take feedback from folks in the next meeting?14:38
mattmceuenso let's keep an eye out for specific topics where focused deisign work would be needed, when we get to that point.  I wouldnt' want to create a SIG for all of these topics necessarily now and then have everyone sitting on calls all day :D14:38
*** zainub_wahid has quit IRC14:38
uzumakihaha, agree! +1 mattmceuen14:39
alexanderhughesI'd like to discuss this with the TC on Thursday.  I'll do a pass through github issues and sync with a few of you to come up with a rough table of what's being worked now and who works that space.  then start adding onto it using the airship design calls for what we think is coming and see if we can start filling it out to make sure we at least have someone thinking about these upcoming topics14:39
alexanderhughesI'll share the etherpad I come up with at our next community meeting on the 17th14:39
pramchanAlso is the wc call timing changed besides zoom link?14:39
alexanderhughesgreat question, all of the Airship meetings to my knowledge are created in US timezones.  because the US observes daylight saving time, meeting times in the US are unchanged - but - for countries where DST is not observed, the meetings are now 1 hour earlier14:40
ashfergdid your calendar invite show the wrong time?14:40
alexanderhughesIE 10 CST / 16:00 UTC is now 10 CDT / 15:00 UTC14:41
uzumakialexanderhughes, I'd like to stay looped into this use cases discussion14:41
pramchanNo ashfreg, it was a late email for monay changing of bridge and that confused me this week with DST changes14:42
pramchanNO issues will review the meeting minutes later14:42
nishantkrok i think we are onto a roundtable discussion already14:42
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129914:43
nishantkris there anything else someone would like to discuss today?14:43
mattmceuenany requests for additional code review?14:44
pramchanIs there any agreement on which metal3.io or capi versions Airship will use?14:44
pramchanI mean airship 2.014:44
alexanderhughesairshipctl in general =/  we've had a huge influx of commits lately, but review counts have been relatively steady so work is outpacing reviews14:44
alexanderhugheshad a big push Friday to get it down, but more eyes in general would be helpful14:44
*** rezroo has quit IRC14:44
mattmceuen++14:44
uzumakiI can look at some things (although I'm not fully intimate with the airshipctl code base yet)14:45
mattmceuenawesome ty uzumaki14:45
uzumakisure, any tips for a new onboarding 'set of eyes' for commit reviews? what are we generally looking for?14:46
nishantkrI think ahmad was looking for some core reviews on a shipyard PS here - https://review.opendev.org/#/c/709056/14:46
nishantkruzumaki - i would look for open PS here - https://review.opendev.org/#/q/project:airship/airshipctl+status:open14:47
alexanderhughesmost patchsets in airshipctl map to an issue https://github.com/airshipit/airshipctl/issues?q=label%3A%22ready+for+review%2214:47
mattmceuenuzumaki: some folks who have more experience in the technology (e.g. go) give reviews from a code convention / cleanliness perspective, and some folks with more of the domain knowledge give review from a "what is being accomplished" perspective, there is no wrong answer!14:47
alexanderhugheswhen reviewing - does the patch meet the story requirements, does the patch pass unit tests (and for new code were new tests added that make sense), does the code make sense14:48
uzumakimattmceuen, I see, that's helpful alexanderhughes14:48
mattmceuenIf anyone is interested in the domains of work we were discussing earlier, then I'd see whether there's any outstanding work in that area -- CICD, bare metal provisioning, etc14:48
mattmceuenoutstanding work needing review, I mean.  That would help ramp up as well.14:49
uzumakiSo, in order to review, I'd just add myself as a reviewer on that change, do my stuff (comments etc) and that's it?14:49
mattmceuenyep!14:49
uzumakicool! I look at all the patchsets in airshipctl anyway, I'll start reviewing given the tips14:50
alexanderhughesthe issues link above routes you to where the patches live on gerrit (Nishant's link) and from there hit the reply button and give a vote with comments14:50
pramchanWe have one and asked Digambar to send email on definiton for BM machine YAML to use for Airship 2.0, if we go by what meatl3.io or cluster api define or we define as what Airship needs?14:50
digamattmceuen:  Baremetal provisioning through metal3 ?14:50
digaYes, pramchan. I will send mail in sometime14:51
pramchan+114:51
nishantkrThanks diga14:51
mattmceuendiga:  yeah, I was kind of lumping together CAPI, M3, and related airshipctl/YAML work into a big bare metal provisioning category14:52
diganishantkr: wc14:52
mattmceueneven though that's a very very broad category14:52
digayeah14:52
digaagree14:52
digaNow CAPBK changed to CAPM314:53
mattmceuenalso, when review is needed on changes to other repos (e.g. metal3) it would be great to bring them to this meeting14:53
pramchanMainly we need to understand gaps to drive gopher cloud and Ironic in advance14:53
uzumakialexanderhughes, that sounds simple enough. SO my workflow so far looks like get the labeled issues from github -> get to the change -> reply/comment looking at the issue and seeing if the code does what it says. That sounds doable.14:53
mattmceuensince they wouldn't show up in the filter nishant posted14:53
digamattmceuen: yeah14:53
mattmceuenpramchan,diga:  sounds great, will watch for the email on airship-discuss!14:53
alexanderhughesyep.  combing through gerrit directly is fine too, patches should be using sufficiently verbose commit messages to describe the intended changes and why they're needed14:54
uzumakiyes, but some of them just reference the git issue, which is fine as well.14:54
nishantkruzumaki: and if there's something you do not understand in the code, it's alright to ask questions on the PS as well to get more clarity14:54
uzumakinishantkr, i see. And if the discussion is ongoing, I don't necessarily have to give it a +1/-1, keep it a 0?14:55
nishantkrI do that all the time :)14:55
mattmceuen++ uzumaki14:55
pramchan+1 matt Diga is working on it and we need comments to plan for Open Infra PTG14:55
pramchan+1 uzumaki14:55
uzumakiAlright. I guess I can lend a hand in some reviews mattmceuen alexanderhughes nishantkr14:55
nishantkryup that's right uzumaki14:55
alexanderhughesthat'd be great, thanks uzumaki14:55
ian-pittwoodHere's a good filter for manually combing gerrit https://review.opendev.org/#/q/status:open+NOT+label:Verified%253D-1+NOT+label:Workflow%253D-1+NOT+message:DNM+NOT+message:WIP+project:airship/airshipctl14:56
nishantkrthanks for the link ian-pittwood14:56
nishantkrok guys any other roundtable items before we close out the meeting?14:57
uzumakithat's cool ian-pittwood I've actually subscribed to the airshipctl project on opendev, I guess I can get rid of it, since I'm gonna be combing gerrit/github for work now.14:57
uzumakinishantkr, nothing from me. I'm good.14:57
pramchanfor review - https://review.opendev.org/#/c/686389/14:58
jtwill98ian:  there are many items on that list which have gone stale like https://review.opendev.org/#/c/690870/14:58
jtwill98Is there a process for moving them to closure14:59
pramchanDoes this suffice for vBMC doc or do we need to place in Treasuremap 2.0 docs?14:59
alexanderhughesgerrit and opendev are interchangeable terms.  any time we're talking about reviewing code on gerrit we mean review.opendev.org for one of the airship projects.  big focus lately is the airship/airshipctl project15:00
ian-pittwoodjtwill98 I don't really have a good answer for that. Eventually those changes should be abandoned most likely15:01
nishantkrwe are out of time guys, Thanks everyone for joining,  we can continue rest of the discussion after the meeting as well :)15:01
nishantkr#endtopic15:01
*** LoicL35 has quit IRC15:01
alexanderhughesthanks all15:01
nishantkr#endmeeting15:01
*** 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:01
openstackMeeting ended Tue Mar 10 15:01:23 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
pramchan+1 jtwill98 repo owners must decide what is stale andgive instructions to abandon or resubmit with new commits based on git issues #airshipit15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-03-10-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-03-10-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-03-10-14.00.log.html15:01
*** alhatneha has quit IRC15:02
uzumakiis dwalt here?15:03
jtwill98I'd really like to see a meeting or process to handle stale issues and agree with Pramchan, that owner repos should drive these to closure.15:03
dwaltUzumaki: o/15:03
pramchan+1 jtwill9815:03
uzumakihey dwalt ! wanted to follow up on what you said on that issue https://github.com/airshipit/airshipctl/issues/7215:03
uzumakihow is the newly merged scripts going to 'change things'?15:04
mattmceuenthanks nishantkr!15:04
*** madhumati has quit IRC15:04
dwaltah yes! I'm sorry that I haven't followed up on that yet-15:04
dwaltI only meant that if you weren't too far along, it might be better if the dev docs follow the new dev scripts that recently merged15:05
*** RaviWaghmare has left #airshipit15:05
dwaltI'll grab the link15:05
openstackgerritSreejith Punnapuzha proposed airship/airshipctl master: [#106] Add docker install role  https://review.opendev.org/71154015:05
uzumakithat'll be great15:05
dwalthttps://github.com/airshipit/airshipctl/tree/master/tools/gate15:05
dwaltIt's just a wrapper around the ansible15:05
dwaltIf you're close to finishing, no need to do it now. We can file a follow-up issue15:06
uzumakioh, I saw this change on gerrit, said something like 'write scripts for ansible' or something, this looks like that15:07
uzumakiLet me check up with my team and see if it's easily doable, otherwise, the follow up issue is always an option. Will definitely have something by the flightplan call tomorrow.15:08
uzumakithanks for letting me know! dwalt15:08
dwaltsounds good. Thanks!15:09
uzumakialright i'm off now. thanks guys! \o15:09
openstackgerritdiwakar thyagaraj proposed airship/maas master: [WIP]Enable Logs Output in Zuul for Deployment Scripts  https://review.opendev.org/70976315:12
*** pramchan has quit IRC15:13
openstackgerritIan Pittwood proposed airship/airshipctl master: [WIP][#19] Add validate schema command  https://review.opendev.org/70386415:34
*** uzumaki has quit IRC15:38
*** KeithMnemonic has joined #airshipit15:38
*** jtwill98 has left #airshipit15:40
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129915:45
*** thansen has quit IRC15:53
*** thansen has joined #airshipit15:54
*** segorov has quit IRC15:54
*** segorov has joined #airshipit15:55
*** segorov has quit IRC16:00
*** AlexNoskov has joined #airshipit16:02
*** ianychoi has quit IRC16:11
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors  https://review.opendev.org/71084516:12
*** ianychoi has joined #airshipit16:12
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors  https://review.opendev.org/71084516:16
openstackgerriteric welch proposed airship/deckhand master: attempting kubernetes cluster launch  https://review.opendev.org/69393516:28
*** rezroo has joined #airshipit16:41
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors  https://review.opendev.org/71084516:42
*** jamesgu has quit IRC16:43
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129916:44
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#38] Add end-user documentation to project  https://review.opendev.org/71163416:45
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#91] refactor secrets as top level command  https://review.opendev.org/71168416:45
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#88] add golang  naming convention documentation  https://review.opendev.org/71152916:45
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#86] remove unused code  https://review.opendev.org/71150616:45
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Remove unnecessary kubectl subcommand  https://review.opendev.org/71008516:46
*** ianychoi has quit IRC16:47
*** ianychoi has joined #airshipit16:48
openstackgerritMerged airship/images master: Image tagging  https://review.opendev.org/71199916:57
*** mfuller has joined #airshipit17:02
*** SRao has quit IRC17:02
*** rpocase has joined #airshipit17:22
rpocaseI'm hitting issues with linting a newly authored airship 1.7 site. "sudo tools/airship pegleg site -r /target lint my_site" gives "pegleg.engine.util.git:normalize_repo_path [497] The repo_path=/home/rpocase/git/architecture/treasuremap-1.7 is17:24
rpocasenot a valid Git repo17:24
rpocaseI've tried switching the argument to -r to both a path with a .git dir and an http git endpoint. The --help text mentions it should be a repo with a site_definition.yaml, but not seeing anything in the authoring docs about this file17:25
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors  https://review.opendev.org/71084517:25
*** ianychoi has quit IRC17:26
*** ianychoi has joined #airshipit17:27
*** evrardjp has quit IRC17:35
*** evrardjp has joined #airshipit17:35
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129917:43
*** mfuller has quit IRC17:48
rpocaseFigured out my problem. Turns out you need to execute from the root of a .git repo (assuming -r isn't a url). I also had to set SITE and SITE_PATH (which isn't mentioned in authoring)17:58
openstackgerritAhmad Mahmoudi proposed airship/shipyard master: (fix) Address image build issues, bionic  https://review.opendev.org/70905618:06
openstackgerritMerged airship/airshipctl master: [#38] Add end-user documentation to project  https://review.opendev.org/71163418:08
*** ianychoi has quit IRC18:10
*** ianychoi has joined #airshipit18:17
openstackgerritIan Pittwood proposed airship/airshipctl master: [WIP] Target test files only in git diff check  https://review.opendev.org/71214818:20
*** segorov has joined #airshipit18:20
openstackgerritAndrew Schiefelbein proposed airship/airshipui master: Makefile plugin copy fix  https://review.opendev.org/71215018:23
*** mfuller has joined #airshipit18:32
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129918:36
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129918:47
*** rpocase has quit IRC18:48
*** diga has quit IRC18:49
openstackgerritStas Egorov proposed airship/airshipctl master: Use local registry for isogen builder  https://review.opendev.org/71200319:06
openstackgerriteric welch proposed airship/deckhand master: deleting extra comments  https://review.opendev.org/69393519:12
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#88] add golang  naming convention documentation  https://review.opendev.org/71152919:14
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#91] refactor secrets as top level command  https://review.opendev.org/71168419:14
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#86] remove unused code  https://review.opendev.org/71150619:15
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors  https://review.opendev.org/71084519:15
openstackgerritAlexander Hughes proposed airship/airshipctl master: [#70] Remove unnecessary kubectl subcommand  https://review.opendev.org/71008519:15
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: test only, DO NOT MERGE  https://review.opendev.org/71216019:20
*** mugsie has quit IRC19:23
*** mugsie has joined #airshipit19:26
openstackgerriteric welch proposed airship/deckhand master: WIP password rotation for deckhand  https://review.opendev.org/71216219:27
openstackgerritSreejith Punnapuzha proposed airship/airshipctl master: [#106] Add docker install role  https://review.opendev.org/71154019:28
*** openstackgerrit has quit IRC19:32
*** openstackgerrit has joined #airshipit19:41
openstackgerritJames Gu proposed airship/airshipctl master: Correct ansible task name for kubectl version  https://review.opendev.org/71216819:41
*** mfuller has quit IRC19:43
*** timClicks has joined #airshipit20:02
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: test only, DO NOT MERGE  https://review.opendev.org/71216020:09
*** ianychoi has quit IRC20:17
*** ianychoi has joined #airshipit20:18
*** openstackstatus has joined #airshipit20:18
*** ChanServ sets mode: +v openstackstatus20:18
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129920:19
*** mfuller has joined #airshipit20:31
*** mfuller has quit IRC20:35
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129920:48
openstackgerritFrancis Bacon Yi proposed airship/airshipctl master: Target test files only in git diff check  https://review.opendev.org/71214820:54
openstackgerritStas Egorov proposed airship/airshipctl master: Use 16GB flavor for gate job  https://review.opendev.org/71216021:02
openstackgerritStas Egorov proposed airship/airshipctl master: Use 16GB flavor for gate job  https://review.opendev.org/71216021:43
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Split document model, add entrypoints for repos  https://review.opendev.org/71157121:59
*** sreejithp has joined #airshipit21:59
*** sreejithp has quit IRC22:02
*** evrardjp has quit IRC22:17
*** evrardjp has joined #airshipit22:18
*** ianychoi has quit IRC22:19
*** ianychoi has joined #airshipit22:20
*** ab2434_ has quit IRC22:27
*** evrardjp has quit IRC22:31
*** evrardjp has joined #airshipit22:33
*** dpawlik has quit IRC22:40
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129922:41
*** ianychoi has quit IRC22:41
*** ianychoi has joined #airshipit22:42
*** zogger has quit IRC22:43
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3  https://review.opendev.org/71129922:49
*** segorov has quit IRC22:57
*** segorov has joined #airshipit22:59
*** segorov has quit IRC23:08
*** zogger has joined #airshipit23:08
*** segorov has joined #airshipit23:10
*** segorov has quit IRC23:16
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Fix dependency cycle of config and document pkg  https://review.opendev.org/71220523:19
openstackgerritAlan Meadows proposed airship/airshipctl master: [#45] iso generation pulls network data from ephemeral host  https://review.opendev.org/70863623:40
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Fix dependency cycle of config and document pkg  https://review.opendev.org/71220523:43
*** dwalt has quit IRC23:52

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