02:59:40 #startmeeting zun 02:59:41 Meeting started Tue Apr 3 02:59:40 2018 UTC and is due to finish in 60 minutes. The chair is fengshengqin. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:59:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:59:44 The meeting name has been set to 'zun' 02:59:51 #topic Roll Call 02:59:52 o/ 03:00:06 i knew kevin is on vacation today 03:00:42 we may have a short meeting 03:00:48 sure 03:00:55 #topic Blueprints 03:01:03 1. OpenStack as a virtual Kubernetes node (assignee: kevinz) 03:01:10 #link https://blueprints.launchpad.net/zun/+spec/zun-connector-for-k8s 03:01:18 let's skip it 03:01:26 2. Introduce quota for containers (assignee: TBD) 03:01:34 #link https://blueprints.launchpad.net/zun/+spec/quota-support 03:01:40 this one is assigned to kien 03:01:53 it looks kien is not here 03:01:59 so we can skip this as well :) 03:02:11 3. Manage the reverse disk for container images (assignee: fengshengqin) 03:02:18 #link https://blueprints.launchpad.net/zun/+spec/manage-container-image-disk 03:02:35 i have some ideas for it 03:02:48 what ideas? 03:03:07 first,we would reverse disk for container images 03:03:18 yes 03:03:34 2. we may get the image disk info by 'docker system df' 03:04:10 3. check the size of free_disk for loading a new image 03:04:27 4. update the disk if the images is deleted 03:04:41 5. as we know, a image may has multilayers. 03:05:09 so if avail_disk < image_size, we may return exception 03:05:37 or parse the layers of image, and check which has loaded, which not. 03:06:13 then we can calculate the size we need 03:06:24 that's all. 03:06:45 since image are with layers, i don't think you can get the exact disk size that will be taken by the image 03:07:32 however, you can run the 'df' command again after the image is pulled 03:07:33 i will check "docker system df" 03:07:50 sure 03:08:03 yes, we can update database by df 03:08:08 what i am commenting is "if avail_disk < image_size, we may return exception" 03:08:44 i don't think it is necessary to raise the exception based on the image size 03:09:22 because it is hard to estimate the size to be taken 03:09:28 i know 03:09:33 however, this is minor 03:10:00 for this one, i think we can do this step by step 03:10:10 we may add a congifure to choose 03:10:25 which config? 03:11:12 whether need to parse mutil layers 03:11:37 i think it will be hard to parse 03:11:45 anyway 03:12:01 a question though 03:12:14 yes, i will think about it more 03:12:24 if the disk is not enough, how about deleting some image? 03:13:09 you can do "docker images" to check which image is not used 03:13:11 no,we may choose other host to create container 03:13:36 ok 03:13:49 but it is not safe 03:13:58 delete images 03:14:12 i think you can find which image is unused 03:14:30 if an image is not used by any container, is it safe to delete ? 03:15:14 #link https://forums.docker.com/t/command-to-remove-all-unused-images/20/2 03:15:35 how about adding a task to delete unused images 03:15:50 yes, it can be a periodic task, that is fine 03:16:48 we can create a new bp 03:16:54 sure 03:17:29 anything else for this? 03:17:35 for this image reserve feature, my suggestion is to make the design/implementation as simple as possible 03:18:02 ack 03:18:25 ok 03:18:34 nothing else from me, go ahead 03:18:47 #topic Bugs 03:18:54 1. Cannot create container with kata runtime (assignee: hongbin) 03:19:00 #link https://bugs.launchpad.net/zun/+bug/1754552 03:19:02 Launchpad bug 1754552 in Zun "Cannot create container with kata runtime" [Critical,Triaged] - Assigned to hongbin (hongbin034) 03:19:24 for this one, i am still waiting for the feedback from kata team 03:19:31 ok 03:19:34 2. Error on running privsep helper command (assignee: hongbin) 03:19:34 we can revisit this bug at the next meeting 03:19:41 #link https://bugs.launchpad.net/zun/+bug/1749342 03:19:43 Launchpad bug 1749342 in Zun queens "Error on running privsep helper command" [Undecided,Fix committed] - Assigned to hongbin (hongbin034) 03:19:52 for this one, all hte patches are merged, so this bug is fixed 03:20:02 thanks for reviewing the patches 03:20:04 great! 03:20:17 #topic Open Discussion 03:20:46 any question ? 03:20:50 no 03:20:58 then we finish :) 03:21:12 see you next time 03:21:19 see you 03:21:26 #endmeeting