Tuesday, 2019-10-29

openstackgerritPrateek Dodda proposed airship/treasuremap master: Integrate openstack utility container in airship/treasuremap  https://review.opendev.org/69173100:05
*** nishantkr has quit IRC00:11
*** jamesgu has quit IRC00:26
*** AlexNoskov has quit IRC01:35
*** dpawlik has joined #airshipit01:40
*** dpawlik has quit IRC01:45
*** segorov has joined #airshipit01:49
*** jamesgu has joined #airshipit01:58
*** SRao has joined #airshipit01:58
*** jamesgu has quit IRC02:04
*** jamesgu has joined #airshipit02:44
openstackgerritKaspars Skels proposed airship/treasuremap master: Add image overrides for all the charts  https://review.opendev.org/69104203:14
openstackgerritPhil Sphicas proposed airship/porthole master: Add xenial-based calicoctl-utility containers  https://review.opendev.org/69149705:05
openstackgerritPrateek Dodda proposed airship/treasuremap master: Integrate openstack utility container in airship/treasuremap  https://review.opendev.org/69173105:13
openstackgerritPrateek Dodda proposed airship/treasuremap master: Integrate openstack utility container in airship/treasuremap  https://review.opendev.org/69173105:16
*** kevinz has joined #airshipit05:58
*** kevinz has quit IRC05:58
openstackgerritRahul Khiyani proposed airship/treasuremap master: Integrate ceph utility container in airship/treasuremap  https://review.opendev.org/68113505:59
openstackgerritRahul Khiyani proposed airship/treasuremap master: Integrate ceph utility container in airship/treasuremap  https://review.opendev.org/68113506:01
*** jamesgu has quit IRC06:04
*** dpawlik has joined #airshipit06:30
*** st4nson_ has joined #airshipit07:43
*** kskels has quit IRC07:47
*** pgaxatte has joined #airshipit07:52
*** JaredSchooley has quit IRC07:56
*** JaredSchooley has joined #airshipit07:58
st4nson_Hi all, got a quick question. Will armada be a default way to deploy OpenStack components in airship 2.0 ?08:04
*** JaredSchooley has quit IRC08:49
*** JaredSchooley has joined #airshipit08:50
openstackgerritSmruti Soumitra Khuntia proposed airship/treasuremap master: Disable TaintBasedEviction feature gate for kubernetes-apiserver  https://review.opendev.org/68886309:50
openstackgerritDmitry Ukov proposed airship/airshipctl master: [AIR-137] Add logic to isogen subcommand  https://review.opendev.org/67585109:55
openstackgerritDmitry Ukov proposed airship/airshipctl master: [AIR-145] Generate cloud init settings  https://review.opendev.org/67956309:55
openstackgerritDmitry Ukov proposed airship/airshipctl master: [AIR-137] Add ISO builder artifacts check  https://review.opendev.org/68836909:55
*** JaredSchooley has quit IRC10:31
*** JaredSchooley has joined #airshipit10:33
*** JaredSchooley has quit IRC10:55
*** JaredSchooley has joined #airshipit10:56
*** ianychoi__ is now known as ianychoi11:24
*** pgaxatte has quit IRC11:38
openstackgerritDoug Aaser proposed airship/promenade master: Migrate config to KubeletConfiguration  https://review.opendev.org/68792711:47
openstackgerritkanwar saad bin liaqat proposed airship/airshipctl master: Bootstrap redfish Remote direct  https://review.opendev.org/68316512:21
*** alexanderhughes has joined #airshipit12:23
*** dpawlik has quit IRC12:27
*** bh526r has joined #airshipit12:50
*** dpawlik has joined #airshipit13:04
*** kskels has joined #airshipit13:20
openstackgerritSteve Wilkerson proposed airship/airshipctl master: Update references to 'kubernetes' to proper name  https://review.opendev.org/69186013:31
*** michael-beaver has joined #airshipit13:35
*** ab2434_ has joined #airshipit13:36
mattmceuenhey st4nson_ -- definitely -- from a workload perspective (e.g. OpenStack-Helm) there are aren't big changes with Airship 2.0.  They'll still be helm charts, and Armada will deploy those helm charts.  There may be some changes to exactly how Armada does that (e.g. leveraging Argo workflows to handle parallelism, sequencing, etc) but that will be an evolution of Armada rather than  a different approach13:36
*** dukov has joined #airshipit13:36
mattmceuen@seaneagan was planning on leading some discussion around Armada plans for Airship 2.0 in this Thursday's Airship design call, if you'd like to join!13:41
*** pgaxatte has joined #airshipit13:47
*** LoicL35 has joined #airshipit13:48
*** ian-pittwood has joined #airshipit13:49
mattmceuenour team meeting is in 10 minutes -- please add anything to the agenda that you'd like to discuss today:  https://etherpad.openstack.org/p/airship-meeting-2019-10-2913:50
*** shubham_kaushal has joined #airshipit13:54
*** nishantkr has joined #airshipit13:56
openstackgerritIan Howell proposed airship/airshipctl master: This updates the current unit tests for testify  https://review.opendev.org/68905113:58
*** pramchan has joined #airshipit13:59
mattmceuen#startmeeting airship14:00
openstackMeeting started Tue Oct 29 14:00:26 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: airship)"14:00
openstackThe meeting name has been set to 'airship'14:00
mattmceuen#topic Rollcall14:00
*** openstack changes topic to "Rollcall (Meeting topic: airship)"14:00
dwalto/14:00
michael-beavero/14:00
pramchano/14:00
mattmceuenhttps://etherpad.openstack.org/p/airship-meeting-2019-10-2914:00
alexanderhugheso/14:01
mattmceuenplease add anything to discuss to today's agenda^ -- we'll give it a minute or two14:01
*** roman_g has joined #airshipit14:01
* ildikov is lurking14:01
nishantkro/14:01
roman_go/14:01
ian-pittwoodo/14:01
kskelso/14:02
seaneagano/14:02
mattmceuenok let's get started14:02
mattmceuen#topic Enforcement of 2x CR +2 before allowing WF +114:02
*** openstack changes topic to "Enforcement of 2x CR +2 before allowing WF +1 (Meeting topic: airship)"14:02
mattmceuenroman_g - this one's yours, take it away14:02
dukovo/14:02
mattmceuenGM / GE all :)14:03
roman_gAh.14:03
pramchanIs anyone reviewing https://review.opendev.org/#/c/683165/27 to give +2 for this ?14:03
roman_gYes. So it's all written in etherpad.14:03
pramchanthamks14:04
mattmceuenpramchan:  want to add that one to the Review Request part of the agenda14:04
roman_gDo we want to enforce rule of 2x WF+2 from cores?14:04
mattmceuenI have an opinion on this14:04
mattmceuenI prefer documenting and communicating our convention about 2x WF+214:04
kskelsI kind a feel that our current ways of working with "soft" enforcement/awareness has been working great14:05
mattmceuenWe haven't done a good job of documenting core responsibilities / role in general, so far we have mostly relied on "do it like openstack does it"14:05
roman_gWe have had changes being merged without this rule followed.14:05
mattmceuenIf we do a good job of documenting/communicating/following our "convention", then the ability to 1x WF+2  a patch -- in case of some emergency -- will come in handy occasionally14:05
mattmceuenAgree roman_g14:06
pramchanwhat does 2x WF_2 mean , you mean two 2_ fro code review for approval?14:06
*** shubham_kaushal_ has joined #airshipit14:06
mattmceuenI followed up on that, and it was due to miscommunication / misunderstanding14:06
roman_gpramchan yes, that's what I mean14:06
pramchanok  thanks14:06
mattmceuenExcept in one case -- me :) -- where I fully documented they "why" of a single-+2 in the patchset14:06
ian-pittwoodDo we check if they're non-author +2's already as well?14:06
mattmceuenThat's definitely a convention ian-pittwood, I don't think it's enforced programmatically14:07
mattmceuenafaik14:07
alexanderhughesit's not but I think it's a convention that gets bent from time to time.  especially on projects with low activity like spyglass/pegleg14:07
alexanderhugheswith only a handful of cores, when the stars align and 2 of them are out for a day a patchset just isn't going to move14:08
ian-pittwoodYeah I know that14:08
ian-pittwoodI just don't like that we can or have to approve our own material14:08
mattmceuenI definitely think that, if we document a convention and allow "break glass in case of emergency" exception to that rule, it should be required that the reviewer add in strong justification into the patchset14:08
alexanderhughes+114:08
portdirect++14:08
mattmceuenand that if the justification is missing, or anyone disagrees with it, we discuss it in the open14:08
ian-pittwoodSure, that works14:09
portdirectThis is the way every openstack project has done it14:09
mattmceuenroman_g:  do you think that is sufficient?14:09
ian-pittwoodWF seems like it should definitely be non-author though14:09
portdirectWf with two plus two's can be author14:09
roman_gOK. So we leave it as-is, and teach those who break rules w/o reason14:09
roman_gmattmceuen, yes, sufficient14:09
mattmceuenYes.  dukov shared the openstack-ansible core guidelines as a good example, I think we could start with those and enhance a bit -- dukov, can you please share them here?14:10
howellthis is probably not doable, but can Zuul post customized comments in response to things like this?14:10
mattmceuenthat's beyond my zuul brainpower howell :D  good question14:10
portdirectIf we need to correct Elmore than once, we should ask if that person should be a core roman_g14:10
roman_ghowell Zuul? Which comments?14:10
portdirectElmore/more14:11
roman_gportdirect yes, I think it wan not once14:11
*** jamesgu has joined #airshipit14:11
mattmceuen+1 portdirect.  Cores must live with the consequences of their actions and take it seriously.14:11
portdirectPrecisely14:11
roman_g*it was not once14:11
kskels+114:11
kskels(also good to hear from you Pete!)14:12
* portdirect waves at kskels 14:12
mattmceuenAlright, I think we have a consensus, speak now or forever hold your peace if not :)14:12
mattmceuenJust two final thoughts from me:14:12
mattmceuenJust to be clear:  the norm, 99.99% of the time is, two non-author +2's and a WF is required to merge a patchset14:13
mattmceuenAnd, we need to document some core reviewer guidelines very soon14:13
michael-beaver+1, I definitely agree with the informal 2x +2, especially if we document it14:13
mattmceuenthank you for bringing this up roman_g14:14
kskelscan a WF be done by the author?14:14
kskelsand only 2x +2 is needed?14:14
portdirectIn openstack, yes14:14
mattmceuenI think that makes sense as well14:14
portdirectI'd advise that path here14:14
portdirect(Again ref cores responsibility)14:14
*** sreejithp has joined #airshipit14:15
mattmceuenok - moving on!14:15
mattmceuen#topic Collaboration between Edge Working Group and Airship at Ussuri PTG or KubeCon14:16
*** openstack changes topic to "Collaboration between Edge Working Group and Airship at Ussuri PTG or KubeCon (Meeting topic: airship)"14:16
mattmceuendwalt this one is yours I believe14:16
dwalto/ ildikov!14:16
ildikovthe OpenStack Project Team Guide has a chapter on reviewing as well: https://docs.openstack.org/project-team-guide/review-the-openstack-way.html14:16
ildikovsorry, just jumped off of my other meeting :)14:16
ildikovhi :)14:16
dwaltno worries :)14:16
dwaltfloor is yours, if you'd like to speak14:17
ildikovso the OSF Edge Computing Group is having a full day on Friday at the PTG and we are looking into cross-project sessions14:17
*** SRao has quit IRC14:18
ildikovwe have a few projects identified that people see relevant or are interested in, etc and Airship is one of these14:18
mattmceuenoh awesome14:18
ildikovI know that edge is not the primary target for the project, but it's still a relevant area so I wanted to ask if people who will be in Shanghai from the team would be interested in joint dicussions?14:18
* mattmceuen thanks for sharing the openstack review guide as well ildikov :)14:18
pramchanWe have our PTG sessions for Airship on Thu + Friday, will see how we can co-ordinate14:18
ildikovthis is our PTG etherpad: https://etherpad.openstack.org/p/PVG-ECG-PTG14:19
dukovmattmceuen: https://docs.openstack.org/openstack-ansible/latest/contributor/core-reviewers.html14:19
ildikova bit more chaotic than I would prefer, but cross-project sessions are harder to schedule :)14:19
pramchanMay be one of us can visit and speak on Airship as how it can be relevant to edge14:19
ildikovmattmceuen: np :)14:19
pramchanSame way you can come to Airship and speak how Aieship is relevant to edge14:20
mattmceuenyeah agree w/ pramchan -- if one of our Airship cores who is present at the PTG can peel off to meet with the edge group (looks like it might be Friday afternoonish) that would be valuable14:20
ildikovI'm more on the side at this point that it comes up in discussions or people ask what's the difference between Airship and StarlingX, etc14:20
ildikovso I think it would be great to share some thoughts about it14:21
ildikovFriday afternoon should work14:21
mattmceuenFor sure.  Would you be able to come fetch someone from the AIrship PTG room when it's about time for that?14:21
pramchanOK let me add my 15 minutes pitch on Friday to edge etherpad14:21
mattmceuenThe same folks will also be leading the PTG so I think someone would just step out to join the edge session, if that's possible14:22
ildikovmattmceuen: I can pop by after lunch to coordinate. Would that work?14:22
pramchansure14:23
pramchanmatt let's do that14:23
mattmceuenildikov:  that's perfect14:23
mattmceuenthanks for making the connection14:23
ildikovI will also be in San Diego for KubeCon and some of the working group members will also, so we could target your gathering there as well, but I know it's limited time and space so I thought the PTG in Shanghai might be better14:24
ildikovmattmceuen: awesome, we have a plan! :)14:24
ildikovsure, looking forward to our chats and working together14:24
mattmceuenyeah, I think that makes sense.  At KubeCon we're planning on "continuing" any needed discussions as well, so that's definitely an option for the Edge+Airship type discussion too14:24
ildikovcool, I'll keep that in mind and share with the group14:25
mattmceuen+114:25
pramchanSure you are welcome to both and matt & me appear to be at both places for co-ordination14:25
mattmceuenty14:25
pramchan+114:25
mattmceuenok!  moving on:14:25
mattmceuen#topic Image overrides in versions.yaml14:25
*** openstack changes topic to "Image overrides in versions.yaml (Meeting topic: airship)"14:25
shubham_kaushal+114:25
mattmceuenhowell, I think this one is yours, if I am properly distinguishing the shades of lavender in the etherpad :)14:26
mattmceuenor kaspars?14:26
kskelsIt's me! :)14:26
mattmceuenlol14:26
openstackgerritSean Eagan proposed airship/promenade master: Dynamic kubelet config support  https://review.opendev.org/69186714:26
mattmceuenhttps://review.opendev.org/#/c/691042/14:27
mattmceuenall yours kskels14:27
kskelsHi everyone! I was the person once back removing image overrides in the `versions.yaml` to stick with defaults but lately due to various issues in the gating and image pulling speeds it's increasingly difficult to keep the pipelines stable, and while putting back versions adds extra work on syncing images with charts  (potential improvements in the `updater.py`) ehre are the follwoing benefits14:27
kskels1) It is now fully capturing all the images and versions of airship in a single file that are now possible to override by internal mirrors/repos14:27
kskels2) this allows overrides for environments that doesn't have access to direct internet/proxy14:28
kskelsI think I had a few more benefits that I forgot now! :)14:28
mattmceuenif we went that way, kaspars, would we also modify the image uplift script to take all those images into account?14:29
pramchanIs this for Ariship 1.x?14:29
mattmceuenyep14:29
kskelsyes, for airship 114:29
roman_g3) people don't get surprised to see way more images and applications being running, than the number of images listed in versions.yaml14:29
kskelswe should.. I may not have time to do it before summit but something to put on the list for todo14:30
mattmceuenAgree, time is short before the summit -- it will be a good enhancement but not "urgent"14:30
mattmceuenI think that change makes sense Kaspars14:30
mattmceuentreasuremap has evolved from a "bare bones reference" toward "real world reference" anyway14:31
kskelsyes, that is very much more and more true!14:31
mattmceuenOk, unless there's anything else on this one, we can move on14:32
kskelsthank you!14:32
mattmceuen#topic Docker image users14:32
*** openstack changes topic to "Docker image users (Meeting topic: airship)"14:32
ian-pittwoodThis is me14:33
openstackgerritMerged airship/porthole master: Pass extra build args to Docker image builds  https://review.opendev.org/69149614:33
ian-pittwoodSorry, kind of last minute thing for me. So currently some of our docker images for each project specify a user and some don't. For instance, promenade specifies "USER promenade" and pegleg does not specify a user at all. This is causing interoperability issues since pegleg is running and root and creating files that the promenade user does not have permissions to.14:34
ian-pittwoodSo I wanted to ask everyone what their opinion would be on creating a common user such as "airship" or using root throughout every image?14:34
ian-pittwoodI'm not sure what the current justifications are for specifying a user on each project vs using root14:35
kskelsI've had issues with this in the deployment and had to do workarounds for this exact reason - I would also be for having a common user14:35
ian-pittwoodExamples:14:35
ian-pittwoodhttps://opendev.org/airship/promenade/src/branch/master/Dockerfile14:35
ian-pittwoodhttps://opendev.org/airship/pegleg/src/branch/master/images/pegleg/Dockerfile.ubuntu_xenial14:35
mattmceuenI think pegleg is probably the exception to the rule (whatever the rule should be) since it outputs files for other things to consume14:36
alexanderhughesnot necessarily14:36
alexanderhughesif we do common user "airship" in all projects14:36
alexanderhugheswe don't have to run anything as root and still avoid permissions issues between projects14:36
*** LoicL35 has quit IRC14:36
alexanderhughesalso gets rid of workarounds like generating files with pegleg then having to chown to promenade to consume14:37
mattmceuenI think making an assumption of coordination of users -- i.e. that users are the same between containers -- introduces a level of coupling we may not need to have14:37
ian-pittwoodI think that the "airship" user would be a good solution so long as we don't need root perms at all. I think having a "promenade" user and a "deckhand" user is a little much unless we have reasons14:37
mattmceuenI am also a fan of following the OSH convention of injecting the running-as user as declarative intent (i.e. operator-specific configuration) for situations where there doesn't need to be any special handling (root filesystem type stuff)14:39
mattmceuenthe majority of containers shouldn't know or care what users other containers are running as14:39
mattmceuenThere has definitely been a desire to make more of our running-as-root containers run as non-root14:40
mattmceuenI propose we bring this to the design call, so we can see it from all angles14:40
alexanderhughessounds good14:41
mattmceuenok cool - I will add it to the agenda14:42
ian-pittwoodOk14:42
kskelsthat does sound good and in the meantime, perhaps this is something we could add in the treasuremap as workaround14:42
kskelshttps://github.com/airshipit/treasuremap/blob/master/tools/airship#L12114:42
mattmceuenpersonally I want to talk through the problem live, I don't think I get it 100% yet :)14:42
kskelsis what we use right now, but we could use "current" user14:42
kskelsanyway! thank you14:42
mattmceuengreat, ty for sharing that kaspars14:42
mattmceuenok, next up:14:43
mattmceuen#topic Review Requests14:43
*** openstack changes topic to "Review Requests (Meeting topic: airship)"14:43
mattmceuenWe have a good list today folks14:43
mattmceuenAnd I know that a number of people are heading out on a plane in the next couple days14:43
mattmceuenSo let's please get some focus on these today and tomorrow so we are in good shape for new discussions at Shanghai14:43
mattmceuen    https://review.opendev.org/686758 - adds testing expectations for airshipctl14:43
mattmceuen    https://review.opendev.org/689051 - updates airshipctl unit tests to use "testify"14:43
mattmceuen    https://review.opendev.org/#/c/691746/2 - Shipyard default network policies14:43
mattmceuen    https://review.opendev.org/#/c/675851 - airshipctl Add logic to isogen subcommand14:43
*** mattmceuen has quit IRC14:43
*** mattmceuen has joined #airshipit14:44
mattmceuenweird, I'm not sure why pasting those kicked me out of IRC :)14:44
pramchanAlso can you add review from flight plan  - https://etherpad.openstack.org/p/Airship_FlightPlan14:45
pramchanThese need review in community14:45
mattmceuen   CONFIG STUFF14:45
mattmceuen    https://review.opendev.org/68985914:45
mattmceuen    https://review.opendev.org/68891414:45
*** mattmceuen has quit IRC14:45
*** mattmceuen has joined #airshipit14:45
mattmceuenyep - hopefully those came through ok, IRCCloud is behaving a little weird for me today14:46
mattmceuenI've added them into the IRC agenda as well14:46
mattmceuenWe have a bit of a backlog of Airship 2.0 patches team14:47
mattmceuenWill be really valuable, as well as a great way to get experience with go, and get started in Airship 2.0 dev, to give those some solid review14:47
pramchan+114:47
mattmceuen#topic Roundtable14:48
*** openstack changes topic to "Roundtable (Meeting topic: airship)"14:48
mattmceuenwe have a few minutes left team - I have one more small item14:48
mattmceuenA number of folks will be in Shanghai next week; shall we cancel next Tuesday's team meeting?14:48
mattmceuenUsually we do, but I didn't want to unilaterally decide :)14:49
mattmceuendo cancel, I mean14:50
dwaltI am in favor, unless someone has pressing items14:50
kskelsSame, as I will be away14:50
*** ab2434_ has quit IRC14:50
pramchan+114:50
mattmceuenok, sounds good -- I will send a note out on the mailing list to make sure everyone knows14:50
*** LoicL35 has joined #airshipit14:51
mattmceuenany other roundtable items?14:51
openstackgerritJagan Mohan Kavva proposed airship/treasuremap master: Integrate compute utility container in airship/treasuremap  https://review.opendev.org/69187514:51
mattmceuenIn that case, thanks all for a good meeting!14:52
mattmceuenHave a great week, and for those in Shanghai, good luck and have fun!14:52
mattmceuenlet us know if you need anything :)14:52
mattmceuen#endmeeting14:52
*** openstack changes topic to "https://opendev.org/airship || https://wiki.openstack.org/wiki/Airship || https://review.opendev.org/#/q/projects:airship+status:open+NOT+label:Verified%253D-1+NOT+label:Workflow%253D-1+NOT+message:DNM+NOT+message:WIP"14:52
openstackMeeting ended Tue Oct 29 14:52:29 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-10-29-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-10-29-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/airship/2019/airship.2019-10-29-14.00.log.html14:52
openstackgerritSean Eagan proposed airship/promenade master: [WIP] Add kubelet_config chart  https://review.opendev.org/69187614:53
roman_gThanks, mattmceuen14:53
kskelsthank you and see you some of you in the summit!14:53
pramchanThanks and hope to see kskels and others at PTG.14:54
*** shubham_kaushal has quit IRC15:03
*** shubham_kaushal_ is now known as shubham_kaushal15:03
openstackgerritIan Howell proposed airship/airshipctl master: This removes golangci-lint as a go module dependency.  https://review.opendev.org/69042215:04
*** SRao has joined #airshipit15:09
*** LoicL35 has quit IRC15:13
*** dpawlik has quit IRC15:18
*** pgaxatte has quit IRC15:19
*** pramchan has quit IRC15:24
*** ian-pittwood has left #airshipit15:28
*** segorov has quit IRC15:28
*** segorov has joined #airshipit15:29
openstackgerritRoman Gorshunov proposed airship/docs master: Add container image and Dockerfile conventions  https://review.opendev.org/68503815:30
openstackgerritSean Eagan proposed airship/promenade master: [WIP] Add kubelet_config chart  https://review.opendev.org/69187615:32
*** pgaxatte has joined #airshipit15:40
openstackgerritMerged airship/treasuremap master: Add image overrides for all the charts  https://review.opendev.org/69104215:47
openstackgerritNishant Kumar proposed airship/maas master: [WIP] Support rotation for maas region secret  https://review.opendev.org/69170616:03
*** bh526r has quit IRC16:29
openstackgerritEvgeniy L proposed airship/treasuremap master: [WIP][DNM] Initial implementation of network policies for UCP  https://review.opendev.org/68413316:33
openstackgerritIan Howell proposed airship/airshipctl master: Fix the `make cover` target  https://review.opendev.org/68905116:46
openstackgerritIan Howell proposed airship/airshipctl master: Fix the `make cover` target  https://review.opendev.org/68905116:46
openstackgerritIan Howell proposed airship/airshipctl master: This updates the current unit tests for testify  https://review.opendev.org/68905116:52
openstackgerritRoman Gorshunov proposed airship/docs master: Add container image and Dockerfile conventions  https://review.opendev.org/68503816:53
openstackgerritIan Howell proposed airship/airshipctl master: This updates the current unit tests for testify  https://review.opendev.org/68905116:53
openstackgerritIan Howell proposed airship/airshipctl master: Fix the `make cover` target  https://review.opendev.org/69191616:54
howell*Sorry about the rapid-fire commits - botched some git stuff16:54
*** sreejithp has quit IRC17:01
*** shubham_kaushal has quit IRC17:12
*** pgaxatte has quit IRC17:16
*** jamesgu has quit IRC17:19
openstackgerritNishant Kumar proposed airship/maas master: [WIP] Support rotation for maas region secret  https://review.opendev.org/69170617:21
*** AlexNoskov has joined #airshipit17:26
*** segorov has quit IRC17:39
openstackgerritRahul Khiyani proposed airship/treasuremap master: Fix path for calicoctl-utility  https://review.opendev.org/69193218:05
*** SRao has quit IRC18:07
*** SRao has joined #airshipit18:18
*** segorov has joined #airshipit18:29
*** segorov has quit IRC18:43
*** segorov has joined #airshipit18:44
openstackgerritRodolfo Pacheco proposed airship/airshipctl master: airshipctl config (replace 686508)  https://review.opendev.org/68985918:52
openstackgerritkanwar saad bin liaqat proposed airship/airshipctl master: Bootstrap redfish Remote direct  https://review.opendev.org/68316519:22
*** jamesgu has joined #airshipit19:26
*** alexanderhughes has quit IRC19:43
openstackgerritMerged airship/treasuremap master: Fix path for calicoctl-utility  https://review.opendev.org/69193219:55
*** dpawlik has joined #airshipit20:14
*** dpawlik has quit IRC20:19
openstackgerritJagan Mohan Kavva proposed airship/treasuremap master: Integrate etcdctl utility container in airship/treasuremap  https://review.opendev.org/68048220:27
openstackgerritRodolfo Pacheco proposed airship/airshipctl master: airshipctl config (replace 686508)  https://review.opendev.org/68985920:34
*** roman_g has quit IRC20:37
*** roman_g has joined #airshipit20:38
*** roman_g has quit IRC20:38
*** roman_g has joined #airshipit20:39
*** roman_g has quit IRC20:39
*** roman_g has joined #airshipit20:40
*** roman_g has quit IRC20:40
*** roman_g has joined #airshipit20:40
*** roman_g has quit IRC20:41
*** roman_g has joined #airshipit20:41
*** roman_g has quit IRC20:41
*** roman_g has joined #airshipit20:42
*** roman_g has quit IRC20:42
*** roman_g has joined #airshipit20:43
*** roman_g has quit IRC20:43
openstackgerritRahul Khiyani proposed airship/treasuremap master: Integrate ceph utility container in airship/treasuremap  https://review.opendev.org/68113521:16
*** rezroo has joined #airshipit21:22
openstackgerritJagan Mohan Kavva proposed airship/treasuremap master: Integrate compute utility container in airship/treasuremap  https://review.opendev.org/69187521:46
openstackgerritJagan Mohan Kavva proposed airship/treasuremap master: Integrate compute utility container in airship/treasuremap  https://review.opendev.org/69187521:56
*** jamesgu has quit IRC21:59
*** SRao has quit IRC22:25
*** jamesgu has joined #airshipit22:58
openstackgerritPrateek Dodda proposed airship/treasuremap master: Integrate openstack utility container in airship/treasuremap  https://review.opendev.org/69173122:59
openstackgerritPrateek Dodda proposed airship/treasuremap master: Integrate openstack utility container in airship/treasuremap  https://review.opendev.org/69173123:21
*** segorov has quit IRC23:22
openstackgerritPrateek Dodda proposed airship/treasuremap master: Integrate openstack utility container in airship/treasuremap  https://review.opendev.org/69173123:23
openstackgerritRodolfo Pacheco proposed airship/airshipctl master: airshipctl config (replace 686508)  https://review.opendev.org/68985923:38
openstackgerritRodolfo Pacheco proposed airship/airshipctl master: airshipctl config (replace 686508)  https://review.opendev.org/68985923:43

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