Wednesday, 2019-02-20

« Tuesday, 2019-02-19 Index Thursday, 2019-02-21 »
*** EricRen has joined #kata-dev00:11
*** EricRen has quit IRC00:23
*** eguan has quit IRC01:15
*** EricRen has joined #kata-dev01:15
*** eguan has joined #kata-dev01:17
*** igordc has quit IRC01:30
*** igordc has joined #kata-dev02:15
*** liwei has joined #kata-dev03:10
*** liwei has quit IRC03:20
*** EricRen has quit IRC03:57
*** igordc has quit IRC05:08
*** igordc has joined #kata-dev05:20
*** igordc has quit IRC06:31
*** tmhoang has joined #kata-dev07:41
*** sgarzare has joined #kata-dev07:45
*** sameo has joined #kata-dev08:07
*** jodh has joined #kata-dev08:43
*** gwhaley has joined #kata-dev09:01
*** davidgiluk has joined #kata-dev09:05
*** sameo has quit IRC11:27
*** gwhaley has quit IRC12:06
*** devimc has joined #kata-dev13:25
*** gwhaley has joined #kata-dev13:41
*** sameo has joined #kata-dev15:14
*** igordc has joined #kata-dev16:20
*** tmhoang has quit IRC16:48
*** devimc has quit IRC17:08
*** devimc has joined #kata-dev17:09
kata-irc-bot1<eric.ernst> did 4.19 changes merge yet @jose.carlos.venegas.m?17:39
kata-irc-bot1<eric.ernst> 4.19.y?17:40
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst not sure17:40
kata-irc-bot1<eric.ernst> @graham.whaley you around still?17:40
kata-irc-bot1Action: jose.carlos.venegas.m looks17:40
kata-irc-bot1<eric.ernst> thx.17:40
kata-irc-bot1<graham.whaley> maybe @eric.ernst;)17:40
kata-irc-bot1<graham.whaley> @eric.ernst - not yet - we are waiting for the ARM configs to get fixed I think17:41
kata-irc-bot1<jose.carlos.venegas.m> not yet, https://github.com/kata-containers/runtime/blob/master/versions.yaml#L13617:41
kata-irc-bot1<eric.ernst> ughhhhhh17:41
kata-irc-bot1<eric.ernst> where's the PR for updating?  Runtime versions?17:41
kata-irc-bot1<eric.ernst> (not for arm config but in general)17:41
kata-irc-bot1<eric.ernst> I wanted to check what version we are moving to.17:41
kata-irc-bot1<graham.whaley> general one above - 4.19.23 iirc17:41
kata-irc-bot1<jose.carlos.venegas.m> https://github.com/kata-containers/runtime/pull/111117:42
kata-irc-bot1<graham.whaley> and then we were going to hop to 'stable' rather than 'longerm' I think is the plan17:42
kata-irc-bot1<graham.whaley> soz, that #1111 one17:42
kata-irc-bot1<eric.ernst> .24 is out now.17:42
kata-irc-bot1<graham.whaley> also waiting for 4.19 to land before I re-visit the .frags17:42
kata-irc-bot1<eric.ernst> we need to merge these quicker.17:42
kata-irc-bot1<graham.whaley> heh, I only got @sebastien.boeuf to update to .23 a few days ago ;)17:42
kata-irc-bot1<eric.ernst> Yeah.  We need to be able to do this faster.  Is there a PR for fixing ARM yet?  Anything we can do to help push this?17:43
kata-irc-bot1<graham.whaley> once we are over this initial 'hump', things should go smoother17:43
kata-irc-bot1<eric.ernst> yeah, i expect so.17:43
kata-irc-bot1<graham.whaley> PR was updated overnight, but a bunch of =m modules got into the config. They are reworking the PR. hopefully that should be ready in (my time) the monring17:43
kata-irc-bot1<eric.ernst> ok.17:43
kata-irc-bot1<jose.carlos.venegas.m> this is the PR from ARM ? https://github.com/kata-containers/packaging/pull/338/files ?17:44
kata-irc-bot1<jose.carlos.venegas.m> if so @sebastien.boeuf need to add a depends-on to that PR17:44
kata-irc-bot1<jose.carlos.venegas.m> to see if with that all CI passes17:44
kata-irc-bot1<jose.carlos.venegas.m> if all green, we have to merge them both at the same time17:45
*** devimc has quit IRC17:52
*** devimc has joined #kata-dev17:54
kata-irc-bot1<eric.ernst> we're scheduled for a stable release this week, and I'm pretty anxious to have this change in.17:59
kata-irc-bot1<eric.ernst> At this poing I"ll hold off until this is merged/available.18:00
*** jodh has quit IRC18:06
*** gwhaley has quit IRC18:10
*** sgarzare has quit IRC18:16
kata-irc-bot1<gmmaharaj> @jose.carlos.venegas.m @eric.ernst recent kata-deploy builds seem to be failing. https://hub.docker.com/r/katadocker/kata-deploy/builds Is there a way we can take a look at the build logs to see what is happenign?18:38
kata-irc-bot1<eric.ernst> We should disable the auto builds18:42
kata-irc-bot1<eric.ernst> It is because it expects a —build-arg18:42
kata-irc-bot1<eric.ernst> We need to do it as part of release process going forward.18:43
kata-irc-bot1<gmmaharaj> @eric.ernst aah. won't it be good to have ti auto-build? this way any changes to scripts surrounding a release can still yield an image that users can use?18:43
kata-irc-bot1<gmmaharaj> wondering if we can automate that or script around it to make sure that arg is passed? is there a way i can see the build logs to understand more on what is happenign?18:44
kata-irc-bot1<eric.ernst> It can be automatic, but probably through CD rolling rather than dockerhub18:45
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst what is the argument you pass to the build ?19:06
kata-irc-bot1<jose.carlos.venegas.m> oh I see the dockerfile19:07
kata-irc-bot1<eric.ernst> Kata release version19:07
kata-irc-bot1<jose.carlos.venegas.m> We can patch it to use latest if not provided ?19:08
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst also what is the trigger that does the autobuild ?19:09
*** eernst has joined #kata-dev19:09
kata-irc-bot1<eric.ernst> we can, if you know what latest is.19:10
kata-irc-bot1<eric.ernst> ideally we'd be able to grab it from a versions file in the repo, but it gets weird.19:10
kata-irc-bot1<eric.ernst> depending on stable, etc.19:10
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst we know what is latest19:11
kata-irc-bot1<jose.carlos.venegas.m> https://raw.githubusercontent.com/kata-containers/runtime/master/VERSION19:11
kata-irc-bot1<jose.carlos.venegas.m> nvm this could be a race condition, because the tarball is not uploaded yet19:12
kata-irc-bot1<eric.ernst> Exactly19:12
kata-irc-bot1<eric.ernst> Easier to do it part of CD imo19:12
kata-irc-bot1<jose.carlos.venegas.m> yes19:13
*** eernst has quit IRC19:13
kata-irc-bot1<jose.carlos.venegas.m> btw how you see to have release automated in azure pipelines or github actions ?19:14
kata-irc-bot1<jose.carlos.venegas.m> instead of jenkins19:14
kata-irc-bot1<jose.carlos.venegas.m> what do you think*19:14
kata-irc-bot1<jose.carlos.venegas.m> sai was looking at but not sure if this is something to bring to arch meeting or just continue with it19:15
kata-irc-bot1<eric.ernst> Continue it as POC imo and document and present it as suggested method.19:15
kata-irc-bot1<eric.ernst> Imo.19:15
kata-irc-bot1<jose.carlos.venegas.m> got it19:15
kata-irc-bot1<eric.ernst> @jose.carlos.venegas.m when we update kernel, we update packaging, and the update runtime?19:16
kata-irc-bot1<eric.ernst> How/which actually exercises the new kernel?19:16
kata-irc-bot1<jose.carlos.venegas.m> in CI ?19:16
kata-irc-bot1<jose.carlos.venegas.m> the kernel installation scripts if the kernel package is updated if not it builds if from source19:17
kata-irc-bot1<jose.carlos.venegas.m> https://github.com/kata-containers/tests/blob/master/.ci/install_kata_kernel.sh#L10519:18
kata-irc-bot1<eric.ernst> Based on version update in Runtime repo? And using latest configs on master from packaging repo?19:18
kata-irc-bot1<jose.carlos.venegas.m> same for the image19:18
kata-irc-bot1<jose.carlos.venegas.m> it ask to the package server what is the latest version, and compare with versions file - yes19:19
kata-irc-bot1<jose.carlos.venegas.m> where the latest version is `current_kernel_version="${kernel_version}.${kata_config_version}" `19:19
kata-irc-bot1<jose.carlos.venegas.m> and `kernel_version` is from version file `assets.kernel.version`19:20
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst for example in @sebastien.boeuf PR where bumps the kernel19:23
kata-irc-bot1<jose.carlos.venegas.m> This is part of the log related with that ``` INFO: Current Kernel version 4.19.23.23 INFO: Get packaged kernel version INFO: Packaged Kernel version 4.14.67.22 INFO: Install kernel from sources INFO: Clone config and patches INFO: Config version: 23 INFO: Kernel version: 4.19.23 INFO: kernel path does not exist, will download kernel   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current ```19:23
kata-irc-bot1<eric.ernst> ok thx19:23
kata-irc-bot1<eric.ernst> but config changes in packaging for "new configs" aren't tested today?19:23
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst no that is until we do a release19:35
kata-irc-bot1<jose.carlos.venegas.m> package update is atomic we update all on release19:35
kata-irc-bot1<jose.carlos.venegas.m> there is not partial package update, we do all of them19:35
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst oh just the configs19:36
kata-irc-bot1<jose.carlos.venegas.m> yes they are tested in the CI today, but not packaged19:36
kata-irc-bot1<eric.ernst> but those configs can only be tested... if the runtime version is appropriate, or?19:37
kata-irc-bot1<jose.carlos.venegas.m> to know if new config was done (but not kernel version update) we use https://github.com/kata-containers/packaging/blob/master/kernel/kata_config_version19:37
kata-irc-bot1<jose.carlos.venegas.m> yes, I mean if you send a config for kernel 5.0 and our runtime versions points to 4.20 the 5.0 configs are not tested19:38
kata-irc-bot1<jose.carlos.venegas.m> both kernel config and version bump must be sync19:38
kata-irc-bot1<jose.carlos.venegas.m> in that case19:38
kata-irc-bot1<eric.ernst> 1. i'm a simple person, i am first to admit.  I get confused too easily 2. I wonder if this is in an .md somewhere that covers this, or if there should be?19:38
kata-irc-bot1<eric.ernst> since it hits a couple different repos.19:39
kata-irc-bot1<jose.carlos.venegas.m> there is not documented anywhere19:39
kata-irc-bot1<jose.carlos.venegas.m> and has a few things to improve19:39
kata-irc-bot1<eric.ernst> k19:40
kata-irc-bot1<eric.ernst> not a critique per se - glad that the testing is in there.19:40
kata-irc-bot1<eric.ernst> I'm just gussing other folks shoudl know this too, and want to make sure we have a reference19:40
kata-irc-bot1<jose.carlos.venegas.m> @eric.ernst agree, let me document as it is and let open for folks to improve to make easy the maintenance19:42
*** davidgiluk has quit IRC20:18
*** eernst has joined #kata-dev20:39
*** eernst has quit IRC20:41
*** devimc has quit IRC22:33
*** eernst has joined #kata-dev22:38
*** eernst has quit IRC22:58
« Tuesday, 2019-02-19 Index Thursday, 2019-02-21 »

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