| *** zerocoolback has joined #kata-dev | 00:39 | |
| *** yingjun has joined #kata-dev | 00:58 | |
| *** gabyc_ has quit IRC | 00:58 | |
| *** zerocoolback has quit IRC | 01:08 | |
| *** liujiong has joined #kata-dev | 01:54 | |
| *** zerocoolback has joined #kata-dev | 02:24 | |
| *** zerocoolback has quit IRC | 02:41 | |
| *** zerocoolback has joined #kata-dev | 02:52 | |
| *** yingjun has quit IRC | 02:52 | |
| *** yingjun has joined #kata-dev | 03:25 | |
| *** zerocoolback has quit IRC | 03:27 | |
| *** eernst has joined #kata-dev | 03:32 | |
| *** diga has joined #kata-dev | 03:46 | |
| *** yingjun has quit IRC | 04:11 | |
| *** eernst has quit IRC | 04:24 | |
| *** sjas has joined #kata-dev | 04:29 | |
| *** yingjun has joined #kata-dev | 04:32 | |
| *** zerocoolback has joined #kata-dev | 04:32 | |
| *** sjas_ has quit IRC | 04:33 | |
| *** zerocoolback has quit IRC | 04:41 | |
| *** yingjun has quit IRC | 04:50 | |
| *** diga has quit IRC | 04:56 | |
| *** yingjun has joined #kata-dev | 05:38 | |
| *** yingjun has quit IRC | 06:03 | |
| *** yingjun has joined #kata-dev | 07:16 | |
| *** jodh has joined #kata-dev | 07:20 | |
| *** jodh has quit IRC | 07:20 | |
| *** jodh has joined #kata-dev | 07:20 | |
| *** sameo has joined #kata-dev | 07:25 | |
| *** cdent has joined #kata-dev | 07:29 | |
| *** dims_ has joined #kata-dev | 07:48 | |
| *** dims has quit IRC | 07:49 | |
| *** gwhaley has joined #kata-dev | 07:57 | |
| *** yingjun has quit IRC | 09:42 | |
| *** zerocoolback has joined #kata-dev | 09:53 | |
| *** zerocoolback has quit IRC | 09:55 | |
| *** liujiong has quit IRC | 10:03 | |
| *** gwhaley has quit IRC | 10:53 | |
| *** gwhaley has joined #kata-dev | 10:53 | |
| *** gwhaley has quit IRC | 11:06 | |
| *** gwhaley has joined #kata-dev | 12:22 | |
| *** yingjun has joined #kata-dev | 12:39 | |
| *** jodh has quit IRC | 13:11 | |
| *** jodh has joined #kata-dev | 13:14 | |
| *** jodh has quit IRC | 13:14 | |
| *** jodh has joined #kata-dev | 13:14 | |
| *** eernst has joined #kata-dev | 13:27 | |
| *** annabelleB has joined #kata-dev | 13:44 | |
| *** yingjun has quit IRC | 13:49 | |
| *** yingjun has joined #kata-dev | 13:50 | |
| kata-dev-irc-bot | <eric.ernst> @zhangwei555 - curious if you have input on https://github.com/kata-containers/runtime/issues/113#issuecomment-375774225 | 13:56 |
|---|---|---|
| kata-dev-irc-bot | <eric.ernst> @jonolson - also curious if you have input on https://github.com/kata-containers/runtime/issues/115#issuecomment-376385384 | 13:56 |
| *** fuentess has joined #kata-dev | 13:57 | |
| kata-dev-irc-bot | <zhangwei555> @eric.ernst I will have a look first, got a real busy day:) | 14:01 |
| *** Margaret_ has joined #kata-dev | 14:02 | |
| kata-dev-irc-bot | <eric.ernst> @zhangwei555 I know how it goes, understood | 14:02 |
| kata-dev-irc-bot | <bergwolf> <here> we need one more ACK from docs team to merge the API design doc https://github.com/kata-containers/documentation/pull/27. Anyone can help? | 14:04 |
| *** cdent has left #kata-dev | 14:05 | |
| kata-dev-irc-bot | <eric.ernst> merged! | 14:06 |
| kata-dev-irc-bot | <eric.ernst> @bergwolf did you get a chance to check out the networking hotplug issue we opened? | 14:08 |
| kata-dev-irc-bot | <bergwolf> thanks! | 14:13 |
| kata-dev-irc-bot | <bergwolf> For network config for docker, runv has a dedicated ns watcher. https://github.com/hyperhq/runv/blob/master/cli/network.go#L251 | 14:15 |
| kata-dev-irc-bot | <bergwolf> It looks close to what @sebastien.boeuf suggested in https://github.com/containers/virtcontainers/issues/241#issuecomment-371200622 | 14:16 |
| *** mcastelinoo has joined #kata-dev | 14:17 | |
| *** mcastelino has quit IRC | 14:17 | |
| kata-dev-irc-bot | <sebastien.boeuf> @bergwolf my understanding from a previous comment from @zhangwei555 was that `runv` was implementing such a thing before but that it was not used anymore. | 14:18 |
| kata-dev-irc-bot | <sebastien.boeuf> @bergwolf anyway, if that's the solution we want to go with, reusing some code from `runv` might be a good idea to speed things up ;) | 14:18 |
| kata-dev-irc-bot | <bergwolf> It was not used by Huawei IIUC. It is in use for runv integrating with docker. Huawei is using `runv network` subcommand that works with their private CNI plugin. | 14:20 |
| kata-dev-irc-bot | <bergwolf> we cannot test Huawei's private code but for docker integration, we did use the standalone ns listener. | 14:21 |
| kata-dev-irc-bot | <eric.ernst> Understood that. I think as a generic (suboptimal?) solution we need the listener. | 14:21 |
| kata-dev-irc-bot | <eric.ernst> I know that folks from ZTE in particular are interestd in this. see https://github.com/containers/virtcontainers/issues/241 | 14:22 |
| kata-dev-irc-bot | <sebastien.boeuf> Yes the listener is (I think) the only option | 14:23 |
| kata-dev-irc-bot | <bergwolf> docker network config is based on iptables. Maybe we should consider to do the same for kata (as runv did) -- `iptables-save` in the netns, `iptables-restore` in the guest. | 14:24 |
| kata-dev-irc-bot | <bergwolf> parsing iptables rules on our own is quite error prone | 14:25 |
| kata-dev-irc-bot | <eric.ernst> This is statically done on init? Or does the listener monitor the tables? | 14:27 |
| kata-dev-irc-bot | <eric.ernst> (ie, if interfaces are added later; do you just re-execute -save and -restore?) | 14:29 |
| kata-dev-irc-bot | <bergwolf> It's done for every new container | 14:33 |
| kata-dev-irc-bot | <eric.ernst> How'd that work if user added a network to a running container? | 14:34 |
| kata-dev-irc-bot | <eric.ernst> Or is that just a limitation? | 14:35 |
| kata-dev-irc-bot | <bergwolf> I don't think that would work for hotplug new interface without creating new container. | 14:35 |
| kata-dev-irc-bot | <eric.ernst> docker network connect , right? | 14:36 |
| *** mcastelinoo has quit IRC | 14:36 | |
| kata-dev-irc-bot | <eric.ernst> This is something we never supported in CC before; instead we'd just do it with runc containers and then steal the runc placeholders' network. | 14:37 |
| kata-dev-irc-bot | <eric.ernst> But, I think this is one of the scenarios that should be handled (ie, not just hotplugging network for performance optimization of boot time, but also being able to hot plug network interfaces?) | 14:38 |
| kata-dev-irc-bot | <eric.ernst> WDYT? | 14:38 |
| kata-dev-irc-bot | <eric.ernst> (side thread- @salvador.fuentes any luck with k8s testing?) | 14:39 |
| kata-dev-irc-bot | <salvador.fuentes> @eric.ernst Im working with @sebastien.boeuf on this, yesterday we could launch the dns pod, so I think we are close on having k8s working | 14:41 |
| kata-dev-irc-bot | <bergwolf> `docker network connect` looks to be a combination of several subcomands of `runv network`. we should be able to support it with the kata library network hotplug APIs, right? | 14:43 |
| *** sameo has quit IRC | 14:50 | |
| kata-dev-irc-bot | <eric.ernst> Yeah. One more general question; with the API extensions documentation (finally, newly) merged, what are next steps for implementation? | 14:51 |
| kata-dev-irc-bot | <eric.ernst> ie, who's working on which portion? | 14:51 |
| kata-dev-irc-bot | <eric.ernst> I think we're starting to get a respectable backlog for this. | 14:51 |
| kata-dev-irc-bot | <bergwolf> Yeah, I think all these APIs are open for contributors as of now. I am planing on taking the built-in shim/proxy support part first. Not sure about others though. Maybe we should have a doc somewhere to list the backlogs and who is working on what part of it? | 15:00 |
| kata-dev-irc-bot | <eric.ernst> Yes. I have a document like this that I have been using internally. | 15:00 |
| kata-dev-irc-bot | <eric.ernst> Perhaps I can scrub and make it externally available. I want to make sure that we are aligned. | 15:01 |
| kata-dev-irc-bot | <bergwolf> yup, that would be really helpful | 15:01 |
| kata-dev-irc-bot | <sebastien.boeuf> +1 | 15:05 |
| *** devimc has joined #kata-dev | 15:07 | |
| kata-dev-irc-bot | <eric.ernst> @bergwolf do you have a reference impl for network ns listener that runv used before for testing with docker? | 15:15 |
| kata-dev-irc-bot | <eric.ernst> This may be a starting point for what we'd want on kata. | 15:16 |
| kata-dev-irc-bot | <bergwolf> @eric.ernst https://github.com/hyperhq/runv/blob/master/cli/network.go#L318 | 15:19 |
| kata-dev-irc-bot | <eric.ernst> thx. | 15:20 |
| *** devimc has quit IRC | 15:22 | |
| *** devimc has joined #kata-dev | 15:32 | |
| *** yingjun has quit IRC | 15:53 | |
| *** mcastelino has joined #kata-dev | 16:00 | |
| kata-dev-irc-bot | <zhangwei555> I like the idea, it sounds workable :) I don’t have better suggestion for docker libnetwork support. A minor problem is this could require lots of annoying things to handle :) | 16:13 |
| *** sameo has joined #kata-dev | 16:15 | |
| *** gwhaley has quit IRC | 16:25 | |
| *** jodh has quit IRC | 17:03 | |
| *** gwhaley has joined #kata-dev | 17:13 | |
| *** sameo has quit IRC | 18:02 | |
| *** annabelleB has quit IRC | 18:25 | |
| *** annabelleB has joined #kata-dev | 18:25 | |
| *** jlbutler has joined #kata-dev | 18:46 | |
| *** gwhaley has quit IRC | 19:31 | |
| *** jlbutler has quit IRC | 20:22 | |
| *** devimc_ has joined #kata-dev | 20:23 | |
| *** eernst has quit IRC | 20:23 | |
| *** eernst has joined #kata-dev | 20:23 | |
| *** devimc_ has quit IRC | 20:24 | |
| *** devimc_ has joined #kata-dev | 20:25 | |
| *** devimc has quit IRC | 20:26 | |
| *** eernst_ has joined #kata-dev | 20:26 | |
| *** eernst has quit IRC | 20:27 | |
| *** eernst_ has quit IRC | 20:31 | |
| *** eernst has joined #kata-dev | 20:40 | |
| *** eernst has quit IRC | 20:41 | |
| *** eernst has joined #kata-dev | 20:41 | |
| *** eernst_ has joined #kata-dev | 20:43 | |
| *** eernst has quit IRC | 20:43 | |
| *** eernst has joined #kata-dev | 20:48 | |
| *** eernst_ has quit IRC | 20:48 | |
| *** eernst has quit IRC | 20:49 | |
| *** eernst has joined #kata-dev | 20:49 | |
| *** eernst has quit IRC | 20:50 | |
| *** eernst has joined #kata-dev | 20:50 | |
| *** eernst has quit IRC | 20:51 | |
| *** eernst has joined #kata-dev | 20:51 | |
| *** eernst has quit IRC | 20:53 | |
| *** eernst has joined #kata-dev | 20:53 | |
| *** oikiki has joined #kata-dev | 21:42 | |
| *** annabelleB has quit IRC | 22:25 | |
| *** annabelleB has joined #kata-dev | 22:28 | |
| *** eernst has quit IRC | 22:33 | |
| *** eernst has joined #kata-dev | 22:33 | |
| *** eernst has quit IRC | 22:38 | |
| *** annabelleB has quit IRC | 22:40 | |
| *** eernst has joined #kata-dev | 22:40 | |
| *** eernst has quit IRC | 22:41 | |
| *** eernst has joined #kata-dev | 22:41 | |
| *** eernst has quit IRC | 22:43 | |
| *** sjas has quit IRC | 22:51 | |
| *** eernst has joined #kata-dev | 22:54 | |
| *** eernst has quit IRC | 22:59 | |
| *** eernst has joined #kata-dev | 23:00 | |
| *** eernst has quit IRC | 23:05 | |
| *** eernst has joined #kata-dev | 23:06 | |
| *** eernst has quit IRC | 23:10 | |
| *** eernst has joined #kata-dev | 23:12 | |
| *** eernst has quit IRC | 23:15 | |
| *** devimc_ has quit IRC | 23:16 | |
| *** eernst has joined #kata-dev | 23:19 | |
| *** eernst has quit IRC | 23:23 | |
| *** mcastelinoo has joined #kata-dev | 23:24 | |
| *** eernst has joined #kata-dev | 23:24 | |
| *** eernst has quit IRC | 23:25 | |
| *** eernst has joined #kata-dev | 23:26 | |
| *** mcastelino has quit IRC | 23:27 | |
| *** eernst_ has joined #kata-dev | 23:28 | |
| *** eernst has quit IRC | 23:28 | |
| *** eernst_ has quit IRC | 23:31 | |
| *** eernst has joined #kata-dev | 23:31 | |
| kata-dev-irc-bot | <tallclair> Can anyone recommend some learning resources (books, articles, etc) to dive deeper into the design, architecture, and mechanisms of VMs (especially KVM, QEMU, and VMX)? I'm finding that low-level technical documentation in the area is surprisingly scarce... | 23:32 |
| *** mcastelinoo has quit IRC | 23:32 | |
| *** eernst has quit IRC | 23:36 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!