On Wed, Jan 20, 2016 at 2:04 AM, Marco Massenzio wrote:
> Great thinking, Kapil!
> (I'm one who got the headache :)
>
> However, having recently gone through the effort of having to figure out it
> all, my +1 goes for *good documentation* of what is necessary.
Totally with you on this :)
> When
I am curious if the zookeeper have the same behavior and issue. do we can
setup a metrics to compare the issue with etcd vs zookeeper. it will driver
us to define the correct scope.
2016-01-20 14:42 GMT+08:00 Shuai Lin :
> Hi Benjamin and all,
>
> I'd like to talk about MESOS-1806. Since I took t
Great thinking, Kapil!
(I'm one who got the headache :)
However, having recently gone through the effort of having to figure out it
all, my +1 goes for *good documentation* of what is necessary.
When installing stuff / magic happening behind the scenes, it is always
difficult to ensure it works o
Hi Benjamin and all,
I'd like to talk about MESOS-1806. Since I took this ticket from halfway,
and there was no design doc for it, I have created one based on the current
implementation.
https://docs.google.com/document/d/1ccY0XJoOODpIiGPllSVvl7t-YRrIEE_NavfbZHKPWBs/edit?usp=sharing
Besides, the
On Tue, Jan 19, 2016 at 11:58 PM, James Peach wrote:
>
>> On Jan 19, 2016, at 2:03 PM, Kapil Arya wrote:
>>
>> Hi All,
>>
>> I wanted to get your opinion on installing the 3rdparty packages glog,
>> protobuf, boost and picojson[1] when installing Mesos itself. These
>> packages are required to bu
On Tue, Jan 19, 2016 at 9:08 PM, zhiwei wrote:
> Hi Kapil,
>
> There are two methods to build Mesos modules, one is using installed Mesos
> files, the other is using compiled Mesos files.
The second method is a hack because the first method is not foolproof.
Ideally, one should be able to build a
> On Jan 19, 2016, at 2:03 PM, Kapil Arya wrote:
>
> Hi All,
>
> I wanted to get your opinion on installing the 3rdparty packages glog,
> protobuf, boost and picojson[1] when installing Mesos itself. These
> packages are required to build Mesos modules.
An alternative approach could be to hide
+1 on installing 3rdpart packages.
I used to build a C++ Mesos framework with local/system packages (protobuf,
boost), but protobuf failed because of header file backward compatibility.
I have to go through the Mesos build to include 3rdpart packages and got
following Makefile:
https://github.com/
+1 on *Request -> *Info :).
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform OpenSource Technology, STG, IBM GCG
+86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me
On Mon, Jan 18, 2016 at 7:38 PM, Alex Rukletsov wrote:
> I agree that the borderline between being rela
Hi Kapil,
There are two methods to build Mesos modules, one is using installed Mesos
files, the other is using compiled Mesos files.
Your proposal only affect the first method.
I don't think packaging 3dparty libraries to Mesos is a good solution if
the 3rdparty libraries have their own standard
Hi All,
I wanted to get your opinion on installing the 3rdparty packages glog,
protobuf, boost and picojson[1] when installing Mesos itself. These
packages are required to build Mesos modules.
Currently, a module write has to manually install these 3rdparty
packages, either system-wide or locally
I think you might be confused. The external facing flag is still
`authenticate`. The internal representation of the flag has been changed to
`authenticate_frameworks` a while back, as you alluded to. I added the JIRA
link to the existing TODO last week :)
On Mon, Jan 18, 2016 at 1:23 AM, Alexander
Hi Alex,
Good point. I added some docs for this behavior a few weeks ago:
https://github.com/apache/mesos/commit/6d0619e2e1fbf78411f881f431269539c7d24565
But that appears in a different doc page. You're probably right that
it is worth mentioning here as well -- I'll send a review shortly.
Neil
Thanks Tim
I'll upload the patch shortly ...
- Ezra
From: Timothy Chen
To: "dev@mesos.apache.org"
Date: 19/01/2016 08:02 PM
Subject:Re: Shepherd for MESOS-4369 (Enhance DockerExecuter to
support Docker's user-defined networks)
I'll shepherd this.
Tim
On Tue, Jan 19,
I'll shepherd this.
Tim
On Tue, Jan 19, 2016 at 10:00 AM, Ezra Silvera wrote:
> Hi all,
>
> Anyone is willing to shepherd
> https://issues.apache.org/jira/browse/MESOS-4369 ?
>
> Thanks
>
> Ezra Silvera
>
>
>
Hi all,
Anyone is willing to shepherd
https://issues.apache.org/jira/browse/MESOS-4369 ?
Thanks
Ezra Silvera
On 01/19/2016 03:55 PM, Jan Schlicht wrote:
> Hi Olivier,
>
> status for the "Unified Containerizer" project is tracked under this epic:
> https://issues.apache.org/jira/browse/MESOS-2840
> There's a design document linked in the epic, unfortunately I'm not able to
> access it.
perfect, thanks
>
> status for the "Unified Containerizer" project is tracked under this epic:
> https://issues.apache.org/jira/browse/MESOS-2840
I think this epic is only about Mesos Containerizer support Docker image,
right? Is it same as "Mesos Containerizer to support docker containers"?
On Tue, Jan 19, 2016 at
I think that this is the entry point if you want to get to know more for
latest container
https://github.com/apache/mesos/blob/master/docs/mesos-provisioner.md
On Tue, Jan 19, 2016 at 10:55 PM, Jan Schlicht wrote:
> Hi Olivier,
>
> status for the "Unified Containerizer" project is tracked under
Hi Olivier,
status for the "Unified Containerizer" project is tracked under this epic:
https://issues.apache.org/jira/browse/MESOS-2840
There's a design document linked in the epic, unfortunately I'm not able to
access it.
Cheers,
Jan
On Tue, Jan 19, 2016 at 3:06 PM, Qian Zhang wrote:
> Hi Oli
Hi Olivier,
Here is the doc of MesosContainerizer:
https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md
And you may also find the following docs helpful:
https://github.com/apache/mesos/blob/master/docs/containerizer.md
https://github.com/apache/mesos/blob/master/docs/container
Hi,
I have seen there are some work on Mesos Containerizer to support docker
containers instead of using Docker Containerizer, which would help
support Docker network etc... with Calico for example.
Is there any doc on this available somewhere ? Where is code of the
Mesos Containerizer? (I found Do
One more caveat here is when there are multiple frameworks in the role: one
framework may successfully reserve certain resources but they will be
offered to another framework in the role. Do you think it's worth
mentioning this use case in the doc?
On 18 January 2016 at 23:30, wrote:
> Repositor
23 matches
Mail list logo
