Tuesday, 2019-06-25

*** igordc has quit IRC00:13
*** sameo has joined #kata-dev05:24
*** pcaruana has joined #kata-dev05:56
*** pcaruana has quit IRC05:57
*** pcaruana has joined #kata-dev05:57
*** lpetrut has joined #kata-dev06:01
*** jodh has joined #kata-dev06:41
*** altlogbot_2 has quit IRC06:46
*** altlogbot_1 has joined #kata-dev06:48
*** sameo has quit IRC06:49
*** altlogbot_1 has quit IRC06:50
*** sgarzare has joined #kata-dev06:51
*** altlogbot_2 has joined #kata-dev06:54
*** sameo has joined #kata-dev07:15
*** tmhoang has joined #kata-dev07:31
*** davidgiluk has joined #kata-dev08:01
*** gwhaley has joined #kata-dev08:06
*** tmhoang has quit IRC08:30
*** tmhoang has joined #kata-dev08:30
kata-irc-bot<graham.whaley> @xu @bergwolf - either of you still online? :slightly_smiling_face:09:16
*** dinechin has joined #kata-dev09:34
dinechinHi. total newbie here. What is the recommended way to run some diagnostics for a running kata container, e.g. similar to `docker exec -i -t my-container /bin/bash`?09:38
kata-irc-bot<xu> @graham.whaley I think I could be online09:42
kata-irc-bot<xu> I am in the convention center for KubeCon/Open Source Summit Shanghai :slightly_smiling_face:09:44
kata-irc-bot<xu> And bergwolf is here as well, but I don't know which room he is in09:44
kata-irc-bot<graham.whaley> ah, np @xu - quick question - do we have any specific documentation, Issues or *code* in Kata about High Availability?09:46
kata-irc-bot<graham.whaley> I think you guys have probably thought about that the most...09:47
kata-irc-bot<xu> I don't think we have doc on it. But we are considering live-upgrade of the kata components in recent weeks, and I think we should create an issue on it. I think @weizhang555’s persistence work could be part of it.09:49
kata-irc-bot<weizhang555> > I think @weizhang555’s persistence work could be part of it.  I agree.09:51
kata-irc-bot<graham.whaley> ah, live upgrade, thx, had not thought of that bit. Other bit I can think of is if agent can restart if running under a systemd rootfs. But, I guess the workload is the child of the agent?, so if the agent dies then the workload probably dies as well. So most HA stuff I imagine comes from the orchestrator ultimately. Also, now we tend to not have a proxy as we have vsock, the proxy does not come into HA any more either \o/09:51
kata-irc-bot<graham.whaley> @dinechin - kata-runtime sits next to the normal 'runc' runtime. If you have it configured as your default runtime in docker, then the command you showed would run a kata container by default. If kata is not the default runtime, then adding the `--runtime kata-runtime` to the command should run a kata for you. `docker info` will tell you which runtimes are installed/configured in your `docker`.09:53
dinechinThanks. Will try that. Thought it was "too simple" ;-)09:55
kata-irc-bot<weizhang555> If people are using containerd-shim-v2, I think the scene could be much simpler. You can safely upgrade kata-components, and new started container will be using new kata components...09:55
kata-irc-bot<graham.whaley> @dinechin - heh, if it's not simple, then we have probably failed ;) Yeah, it should be a pretty simple 'drop in replacement', and look and feel just like a container...09:56
kata-irc-bot<xu> I think the HA in kata may include the shimv2 and agent upgrade, and kernel live patching without interrupting the user workload.09:57
kata-irc-bot<weizhang555> That sounds great, but requires lots of work :bananadance:09:58
kata-irc-bot<graham.whaley> thanks @xu @weizhang555 - that has given me things to think about (trying to list what we have and where the gaps/plans are etc.).10:01
kata-irc-bot<graham.whaley> so, have an excellent conference!10:01
kata-irc-bot<graham.whaley> must be nearly time for beer there? ;) :beer:10:02
kata-irc-bot<weizhang555> @graham.whaley One issue for reference: https://github.com/kata-containers/runtime/issues/492 ;)10:03
kata-irc-bot<graham.whaley> oh, excellent :clap:10:03
kata-irc-bot<xu> The exhibition hall reception will begin in 50 minutes10:04
*** gwhaley has quit IRC11:03
*** sgarzare has quit IRC11:36
*** sgarzare has joined #kata-dev11:55
*** gwhaley has joined #kata-dev12:01
*** fuentess has joined #kata-dev12:37
*** sameo has quit IRC13:39
*** sameo has joined #kata-dev14:13
*** lpetrut has quit IRC14:38
*** igordc has joined #kata-dev14:49
*** jodh has quit IRC15:01
*** lpetrut has joined #kata-dev15:17
*** lpetrut has quit IRC15:23
*** igordc has quit IRC15:32
*** igordc has joined #kata-dev16:04
*** sameo has quit IRC16:05
*** sgarzare has quit IRC16:17
*** tmhoang has quit IRC16:47
*** igordc has quit IRC16:56
*** igordc has joined #kata-dev16:59
*** dinechin has quit IRC17:30
*** eernst has joined #kata-dev17:45
*** sameo has joined #kata-dev18:06
kata-irc-bot<eric.ernst> @jose.carlos.venegas.m - FYI: https://github.com/kata-containers/runtime/pull/1823#issuecomment-50556085818:15
kata-irc-bot<eric.ernst> @manohar.r.castelino ^ curious for your thoughts here.18:15
kata-irc-botAction: jose.carlos.venegas.m looks18:16
*** davidgiluk has quit IRC19:17
*** lpetrut has joined #kata-dev19:18
*** lpetrut has quit IRC19:23
kata-irc-bot<graham.whaley> hi fuentess - I hit an error trying to run `setup.sh` under my jenkins magic pipeline - it does not give a lot of clues :( per chance, have you seen this before when trying to install/setup the CNI stuff: ```var/spool/ var/spool/mail/ var/www/ ~/workspace/Graham-test-pipeline/go/src/github.com/grahamwhaley/kata-containers-runtime Move to /tmp/tmp.QXQfLsdlFc/virtcontainers/build /tmp/tmp.QXQfLsdlFc/virtcontainers/build19:28
kata-irc-bot~/workspace/Graham-test-pipeline/go/src/github.com/grahamwhaley/kata-containers-runtime Clone cni Copy CNI config files /tmp/tmp.QXQfLsdlFc/virtcontainers/build/plugins /tmp/tmp.QXQfLsdlFc/virtcontainers/build ~/workspace/Graham-test-pipeline/go/src/github.com/grahamwhaley/kata-containers-runtime ```19:28
kata-irc-bot<salvador.fuentes> @graham.whaley hmmm, not really, is that where the job stopped?19:29
kata-irc-bot<graham.whaley> ah, hold on, maybe I know.....19:29
kata-irc-bot<graham.whaley> because my 'runtime repo' is not in is 'natural path' - it is under my name. and golang don't like that, or not for vc/runtime repo anyhow....19:30
kata-irc-bot<graham.whaley> and, yep, that is where the job stopped! :(19:30
kata-irc-bot<graham.whaley> Right, I can rework this in the morning! Probably pick a repo that is *not* the runtime ;)19:31
kata-irc-bot<salvador.fuentes> ok, at least you know what happened, but yeah, seem that it is very hard to debug this way19:31
*** gwhaley has quit IRC19:33
*** pcaruana has quit IRC19:38
*** sameo has quit IRC20:38
*** fuentess has quit IRC21:34
*** tobberydberg has quit IRC21:49
*** tobberydberg has joined #kata-dev21:51
*** eernst has quit IRC23:14
*** eernst has joined #kata-dev23:29
*** eernst_ has joined #kata-dev23:30
*** eernst has quit IRC23:30
*** eernst_ has quit IRC23:35

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