Thanks for the reply.
To be honest, I'm not start from mesos container era. We use docker first, and then try mesos to be a scheduler. It's true, I could control more on mesos framwork. But it's much more costly than k8s. Switch to another containerizer technology may be simple and easy to me, but seems impassible to my company in a period of time. ________________________________ From: haosdent <[email protected]> Sent: Monday, November 21, 2016 9:08:23 AM To: user Subject: Re: Question on Mesos 1.1.0 LaunchGroup Hi, @Qi Feng. Actually you could continue to use docker image via Mesos container. You could refer to https://github.com/apache/mesos/blob/master/docs/container-image.md for more details. [https://avatars1.githubusercontent.com/u/47359?v=3&s=400]<https://github.com/apache/mesos/blob/master/docs/container-image.md> mesos/container-image.md at master · apache/mesos · GitHub<https://github.com/apache/mesos/blob/master/docs/container-image.md> github.com mesos - Mirror of Apache Mesos ... release-0.11.0-incubating-RC3 release-0.11.0-incubating-RC2 release-0.11.0-incubating-RC1 release ... On Mon, Nov 21, 2016 at 5:04 PM, Qi Feng <[email protected]<mailto:[email protected]>> wrote: I don't understand why leave docker. Would we could have launch_group for docker in the future? Or we can only write an executor for that. Thanks. ________________________________ From: haosdent <[email protected]<mailto:[email protected]>> Sent: Monday, November 21, 2016 8:18:13 AM To: user Subject: Re: Question on Mesos 1.1.0 LaunchGroup Yep, only mesos container is supported. On Mon, Nov 21, 2016 at 4:14 PM, Qi Feng <[email protected]<mailto:[email protected]>> wrote: Thanks haosdent. I tried to use docker containerInfo to launch group task, but got "Docker ContainerInfo is not supported on the task". Is it support mesos container only? ________________________________ From: haosdent <[email protected]<mailto:[email protected]>> Sent: Friday, November 18, 2016 4:54:07 PM To: user Subject: Re: Question on Mesos 1.1.0 LaunchGroup Hi, @Qi You may refer `mesos-executor` about how to build `LaunchGroup` https://github.com/apache/mesos/blob/master/src/cli/execute.cpp#L498-L524 ``` operation->set_type(Offer::Operation::LAUNCH_GROUP); ExecutorInfo* executorInfo = operation->mutable_launch_group()->mutable_executor(); executorInfo->set_type(ExecutorInfo::DEFAULT); executorInfo->mutable_executor_id()->set_value( "default-executor"); ... ``` As you see, executor-id is a string here and you could use any string to identify the executor. On Fri, Nov 18, 2016 at 3:47 PM, Qi Feng <[email protected]<mailto:[email protected]>> wrote: I'm trying the LaunchGroup feature. But I find the an executorInfo is required. message LaunchGroup { required ExecutorInfo executor =3D 1; required TaskGroupInfo task_group =3D 2; } What's more, an executor id is required in executorInfo. How would I build = the executorInfo if I use the default executor of mesos? https://github.com/apache/mesos/blob/1.1.x/include/mesos/mesos.proto#L566 Thanks for any reply. -- Best Regards, Haosdent Huang -- Best Regards, Haosdent Huang -- Best Regards, Haosdent Huang
