Chinese version below/ 中文详情请见下文
In order to allow for more submissions, we have extended the CFP deadline
for MesosCon Asia until April 5th 11:59pm PDT.
http://events.linuxfoundation.org/events/mesoscon-asia/program/cfp
None of the other submission dates have changed. Community voting on
submissi
Thanks. Good to see it is already being tracked.
On 2017-03-20 14:39 (-0600), Avinash Sridharan wrote:
> Hi Marcus,
> The reason we need connectivity from the container's network namespace to
> the host network namespace is that the Mesos executor running in the
> container's network namespace
Hi Marcus,
The reason we need connectivity from the container's network namespace to
the host network namespace is that the Mesos executor running in the
container's network namespace needs to register back with the agent in
order to send TASK updates about the container to the agent. Without this
Hello,
I'm trying to create a custom authentication and I was wondering if anyone
could give me some help.
Is there any kind of documentation regarding the authentication process?
What about examples and/or "templates"? (i.e. getting the credentials from
a database?
Any kind of help is more tha
Thanks for taking the time to respond.
On 2017-03-17 13:02 (-0600), Avinash Sridharan wrote:
> Hi Marcus,
> The CNI Spec you are seeing is the latest SPEC of v0.3 . Mesos currently
> supports v0.2 and below. You can check out the by looking at the "tags" in
> the CNI repo. For e.g.,
> https://g
http://mesos.apache.org/documentation/latest/cni/
"For Mesos, the executors launched as containers need to register with the
Agent in order for a task to be successfully launched. Hence, it is imperative
that the Agent IP is reachable from the container IP and vice versa. "
Can anyone shed some
