Tuesday, 2020-02-25

openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: scripts for local run playbooks  https://review.opendev.org/70963600:02
openstackgerritMatthew Fuller proposed airship/treasuremap master: Add support for modifying genesis kernel parameters for OVS-DPDK  https://review.opendev.org/70963800:02
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: scripts for local run playbooks  https://review.opendev.org/70963600:09
*** rezroo has quit IRC00:16
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: scripts for local run playbooks  https://review.opendev.org/70963600:22
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: scripts for local run playbooks  https://review.opendev.org/70963600:25
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: scripts for local run playbooks  https://review.opendev.org/70963600:26
openstackgerritStas Egorov proposed airship/airshipctl master: [WIP]: scripts for local run playbooks  https://review.opendev.org/70963600:29
*** jojensen has joined #airshipit00:35
*** jojensen has quit IRC00:37
*** jojensen has joined #airshipit00:38
*** jojensen has left #airshipit00:38
*** dwalt has quit IRC00:39
openstackgerritdiwakar thyagaraj proposed airship/maas master: Enable Docker default AppArmor profile to maas  https://review.opendev.org/70513600:44
*** nishantkr has quit IRC01:10
*** rezroo has joined #airshipit01:26
openstackgerritAhmad Mahmoudi proposed airship/drydock master: (fix) Address uwsgi segmentation fault issue  https://review.opendev.org/70933301:39
openstackgerritAhmad Mahmoudi proposed airship/drydock master: (fix) Address uwsgi segmentation fault issue  https://review.opendev.org/70933302:11
*** AlexNoskov has quit IRC02:12
openstackgerritAhmad Mahmoudi proposed airship/shipyard master: (fix) Address uwsgi fragmentation issue  https://review.opendev.org/70905602:21
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: (fix) Address uwsgi and other gating issues  https://review.opendev.org/70895802:25
*** siraj_ has quit IRC02:29
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [#20] Add abstraction to kubernetes interactions  https://review.opendev.org/70896303:34
*** clarkb has quit IRC03:45
*** clarkb has joined #airshipit03:45
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: (fix) Address uwsgi and other gating issues  https://review.opendev.org/70895805:18
*** evrardjp has quit IRC05:34
*** evrardjp has joined #airshipit05:35
*** jamesgu has quit IRC06:36
*** roman_g has quit IRC06:48
openstackgerritDmitry Ukov proposed airship/airshipctl master: Refactor document Bundle interface  https://review.opendev.org/70813207:09
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: (fix) Address uwsgi and other gating issues  https://review.opendev.org/70895807:15
openstackgerritNikolay Fedorov proposed airship/airshipctl master: [WIP] Add Bare Metal Operator Ironic entrypoints  https://review.opendev.org/70673707:20
openstackgerritNikolay Fedorov proposed airship/airshipctl master: [WIP] Add Metal3 - Bare metal host provisioning  https://review.opendev.org/70865407:23
*** dpawlik has joined #airshipit07:26
*** pgaxatte has joined #airshipit07:47
*** rezroo has quit IRC08:16
*** ansumanbebarta has joined #airshipit10:40
openstackgerritDmitry Ukov proposed airship/airshipctl master: [#45] Add support for network_data.json  https://review.opendev.org/70863610:41
*** roman_g has joined #airshipit12:25
*** nishantkr has joined #airshipit13:36
*** Connoreika has joined #airshipit13:41
ConnoreikaHello!13:43
ConnoreikaI'm having some troubles with deployment of airsloop. Can anyone help me with it?13:44
ConnoreikaFirst of all, when deploying genesis node, genesis.sh didnt finishing. Is it normal?13:45
ConnoreikaSecond thing is after deploying genesis node, there is Deploy site step in docs, but it failing at start with error "The request you have made requires authentication"13:47
ConnoreikaI figured out that i need to set os_auth_url, but i don't know what it should be.13:48
ConnoreikaIn docs(authoring) it says https://iam-sw.DOMAIN:443/v3 but what is domain? Should it be in /etc/hosts?13:51
*** aaronsheffield has joined #airshipit14:00
*** SRao has joined #airshipit14:03
*** zogger has joined #airshipit14:08
ConnoreikaIf i creating in /etc/hosts entry, with ip of genesis node and name iam-sw domain that i said to create in networks.yml and common-addresses.yaml, shipyard create configdocs failin with error "certificate verify failed"14:17
ConnoreikaAny ideas what I'm doing wrong?14:18
*** ab2434_ has joined #airshipit14:37
*** dwalt has joined #airshipit14:52
*** souradage has joined #airshipit14:54
alexanderhughesagenda for meeting (5 minutes from now) https://etherpad.openstack.org/p/airship-meeting-2020-02-2514:55
*** michael-beaver has joined #airshipit14:57
*** Connoreika has quit IRC14:58
*** sanjib has joined #airshipit15:00
dwalt#startmeeting airship15:01
openstackMeeting started Tue Feb 25 15:01:39 2020 UTC and is due to finish in 60 minutes.  The chair is dwalt. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: airship)"15:01
openstackThe meeting name has been set to 'airship'15:01
dwaltHello all!15:01
dwalt#link https://etherpad.openstack.org/p/airship-meeting-2020-02-2515:01
mattmceueno/15:02
souradageo/15:02
dwaltAgenda is above. The weekly design call is ongoing, so I suspect that most still have their attention over there15:02
ian-pittwoodo/15:02
michael-beavero/15:02
*** ashferg has joined #airshipit15:03
*** Connoreika has joined #airshipit15:04
aaronsheffieldo/15:04
*** diga_ has joined #airshipit15:04
diga_Hi15:04
ConnoreikaHi15:05
alexanderhugheso/15:05
howello/15:05
ConnoreikaAny help on my question?15:05
diga_are we having meeting today ?15:05
dwalto/ diga_ Connoreika15:05
*** sreejithp has joined #airshipit15:05
*** sreejithp has quit IRC15:05
mattmceuenYeah, meeting starting now15:05
dwaltWe're just getting started!15:05
dwaltFolks are filtering in from the design call15:05
mattmceuenSorry Connoreika, missed your question - can you please reask?15:05
ConnoreikaAfter meeting then.15:06
*** uzumaki has joined #airshipit15:06
*** kkalina has joined #airshipit15:06
mattmceuensure thing, we usually have roundtable discussion at the end as well, you're welcome to ask there too15:06
dwaltAnyway, let's go ahead and start15:06
dwalt#topic KubeCon Amsterdam Meetup15:06
*** openstack changes topic to "KubeCon Amsterdam Meetup (Meeting topic: airship)"15:06
mattmceuenthat's mine15:07
dwaltall yours mattmceuen15:07
diga_#topic I wants to discuss about https://github.com/airshipit/airshipctl/issues/6415:07
mattmceuenSo I sent out an email on the ML on this topic this morning15:07
dwaltI'll add that to our agenda diga_ :)15:07
diga_Thank you!15:07
mattmceuenThe gist is that we're planning on hosting an Airship Meetup again at KubeCon in Amsterdam15:07
jemangso/15:07
mattmceuenSo if you're at KubeCon, you are welcomed and encouraged to attend!15:08
uzumakio/15:08
mattmceuenI want to give it a bit more time this time, the majority of a day, to allow breathing room and deep dive discussion on work that's going on15:08
mattmceuenI proposed a couple of days in there, so if you're planning on attending KubeCon, please take a look and give it some thought15:09
mattmceuenThat's really all I had to bring up on this in the meeting, though.  Any questions?15:09
mattmceuenok then we can move on drew!15:10
uzumakican somebody share the agenda etherpad link?15:10
dwaltUzumaki: https://etherpad.openstack.org/p/airship-meeting-2020-02-2515:10
dwaltmattmceuen: thanks!15:10
dwaltthe next one is also yours15:10
uzumakidwalt, thanks!15:10
dwalt#topic Slack15:10
*** openstack changes topic to "Slack (Meeting topic: airship)"15:10
mattmceuenThanks15:11
mattmceuenThis is just to drop the idea in you guys' ears15:11
mattmceuenone sec15:12
mattmceuenOk I'm back15:12
roman_gI'm fine with IRC. Anyhow there is not much activity.15:12
*** Connoreika has quit IRC15:12
mattmceuenWe have a number of new team members joining Airship 2 development15:13
mattmceuenFrom different companies15:13
mattmceuenso I thin IRC and/or Slack as a communication tool will spike in value here shortly15:13
uzumakiYes, it's very convenient15:13
souradageWhat was the driving factor to use IRC over like Slack in the first place?15:13
mattmceuenI'm interested in exploring IRC/Slack integration again; we had this a couple years ago, but have not used it since15:13
mattmceuenThat would allow folks to choose whichever client they prefer, but the sync'ing would need to be rock solid (this was a problem before)15:14
*** Connoreika has joined #airshipit15:14
roman_gSlack becomes paid at some moment of time, you know.15:14
mattmceuenMany people have weighed in that they prefer Slack15:14
*** jamesgu has joined #airshipit15:14
mattmceuenSlack is free unless you choose to pay for it15:14
uzumakilol15:14
ConnoreikaMb discord? Same but free, and good voice15:15
alexanderhughesas long as there is integration I don't think it matters - but I would encourage everyone to continue their IRC as that's the platform the other projects use that we integrate with15:15
mattmceuenIRC is the standard in the OSF world, and it puts us right next to our OpenStack collaborators15:15
mattmceuenThe opinions above are exactly why I'm interested in mirroring back and forth from Slack<->IRC15:15
uzumakiI'm fine with IRC. It's easy and convenient and simple15:15
mattmceuenwhen it works it works well15:15
mattmceuenand we have vastly different preferences15:16
mattmceuenand value to both15:16
mattmceuenAnyway, I didn't bring it up to make a decision today, just to gather more opinions, and let y'all know that I'm investigating the state-of-the-integration15:16
uzumakiokay15:16
mattmceuenWill report back with findings hopefully next week -- please think about the pros/cons/etc in the meantime!15:16
mattmceuenThat's all from me dwalt15:17
dwaltthanks mattmceuen15:17
dwaltlet's keep things moving15:17
alexanderhugheson a related note, might be a good opportunity to add to wiki the IRC links to our collaborative projects15:17
alexanderhughesmetal3 etc15:17
dwalt#topic https://github.com/airshipit/airshipctl/issues/6415:17
*** openstack changes topic to "https://github.com/airshipit/airshipctl/issues/64 (Meeting topic: airship)"15:17
roman_gmattermost has been researchd as an alternative to slack, mattmceuen15:17
diga_Hey15:17
dwalthey diga_15:17
diga_I request everyone to go through the issue once15:18
diga_This is regarding JIRA AIR 79 the Expected HArdware Configuration15:18
mattmceuenroman_g Connoreika:  I'll take a look at mattermost and discord, thanks :)15:18
diga_There are two part of this work15:18
diga_1. South Bound - Metal315:18
diga_2. Airship - We have to introduce mechnism at Airship level to adopt this feature15:19
mattmceuenThat's great diga_, thanks15:20
diga_We already had discussion with MEtal3 community and came to conclusion that instead of implementing in BMO, let's have seperate CRD called Hardware-Classification-Controller15:20
diga_Already base framework is merged15:20
mattmceuenYeah, I see there's a lot of discussion/work in the corresponding Metal3 issue15:20
diga_We are testing some code, by Friday we are submitting two PR's to this repo15:20
diga_Yeah mattmceuen15:20
diga_I would like to understand where is the right place in Airshipctl for this mechnism to implement15:21
mattmceuenSo the good news is that I think the change is "mostly" transparent from an Airship perspective.  Here's why:15:22
mattmceuenAirship is already going to need to invoke ClusterAPI -> Metal3 to accomplish BM provisioning,15:22
mattmceuenand your M3 change lives 100% so far in Metal3, so I think airship simply benefits from it being there15:23
mattmceuenthere are a couple things I can think of that airship will need to take into account:15:23
mattmceuen1. making sure the BMO documents are populated with expected hardware info15:23
mattmceuen2. good error handling when the expected hardware doesn't match the real hardware15:23
mattmceuencan you think of anything additional?15:23
diga_Yeah15:24
diga_We can also think of other classification filters like GPU, NFV params where we can filter the hosts accordingly15:24
diga_Do we have any standard labels for use by our HCC (Hardware-Classification-Controller)15:25
alexanderhughesI think this is a topic that would benefit from the flight plan call to groom this and think through implications and followup work that needs to occur15:25
alexanderhughes#link https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Management_Meetings15:25
*** SRao has quit IRC15:25
diga_okay15:25
diga_Thank you, Will attend it15:25
*** SRao has joined #airshipit15:26
dwaltthis may also be a relevant issue on airshipctl15:26
dwalt#link https://github.com/airshipit/airshipctl/issues/2915:26
dwaltto take advantage of the work being done in ClusterAPI15:26
diga_I think Hardware-Classification-Controller will play big role in classifying hosts. That way, we can select right host for provisioning also15:26
diga_and we can do entire lifecycle management easy15:27
*** irclogbot_1 has quit IRC15:27
*** irclogbot_1 has joined #airshipit15:27
mattmceuendiga_:  what kinds of labels are you thinking of?15:28
mattmceuenToday we label hosts dynamically based on declared intent, for things like "this is an openstack control plane host" or "this is a compute host" etc etc15:29
mattmceuenbut that's actually labelling the k8s node, not the host15:29
diga_Yes15:29
diga_Currently we are following the same, we are adding Hardware profile labels to host CR15:30
mattmceuenSo I don't think we have any standards yet15:30
mattmceuenCool15:30
diga_ohh15:30
diga_:)15:30
mattmceuenWell let me clarify :)15:30
diga_Sure15:30
mattmceuenIdeally we'd keep it flexible and data-driven. I can find some similar labelling done in Airship 1 for you, let me find it real quick15:30
diga_okay.15:31
mattmceuenhttps://opendev.org/airship/treasuremap/src/branch/master/global/profiles/host/cp.yaml#L57-L11615:32
diga_let me take a loot at it15:32
*** souradage has quit IRC15:33
mattmceuenthat's defining the labels for the host, and then the different helm chart-deployed software running on top of the cluster is targeted at hosts with particular labels15:33
mattmceuenhost->node :D15:33
*** jamesgu has quit IRC15:33
diga_Okay15:33
*** jamesgu has joined #airshipit15:34
diga_Then we are on right track because we are adding profile label to the host15:34
dwaltthanks for the links mattmceuen15:34
diga_Do we need to introduce another label in this file for BM and Hardware profiles ?15:34
mattmceuendiga_ -- I'll try to catch up on those two issues and have a better idea going forward15:34
diga_https://www.irccloud.com/pastebin/IhFC9Kc8/15:34
diga_Because only relative stuff I found is above15:34
diga_Sure mattmceuen15:35
mattmceuenThat whole file will be basically replaced by a similar file (different schema) in Airship 215:35
mattmceuenAnd the new file doesn't really exist yet15:35
diga_mattmceuen Can we discuss this feature in next design meeting ?15:35
mattmceuenYup I think that would be a good idea -- can you add it to the agenda here?   https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions15:36
diga_Sure mattmceuen15:36
dwaltgreat. Anything else on this one?15:36
diga_I will add there15:36
dwalt#topic metal3 + Airship 215:36
*** openstack changes topic to "metal3 + Airship 2 (Meeting topic: airship)"15:37
diga_Thanks mattmceuen, it was nice talking to you :)15:37
mattmceuenSame diga_ :)15:37
dwaltuzumaki: all yours15:37
uzumakidwalt, thanks!15:37
uzumakiSo, I just have a few quick question I guess. 1- where are things regarding merging metal3 in Airship 2.0?15:37
mattmceuenSo we're migrating to github issues uzumaki - we don't have everything in place quite yet,15:38
mattmceuenbut we're adding items quickly and as needed15:39
mattmceuenThis might be a good one for that15:39
mattmceuenThe Airship 2.0 work will mostly be two things in this area:15:39
mattmceuen1. integrating with Cluster API (work in progress)15:39
uzumakiSure, I can add an issue to airshipctl repo to keep this going.15:39
mattmceuen(since cluster will drive metal3)15:40
mattmceuenand 2.  configuring the bare metal crds appropriately15:40
mattmceuenthat sounds good to me uzumaki15:40
mattmceuenand then we can review it in the flight plan call15:40
dwalt++15:40
uzumakiyes, that'll be good15:40
mattmceuendwalt:  we're currently putting issues against specific projects, and then pulling them all into the Airship 2 board for display, right?15:41
mattmceuen(just wanted to make sure airshipctl is the right place to create the issue)15:41
dwaltmattmceuen: that's correct15:41
dwalt#link https://github.com/orgs/airshipit/projects/115:41
dwaltAbove is the board. Once an issue is created, a core just adds it15:41
dwaltAnd then we assign further labels in the flight plan call15:42
mattmceuenok, great thanks15:42
dwaltsure15:42
uzumakiSo, it's safe to put the issue in airshipctl repo?15:42
dwaltuzumaki: I think that makes the most sense15:42
uzumakigreat15:42
dwaltalrighty, moving along15:42
dwalt#topic Amsterdam Update15:43
*** openstack changes topic to "Amsterdam Update (Meeting topic: airship)"15:43
mattmceuenHello15:43
mattmceuenIt's me again15:43
dwaltmattmceuen: all yours again15:43
mattmceuenSo I wanted to add an addendum around the Meetup in Amsterdam15:43
mattmceuenword of caution:  with the spread of the coronavirus, there's a lot up in the air15:43
mattmceuenaround whether the conference will still happen (LSF is still planning on it as of yesterday), and whether collaborating companies will allow folks to attend15:44
mattmceuenSo I would just suggest, if you haven't already booked travel, please don't do it now just for Airship15:44
mattmceuenIf for some reason things go sideways, we'll find some other means to have a Meetup instead15:45
mattmceuen(since it's the thing I am most looking forward to at kubecon!)15:45
mattmceuenAlright that's all from me dwalt15:45
uzumakione quick question15:46
mattmceuensure15:46
dwaltthanks mattmceuen15:46
jemangs(re: KubeCon, Ericsson have today until further notice suspended all non-essential international business travel)15:46
uzumakiWhere are some areas I can start contributing into, regarding metal3 in Airship2.0? I can see the YAML part of things, which I'm looking at, trying to get upto speed. what else?15:46
mattmceuenThe first thing I'd suggest is to get looped in on the zuul CI stuff that's being set up to stand up a dev/test environment15:48
mattmceuenLet me find a link or two:15:48
uzumakithat'll be great15:48
mattmceuenhttps://review.opendev.org/#/c/708654/15:49
mattmceuenhttps://review.opendev.org/#/c/693238/15:49
mattmceuenwe haven't made it too deep into the metal3 provisioning yet (focusing first on getting redfish-based provisioning of the ephemeral node, which will actually run metal3)15:50
uzumakioh, I see15:50
mattmceuenSo if you take a peek at those works-in-progress then come to the flight plan call and see what you can volunteer for (or ask be created in github issues) I think that's a good plan15:50
uzumakiyeah that sounds good. Another thing, if I want to setup a dev environment for airshipctl, on my laptop, quickest way to do that?15:51
mattmceuenWe're adding CI jobs to airshipctl now just for the sake of speed; we'll move them all to the zuul jobs repo after they're in good shape15:51
mattmceuenShould be the same set of zuul jobs :)  it's actually just ansible + shell scripts that mostly can be run in your own vm the same way as is done by zuul15:52
mattmceuenOr at least that's the intent15:52
mattmceuenmay still be some rough edges :)15:52
uzumakiwell, rough edges are fine, as long as something's setup for convenience :D15:52
mattmceuenyup!  and every rough edge is something we want to smooth down!15:53
uzumakiwe do, indeed.15:53
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323815:53
uzumakiwhat about the other question, quickly setting up a dev env for airchipctl?15:53
mattmceuenthe goal is it to be the same set of ansible, really15:53
mattmceuenthat goes through the steps of building, installing, running the various stages of the deployment process15:54
mattmceuenany other ideas from airshipctl devs?15:54
dwaltIn addition to the playbooks, this should help get you started15:54
dwalt#link https://github.com/airshipit/airshipctl/blob/master/docs/source/developers.md15:54
uzumakiAnd how does gerrit review tie in, with all of this contribution process?15:55
dwaltIf you find anything along the way that would be helpful to add, please don't hesitate to do so!15:55
uzumakithanks, dwalt15:55
openstackgerritdiwakar thyagaraj proposed airship/divingbell master: [FIX] Enable DivingBell Gate Job  https://review.opendev.org/70976115:55
dwaltuzumaki: yep, we still use gerrit15:55
mattmceuengerrit is the review process / repo for the projects in the airship namespace15:56
mattmceuen(like airshipctl)15:56
dwalt#link https://review.opendev.org/#/q/project:airship/airshipctl15:56
mattmceuenThey get mirrored over to github whenever there's a merge15:56
mattmceuenSo the github issues point at the github "copy" of the code15:56
uzumakiSo github is the main upstream, and the opendev repo's are the 'waiting list' until reviewed and tested?15:56
mattmceuenYep that's a good way of looking at it.  The repos in open infra world also have a nice github-like UI, so you can really browse the code either place:  e.g.15:57
mattmceuenhttps://opendev.org/airship/airshipctl15:57
mattmceuenwhich UI etc you use is just up to personal preference15:58
dwaltSorry to interject, but we are almost out of time. Is there anything else pressing before we close? We can also take these questions offline and continue discussing.15:58
mattmceuensure sounds good to me15:58
dwaltGreat, thanks for coming all! Have a good day.15:59
dwalt#endmeeting15:59
*** 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:59
openstackMeeting ended Tue Feb 25 15:59:11 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-02-25-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-02-25-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-02-25-15.01.log.html15:59
alexanderhughesthanks all15:59
uzumakithanks guys! it's been very helpful15:59
openstackgerritdiwakar thyagaraj proposed airship/divingbell master: [WIP][FIX] Enable DivingBell apparmor  https://review.opendev.org/70976116:00
mattmceuenthanks everyone16:00
dwalthey uzumaki: did we clear up the GitHub/gerrit differences?16:01
openstackgerritdiwakar thyagaraj proposed airship/maas master: [WIP] Enable Logs  Append for maas  https://review.opendev.org/70976316:01
uzumakiyeah. I'm just curious as to a typical workflow process of gerrit. Each changes/patchsets need to be created manually?16:02
*** pgaxatte has quit IRC16:04
clarkbuzumaki: they are created by the git-review tool (which essnetially does a push to the gerrit server)16:06
clarkbuzumaki: in that way it is manual (you run the git review command), but the underlying details are largely ignored by the user. You edit git locally and then git review reflects that in gerrit16:07
uzumakiI see. That makes it very clear. Thanks clark! I've got a lot of groundwork to cover.16:07
dwaltuzumaki: let us know if you think of any more questions along the way!16:08
uzumakiWill do. Thanks a lot! :)16:09
*** ansumanbebarta has quit IRC16:22
openstackgerritSean Eagan proposed airship/armada master: Add apply_chart entrypoint  https://review.opendev.org/69772816:23
openstackgerritSean Eagan proposed airship/armada master: [WIP] Add chart CRD and associated reference resolver  https://review.opendev.org/70696716:24
openstackgerritSean Eagan proposed airship/armada master: [WIP] Add chart CRD and associated reference resolver  https://review.opendev.org/70696716:26
*** kkalina has quit IRC16:31
*** uzumaki has quit IRC16:36
*** SRao has quit IRC16:38
*** jojensen has joined #airshipit17:10
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963617:15
*** siraj_ has joined #airshipit17:20
*** evrardjp has quit IRC17:39
*** evrardjp has joined #airshipit17:39
openstackgerritDrew Walters proposed airship/docs master: Update docs theme  https://review.opendev.org/70980417:47
openstackgerritDrew Walters proposed airship/docs master: Update docs theme  https://review.opendev.org/70980418:00
*** sanjib has quit IRC18:03
openstackgerritDrew Walters proposed airship/docs master: Update docs theme  https://review.opendev.org/70980418:06
openstackgerritDrew Walters proposed airship/airshipctl master: [#59] Publish airshipctl docs to RTD  https://review.opendev.org/70894118:14
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: (fix) Address uwsgi and other gating issues  https://review.opendev.org/70895818:21
openstackgerritDrew Walters proposed airship/docs master: Update docs theme  https://review.opendev.org/70980418:21
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [#20] Add abstraction to kubernetes interactions  https://review.opendev.org/70896318:21
*** michael-beaver has quit IRC18:27
*** Connoreika has quit IRC18:29
openstackgerritDrew Walters proposed airship/docs master: Update docs theme  https://review.opendev.org/70980418:37
*** diga_ has quit IRC18:43
openstackgerritDrew Walters proposed airship/docs master: Update docs theme  https://review.opendev.org/70980418:50
openstackgerritJagan Mohan Kavva proposed airship/maas master: Enable Docker default AppArmor profile to maas  https://review.opendev.org/70513618:59
openstackgerritJagan Mohan Kavva proposed airship/maas master: Enable Docker default AppArmor profile to maas  https://review.opendev.org/70513619:06
openstackgerritDrew Walters proposed airship/docs master: Add Airship logo to docs  https://review.opendev.org/70981919:19
openstackgerritDrew Walters proposed airship/airshipctl master: [#59] Publish airshipctl docs to RTD  https://review.opendev.org/70894119:25
openstackgerritDrew Walters proposed airship/airshipctl master: [#59] Publish airshipctl docs to RTD  https://review.opendev.org/70894119:30
openstackgerritDrew Walters proposed airship/airshipctl master: [#59] Publish airshipctl docs to RTD  https://review.opendev.org/70894119:35
openstackgerritPrateek Dodda proposed airship/shipyard master: Implement Security Context for Airflow_Worker  https://review.opendev.org/69222419:36
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963619:44
openstackgerritdiwakar thyagaraj proposed airship/maas master: Enable Docker default AppArmor profile to maas  https://review.opendev.org/70513619:45
openstackgerritDrew Walters proposed airship/docs master: Add Airship logo to docs  https://review.opendev.org/70981919:47
*** aaronsheffield has quit IRC20:00
openstackgerritMerged airship/airshipctl master: [#59] Publish airshipctl docs to RTD  https://review.opendev.org/70894120:08
openstackgerritPrateek Dodda proposed airship/divingbell master: [WIP] Implement Security Context for Divingbell  https://review.opendev.org/70788520:12
openstackgerritDrew Walters proposed airship/docs master: Add Airship logo to docs  https://review.opendev.org/70981920:18
openstackgerritDrew Walters proposed airship/airshipctl master: [#59] Fix docs publish job  https://review.opendev.org/70982820:30
openstackgerritMerged airship/airshipctl master: [#20] Add abstraction to kubernetes interactions  https://review.opendev.org/70896320:31
openstackgerritPrateek Dodda proposed airship/divingbell master: [WIP] Implement Security Context for Divingbell  https://review.opendev.org/70788520:39
openstackgerriteric welch proposed airship/deckhand master: deleting extra comments  https://review.opendev.org/69393520:52
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323820:52
openstackgerritPrateek Dodda proposed airship/divingbell master: [WIP] Implement Security Context for Divingbell  https://review.opendev.org/70788520:57
openstackgerritMerged airship/airshipctl master: [#59] Fix docs publish job  https://review.opendev.org/70982821:03
openstackgerritDrew Walters proposed airship/docs master: Restructure Documentation  https://review.opendev.org/70983921:16
openstackgerritDrew Walters proposed airship/docs master: Restructure Documentation  https://review.opendev.org/70983921:17
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963621:41
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963621:42
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323821:42
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963621:42
openstackgerritDrew Walters proposed airship/armada master: Added Yaml Linting  https://review.opendev.org/69286721:44
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add role to build ephemeral iso image  https://review.opendev.org/70587221:47
jamesgu@dwalt: is there instruction how to link gerrit review with github issue?21:48
openstackgerritDrew Walters proposed airship/deckhand master: deleting extra comments  https://review.opendev.org/69393521:50
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963621:53
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: (fix) Address uwsgi and other gating issues  https://review.opendev.org/70895822:02
*** kvenkata has joined #airshipit22:28
openstackgerritStas Egorov proposed airship/airshipctl master: [#32]: scripts for local run playbooks  https://review.opendev.org/70963622:30
dwalt jamesgu: not yet! We are still in the trial phase. For now, we just add the issue to the commit message in brackets (i.e. [#42] commit-message). You can also close the issue on merge by adding closes #42 to your commit message.22:38
jamesgudwalt: does it matter which line to add the issue id?22:39
dwaltnope. Just adding #issue-num should reference it on GitHub when it merges22:40
*** michael-beaver has joined #airshipit22:40
*** mattmceuen is now known as airshipbot22:43
*** airshipbot is now known as mattmceuen22:44
jamesgumattmceuen: good to know you are a bot :-)22:45
jamesguthanks dwalt22:45
dwaltmattmceuen: we're on to you22:52
dwaltjamesgu: np :)22:53
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323823:15
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add role to deploy ephemeral node  https://review.opendev.org/70587423:20
openstackgerritdiwakar thyagaraj proposed airship/maas master: Enable Docker default AppArmor profile to maas  https://review.opendev.org/70513623:23
openstackgerritdiwakar thyagaraj proposed airship/maas master: Enable Docker default AppArmor profile to maas  https://review.opendev.org/70513623:23
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323823:25
openstackgerritAhmad Mahmoudi proposed airship/deckhand master: (fix) Address uwsgi and other gating issues  https://review.opendev.org/70895823:27
*** ab2434_ has quit IRC23:29
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [#11] Implement selector kustomize primitive  https://review.opendev.org/70925223:31
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323823:42
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: [AIR-97] Adding initinfra subcommand  https://review.opendev.org/69323823:43
openstackgerritKostyantyn Kalynovskyi proposed airship/airshipctl master: Add role to deploy ephemeral node  https://review.opendev.org/70587423:51

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