| *** df has joined #kata-dev | 00:50 | |
| kata-dev-irc-bot | <bergwolf> @sebastien.boeuf I'm not sure I fully understand your question. A storage is a sandbox level resource. A container just references it in the spec. It is actually out of the scope of new container creation to hotplug the storage. We should always hotplug necessary storage before creating new containers in the agent. | 00:51 |
|---|---|---|
| *** df has quit IRC | 00:54 | |
| kata-dev-irc-bot | <sebastien.boeuf> @bergwolf the rootfs is passed when the container is created. How do you know from a sandbox perspective what the container will need ? | 01:11 |
| kata-dev-irc-bot | <sebastien.boeuf> and I might be confused on the meaning of storage | 01:12 |
| *** mcastelinoo has joined #kata-dev | 01:14 | |
| *** mcastelino has quit IRC | 01:17 | |
| *** mcastelinoo has quit IRC | 01:22 | |
| *** oikiki has joined #kata-dev | 01:29 | |
| kata-dev-irc-bot | <bergwolf> well, hyperd knows when creating new containers. I think you are confusing cri container creation with kata container creation. In hyperd, we'll split the creation in many steps and calling kata createcontainer is just one of them. | 01:31 |
| kata-dev-irc-bot | <bergwolf> a storage van be either a rootfs or a volume. hyperd knows the difference and will craft proper container spec to ask virtcontainers to create it. | 01:33 |
| kata-dev-irc-bot | <zhangwei555> I think @bergwolf is trying to do these operations in parallel for performance. Right? | 01:34 |
| kata-dev-irc-bot | <bergwolf> yes @zhangwei555 | 01:38 |
| *** oikiki has quit IRC | 02:26 | |
| *** sjas_ has joined #kata-dev | 04:22 | |
| *** sjas has quit IRC | 04:26 | |
| *** oikiki has joined #kata-dev | 05:43 | |
| *** oikiki has quit IRC | 05:44 | |
| *** sjas_ is now known as sjas | 08:18 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!