Wednesday, 2020-04-08

*** ailan has quit IRC00:36
*** th0din has quit IRC00:44
*** th0din has joined #kata-dev00:52
*** jugs has quit IRC04:20
*** jugs has joined #kata-dev04:21
*** sameo has joined #kata-dev05:10
*** igordc has quit IRC05:32
*** dklyle has quit IRC06:48
*** amorenoz has quit IRC06:56
*** amorenoz has joined #kata-dev06:57
*** sgarzare has joined #kata-dev07:15
*** jodh has joined #kata-dev07:16
*** sgarzare has quit IRC07:44
*** sgarzare has joined #kata-dev07:51
*** davidgiluk has joined #kata-dev08:03
*** gwhaley has joined #kata-dev08:03
*** ailan has joined #kata-dev08:23
errordeveloperdavidgiluk: does the agent mount /sys/fs/bpf by defualt? if now, is there a way to make it do that?10:01
davidgilukerrordeveloper: Don't know10:02
errordeveloperok, I'll just go and check10:02
errordeveloperdavidgiluk: it does actually :)10:05
errordeveloperbut looks like it is an implicit feature actually10:06
errordevelopercannot grep anything out in osbuilder, or the agent repo10:06
gwhaleyerrordeveloper: probably - probably mounts much of /sys - try a 'mount' in the container to see what is actually mounted ;-)10:06
errordevelopergwhaley: yeah, already tested that10:06
errordeveloperno bug upstream as such10:07
errordeveloperthe clearlinux image definetly does the right thing10:07
gwhaleyI have a feeling we had to enable some ebpf recently to support cgroupsv2 - which may have bought some stuff in10:07
fidenciogwhaley: I'm wondering there, when 1.11.0 is planned to be released and how could we try to ensure we have some patches (some already in master, some not yet) there?10:22
gwhaleyhi fidencio - anything merged into master would make the next major point release, which I think is the next release? I don't actually get involved in the releases ;-), so I'm not actually sure if once we have the alpha tags if we then backport to those, or just continue to re-tag the HEAD until the release. There is a release schedule wiki page, but I think it needs updating.... https://github.com/kata-containers/community/wiki/Releas10:36
gwhaleye-Team-Rota10:36
gwhaley@egernse @amshinde @fuentess ^^^ wrt release schedule etc.10:37
gwhaleynow, I am pretty sure the release team are always looking for new members to help out fidencio ;-)10:37
fidenciogwhaley: :-) I see what you did there10:38
gwhaleyheh heh.....10:38
gwhaleyI'm not sure if the release process docs clarify either... https://github.com/kata-containers/documentation/blob/master/Release-Process.md10:38
fidenciobasically what I want to know is whether I should open a PR for SELinux patch backporting it to some specific branch or not10:39
fidencioI'll bother the others when they wake up :-)10:39
fidenciogwhaley: thanks for the pointers!10:40
gwhaleyack. and there are probably two questions there - 1) do you need to backport to the alpha 'next release' branches10:40
gwhaleyand 2) do we want to backport to the stable branch/releases ... which I suspect is a 'no', as we tend to only backport fixes, not features10:40
gwhaleyI think we'll have to wait for the americas to wake up to get some answers10:41
fidenciogwhaley: i agree with 2) :-)10:43
*** gwhaley has quit IRC10:59
*** gwhaley has joined #kata-dev12:09
*** crobinso has joined #kata-dev13:45
*** hashar has joined #kata-dev13:48
*** igordc has joined #kata-dev14:45
*** dklyle has joined #kata-dev15:00
kata-irc-bot<eric.ernst> i'm awake. What's good @graham.whaley15:02
kata-irc-bot<eric.ernst> for alpha, we are just tracking master.  Once we hit RC we create a branch and backport15:03
kata-irc-bot<graham.whaley> morning @eric.ernst - well, it is sunny and warm here atm, which makes a nice change.15:03
kata-irc-bot<graham.whaley> thx for the clarification on alpha/release - /cc @fidencio ^^15:04
kata-irc-bot<eric.ernst> Yeah, we're getting the same.  Makes life a lot brighter ;)15:04
kata-irc-bot<graham.whaley> I presume you are really missing the coffee shop....15:04
kata-irc-bot<eric.ernst> About to read through and see how accurate this is : https://github.com/kata-containers/documentation/blob/master/Stable-Branch-Strategy.md15:04
kata-irc-bot<eric.ernst> Yeah... seriously.  I miss espresso most.15:04
kata-irc-bot<fidencio> @eric.ernst, cool, so SELinux will be present in the 1.11.0, once it's released15:04
kata-irc-bot<eric.ernst> I miss espresso, and I somewhat miss being more than 30 feet from my kids ;)15:04
kata-irc-bot<fidencio> I'd love to have the patches related to virtiofs patches merged as well15:05
kata-irc-bot<eric.ernst> (I use gitlab during the day now --- good heavens, how I miss GitHub)15:05
kata-irc-bot<eric.ernst> Just checking to see if there was a 1.11 project in place; I'm not seeing one.15:06
kata-irc-bot<eric.ernst> This is best way to make sure everyone is on same page 'feature wise' on what wants to land in that release.  Let me TAL at making one.15:06
kata-irc-bot<eric.ernst> What particular PRs are you looking at @fidencio?15:08
kata-irc-bot<eric.ernst> Good news is it doesn't appear a 1.11 branch was cut, so SELinux should be included.  The bad news is it doesn't look like release rotation is up to date15:09
kata-irc-bot<fidencio> https://github.com/kata-containers/agent/pull/738 https://github.com/kata-containers/runtime/pull/2463 https://github.com/kata-containers/runtime/pull/247315:10
kata-irc-bot<fidencio> Those are the ones that I'd like to have merged for 1.11.015:10
kata-irc-bot<fidencio> SELinux one is merged already, thankfully!15:11
kata-irc-bot<eric.ernst> @salvador.fuentes -- hola big boss!  You know when we are planning on cutting the 1.11 RC?15:12
kata-irc-bot<eric.ernst> barely started, but if it is helpful to add other items that'll land for 1.11.  I think in particular we have some CLH enhancements (:wave: @jose.carlos.venegas.m @chen.bo) .    https://github.com/orgs/kata-containers/projects/2215:19
kata-irc-bot<jose.carlos.venegas.m> @eric.ernst hey there15:43
kata-irc-bot<jose.carlos.venegas.m> cool I just added a card we have as a blocker for clh, apt-get upgrade is not working until we enable (or not) no_posix_lock in virtifosd for clh15:46
*** ailan has quit IRC15:51
*** ailan has joined #kata-dev15:51
kata-irc-bot<salvador.fuentes> @eric.ernst hey, I think it is planned to be on 2020-04-20, at least taking a look at the release rota page, although it seems little bit outdated15:53
*** hashar is now known as hasharAway16:05
*** hasharAway is now known as hashar16:23
*** sgarzare has quit IRC16:28
*** errordeveloper has quit IRC16:33
kata-irc-bot<archana.m.shinde> @eric.ernst @salvador.fuentes @fidencio Yes the release page needs an update as we were late by a week for a previous release16:55
kata-irc-bot<archana.m.shinde> We should target an rc0 release next week, rc is where the features are locked16:55
kata-irc-bot<fidencio> Okay, what could I do to help with the process?16:56
kata-irc-bot<archana.m.shinde> for your virtiofs renaming changes, the CI is failing right16:56
kata-irc-bot<archana.m.shinde> I gather we need a kernel update for those16:56
kata-irc-bot<fidencio> IIUC, CI has to be updated to a released kernel16:56
kata-irc-bot<fidencio> as it was using some kind of dev branch16:57
kata-irc-bot<archana.m.shinde> I talked to david offhand about having the virtiofs kernel updated16:57
kata-irc-bot<archana.m.shinde> yes Vivek Goyal maintains that16:57
kata-irc-bot<fidencio> Hmm. Right, I can ping Vivek as well16:57
kata-irc-bot<archana.m.shinde> This is the one https://github.com/kata-containers/runtime/blob/master/versions.yaml#L11016:58
kata-irc-bot<archana.m.shinde> Yes, We also talked about having patches to make docker in docker work with Kata applied on top of those16:59
*** gwhaley has quit IRC16:59
kata-irc-bot<fidencio> Wait, is this qemu or kernel? I thought the blocker was in the kernel side17:00
davidgilukyeh the docker-in-docker thing is an overlayfs fix by msceredi17:03
davidgilukmszeredi17:03
*** jodh has quit IRC17:09
kata-irc-bot<salvador.fuentes> fidencio: we are using both qemu and kernel from that old tag in the gitlab virtiofs repo: https://github.com/kata-containers/runtime/blob/master/versions.yaml#L16217:31
*** sunnycai has joined #kata-dev17:45
kata-irc-bot<archana.m.shinde> fidencio: my bad with the paste :slightly_smiling_face: Yes the blocker is from kernel side17:51
kata-irc-bot<salvador.fuentes> @archana.m.shinde @jose.carlos.venegas.m @eric.ernst I have updated the release rota page with new dates, next release set for next Tuesday and then the next ones with a 3 week cadence, pls check and let me know if this is fine: https://github.com/kata-containers/community/wiki/Release-Team-Rota#the-rota18:07
kata-irc-bot<jose.carlos.venegas.m> the date for next schedule for me is OK18:10
kata-irc-bot<jose.carlos.venegas.m> thanks for update it18:10
kata-irc-bot<archana.m.shinde> thanks @salvador.fuentes18:12
kata-irc-bot<eric.ernst> Looks good - thanks @salvador.fuentes18:12
kata-irc-bot<archana.m.shinde> Lets send out a mail to community to backport any bug fixes18:13
kata-irc-bot<archana.m.shinde> Calling out here as well :slightly_smiling_face: ...Please backport any changes needed to stable branches18:14
kata-irc-bot<salvador.fuentes> yeah, let me send that email18:14
*** crobinso has quit IRC18:27
*** ChanServ changes topic to "Kata Containers Development & User discussions | https://github.com/kata-containers | http://lists.katacontainers.io/ | http://bit.ly/katacontainersslack | https://katacontainers.io/ | General topics in #kata-general"18:32
*** hashar has quit IRC18:33
*** hashar has joined #kata-dev18:36
*** davidgiluk has quit IRC19:57
*** igordc has quit IRC20:17
*** igordc has joined #kata-dev20:18
*** hashar has quit IRC20:19
*** sunnycai has quit IRC20:41
*** sameo has quit IRC21:12
*** ailan has quit IRC21:14
*** jugs has quit IRC21:45
*** jugs has joined #kata-dev21:46

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