Thanks, appreciate that. Would you have a high level diagram to show this scenario please,interesting ? ( I hear you say K8s for control plane , Openstack as tenant on top of it and then again Openstack utilizing K8s for application orchestration , did I get it right ?)
Also please share your Summit presentation link ( I Would RSVP and attend ☺ ). Thanks, Sudeep Batra +1.469.975.1645 From: Harshad Nakil [mailto:[email protected]] Sent: Monday, April 17, 2017 11:06 AM To: Sudeep Batra <[email protected]> Cc: Jakub Pavlik <[email protected]>; [email protected] Subject: Re: [Users] Support for Calico Off course users can chose whatever they prefer. Simplicity and openness is in eyes of beholder. Since this open Contrail user group I would like to say what development team intends to do. We think that single contrail instance can solve SDN requirements for 1. Kubernetes for control plane orchestration. 2. Openstack. 3. Kubernetes on this openstack for application orchestration. We would rather fix/implement things that contrail lack rather then make users life complicated by having to deal with multiple SDNs. We would be demoing some of this upcoming openstack summit. Regards -Harshad On Apr 16, 2017, at 9:29 PM, Sudeep Batra <[email protected]<mailto:[email protected]>> wrote: Thanks Jakub and Harshad, Simplicity, opennesss depending on customer needs and ability to scale out individually(so that there is no monolithic dependency) is the key. As I observe that vRouter agent is running in the user space, if we can have the vrouter-agent as a container ,whereas the vrouter continues to run in the Kernel space in Hypervisor it should work seamlessly. (Ref: http://www.opencontrail.org/opencontrail-architecture-documentation/#section1_2 ) Thanks, Sudeep Batra +1.469.975.1645 From: Harshad Nakil [mailto:[email protected]] Sent: Thursday, April 13, 2017 11:00 AM To: Jakub Pavlik <[email protected]<mailto:[email protected]>> Cc: Sudeep Batra <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [Users] Support for Calico Why would use Calico to run Contrail? May be these are Mirantis specific philosophy and not open Contrail position. In kubernetes when you support a SDN you should not need yet another SDN to install and run a given SDN. Hence once Contrail is properly supported in kubernetes you should not need yet another SDN. This is what OpenContrail team intends to do. Regards -Harshad On Apr 13, 2017, at 12:17 AM, Jakub Pavlik <[email protected]<mailto:[email protected]>> wrote: Hi Sudeep, 1) Containerized contrail control plane can run on top of kubernetes, where you can have for instance calico as cni plugin. However you can flannel or any other plugin. The reason for calico is because is very simple. 2) There is huge differences, please take a look on our session https://youtu.be/RMD-ofkqIq0 Jakub On Thu, Apr 13, 2017 at 1:17 AM, Sudeep Batra <[email protected]<mailto:[email protected]>> wrote: Hi All, Appreciate if anyone can help me confirm the below : 1. support for Calico in place of Contrail control cluster for Kubernetes. 2. Difference between Features not supported in Calico compared to Contrail ( like Service Chaining,etc) <image001.png> Thanks, Sudeep Batra +1.469.975.1645<tel:(469)%20975-1645> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org -- Jakub Pavlik +420 602 177 027 [email protected]<mailto:[email protected]> _______________________________________________ Users mailing list [email protected]<mailto:[email protected]> http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
_______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
