Friday, 2018-03-09

*** zerocoolback has joined #kata-dev00:15
*** zerocoolback has quit IRC00:21
*** oikiki has quit IRC00:35
*** mcastelino has quit IRC02:09
*** zerocoolback has joined #kata-dev02:44
*** zerocoolback has quit IRC03:38
*** oikiki has joined #kata-dev04:01
*** zerocoolback has joined #kata-dev04:17
*** oikiki_ has joined #kata-dev04:19
*** oikiki has quit IRC04:21
*** eernst has quit IRC05:13
*** mylinux has joined #kata-dev05:48
*** oikiki_ has quit IRC05:56
*** sjas_ has joined #kata-dev05:56
*** oikiki has joined #kata-dev05:56
*** sjas has quit IRC05:59
*** zerocoolback has quit IRC06:08
*** zerocoolback has joined #kata-dev06:13
*** zerocoolback has quit IRC06:13
*** mylinux has quit IRC06:43
*** zerocoolback has joined #kata-dev06:44
*** mylinux has joined #kata-dev06:50
*** mylinux_ has joined #kata-dev06:53
*** mylinux has quit IRC06:53
*** zerocoolback has quit IRC06:59
*** mylinux_ has quit IRC07:08
*** zerocoolback has joined #kata-dev07:10
*** oikiki has quit IRC07:14
*** zerocoolback has quit IRC07:15
*** zerocoolback has joined #kata-dev07:17
*** zerocoolback has quit IRC07:17
*** jodh has joined #kata-dev07:23
*** mylinux has joined #kata-dev08:22
*** mylinux has quit IRC08:27
kata-dev-irc-bot<samuel.ortiz> @laijs Thanks for the analysis on https://github.com/kata-containers/runtime/issues/4608:30
kata-dev-irc-bot<samuel.ortiz> @laijs I'll reply to it today.08:30
*** gwhaley has joined #kata-dev09:02
*** zerocoolback has joined #kata-dev09:13
*** zerocoolback has quit IRC09:19
*** mylinux has joined #kata-dev09:19
*** zerocoolback has joined #kata-dev09:23
*** zerocoolback has quit IRC09:24
*** mylinux has quit IRC09:24
*** zerocoolback has joined #kata-dev09:30
*** cdent has joined #kata-dev09:47
*** zerocoolback has quit IRC09:49
*** zerocoolback has joined #kata-dev09:53
*** zerocoolback has quit IRC09:58
*** mylinux has joined #kata-dev10:22
*** mylinux has quit IRC10:26
kata-dev-irc-bot<samuel.ortiz> @bergwolf Hey11:06
kata-dev-irc-bot<bergwolf> hi @samuel.ortiz just saw it11:20
kata-dev-irc-bot<samuel.ortiz> @bergwolf Hey. I'm trying to understand the Frakti/runv code path that currently calls AddStorage(). Do you have a pointer showing where that's being called?11:21
kata-dev-irc-bot<bergwolf> it's called here https://github.com/hyperhq/hyperd/blob/master/daemon/pod/volume.go#L6611:23
kata-dev-irc-bot<samuel.ortiz> @bergwolf I'd just like to understand how the CRI mounts get translated into the frakti storage structures...11:23
kata-dev-irc-bot<bergwolf> oh, that's in frakti then11:24
kata-dev-irc-bot<samuel.ortiz> Yes, and eventually falls down to hyperd I guess.11:24
kata-dev-irc-bot<samuel.ortiz> Also, if you could point me to where the volume.add() gets called, I'd appreciate.11:25
kata-dev-irc-bot<samuel.ortiz> gtg for lunch, I'll read your replies in an hour. Thanks in advance.11:26
kata-dev-irc-bot<bergwolf> here it is https://github.com/kubernetes/frakti/blob/master/pkg/hyper/container.go#L16511:27
*** mylinux has joined #kata-dev11:27
kata-dev-irc-bot<bergwolf> volume.add() is called by hyperd here: https://github.com/hyperhq/hyperd/blob/master/daemon/pod/provision.go#L44111:28
kata-dev-irc-bot<bergwolf> the idea is to prepare volumes/nics/rootfs in parallel11:30
*** mylinux has quit IRC11:31
*** mylinux has joined #kata-dev11:49
*** zerocoolback has joined #kata-dev11:51
*** mylinux has quit IRC11:54
*** zerocoolback has quit IRC11:55
*** gwhaley has quit IRC12:02
*** mylinux has joined #kata-dev12:03
*** mylinux has quit IRC12:07
*** zerocoolback has joined #kata-dev12:51
*** zerocoolback has quit IRC12:56
*** mylinux has joined #kata-dev13:05
*** mylinux has quit IRC13:09
*** gabyc_ has joined #kata-dev13:20
*** gwhaley has joined #kata-dev13:23
*** devimc has joined #kata-dev13:28
*** zerocoolback has joined #kata-dev13:52
*** zerocoolback has joined #kata-dev13:53
*** sameo has joined #kata-dev14:22
*** rcw has joined #kata-dev14:26
*** fuentess has joined #kata-dev14:36
*** mylinux has joined #kata-dev15:21
*** mylinux has quit IRC15:25
*** mylinux has joined #kata-dev15:29
*** mylinux has quit IRC15:50
*** mylinux has joined #kata-dev15:51
*** devimc has quit IRC15:52
*** sameo has quit IRC15:52
*** mylinux has quit IRC15:55
*** sameo has joined #kata-dev15:56
*** eernst has joined #kata-dev15:57
*** mylinux has joined #kata-dev15:58
*** diga has joined #kata-dev15:58
*** mylinux has quit IRC16:02
*** mylinux has joined #kata-dev16:02
kata-dev-irc-bot<samuel.ortiz> @bergwolf Still around?16:18
kata-dev-irc-bot<bergwolf> yup16:18
kata-dev-irc-bot<samuel.ortiz> Let me try to understand: You guys do 2 things in parallel: start the VM and then in parallel: add storage to the vm, prepare the container rootfs on the host and hotplug it in the VM?16:20
kata-dev-irc-bot<bergwolf> yes16:21
kata-dev-irc-bot<bergwolf> and nics are added in parallel as well16:22
kata-dev-irc-bot<samuel.ortiz> So if starting the VM would include adding storage and NICs to it in parallel, you could start the VM and prepare the rootfs on the host in parallel as well, right ?16:23
kata-dev-irc-bot<bergwolf> that is different. In CRI, CreateContainer() is separate from RunPodSandbox() so there is no way to know which rootfs/volume/nics to prepare when starting them VM.16:25
kata-dev-irc-bot<bergwolf> And there can be more than one CreateContainer()16:25
kata-dev-irc-bot<samuel.ortiz> Then add storage and nics to CreateContainer(), in parallel, as well?16:25
kata-dev-irc-bot<bergwolf> The flow is, we get CRI `CreateContainer()`, then we need to 1. prepare the rootfs and hotplug it 2. prepare the volume and hotplug it 3. prepare the nics and hotplug it 4. call `sandbox.CreateContainer`  We want to parallel 1/2/3 and then do 4. what sequence are you suggesting?16:28
kata-dev-irc-bot<bergwolf> If we do not export hotplug API, we have to wait in 1, and then call `sandbox.CreateContainer` which would internally do 2/3, wait, and then create the container.  So it's 1 waiting vs. 2 waitings.16:30
*** sameo has quit IRC16:32
*** mylinux has quit IRC16:33
*** mylinux has joined #kata-dev16:36
kata-dev-irc-bot<bergwolf> I gotta sleep. ttyl16:42
*** zerocoolback has quit IRC17:08
*** devimc has joined #kata-dev17:08
*** mcastelino has joined #kata-dev17:10
*** diga has quit IRC17:42
*** jodh has quit IRC18:04
*** gwhaley has quit IRC18:19
*** oikiki has joined #kata-dev18:33
*** oikiki has quit IRC19:48
*** oikiki has joined #kata-dev19:48
*** oikiki has quit IRC20:13
*** oikiki has joined #kata-dev20:15
*** cdent has quit IRC20:52
*** devimc has quit IRC21:33
*** sameo has joined #kata-dev21:50
*** sameo has quit IRC22:13
*** rcw has quit IRC22:14
*** mylinux has quit IRC23:00
*** mylinux has joined #kata-dev23:01
*** gabyc_ has left #kata-dev23:01
*** mylinux has quit IRC23:06
*** mylinux has joined #kata-dev23:12
*** mylinux has quit IRC23:17
*** eernst has quit IRC23:22
*** eernst has joined #kata-dev23:23
*** mylinux has joined #kata-dev23:25
*** eernst has quit IRC23:25
*** mylinux_ has joined #kata-dev23:27
*** mylinux has quit IRC23:29
*** mylinux_ has quit IRC23:32

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