CMake support is not quite mature yet. I think we're at least a couple
months out before it's really ready to rely on, but I'm quite happy to
hear about your bugs! Feel free to file them against me (I'm
`hausdorff` on the JIRA), and I'll make sure they get routed properly.
On Wed, Nov 25, 2015 at
I set up success for it. Because Mesos have cmake support now. Import it as
a cmake project.
On Thu, Nov 26, 2015 at 12:21 PM, Shiyao Ma wrote:
> Hi,
>
> I'd like to browse the mesos code with abilities such as jump to
> definitions, etc.
>
> Ctags and Youcompleteme fall short here.
>
> So I th
Hi,
I'd like to browse the mesos code with abilities such as jump to
definitions, etc.
Ctags and Youcompleteme fall short here.
So I think CLION might be a good way to go, so anybody managed to do that
with CLion?
What's the setup ?
Thanks.
shiyao
I think the six month deprecation period is much better than what Mesos
provides currently. Apache Aurora has recently struggled with how to handle
the current Mesos deprecation policy, adopting a new policy of six months
will make it easier for us to adopt new Mesos releases without backwards
comp
Hi Tommy,
We didn't modify MesosContainerizer container creation but only just
added image support and the ability to inherit runtime configuration
from images.
We're considering different options like runc for OCI but still just
investigating, if you have any more thoughts let us know!
Tim
On
Hi Marco,
Thanks for your comments! I agree that extending "mixed version"
compatibility to N-6 versions is not warranted, at least right now.
Going by lazy consensus: if anyone does NOT like the idea of a six
release deprecation period (~six months), please speak up soon.
Otherwise, I'll writeup
Community growth starts by talking with those interested in your
project. ApacheCon North America is coming, are you?
We are delighted to announce that the Call For Presentations (CFP) is
now open for ApacheCon North America. You can submit your proposed
sessions at
http://events.linuxfoundation.o
A quick glance of the logs doesn't show anything that stands out, apart
from:
--zk_session_timeout="10secs"
which seems to lead to:
Nov 23 16:50:13 node1 mesos-master[17501]: I1123 16:50:13.594151 17521
recover.cpp:111] Unable to finish the recover protocol in 10secs,
retrying
That is the defau
Tim,
interesting on the MesosContainerizer's design, what technology to support
it? runC solution?
2015-11-25 19:09 GMT+08:00 Timothy Chen :
> Hi there,
>
> DockerContainerizer doesn't support isolators simply because we
> delegate all container creation to Docker via docker client, and
> theref
Hi there,
DockerContainerizer doesn't support isolators simply because we
delegate all container creation to Docker via docker client, and
therefore we don't have a way to run our isolators that's in
mesos-slave from docker.
We're working on unified containerizer that brings Docker images to
Meso
https://issues.apache.org/jira/browse/MESOS-4010
On 24 November 2015 at 13:55, Klaus Ma wrote:
> I'd suggest to open a JIRA to trace issue; I think you can append
> master.log & slave.log for owner reference.
>
>
> Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
> Platform Symphony/
Hi all,
We (Frank Scholten and Phil Winder) are currently developing the Mesos
Flocker framework. As part of this framework we want to develop a
custom isolator module which interacts with the Flocker Control
Service.
After creating a simple stub isolator and installing it on one of the
agents we
12 matches
Mail list logo