This is correct. However, it is probably much easier to implement that I anticipated.
Triggered by your question, I looked into https://issues.apache.org/jira/browse/MESOS-6281 again. I was operating under the impression that we need a Mesos change for proper CNI support in Aurora. Turns out that this is (very likely) not the case. Good news after all :-). From: vincent gromakowski <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, 5 January 2017 at 15:12 To: "[email protected]" <[email protected]> Subject: Re: Aurora cni Hi, Thanks a lot for your answers. As I understand Aurora use a custom executor on top of Mesos to bring additional functionalities and that means we need to reinject the container/Ip mapping in thermos ? Vincent 2017-01-04 16:46 GMT+01:00 Erb, Stephan <[email protected]<mailto:[email protected]>>: Hi Vincent, If you are looking for a multi-tenant PaaS Aurora might be good match. It provides several features specifically designed for multi-tenant environments. For example, the quota support can help to ensure important services can preempt less important instances in case of resource shortage (https://github.com/apache/aurora/blob/master/docs/features/multitenancy.md). Aurora also offers UIs and APIs so that users can find out why their services are not running as expected, without requiring any assistance by cluster operators. Specifically regarding CNI: I have filed https://issues.apache.org/jira/browse/AURORA-1790 because we are interested in CNI support internally as well. We might invest into this eventually but probably not within the next 6 months. However, if anyone else from the community wants to step up here, I am happy to assist! Getting a rough prototype going should not be very hard. Essential one needs plumbing from user/operator input to the Aurora storage and the factory where Mesos tasks are created. If you are interested in the code here are two changes that are very similar in nature https://reviews.apache.org/r/53333/diff/3#index_header and https://reviews.apache.org/r/52588/diff/7#index_header. Doing something similar for CNI should be sufficient for preliminary support in Aurora. However, there are also couple of (important) corner cases that require more thought and planning, most notably the Thermos UI and the part where services are announced into Zookeeper for easy service discovery. Best regards, Stephan From: vincent gromakowski <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, 30 December 2016 at 13:51 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Aurora cni Hi all I am new to aurora and evaluating against marathon for a multi tenant PaaS. I have a question regarding CNI support with tools like Calico. I know a jira exists on it (1790) but I don't understand the difference with marathon which seems to support it. And what would be the effort to make it work on aurora? Thanks for your help. V
