Wednesday, 2017-06-14

*** zhurong has joined #openstack-zun00:45
*** hongbin has quit IRC00:54
*** zhurong has quit IRC01:33
*** zhurong has joined #openstack-zun01:35
openstackgerritShu Muto proposed openstack/zun-ui master: Add parameters for cluster creation  https://review.openstack.org/47377101:44
*** shu-mutou-AWAY is now known as shu-mutou01:47
*** rbudden has quit IRC02:36
*** nicolasbock has joined #openstack-zun02:56
*** Shunli has joined #openstack-zun03:24
*** hongbin has joined #openstack-zun03:51
*** caowei has joined #openstack-zun04:03
*** zhurong has quit IRC04:28
*** zhurong has joined #openstack-zun04:38
*** janki has joined #openstack-zun04:40
*** adisky__ has joined #openstack-zun04:50
openstackgerritMerged openstack/zun-ui master: Add parameters for cluster creation  https://review.openstack.org/47377104:54
*** hongbin has quit IRC05:03
*** hongbin has joined #openstack-zun05:07
*** caowei_ has joined #openstack-zun05:12
*** caowei has quit IRC05:15
*** caowei_ is now known as caowei05:15
*** zhurong has quit IRC05:17
*** hongbin_ has joined #openstack-zun05:19
*** hongbin has quit IRC05:20
*** zhurong has joined #openstack-zun05:20
*** hongbin has joined #openstack-zun05:23
*** hongbin_ has quit IRC05:24
*** caowei has quit IRC05:24
*** caowei has joined #openstack-zun05:25
*** hongbin_ has joined #openstack-zun05:26
*** hongbin has quit IRC05:27
*** hongbin has joined #openstack-zun05:28
*** hongbin_ has quit IRC05:30
*** hongbin_ has joined #openstack-zun05:30
*** hongbin__ has joined #openstack-zun05:33
*** hongbin has quit IRC05:33
*** hongbin_ has quit IRC05:34
*** hongbin has joined #openstack-zun05:35
*** hongbin__ has quit IRC05:37
*** hongbin_ has joined #openstack-zun05:38
*** hongbin has quit IRC05:40
*** hongbin has joined #openstack-zun05:42
*** hongbin_ has quit IRC05:43
*** caowei_ has joined #openstack-zun06:02
*** caowei has quit IRC06:05
*** caowei_ is now known as caowei06:05
*** jwcroppe_ has joined #openstack-zun06:07
*** jwcroppe has quit IRC06:09
*** caowei_ has joined #openstack-zun06:16
*** caowei has quit IRC06:19
openstackgerritShu Muto proposed openstack/zun-ui master: Use Angular-Schema-Form for cluster creation  https://review.openstack.org/47407206:20
openstackgerritShu Muto proposed openstack/zun-ui master: Use Angular-Schema-Form for container creation  https://review.openstack.org/47407206:22
*** caowei_ has quit IRC06:23
*** caowei has joined #openstack-zun06:26
*** sudipto has joined #openstack-zun06:33
*** sudipto has quit IRC06:33
*** sudipto has joined #openstack-zun06:33
*** sudipto_ has joined #openstack-zun06:33
openstackgerritDai Dang Van proposed openstack/zun master: Fix api-ref generation  https://review.openstack.org/47408506:57
*** hongbin_ has joined #openstack-zun06:59
*** jwcroppe_ has quit IRC06:59
*** hongbin has quit IRC07:01
jankimkrai, hey07:01
*** hongbin has joined #openstack-zun07:08
openstackgerritShunli Zhou proposed openstack/zun master: Add label filter  https://review.openstack.org/46660307:08
*** arund has joined #openstack-zun07:10
*** hongbin_ has quit IRC07:11
*** hongbin has quit IRC07:13
*** sudipto_ has quit IRC07:16
*** sudipto has quit IRC07:16
*** sudipto has joined #openstack-zun07:17
*** sudipto has quit IRC07:17
*** sudipto has joined #openstack-zun07:17
*** sudipto_ has joined #openstack-zun07:17
*** hongbin has joined #openstack-zun07:18
*** hongbin_ has joined #openstack-zun07:21
*** hongbin has quit IRC07:22
*** hongbin has joined #openstack-zun07:23
*** hongbin_ has quit IRC07:25
*** arund has quit IRC07:28
*** diga has joined #openstack-zun07:30
*** egonzalez has joined #openstack-zun07:46
*** hongbin_ has joined #openstack-zun07:47
*** hongbin has quit IRC07:48
*** egonzalez has quit IRC07:55
*** egonzalez has joined #openstack-zun07:58
openstackgerritShu Muto proposed openstack/zun-ui master: Use Angular-Schema-Form for container creation  https://review.openstack.org/47407208:09
openstackgerritShu Muto proposed openstack/zun-ui master: Add update action for container  https://review.openstack.org/47410108:11
*** hongbin has joined #openstack-zun08:21
*** hongbin__ has joined #openstack-zun08:23
*** hongbin_ has quit IRC08:24
*** hongbin has quit IRC08:26
*** hongbin has joined #openstack-zun08:26
*** hongbin__ has quit IRC08:28
*** hongbin_ has joined #openstack-zun08:30
openstackgerritShu Muto proposed openstack/zun-ui master: Add update action for container  https://review.openstack.org/47410108:30
*** hongbin has quit IRC08:31
*** hongbin has joined #openstack-zun08:44
openstackgerritShu Muto proposed openstack/zun-ui master: Enable to rename container in update action  https://review.openstack.org/47411308:44
*** hongbin_ has quit IRC08:45
openstackgerritMadhuri Kumari proposed openstack/zun master: Add api-ref for container create  https://review.openstack.org/46938608:45
*** hongbin_ has joined #openstack-zun08:46
*** hongbin has quit IRC08:48
*** hongbin has joined #openstack-zun08:49
*** hongbin_ has quit IRC08:51
*** hongbin_ has joined #openstack-zun08:53
*** hongbin has quit IRC08:53
openstackgerritMadhuri Kumari proposed openstack/zun master: Add missing compute_node etcd API  https://review.openstack.org/47253808:57
openstackgerritShu Muto proposed openstack/zun-ui master: Fix execute action  https://review.openstack.org/47412609:12
openstackgerritfeng.shengqin proposed openstack/python-zunclient master: [WIP]Enhance api version support in CLI  https://review.openstack.org/47412809:16
openstackgerritShubhendu Poothia proposed openstack/zun master: Set access_policy for messaging's dispatcher  https://review.openstack.org/47413409:21
*** diga has quit IRC09:24
*** Shunli has quit IRC09:32
*** zhurong has quit IRC09:40
openstackgerritfeng.shengqin proposed openstack/python-zunclient master: [WIP]Enhance api version support in CLI  https://review.openstack.org/47412809:48
*** shu-mutou is now known as shu-mutou-AWAY10:06
*** manikanta_tadi has joined #openstack-zun10:21
*** hongbin_ has quit IRC10:27
*** sudipto has quit IRC11:43
*** sudipto_ has quit IRC11:43
*** rbudden has joined #openstack-zun11:44
*** caowei has quit IRC12:01
*** sudipto_ has joined #openstack-zun12:50
*** sudipto has joined #openstack-zun12:50
*** catintheroof has joined #openstack-zun12:52
*** openstackgerrit has quit IRC13:18
*** lakerzhou has joined #openstack-zun13:19
*** jwcroppe has joined #openstack-zun13:40
*** zhurong has joined #openstack-zun13:43
*** hongbin has joined #openstack-zun14:37
*** janki has quit IRC14:38
*** zhurong has quit IRC14:49
*** exploreshaifali has joined #openstack-zun15:38
*** openstackgerrit has joined #openstack-zun15:56
openstackgerritMerged openstack/python-zunclient master: Updated from global requirements  https://review.openstack.org/47292715:56
*** vikasc has quit IRC16:44
*** sudipto has quit IRC16:51
*** sudipto_ has quit IRC16:51
*** egonzalez has quit IRC16:55
*** catintheroof has quit IRC17:02
*** catintheroof has joined #openstack-zun17:03
lakerzhouhongbin, I have few questions about the capsule feature. Is the implementation based on docker compose api only?17:05
lakerzhouHongbin, according to the spec, we are defining something between docker compose and k8ts pods.17:07
lakerzhouHongbin, docker compose is just a way to run an application consisting of multiple micro-services, which share the yml model, NOT cgroup, not IP address, not even a host.,17:11
lakerzhouhongbin, while k8ts pods are quite different. user will not create pod directly. It is managed by k8ts.17:14
lakerzhouhongbin, my concerns are mainly on the networking side for capsule. If it is close to docker compose, we are missing networking fields in yml modeling.17:15
lakerzhouhongbin, if it is similar to k8ts pod, e.g. reside within the same host always, then all the containers in a pod share the same network namespace/drivers.17:18
lakerzhouHongbin, I need some guidance on the networking consideration for capsule, when we introduce SR-IOV for example. I will move on and focus on container-only SR-IOV support for now.17:20
hongbinlakerzhou: i think you can consider it as a pod from networking perspective17:38
hongbinlakerzhou: that is, all containers inside a capsule share a network namespace17:38
lakerzhouhongbin, it is my understanding of capsule so far. But how to create the individual containers while sharing the same network namespace USING DOCKER is a puzzle to me.17:41
hongbinlakerzhou: the approach we are using right now is to create an infra container, then create a real container that joins the network namespace of the infra container17:43
*** sudipto has joined #openstack-zun17:45
*** sudipto_ has joined #openstack-zun17:46
hongbinlakerzhou: the trick is this option: https://github.com/openstack/zun/blob/master/zun/container/docker/driver.py#L9217:46
lakerzhouhongbin, according to docker's Container Network Model, there are only three components: Sandbox (network configurations), endpoints(service), network (can be single-host or multi-hosts).17:47
lakerzhouhongbin, sharing the sandbox, meaning sharing network configuration. I agree.17:49
hongbinlakerzhou: i think our definition of sandbox is different from the libnetwork definition of sandbox17:49
hongbinlakerzhou: our definition of sandbox is just an infra container17:50
lakerzhouhongbin, I was referring to the official libnetwork doc: https://github.com/docker/libnetwork/blob/master/docs/design.md17:52
hongbinlakerzhou: then "sandbox" in zun is a "docker container" in their doc17:53
lakerzhouhongbin, the way VM using SR-IOV is to create a SR-IOV port, then attach the port to VM (as nova boot option). I am trying to find the similar option in the container world.17:55
hongbinlakerzhou: ok, let me check17:57
lakerzhouhongbin, I originally thought it is similar to endpoint.join function -- attach an endpoint to a container17:57
lakerzhouhongbin, but now I am not so sure. Nevertheless, endpoint is similar to the neutron port concept to me.17:59
hongbinlakerzhou: not sure if you see this: https://docs.openstack.org/developer/kuryr-libnetwork/devref/libnetwork_remote_driver_design.html18:00
*** sudipto_ has quit IRC18:01
*** sudipto has quit IRC18:01
hongbinlakerzhou: it looks it is similar to endpoint.join18:01
lakerzhouhongbin, if endpoint are the same counterpart in container world, then each endpoint connecting to SRIOV network will consume a VF, e.g. I don't think we can share it in a capsule. I am just trying connect my previous concern back to SR-IOV design.18:02
lakerzhouhongbin, I did not find the link you sent, it is exactly what I wanted to see. Let me read through it.18:03
hongbinlakerzhou: ack18:04
*** nicolasbock has quit IRC18:04
*** nicolasbock has joined #openstack-zun18:05
hongbinlakerzhou: i think yes, if users choose to use capsule instead of an individual container, then they should expect all containers inside a capsule can consume a VF18:06
hongbinbrb18:07
hongbinback18:12
lakerzhouhongbin, I agree the goal is to have all containers within a capsule sharing same VF18:14
lakerzhouhongbin, but an endpoint can only attached to one container.18:18
hongbinlakerzhou: yes, which is the infra container18:18
hongbinlakerzhou: only the infra container follows the libnetwork model18:18
lakerzhouhongbin, I see.18:19
hongbinlakerzhou: all containers inside a capsule won't have any endpoint since it simply share the network namespace of the infra container18:19
lakerzhouhongbin, got it.18:20
hongbinok18:21
hongbini will talk to kevin later, i think the capsule should have its own API, since it is duplicated with the container API18:22
hongbinmy thinking is to have zun-api serve the container API, and have another process (i.e. zun-capsule-api) that serves the capsule API18:23
hongbinhopefully, it will make everything clear to end-users18:23
hongbineventually, i think capsule can be an optional add-on feature18:25
hongbinlakerzhou: what do you think?18:26
hongbinfor sr-iov implementation, i think the implementation for container and capsule should be the same, because capsule is also a container18:27
hongbin(from networking point of view)18:28
lakerzhouhongbin, sorry was away from my desk. I am thinking zun capsule client side only parses the yml and send json to the server. Server will do all the handing. the yml will grow to our single-host orchestration model18:29
lakerzhouhongbin, in the future, we might have a separated multi-host orchestration model build on top of capsule.18:30
hongbinlakerzhou: yes, that could be a direction18:31
lakerzhouhongbin, I got your point. I will assume capsule is a container now, and leave the implementation details of sharing network namespace to capsule.18:32
hongbinlakerzhou: yes, i think that is a right approach18:33
*** exploreshaifali has quit IRC18:49
*** exploreshaifali has joined #openstack-zun18:51
*** exploreshaifali has quit IRC19:02
*** jwcroppe has quit IRC19:05
*** jwcroppe has joined #openstack-zun19:06
*** jwcroppe has quit IRC19:11
*** exploreshaifali has joined #openstack-zun19:17
*** nicolasbock has quit IRC19:22
*** exploreshaifali has quit IRC20:15
*** jwcroppe has joined #openstack-zun20:52
*** lakerzhou has quit IRC20:52
*** jwcroppe has quit IRC20:52
*** jwcroppe has joined #openstack-zun20:52
*** adisky__ has quit IRC22:37
*** catintheroof has quit IRC23:09
*** hongbin has quit IRC23:46

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