Wednesday, 2018-06-20

*** fuentess has quit IRC00:03
*** LinuxMe has joined #kata-dev00:03
*** LinuxMe has quit IRC00:04
*** LinuxMe has joined #kata-dev00:04
*** eernst has quit IRC00:06
*** LinuxMe has quit IRC01:22
*** dlw has joined #kata-dev01:29
*** zerocoolback has joined #kata-dev01:38
*** zerocoolback has quit IRC02:07
*** zerocoolback has joined #kata-dev02:08
*** LinuxMe has joined #kata-dev02:12
*** LinuxMe has quit IRC02:17
*** LinuxMe_ has joined #kata-dev03:07
*** annabelleB has joined #kata-dev03:07
*** tonyb has joined #kata-dev03:11
*** annabelleB has quit IRC03:12
*** lsm5 has quit IRC03:22
*** lsm5 has joined #kata-dev03:22
*** lsm5 has quit IRC03:23
*** lsm5 has joined #kata-dev03:25
*** lsm5 has joined #kata-dev03:25
*** mrbobbytables has quit IRC03:49
*** din has quit IRC03:49
*** jbryce has quit IRC03:49
*** srwilkers has quit IRC03:50
*** fdegir has quit IRC03:51
*** LinuxMe_ has quit IRC03:57
*** annabelleB has joined #kata-dev04:14
*** sjas has joined #kata-dev04:16
*** annabelleB has quit IRC04:19
*** sjas_ has quit IRC04:19
*** openstack has joined #kata-dev04:29
*** ChanServ sets mode: +o openstack04:29
*** ur5us has joined #kata-dev05:10
*** LinuxMe has joined #kata-dev05:13
*** din has joined #kata-dev05:21
*** srwilkers has joined #kata-dev05:22
*** annabelleB has joined #kata-dev05:24
*** LinuxMe has quit IRC05:24
*** mrbobbytables has joined #kata-dev05:25
*** ur5us has quit IRC05:26
*** annabelleB has quit IRC05:29
*** fdegir has joined #kata-dev05:35
*** din has quit IRC05:51
*** din has joined #kata-dev05:51
*** din has quit IRC05:55
*** srwilkers has quit IRC05:55
*** fdegir has quit IRC05:58
*** mrbobbytables has quit IRC05:59
*** dims has quit IRC06:09
*** dims has joined #kata-dev06:10
*** din has joined #kata-dev06:10
*** dims has quit IRC06:16
*** dims has joined #kata-dev06:17
*** jbryce has joined #kata-dev06:21
*** mrbobbytables has joined #kata-dev06:21
*** fdegir has joined #kata-dev06:23
*** srwilkers has joined #kata-dev06:26
*** annabelleB has joined #kata-dev06:29
*** annabelleB has quit IRC06:34
*** sameo has joined #kata-dev07:03
*** jodh has joined #kata-dev07:25
*** jodh has quit IRC07:25
*** jodh has joined #kata-dev07:25
*** annabelleB has joined #kata-dev07:29
*** annabelleB has quit IRC07:35
*** zerocoolback has quit IRC07:52
*** gwhaley has joined #kata-dev08:02
*** davidgiluk has joined #kata-dev08:03
*** annabelleB has joined #kata-dev08:19
*** annabelleB has quit IRC08:24
*** zerocoolback has joined #kata-dev08:34
*** zerocoolback has quit IRC08:55
*** zerocoolback has joined #kata-dev08:55
*** annabelleB has joined #kata-dev09:16
*** FL1SK has quit IRC09:18
*** annabelleB has quit IRC09:28
kata-irc-bot<niteshkonkar007> Hello, When we run `docker run -it --runtime=kata-runtime busybox sh` what all gets `hotplugged` as of today and what are we planning to hotplug in future?10:23
*** annabelleB has joined #kata-dev10:25
*** annabelleB has quit IRC10:30
gwhaley^^ maybe @devimc can reply best I think10:31
*** dlw has quit IRC10:43
*** gwhaley has quit IRC11:14
*** annabelleB has joined #kata-dev11:25
*** FL1SK has joined #kata-dev11:28
*** annabelleB has quit IRC11:29
*** devimc has joined #kata-dev11:54
*** annabelleB has joined #kata-dev12:02
*** annabelleB has quit IRC12:07
*** annabelleB has joined #kata-dev12:16
*** annabelleB has quit IRC12:20
*** gwhaley has joined #kata-dev12:27
*** fuentess has joined #kata-dev12:29
kata-irc-bot<eric.ernst> Cpus, network, any devices (vfio), container image12:57
*** jugs has quit IRC12:58
*** jugs has joined #kata-dev13:01
*** jugs has quit IRC13:31
*** jugs has joined #kata-dev13:31
*** lamego has joined #kata-dev13:32
*** annabelleB has joined #kata-dev13:51
*** david-lyle has joined #kata-dev13:57
*** dklyle has quit IRC13:57
*** annabelleB has quit IRC13:58
*** annabelleB has joined #kata-dev14:13
*** annabelleB has quit IRC14:17
*** sameo has quit IRC14:25
*** annabelleB has joined #kata-dev14:30
*** LinuxMe has joined #kata-dev14:33
*** LinuxMe has quit IRC14:33
*** annabelleB has quit IRC14:35
*** annabelleB has joined #kata-dev14:37
*** annabelleB has quit IRC14:42
*** fuentess1 has joined #kata-dev14:46
*** fuentess1 has quit IRC14:47
*** david-lyle has quit IRC14:56
*** dklyle has joined #kata-dev15:01
*** sameo has joined #kata-dev15:09
*** annabelleB has joined #kata-dev15:14
kata-irc-bot<sebastien.boeuf> @niteshkonkar007 as of today, CPUs, devices and container image through SCSI. For the future, memory and network15:20
kata-irc-bot<jonolson> Can someone who’s more familiar with typical Jenkins output give me a hint as to what failed here: http://jenkins.katacontainers.io/job/kata-containers-documentation-ubuntu-16-04-PR/18/console ?15:48
*** jodh_ has joined #kata-dev15:50
*** jodh has quit IRC15:50
kata-irc-bot<raravena80> looks like here ```[Service] ExecStart= ExecStart=/usr/bin/dockerd -D --add-runtime kata-runtime=/usr/bin/kata-runtime --default-runtime=kata-runtime the input device is not a TTY```  I don't have access to the job config so I'm not sure what the step or cmd.15:51
gwhaley@@jonolson - I'll go have a look to. @raravena80 - the job run is pretty much ... /me goes to find link15:52
gwhaleyhttps://github.com/kata-containers/tests/blob/master/.ci/jenkins_job_build.sh15:53
clarkbset -x can help debug this in the bash scripts. Gives you a better idea of what command produces the output15:53
gwhaleyThe Jenkins config is a very think wrapper around that. You can find the actual Jenkins configs in https://github.com/kata-containers/ci/tree/master/jenkins - if you like reading XML :-)15:53
gwhaleybleh15:53
gwhaleybut, yes, Jenkins tends to run with no TTY - and that can upset a bunch of things, including docker if you have a -ti on your test - don't do that ;-)15:54
gwhaley@jonolson - so, I think that was trying to execute your GCE install guide document at a guess (looking back up the logs) - does that match up with the PR being tested? (/me goes to check)15:55
kata-irc-bot<jonolson> Yup, that's the PR in question15:55
kata-irc-bot<jonolson> Awkward :)15:55
gwhaleyI suspect you have a ```bash section in that doc that is doing a docker -ti - if you remove the `bash` from the triplequote, it will stop trying to execute that section ;-)15:56
gwhaleyor, remove the -ti15:56
kata-irc-bot<jonolson> hmmm… no docker in the PR, but I wonder if it tries to run the scripts inside a docker container15:57
kata-irc-bot<james.o.hunt> @graham.whaley, @jonolson - the CI has detected that "an install guide" file was modified, so it attempts to install kata based on the distro you (or Jenkins is running on), Ubuntu in this case. We could tighten up the heuristic a bit there to avoid it triggering on gce as we're not running that code on Jenkins ;)15:57
gwhaleyOh, so, I see no docker in the PR ^^ ;-)15:57
*** pranjal has joined #kata-dev15:58
kata-irc-bot<james.o.hunt> @jonolson, @graham.whaley - it's this code ftr: https://github.com/kata-containers/documentation/blob/master/.ci/test-install-docs.sh#L1815:58
kata-irc-bot<jonolson> @james.o.hunt There _is_ an account set up on GCE with credits for running CI there, but it seems a bit like putting the cart before the horse to get CI set up for GCE without having a merged install guide for GCE :slightly_smiling_face:15:59
*** sameo has quit IRC15:59
kata-irc-bot<james.o.hunt> but yes, the failure is prolly related to that tty message and is clearly unrelated to your PR.15:59
kata-irc-bot<jonolson> (more importantly, the credit stream is pretty thin, so any CI that runs there needs to be set up to clean up after itself)15:59
kata-irc-bot<jonolson> hah, even better :slightly_smiling_face:16:00
gwhaley@james.o.hunt - had a sneaky thought (might not apply here)... we only execute 'bash' sections, yes? - for those we want to highlight but not execute, we could probably mark as 'sh' sections. list of available things is here I think: https://github.com/github/linguist/blob/master/lib/linguist/languages.yml16:01
kata-irc-bot<james.o.hunt> @graham.whaley - yes, by design so that you can still include "code" but force it to be ignored by the "executor" (kata-doc-to-script.sh / kata-manager.sh)16:01
kata-irc-bot<james.o.hunt> sparky...? is that like the kata/jezz thing? yep - could use a sh block rather than a bash block, but I don't think in this instance that's the problem.16:03
gwhaleysparky... ??? I didn't see that here - so, quote that back to me, and I'll see if I can do it again from irc. That bot has a mind of its own ;-)16:06
gwhaley@james.o.hunt ^^16:06
jodh_gwhaley: my sparky comment might be confusing... until you see this conversation on slack. Yep - we seem to have a new oddity "m a r k" -> "s p a r k y c o l l i e r"16:06
jodh_we need to replace the bot with that IBM AI. Wait, that thing argues doesn't it?16:07
gwhaleyright - let's give it a spin, and watch @anne twitch ... I'm going to type 'm a r k', and see if you get sparky..... mark ???16:07
jodh_I do indeed over in Slack world ;)16:07
gwhaleyheh ^^@anne - err, the bot has more than one nervous k a t a f r a z e l l e twitch it appears... @openstack ^^16:08
jodh_"cat /usr/share/dict/words|slack" ftw?! ;)16:08
kata-irc-bot<anne> noooooooooooooo ::shakes fist at sky::16:08
gwhaleyit's like hunting easter eggs :-)16:08
jodh_we might find more.16:08
annabelleBanne (testing!)16:10
kata-irc-bot<anne> innnnnteresting16:10
kata-irc-bot<anne> so if your name is also a verb, take cover!16:11
gwhaleywhere is little jonny drop tables when you need him eh?16:11
annabelleBha!16:11
gwhaleywhich reminds me (don't ask how) - I'd better go do those CFP submissions!!!16:12
kata-irc-bot<raravena80> need to start using irc :,)16:12
kata-irc-bot<james.o.hunt> Are we brave enough I wonder...? :slightly_smiling_face: https://mergify.io/16:16
*** LinuxMe has joined #kata-dev16:18
gwhaley@anne - do we have a kata 'twitter handle'? I'll stick it on the CFP (as, err, coz, like I don't have one ;-) )16:22
kata-irc-bot<kata> @katacontainers16:22
kata-irc-bot<anne> thanks jessie! tweet away, @graham.whaley!16:23
kata-irc-bot<anne> @james.o.hunt @graham.whaley et all! I'm in the middle of digging through openstack election process to start drafting up a proposal for kata's and the outstanding questions we need to decide. Thinking of how many edits there might be, are people okay with a first collaborate draft going in etherpad before github? (I feel like I make a mess with GitHub comments...I'm better with gerrit, I swear!)16:24
kata-irc-bot<james.o.hunt> @anne - wfm. either etherpad or maybe https://github.com/kata-containers/community/wiki somewhere?16:28
kata-irc-bot<jose.carlos.venegas.m> woot?16:29
kata-irc-bot<james.o.hunt> ... speaking of the wiki, @niteshkonkar007, @julio.montes, @jose.carlos.venegas.m, @bergwolf - it would be good to get some content into https://github.com/kata-containers/community/wiki/Document-essential-kernel-config-options-for-ppc64le,-arm64-and-x86_64 at some point :)16:30
gwhaley@anne - etherpad fine I think16:37
kata-irc-bot<jose.carlos.venegas.m> @james.o.hunt yes, sounds good to me the minimal set of options that kata requires to at least boot.16:38
kata-irc-bot<jose.carlos.venegas.m> @laijs @bergwolf, quick question does https://github.com/intel/govmm/pull/16 and https://github.com/intel/govmm/pull/18 add memory backed file support in different ways but they complement or only one of those changes are the one that we will keep?16:41
*** zerocoolback has quit IRC16:46
*** sameo has joined #kata-dev16:50
*** jodh_ has quit IRC17:00
*** gwhaley has quit IRC17:29
*** LinuxMe has quit IRC17:30
*** LinuxMe_ has joined #kata-dev17:34
*** fiddletwix has joined #kata-dev17:40
*** pranjal has quit IRC17:55
kata-irc-bot<anne> @james.o.hunt @graham.whaley et all interested in election process: Draft started with many outstanding questions, please comment and tear it apart so we can make a robust system! https://etherpad.openstack.org/p/KataArchElections17:59
*** pranjal has joined #kata-dev18:18
*** pranjal has quit IRC18:26
* davidgiluk is surprised about that discussion of needing 240 sockets, 1 core/socket - I've just tried a 240 core config on an 2.10 qemu with -smp 240,sockets=15,cores=16,threads=1 and it seems to have survived (on a somewhat less beafy host)18:49
*** pranjal has joined #kata-dev19:02
*** pranjal_ has joined #kata-dev19:03
kata-irc-bot<jonolson> not sure about qemu specifically, but certainly Linux doesn’t care how you hotplug processors (our VMM supported CPU hotplug long before it supported advertising multi-socket topologies)19:06
kata-irc-bot<jonolson> sockets=15 is fine, though19:07
kata-irc-bot<jonolson> er, fun19:07
*** pranjal has quit IRC19:07
davidgiluk240 limit, one socket fell off the side :-)19:07
*** annabelleB has quit IRC19:12
davidgiluknote you can try these things on much smaller hosts - I was doing that on a 12 core host, so you can play around without too many issues19:16
*** davidgiluk has quit IRC19:21
*** devimc has quit IRC19:41
*** devimc has joined #kata-dev20:22
*** devimc has quit IRC20:28
*** devimc has joined #kata-dev20:28
*** annabelleB has joined #kata-dev20:36
*** LinuxMe_ has quit IRC22:04
*** eernst has joined #kata-dev22:20
*** devimc has quit IRC22:36
*** LinuxMe has joined #kata-dev22:40
*** LinuxMe has quit IRC22:44
*** annabelleB has quit IRC22:46
*** annabelleB has joined #kata-dev22:57
*** lamego has quit IRC23:06
*** annabelleB has quit IRC23:14
*** annabelleB has joined #kata-dev23:15
*** LinuxMe has joined #kata-dev23:18
*** annabelleB has quit IRC23:19
*** LinuxMe has quit IRC23:48
*** LinuxMe has joined #kata-dev23:48

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