*** AlexNoskov has quit IRC | 00:30 | |
openstackgerrit | diwakar thyagaraj proposed airship/maas master: [WIP]Enable Logs Output in Zuul for Deployment Scripts https://review.opendev.org/709763 | 00:35 |
---|---|---|
*** segorov has joined #airshipit | 00:48 | |
*** thansen has quit IRC | 01:00 | |
*** thansen has joined #airshipit | 01:02 | |
*** rezroo has quit IRC | 01:27 | |
*** happyhemant has quit IRC | 02:05 | |
openstackgerrit | Kostyantyn Kalynovskyi proposed airship/airshipctl master: Add repository to airship config template, ansible https://review.opendev.org/711822 | 02:12 |
openstackgerrit | Kostyantyn Kalynovskyi proposed airship/airshipctl master: Split document model, add entrypoints for repos https://review.opendev.org/711571 | 02:12 |
*** mfuller has quit IRC | 02:52 | |
*** mfuller has joined #airshipit | 02:53 | |
*** mfuller has quit IRC | 02:53 | |
openstackgerrit | Vladimir Maliaev proposed airship/promenade master: Updated resiliency gate https://review.opendev.org/708545 | 03:09 |
*** airshipbot has quit IRC | 03:37 | |
*** roman_g has quit IRC | 04:02 | |
*** krishnaposa has quit IRC | 04:13 | |
*** ianychoi has quit IRC | 04:39 | |
*** ianychoi has joined #airshipit | 04:40 | |
*** rezroo has joined #airshipit | 05:29 | |
*** evrardjp has quit IRC | 05:35 | |
*** evrardjp has joined #airshipit | 05:35 | |
*** rezroo has quit IRC | 06:29 | |
*** dpawlik has joined #airshipit | 07:21 | |
*** ianychoi has quit IRC | 11:16 | |
*** ianychoi has joined #airshipit | 11:16 | |
openstackgerrit | Dmitry Ukov proposed airship/airshipctl master: Fix go get for airshipctl module https://review.opendev.org/710400 | 11:58 |
openstackgerrit | Nikolay Fedorov proposed airship/airshipctl master: Add Bare Metal Operator resources https://review.opendev.org/706533 | 12:00 |
openstackgerrit | Nikolay Fedorov proposed airship/airshipctl master: Add Bare Metal Operator Ironic config files https://review.opendev.org/706736 | 12:01 |
openstackgerrit | Nikolay Fedorov proposed airship/airshipctl master: Add Bare Metal Operator Ironic entrypoints https://review.opendev.org/706737 | 12:01 |
*** happyhemant has joined #airshipit | 12:40 | |
*** ianychoi has quit IRC | 12:49 | |
*** ianychoi has joined #airshipit | 12:50 | |
*** SRao has joined #airshipit | 13:01 | |
*** rezroo has joined #airshipit | 13:13 | |
mattmceuen | Hey everyone, good morning/evening -- reminder that our team IRC meeting will be in 30min due to daylight savings time change | 13:28 |
mattmceuen | The 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-10 | 13:28 |
*** nishantkr has joined #airshipit | 13:42 | |
nishantkr | Hello everyone, Here is the meeting agenda for today - https://etherpad.openstack.org/p/airship-meeting-2020-03-10 | 13:46 |
nishantkr | we will start the meeting in 15 mins | 13:46 |
*** LoicL35 has joined #airshipit | 13:48 | |
*** ab2434_ has joined #airshipit | 13:48 | |
*** uzumaki has joined #airshipit | 13:50 | |
mattmceuen | Since we have a light agenda today - please add any patchsets you'd either like review on or would like to discuss^^ | 13:50 |
mattmceuen | so that, if we give time back, we can spend it doing reviews :) | 13:51 |
*** zainub_wahid has joined #airshipit | 13:52 | |
nishantkr | #startmeeting airship | 14:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
*** openstack changes topic to " (Meeting topic: airship)" | 14:00 | |
openstack | The meeting name has been set to 'airship' | 14:00 |
nishantkr | #topic Rollcall | 14:00 |
*** openstack changes topic to "Rollcall (Meeting topic: airship)" | 14:00 | |
ian-pittwood | o/ | 14:00 |
alexanderhughes | o/ | 14:00 |
uzumaki | o/ | 14:01 |
nishantkr | Hello guys, Here is the agenda for today's meeting - https://etherpad.openstack.org/p/airship-meeting-2020-03-10 | 14:01 |
mattmceuen | o/ | 14:01 |
nishantkr | Please add any topics you would like to discuss, we will get started in couple of minutes | 14:01 |
*** madhumati has joined #airshipit | 14:01 | |
*** ashferg has joined #airshipit | 14:02 | |
*** dwalt has joined #airshipit | 14:02 | |
nishantkr | #topic Announcements | 14:03 |
*** openstack changes topic to "Announcements (Meeting topic: airship)" | 14:03 | |
nishantkr | alexanderhughes: please go for it | 14:04 |
dwalt | o/ | 14:04 |
*** kkalina has joined #airshipit | 14:04 | |
nishantkr | o/ dwalt | 14:04 |
jamesgu | o/ | 14:04 |
alexanderhughes | hello, 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 recommend | 14:04 |
seaneagan | o/ | 14:05 |
*** alhatneha has joined #airshipit | 14:05 | |
alexanderhughes | 1. 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/milestones | 14:05 |
alexanderhughes | or 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 interests | 14:06 |
mattmceuen | ++ | 14:06 |
alexanderhughes | if 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 wednesdays | 14:07 |
*** jtwill98 has joined #airshipit | 14:07 | |
alexanderhughes | that's all from me :) | 14:07 |
nishantkr | thanks for sharing that information alexanderhughes , This is really helpful | 14:08 |
nishantkr | #topic Does the community see any obvious knowledge gaps | 14:09 |
*** openstack changes topic to "Does the community see any obvious knowledge gaps (Meeting topic: airship)" | 14:09 | |
nishantkr | alexanderhughes: that's you again, please go for it :) | 14:09 |
*** ianychoi has quit IRC | 14:10 | |
*** RaviWaghmare has joined #airshipit | 14:10 | |
alexanderhughes | thanks 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, cluster | 14:10 |
*** ianychoi has joined #airshipit | 14:11 | |
alexanderhughes | etc. 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 quickly | 14:11 |
mattmceuen | I feel like some "domains" of work have been shaping up for airship2, like UI, provisioning, YAML engineering, CI automation... | 14:12 |
*** pramchan has joined #airshipit | 14:13 | |
mattmceuen | some of those have SIG meetings, and some do not (but they could consider spinning them up if helpful) | 14:13 |
mattmceuen | I'm trying to think of gaps | 14:13 |
portdirect | provisioning is a rather loaded term in the world of airship ;) | 14:13 |
portdirect | from the call earlier today - i wonder how much we are looking at things like the kubeadm capi implementation? | 14:14 |
mattmceuen | to be specific, I meant "widget provisioning" | 14:14 |
portdirect | esp for things like etcd | 14:14 |
mattmceuen | good point, and kubeadm deep knowledge for both config and management would be uber helpful to grow on our team | 14:15 |
pramchan | well we can use pre-provisioning and post-provisionong wrt BM and clusters to segregate the associated tasks | 14:15 |
portdirect | the other aspect i think that woudl be great to see - is real thought given to failure domain handling and labeling | 14:16 |
portdirect | this is less of a 'pure' airship2 issue, but one we also have in airship1 today | 14:16 |
portdirect | is 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 things | 14:17 |
pramchan | well 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 use | 14:17 |
portdirect | pramchan: but what should we define ;) also this goes beyond kust labeling | 14:17 |
portdirect | things like pod affinity, etc | 14:18 |
pramchan | sure but that's the architecture and design call to freez labels for different use as 10 use cases Rodolfo was mentioning | 14:19 |
portdirect | pramchan: im reffering more to what runs ONTOP of airship itself | 14:19 |
portdirect | one day we will have a working cluster, then the real work begins | 14:19 |
*** diga has joined #airshipit | 14:20 | |
pramchan | my 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 later | 14:21 |
uzumaki | I 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, gosh | 14:21 |
*** kkalina has quit IRC | 14:21 | |
pramchan | yes UCP -undercloud platform still exists although we do not want to use that term. | 14:23 |
portdirect | anyway - 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 community | 14:23 |
uzumaki | +1 | 14:24 |
portdirect | and closing them may help make some of what we do simpler to conceptualizes, but also ensure that we are building a platform that supports them | 14:24 |
mattmceuen | lol hopefully something in there piqued everyone's interest for digging into -- good topic alexanderhughes | 14:24 |
alexanderhughes | would 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 move | 14:25 |
*** kkalina has joined #airshipit | 14:25 | |
portdirect | alexanderhughes: for much of this is just not having looked out that far with airship2 | 14:26 |
portdirect | som of this is fairly high level - eg CNFs needx, AI needs y etc | 14:27 |
pramchan | Lets bring it to community gathering once MM anounces the dates and bridge and open topics to debate | 14:27 |
uzumaki | portdirect, agree. I don't think the 2.0 community is thinking of these things | 14:27 |
mattmceuen | alexanderhughes: 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 valuable | 14:27 |
portdirect | but 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 etc | 14:28 |
portdirect | 100% agree with mattmceuen's comment above | 14:28 |
portdirect | simple things - eg whats going on with etcdadm, or was that effort abandonded? | 14:28 |
nishantkr | Is 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 |
pramchan | etcadm is trying to align with kubeadm as last i evesdropped to hear their take | 14:29 |
uzumaki | that sounds like a good idea | 14:29 |
uzumaki | nishantkr, create a new etherpad and link it in the design one? | 14:30 |
pramchan | +1 | 14:30 |
nishantkr | Yup that's always an option :) | 14:31 |
pramchan | call it user stories plus use cases | 14:31 |
uzumaki | cool, what do you guys this? alexanderhughes mattmceuen portdirect | 14:31 |
alexanderhughes | I'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 updates | 14:32 |
mattmceuen | we could consider using tags for different (coursegrained!) domains, and tagging work in github issues | 14:32 |
mattmceuen | so we'd be maintaining all of that stuff in one place | 14:32 |
mattmceuen | but I don't have a strong opinion | 14:32 |
nishantkr | yeah even i was thinking if we could somehow track this in github | 14:32 |
mattmceuen | thensomeone could search github issues for upcoming e.g. bare metal provisiong scope or what have you | 14:33 |
pramchan | remember adding too many issues and backlogs to github will strain the githup pipeline , rather discuss agree and then add new issues to github | 14:34 |
uzumaki | agree. 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 what | 14:34 |
nishantkr | This 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 |
mattmceuen | pramchan: 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 through | 14:35 |
uzumaki | I'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 |
alexanderhughes | I 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 contributors | 14:36 |
uzumaki | exactly my though alexanderhughes | 14:36 |
pramchan | +1 | 14:37 |
mattmceuen | the good thing about these SIG meetings is that they kinda start up when we need them, and then expire when they're not needed anymore | 14:37 |
pramchan | well that's case with Bootstrap SIG for now | 14:37 |
nishantkr | ok sounds good, is that something you would want to start up with alexanderhughes and take feedback from folks in the next meeting? | 14:38 |
mattmceuen | so 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 :D | 14:38 |
*** zainub_wahid has quit IRC | 14:38 | |
uzumaki | haha, agree! +1 mattmceuen | 14:39 |
alexanderhughes | I'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 topics | 14:39 |
alexanderhughes | I'll share the etherpad I come up with at our next community meeting on the 17th | 14:39 |
pramchan | Also is the wc call timing changed besides zoom link? | 14:39 |
alexanderhughes | great 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 earlier | 14:40 |
ashferg | did your calendar invite show the wrong time? | 14:40 |
alexanderhughes | IE 10 CST / 16:00 UTC is now 10 CDT / 15:00 UTC | 14:41 |
uzumaki | alexanderhughes, I'd like to stay looped into this use cases discussion | 14:41 |
pramchan | No ashfreg, it was a late email for monay changing of bridge and that confused me this week with DST changes | 14:42 |
pramchan | NO issues will review the meeting minutes later | 14:42 |
nishantkr | ok i think we are onto a roundtable discussion already | 14:42 |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 14:43 |
nishantkr | is there anything else someone would like to discuss today? | 14:43 |
mattmceuen | any requests for additional code review? | 14:44 |
pramchan | Is there any agreement on which metal3.io or capi versions Airship will use? | 14:44 |
pramchan | I mean airship 2.0 | 14:44 |
alexanderhughes | airshipctl in general =/ we've had a huge influx of commits lately, but review counts have been relatively steady so work is outpacing reviews | 14:44 |
alexanderhughes | had a big push Friday to get it down, but more eyes in general would be helpful | 14:44 |
*** rezroo has quit IRC | 14:44 | |
mattmceuen | ++ | 14:44 |
uzumaki | I can look at some things (although I'm not fully intimate with the airshipctl code base yet) | 14:45 |
mattmceuen | awesome ty uzumaki | 14:45 |
uzumaki | sure, any tips for a new onboarding 'set of eyes' for commit reviews? what are we generally looking for? | 14:46 |
nishantkr | I think ahmad was looking for some core reviews on a shipyard PS here - https://review.opendev.org/#/c/709056/ | 14:46 |
nishantkr | uzumaki - i would look for open PS here - https://review.opendev.org/#/q/project:airship/airshipctl+status:open | 14:47 |
alexanderhughes | most patchsets in airshipctl map to an issue https://github.com/airshipit/airshipctl/issues?q=label%3A%22ready+for+review%22 | 14:47 |
mattmceuen | uzumaki: 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 |
alexanderhughes | when 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 sense | 14:48 |
uzumaki | mattmceuen, I see, that's helpful alexanderhughes | 14:48 |
mattmceuen | If 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, etc | 14:48 |
mattmceuen | outstanding work needing review, I mean. That would help ramp up as well. | 14:49 |
uzumaki | So, 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 |
mattmceuen | yep! | 14:49 |
uzumaki | cool! I look at all the patchsets in airshipctl anyway, I'll start reviewing given the tips | 14:50 |
alexanderhughes | the 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 comments | 14:50 |
pramchan | We 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 |
diga | mattmceuen: Baremetal provisioning through metal3 ? | 14:50 |
diga | Yes, pramchan. I will send mail in sometime | 14:51 |
pramchan | +1 | 14:51 |
nishantkr | Thanks diga | 14:51 |
mattmceuen | diga: yeah, I was kind of lumping together CAPI, M3, and related airshipctl/YAML work into a big bare metal provisioning category | 14:52 |
diga | nishantkr: wc | 14:52 |
mattmceuen | even though that's a very very broad category | 14:52 |
diga | yeah | 14:52 |
diga | agree | 14:52 |
diga | Now CAPBK changed to CAPM3 | 14:53 |
mattmceuen | also, when review is needed on changes to other repos (e.g. metal3) it would be great to bring them to this meeting | 14:53 |
pramchan | Mainly we need to understand gaps to drive gopher cloud and Ironic in advance | 14:53 |
uzumaki | alexanderhughes, 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 |
mattmceuen | since they wouldn't show up in the filter nishant posted | 14:53 |
diga | mattmceuen: yeah | 14:53 |
mattmceuen | pramchan,diga: sounds great, will watch for the email on airship-discuss! | 14:53 |
alexanderhughes | yep. combing through gerrit directly is fine too, patches should be using sufficiently verbose commit messages to describe the intended changes and why they're needed | 14:54 |
uzumaki | yes, but some of them just reference the git issue, which is fine as well. | 14:54 |
nishantkr | uzumaki: 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 clarity | 14:54 |
uzumaki | nishantkr, 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 |
nishantkr | I do that all the time :) | 14:55 |
mattmceuen | ++ uzumaki | 14:55 |
pramchan | +1 matt Diga is working on it and we need comments to plan for Open Infra PTG | 14:55 |
pramchan | +1 uzumaki | 14:55 |
uzumaki | Alright. I guess I can lend a hand in some reviews mattmceuen alexanderhughes nishantkr | 14:55 |
nishantkr | yup that's right uzumaki | 14:55 |
alexanderhughes | that'd be great, thanks uzumaki | 14:55 |
ian-pittwood | Here'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/airshipctl | 14:56 |
nishantkr | thanks for the link ian-pittwood | 14:56 |
nishantkr | ok guys any other roundtable items before we close out the meeting? | 14:57 |
uzumaki | that'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 |
uzumaki | nishantkr, nothing from me. I'm good. | 14:57 |
pramchan | for review - https://review.opendev.org/#/c/686389/ | 14:58 |
jtwill98 | ian: there are many items on that list which have gone stale like https://review.opendev.org/#/c/690870/ | 14:58 |
jtwill98 | Is there a process for moving them to closure | 14:59 |
pramchan | Does this suffice for vBMC doc or do we need to place in Treasuremap 2.0 docs? | 14:59 |
alexanderhughes | gerrit 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 project | 15:00 |
ian-pittwood | jtwill98 I don't really have a good answer for that. Eventually those changes should be abandoned most likely | 15:01 |
nishantkr | we are out of time guys, Thanks everyone for joining, we can continue rest of the discussion after the meeting as well :) | 15:01 |
nishantkr | #endtopic | 15:01 |
*** LoicL35 has quit IRC | 15:01 | |
alexanderhughes | thanks all | 15:01 |
nishantkr | #endmeeting | 15: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 | |
openstack | Meeting 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 #airshipit | 15:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-03-10-14.00.html | 15:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-03-10-14.00.txt | 15:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-03-10-14.00.log.html | 15:01 |
*** alhatneha has quit IRC | 15:02 | |
uzumaki | is dwalt here? | 15:03 |
jtwill98 | I'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 |
dwalt | Uzumaki: o/ | 15:03 |
pramchan | +1 jtwill98 | 15:03 |
uzumaki | hey dwalt ! wanted to follow up on what you said on that issue https://github.com/airshipit/airshipctl/issues/72 | 15:03 |
uzumaki | how is the newly merged scripts going to 'change things'? | 15:04 |
mattmceuen | thanks nishantkr! | 15:04 |
*** madhumati has quit IRC | 15:04 | |
dwalt | ah yes! I'm sorry that I haven't followed up on that yet- | 15:04 |
dwalt | I 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 merged | 15:05 |
*** RaviWaghmare has left #airshipit | 15:05 | |
dwalt | I'll grab the link | 15:05 |
openstackgerrit | Sreejith Punnapuzha proposed airship/airshipctl master: [#106] Add docker install role https://review.opendev.org/711540 | 15:05 |
uzumaki | that'll be great | 15:05 |
dwalt | https://github.com/airshipit/airshipctl/tree/master/tools/gate | 15:05 |
dwalt | It's just a wrapper around the ansible | 15:05 |
dwalt | If you're close to finishing, no need to do it now. We can file a follow-up issue | 15:06 |
uzumaki | oh, I saw this change on gerrit, said something like 'write scripts for ansible' or something, this looks like that | 15:07 |
uzumaki | Let 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 |
uzumaki | thanks for letting me know! dwalt | 15:08 |
dwalt | sounds good. Thanks! | 15:09 |
uzumaki | alright i'm off now. thanks guys! \o | 15:09 |
openstackgerrit | diwakar thyagaraj proposed airship/maas master: [WIP]Enable Logs Output in Zuul for Deployment Scripts https://review.opendev.org/709763 | 15:12 |
*** pramchan has quit IRC | 15:13 | |
openstackgerrit | Ian Pittwood proposed airship/airshipctl master: [WIP][#19] Add validate schema command https://review.opendev.org/703864 | 15:34 |
*** uzumaki has quit IRC | 15:38 | |
*** KeithMnemonic has joined #airshipit | 15:38 | |
*** jtwill98 has left #airshipit | 15:40 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 15:45 |
*** thansen has quit IRC | 15:53 | |
*** thansen has joined #airshipit | 15:54 | |
*** segorov has quit IRC | 15:54 | |
*** segorov has joined #airshipit | 15:55 | |
*** segorov has quit IRC | 16:00 | |
*** AlexNoskov has joined #airshipit | 16:02 | |
*** ianychoi has quit IRC | 16:11 | |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors https://review.opendev.org/710845 | 16:12 |
*** ianychoi has joined #airshipit | 16:12 | |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors https://review.opendev.org/710845 | 16:16 |
openstackgerrit | eric welch proposed airship/deckhand master: attempting kubernetes cluster launch https://review.opendev.org/693935 | 16:28 |
*** rezroo has joined #airshipit | 16:41 | |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors https://review.opendev.org/710845 | 16:42 |
*** jamesgu has quit IRC | 16:43 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 16:44 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#38] Add end-user documentation to project https://review.opendev.org/711634 | 16:45 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#91] refactor secrets as top level command https://review.opendev.org/711684 | 16:45 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#88] add golang naming convention documentation https://review.opendev.org/711529 | 16:45 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#86] remove unused code https://review.opendev.org/711506 | 16:45 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Remove unnecessary kubectl subcommand https://review.opendev.org/710085 | 16:46 |
*** ianychoi has quit IRC | 16:47 | |
*** ianychoi has joined #airshipit | 16:48 | |
openstackgerrit | Merged airship/images master: Image tagging https://review.opendev.org/711999 | 16:57 |
*** mfuller has joined #airshipit | 17:02 | |
*** SRao has quit IRC | 17:02 | |
*** rpocase has joined #airshipit | 17:22 | |
rpocase | I'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 is | 17:24 |
rpocase | not a valid Git repo | 17:24 |
rpocase | I'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 file | 17:25 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors https://review.opendev.org/710845 | 17:25 |
*** ianychoi has quit IRC | 17:26 | |
*** ianychoi has joined #airshipit | 17:27 | |
*** evrardjp has quit IRC | 17:35 | |
*** evrardjp has joined #airshipit | 17:35 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 17:43 |
*** mfuller has quit IRC | 17:48 | |
rpocase | Figured 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 |
openstackgerrit | Ahmad Mahmoudi proposed airship/shipyard master: (fix) Address image build issues, bionic https://review.opendev.org/709056 | 18:06 |
openstackgerrit | Merged airship/airshipctl master: [#38] Add end-user documentation to project https://review.opendev.org/711634 | 18:08 |
*** ianychoi has quit IRC | 18:10 | |
*** ianychoi has joined #airshipit | 18:17 | |
openstackgerrit | Ian Pittwood proposed airship/airshipctl master: [WIP] Target test files only in git diff check https://review.opendev.org/712148 | 18:20 |
*** segorov has joined #airshipit | 18:20 | |
openstackgerrit | Andrew Schiefelbein proposed airship/airshipui master: Makefile plugin copy fix https://review.opendev.org/712150 | 18:23 |
*** mfuller has joined #airshipit | 18:32 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 18:36 |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 18:47 |
*** rpocase has quit IRC | 18:48 | |
*** diga has quit IRC | 18:49 | |
openstackgerrit | Stas Egorov proposed airship/airshipctl master: Use local registry for isogen builder https://review.opendev.org/712003 | 19:06 |
openstackgerrit | eric welch proposed airship/deckhand master: deleting extra comments https://review.opendev.org/693935 | 19:12 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#88] add golang naming convention documentation https://review.opendev.org/711529 | 19:14 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#91] refactor secrets as top level command https://review.opendev.org/711684 | 19:14 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#86] remove unused code https://review.opendev.org/711506 | 19:15 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Resolve kubectl gate errors https://review.opendev.org/710845 | 19:15 |
openstackgerrit | Alexander Hughes proposed airship/airshipctl master: [#70] Remove unnecessary kubectl subcommand https://review.opendev.org/710085 | 19:15 |
openstackgerrit | Stas Egorov proposed airship/airshipctl master: [WIP]: test only, DO NOT MERGE https://review.opendev.org/712160 | 19:20 |
*** mugsie has quit IRC | 19:23 | |
*** mugsie has joined #airshipit | 19:26 | |
openstackgerrit | eric welch proposed airship/deckhand master: WIP password rotation for deckhand https://review.opendev.org/712162 | 19:27 |
openstackgerrit | Sreejith Punnapuzha proposed airship/airshipctl master: [#106] Add docker install role https://review.opendev.org/711540 | 19:28 |
*** openstackgerrit has quit IRC | 19:32 | |
*** openstackgerrit has joined #airshipit | 19:41 | |
openstackgerrit | James Gu proposed airship/airshipctl master: Correct ansible task name for kubectl version https://review.opendev.org/712168 | 19:41 |
*** mfuller has quit IRC | 19:43 | |
*** timClicks has joined #airshipit | 20:02 | |
openstackgerrit | Stas Egorov proposed airship/airshipctl master: [WIP]: test only, DO NOT MERGE https://review.opendev.org/712160 | 20:09 |
*** ianychoi has quit IRC | 20:17 | |
*** ianychoi has joined #airshipit | 20:18 | |
*** openstackstatus has joined #airshipit | 20:18 | |
*** ChanServ sets mode: +v openstackstatus | 20:18 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 20:19 |
*** mfuller has joined #airshipit | 20:31 | |
*** mfuller has quit IRC | 20:35 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 20:48 |
openstackgerrit | Francis Bacon Yi proposed airship/airshipctl master: Target test files only in git diff check https://review.opendev.org/712148 | 20:54 |
openstackgerrit | Stas Egorov proposed airship/airshipctl master: Use 16GB flavor for gate job https://review.opendev.org/712160 | 21:02 |
openstackgerrit | Stas Egorov proposed airship/airshipctl master: Use 16GB flavor for gate job https://review.opendev.org/712160 | 21:43 |
openstackgerrit | Kostyantyn Kalynovskyi proposed airship/airshipctl master: Split document model, add entrypoints for repos https://review.opendev.org/711571 | 21:59 |
*** sreejithp has joined #airshipit | 21:59 | |
*** sreejithp has quit IRC | 22:02 | |
*** evrardjp has quit IRC | 22:17 | |
*** evrardjp has joined #airshipit | 22:18 | |
*** ianychoi has quit IRC | 22:19 | |
*** ianychoi has joined #airshipit | 22:20 | |
*** ab2434_ has quit IRC | 22:27 | |
*** evrardjp has quit IRC | 22:31 | |
*** evrardjp has joined #airshipit | 22:33 | |
*** dpawlik has quit IRC | 22:40 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 22:41 |
*** ianychoi has quit IRC | 22:41 | |
*** ianychoi has joined #airshipit | 22:42 | |
*** zogger has quit IRC | 22:43 | |
openstackgerrit | Ahmad Mahmoudi proposed airship/deckhand master: Replaced pip with pip3 https://review.opendev.org/711299 | 22:49 |
*** segorov has quit IRC | 22:57 | |
*** segorov has joined #airshipit | 22:59 | |
*** segorov has quit IRC | 23:08 | |
*** zogger has joined #airshipit | 23:08 | |
*** segorov has joined #airshipit | 23:10 | |
*** segorov has quit IRC | 23:16 | |
openstackgerrit | Kostyantyn Kalynovskyi proposed airship/airshipctl master: Fix dependency cycle of config and document pkg https://review.opendev.org/712205 | 23:19 |
openstackgerrit | Alan Meadows proposed airship/airshipctl master: [#45] iso generation pulls network data from ephemeral host https://review.opendev.org/708636 | 23:40 |
openstackgerrit | Kostyantyn Kalynovskyi proposed airship/airshipctl master: Fix dependency cycle of config and document pkg https://review.opendev.org/712205 | 23:43 |
*** dwalt has quit IRC | 23:52 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!