03:00:14 #startmeeting zun 03:00:15 Meeting started Tue Apr 11 03:00:14 2017 UTC and is due to finish in 60 minutes. The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:00:18 The meeting name has been set to 'zun' 03:00:22 #link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-04-11_0300_UTC Today's agenda 03:00:27 #topic Roll Call 03:00:31 kevinz 03:00:32 Namrata 03:00:38 shubham kumar sharma 03:00:46 shunli 03:01:34 lakerzhou 03:02:01 thanks for joining the meeting kevinz Namrata shubhams Shunli lakerzhou 03:02:08 let's get started 03:02:14 #topic Announcements 03:02:20 1. Madhuri and Pradeep are on leave, so might not be able to join the meeting 03:02:34 2. Zun will hold a feedback session at Boston Forum (Thursday 11:00 - 11:40) 03:02:41 #link http://lists.openstack.org/pipermail/openstack-dev/attachments/20170410/32dd3c13/attachment.pdf 03:03:05 if you go to boston summit, remember to come to the feedback session :) 03:03:24 this session is for the team to get boarder feedback from the community 03:03:51 you just answered my question 03:03:51 Cool 03:03:53 i will chair the session, hopefully, we could get some helpful input 03:04:03 great 03:04:05 great 03:04:15 how many of you will go to the boston summit? 03:04:22 But I can't go to Boston.. 03:04:24 I will. 03:04:37 kevinz: lakerzhou ack 03:04:48 lakerzhou: look forward to seeing you there :) 03:05:08 3. Propose to have a "Boston Summit" release by the end of April 03:05:10 hongbin: I wont be coming 03:05:13 I cannot 03:05:13 sure, I will have a lighting talk there. 03:05:19 if visa gets approved 03:05:26 then i will 03:05:43 Shunli: shubhams ack, hope to have a chance to see you in elsewhere 03:05:51 Namrata: ack 03:06:13 3. Propose to have a "Boston Summit" release by the end of April 03:07:03 i propose to make a release before the boston summit, the date would be roughly by the end of april 03:07:24 the goal of this release is to have a version to demo on the summit 03:07:54 That greate 03:08:03 just let me know if anything you want to include in this summit 03:08:27 i will try to get them in and incorproate it in a demo if possible 03:08:38 great 03:08:58 cool 03:09:02 any qestion for hte above announment? 03:09:25 do we have a demo in Keynote? 03:09:36 kevinz: i am not sure yet 03:09:59 hongbin: OK 03:10:00 kevinz: will let you know if there is one 03:10:16 o/ 03:10:23 sorry got late 03:10:27 diga: hi diga, thianks for joining 03:10:38 #topic Cinder integration (diga) 03:10:44 hongbin: hi 03:11:04 diga: you are arriving at the right time, want to give the team a update? 03:11:05 hongbin: I have incorporated your comments and have made the changes accordingly 03:11:11 hongbin: :) 03:11:28 hongbin: I will push my patch in sometime, 03:11:46 diga: ack 03:11:49 #link https://review.openstack.org/#/c/429943/ 03:12:14 hongbin: will ping you later 03:12:31 diga: i saw the gate was failed, do you need help for trouble-shooting the gate? 03:12:49 hongbin: also CLI is also implemented & working, 03:12:56 hongbin: Yeah 03:13:11 diga: ok, i can help you with that 03:13:11 hongbin: I dont know how to pass the gate without test cases 03:13:20 hongbin: it will be really helpful 03:13:32 sure, will help you offline 03:13:32 hongbin: Thank you! 03:13:48 hongbin: sure 03:13:53 #action hongbin help diga to get the cinder integration patch passed the gate 03:14:24 hongbin: sorry I wasn't active on irc/zun in last two weeks due product release 03:14:36 diga: that is fine 03:14:46 diga: thanks for your contribution on this feature 03:14:55 hongbin: welcome! 03:15:12 all, any remark on this bp? 03:15:50 seems no, advance topic 03:15:52 #topic Kuryr integration (hongbin) 03:15:58 #link https://blueprints.launchpad.net/zun/+spec/kuryr-integration The BP 03:16:20 this is hte patch: https://review.openstack.org/#/c/453387/ 03:16:22 #link https://review.openstack.org/#/c/453387/ 03:16:53 i think this patch is pretty close to remove the aip 03:16:55 wip 03:17:45 hongbin: will take a look at it today 03:17:48 what it does is to find a neutron network, and use kuryr plugin to create a docker network 03:18:11 diga: ack 03:18:14 hongbin: looks good approach 03:18:51 hongbin: 1 question, this is only for docker right, not k8s 03:19:05 diga: yes, only for docker 03:19:12 hongbin: got it 03:19:38 hongbin: Thanks for this great work. I will find time to review and try it:-) 03:20:03 kevinz: ack, perhaps try it after the wip is removed 03:20:24 Yeah sure 03:20:38 ok, any question about this topic? 03:20:47 Hi! 03:20:57 shu-mutou: hi shu, thanks for joining 03:21:13 I wrote up the priorities of Zun UI for Pike, please check it. https://etherpad.openstack.org/p/pike-zun-ui 03:21:21 hongbin: I will post my comments on patch if any 03:21:26 #link https://etherpad.openstack.org/p/pike-zun-ui 03:21:55 #action everyone review the zun ui ehterpad: https://etherpad.openstack.org/p/pike-zun-ui 03:22:28 ok, advance topic 03:22:36 #topic Introduce container composition 03:22:45 #link https://review.openstack.org/#/c/437759/ 03:22:58 kevinz: want to drive this one? 03:23:15 kevinz: Yeah 03:23:42 Here is the details. https://etherpad.openstack.org/p/zun-container-composition 03:24:01 Including the yaml file structure and API for "Capsule" 03:25:05 the format of yaml file is like docker-compose? 03:25:33 kevinz: i think you are ready to incorporate the sample yaml file into the spec 03:25:33 FengShengqin: The format is more like Kubernetes 03:26:11 like pod ? 03:26:13 hongbin: OK, I will add it to spec 03:26:20 kevinz: whenever you think it is ready, you can remove the wip , and we will do another iteration of reviews 03:26:21 hongbin: can you explain what is the purpose of this use case in short? 03:26:44 Yeah like a pod 03:26:50 diga: the use case is supporting multi-container application 03:27:01 hongbin: okay 03:27:03 hongbin: OK I will. That's cool 03:27:53 kevinz: yes, this feature looks ready to move forward from my side 03:28:02 hongbin: in this case, we are going to implement app containers scenario 03:28:23 hongbin: only app endpoint will be shared to the end user 03:28:43 diga: don't get what is "app containers scenario" 03:28:44 hongbin: Thanks, I'll continue 03:29:35 diga: i think it is simply the pod use cases 03:29:52 diga: group multiple containers into a single host 03:30:09 hongbin: means, lets say I want to deploy wordpress website, wordpresse app needed (wordpress, mysql etc), so in this case, we are going to start two container simultaneously 03:30:16 hongbin: okay 03:30:38 diga: yes, you can group wordpress and mysql into a capsule 03:30:40 hongbin: ohh its pod like, got it 03:30:49 hongbin: yeah 03:31:11 kevinz: thanks kevin for working on this feature 03:31:29 hongbin: My pleasure :-) 03:31:31 before advance topic, any other questions for kevinz ? 03:32:19 #topic Open Discussion 03:32:22 why group multiple containers into a single host ? 03:33:10 FengShengqin: That will be easy for user to use multiple containers according to their requests 03:33:19 FengShengqin: to support use cases that needs a set of closely-related containers that are pysically collocated 03:34:21 yes, it is basically the pod/compose use cases 03:34:52 i see 03:34:58 any flag or policies like nova server group to control? 03:35:16 containers on a host or some host 03:36:45 Shunli: i think contianers in the capsule would have only one policy: scheduled to the same host 03:37:21 Shunli: you have use cases for supporting additional scheduling policies? 03:38:11 I guess containers like vms, there are anti-affinity use cases. 03:38:26 Shunli: ack 03:39:00 Shunli: i think we can record this use case as a bp, then i willl have the team to review it later 03:39:35 OK. Log a bp first 03:39:54 Shunli: mind i assign you an action item to create the bp? 03:39:59 But i'm not sure how this will relate to 'capsule' 03:40:17 it doesn't have to relate to capsule imo 03:40:19 Sure, I will log one. 03:40:47 #action Shunli created a bp for descriping anti-infinity scheduling use cases 03:41:32 Shunli: btw, i sent you and sudipta an email about the host capability 03:42:36 Shunli: do you have any question about what i said about the host capability? 03:42:37 seems it's drawn in the mails. Let me find it out. 03:42:57 ok 03:43:30 Namrata: lakerzhou : if you want, feel free to chime in and give the team an update of the work you did 03:43:53 Seems I didn't get the mail. Did you send to slzhou@fiberhome.com? 03:44:26 Shunli: don't remember the address, will confirm it 03:44:50 Shunli: i will re-send if hte address is wrong 03:44:57 OK. thx. 03:45:04 np 03:45:32 Thanks hongbin 03:46:00 Namrata: yes, please go ahead and talk about your heat work 03:46:21 yeah sure 03:48:50 Namrata: do you have a chance to update the spec: https://review.openstack.org/#/c/426210/ 03:49:22 Hongbin : was busy with another work 03:49:24 Namrata: huangtianhua give a few suggestions about several things 03:49:30 Namrata: i see 03:49:34 will complete this week 03:49:40 all the patches related to heat 03:49:48 sorry for the inconvinience 03:49:54 Namrata: sure, np 03:50:01 Namrata: thanks for the work 03:50:05 thanks 03:50:09 a quick update of container snapshot. I just tested the following: generate snapshot; verify the snapshot with docker images; created glance image; created new zun container from the glance image; verified the container created properly. 03:50:23 I am working on unit testing codes now 03:50:55 lakerzhou: cool, thanks zhou 03:51:10 np 03:51:42 I will try to complete the BP before BSS release 03:52:05 thx 03:52:15 ok, sounds like we finish the agenda of the meeting 03:52:29 any last minute remark? 03:52:54 seems no, all thanks for joining the meeting, have a good day 03:52:58 #endmeeting