deciding votes by 6pm Pacific today, I'll extend the
vote for another day.
On Thu, Jul 9, 2015 at 6:09 PM, Khanduja, Vaibhav vaibhav.khand...@emc.com
wrote:
+1
Sent from my iPhone. Please excuse the typos and brevity of this message.
On Jul 9, 2015, at 6:07 PM, Adam Bordelon
Related: https://issues.apache.org/jira/browse/MESOS-3024 HTTP endpoint
authN is enabled merely by specifying --credentials
We cannot rely on --credentials as the only way to enable/disable HTTP
endpoints, as web auth should not be tied so closely to framework/slave
auth. There needs to be a
of
'required'. That's an API change, which would be nice to go into 0.23.0
as
well.
So, not a -1 per se, but if you are willing to cut another RC, I can
land
the fixes today. Sorry for the trouble.
On Thu, Jul 16, 2015 at 11:48 AM, Adam Bordelon a...@mesosphere.io
wrote:
+1 (binding
it a blocker.
Can't update the spreadsheet. So here are the commits I would like
cherry-picked.
fc85cc512b7767fc2e3921b15cf6602c0c68593e
bfe6c07b79550bb3d1f2ab6f5344d740e6eb6f60
Thanks Adam.
On Thu, Jul 16, 2015 at 7:39 PM, Adam Bordelon a...@mesosphere.io
wrote:
The 7 day voting period
...@mesosphere.io
wrote:
Reminder: The Mesos Community Developer Sync will be happening today at
3pm Pacific.
To participate remotely, join the Google hangout:
https://plus.google.com/hangouts/_/twitter.com/mesos-sync
On Thu, Jun 18, 2015 at 7:22 AM, Adam Bordelon a...@mesosphere.io wrote
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Dockerized slaves will properly recover Docker
Release Candidate 2 did not pass, due to MESOS-3025.
I just cut rc3 and opened the vote (in a separate thread).
On Thu, Jul 9, 2015 at 5:20 PM, Ian Downes idow...@twitter.com wrote:
No it doesn't block me (I normally compile without python...).
On Thu, Jul 9, 2015 at 4:48 PM, Adam Bordelon
PM, Adam Bordelon a...@mesosphere.io wrote:
In case it wasn't obvious, rc1 did not pass the vote, due to a few build
and unit test issues.
Most of those fixes have been committed, so we will cut rc2 when the last
blocker is resolved.
This is your last chance to get any recently committed
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Dockerized slaves will properly recover Docker
?selectPageId=12326227
On Tue, Jul 7, 2015 at 1:59 PM, Adam Bordelon a...@mesosphere.io wrote:
-1 (non-binding) Network isolator will not compile.
https://issues.apache.org/jira/browse/MESOS-3002
The changes for MESOS-2800
https://issues.apache.org/jira/browse/MESOS-2800 to Rename
OptionT::get
Gidon,
If your allocation module is capable of sending protobuf messages to the
master, you could send a KillTaskMessage with the proper frameworkId and
taskId and hack a way around the if condition at
https://github.com/apache/mesos/blob/0.23.0-rc1/src/master/master.cpp#L2946
I think in general,
Ryuichi, you've been added. Thanks for contributing!
Join us at MesosCon: http://events.linuxfoundation.org/events/mesoscon
Cheers,
-Adam-
On Sat, Jul 4, 2015 at 6:37 AM, Ryuichi Okumura oku...@okuryu.com wrote:
Hi there,
I've created an issue on JIRA, so I want to assign to myself on the
Hello Mesos community,
Please vote on releasing the following candidate as Apache Mesos 0.23.0.
0.23.0 includes the following:
- Per-container network isolation
- Upgraded minimum required compilers to GCC 4.8+ or
What version of Mesos are you using? Something similar was fixed in 0.22.1.
See https://issues.apache.org/jira/browse/MESOS-1837 and
https://issues.apache.org/jira/browse/MESOS-2583
If you're running mesos-slave inside a Docker container, there are other
complications to consider. See
, 2015 at 1:22 AM, Alex Rukletsov a...@mesosphere.com wrote:
Hi Haosdent,
Do you have a shepherd for this change?
On 1 Jul 2015 8:06 am, Adam Bordelon a...@mesosphere.io wrote:
The original ticket MESOS-1865
https://issues.apache.org/jira/browse/MESOS-1865 argues the point that
requesting
The original ticket MESOS-1865
https://issues.apache.org/jira/browse/MESOS-1865 argues the point that
requesting state data (e.g. tasks.json) from a non-leading master should
not return 200 OK status code with empty data, as that is misleading. It
should either return an error code, or valid data.
Many setups use something like systemd to ensure that if the slave is
shutdown/killed, it will start up again, causing it to register as a new
slaveId. This should solve your first point, An.
On Tue, Jun 30, 2015 at 8:20 AM, Roger Ignazio m...@rogerignazio.com wrote:
I recently posted a similar
+1!
On Tue, Jun 23, 2015 at 4:31 PM, Yan Xu y...@jxu.me wrote:
So I'd like to resurface this topic. The last attempt
https://reviews.apache.org/r/33090/ to remove things under frameworks/
was put off because scripts under ec2/ still reference these frameworks.
However we seem to have
Aditi,
driver-stop() will shutdown the schedulerDriver, and passing in 'true'
just means that it doesn't shutdown the framework within Mesos and kill its
tasks. You will have to manually create a new SchedulerDriver for it to
reregister with Mesos, whether you do that within your still-running
Aha! You also need to set the FrameworkInfo.failover_timeout to a non-zero
value. If it is 0, then Mesos will instantly shutdown your framework when
the schedulerdriver disconnects.
On Fri, Jun 19, 2015 at 9:56 AM, haosdent haosd...@gmail.com wrote:
From you gist, I think `reregistered` would
/_/mesosphere.io/mesos-developer
On Mon, Jun 15, 2015 at 10:46 AM, Adam Bordelon a...@mesosphere.io wrote:
As previously mentioned, we would like to host additional Mesos developer
syncs at our new Mesosphere HQ at 88 Stevenson St (tucked behind Market
2nd), starting this Thursday from 9-11am
Thanks,
-Adam-
On Thu, May 28, 2015 at 10:08 AM, Vinod Kone vinodk...@gmail.com wrote:
Cool.
Here's the agenda doc
https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
for next week that folks can fill in.
On Thu, May 28, 2015 at 9:52 AM, Adam Bordelon
You can query the slave's state.json to get the container ID.
See the previous thread:
http://search-hadoop.com/m/0Vlr6OtCiO1p8ypc2/mesos+accessing+programmatticallysubj=Re+Accessing+stdout+stderr+of+a+task+programmattically+
On Fri, Jun 12, 2015 at 2:35 AM, Olivier Sallou olivier.sal...@irisa.fr
+1 to removing Closed. In other projects, I've seen Resolved mean that a
supposed fix has been committed, and Closed means that somebody (QA?
Reporter?) has verified the fix, but we don't wait for verification, so
it's probably pointless for us.
+1 to removing Reopened, and just going back to
Wow, what a response! Allow me to attempt to summarize the sentiment so far.
Let's start with the implicit question,
*0. Should we rename Mesos Slave?*
+1 (Explicit approval) 12, including 7 from JIRA
+0.5 (Implicit approval, suggested alternate name) 18
-0.5 (Some disapproval, wouldn't block it)
In the spirit of transparency in our release planning, I’d like to propose
some guidelines for our JIRA use that will help us all track the release
progress together and discover where we can help out others. The Mesos 0.23
release will be gated by a few major features (SSL, Persistent Volumes,
Welcome to the Mesos community Aditi!
I'm very excited to see you moving forward with Updating FrameworkInfo.
Have you reached out to Vinod to Shepherd/mentor you through the process?
There's a bit more history in the Epic JIRA MESOS-703
https://issues.apache.org/jira/browse/MESOS-703. Also note
I'd recommend filing a JIRA, since that's how we're tracking all our issues.
I have added 'rji' as a Contributor in Mesos JIRA, so now you can have
tasks assigned to yourself.
I haven't seen any specific patch-submission documentation for mesos/site.
DLester may know better.
Best website doc I've
Robin, thanks for your interest in compiling and running Mesos on arm64.
I have added you as a JIRA contributor and assigned the JIRA to you.
Let's try to find you a Shepherd who can review and commit these changes
for you.
TimStClair and Till have been involved in previous ARM issues: MESOS-1693
There has been much discussion about finding a less offensive name than
Slave, and many of these thoughts have been captured in
https://issues.apache.org/jira/browse/MESOS-1478
I would like to open up the discussion on this topic for one week, and if
we cannot arrive at a lazy consensus, I will
Roshan, do you even have Java installed on your machine? If not, you can
disable Java support in Mesos by specifying `./configure --disable-java`
On Thu, May 28, 2015 at 4:42 AM, Alex Rukletsov a...@mesosphere.com wrote:
Roshan,
Let's assume the configure script is right: could you please
I don't know of a C++ framework that uses docker containers yet, but for a
simple example C++ framework, check out the RENDLER:
https://github.com/mesosphere/RENDLER/tree/master/cpp
For a docker-enabled framework written in Go, try Swarm:
Hi Joe,
Thanks for organizing this. I just want to make sure we handle our
community hangouts according to Apache guidelines. Since this is a
community meeting for an Apache project, let's make sure that everybody is
invited and allowed in, and that the notes are written up and shared
afterwards.
Shuai Lin,
You'll also want to find a Shepherd for MESOS-2724 to help you assess the
need, design, interaction with other features, etc.
I would suggest Tim Chen, since he's been very involved in the Docker
containerizer so far.
On Tue, May 26, 2015 at 10:31 PM, Vinod Kone vinodk...@gmail.com
Are you running mesos-slave itself inside a docker container? We recently
fixed problems with this.
See https://issues.apache.org/jira/browse/MESOS-2115
On Tue, May 26, 2015 at 6:54 AM, Olivier Sallou olivier.sal...@irisa.fr
wrote:
On 05/26/2015 03:44 PM, Olivier Sallou wrote:
Hi,
I could
Thanks for the write up Ben!
On Tuesday, February 10, 2015, Dominic Hamon
dha...@twitter.com.invalid
wrote:
Well, we should probably do that anyway :)
On Feb 10, 2015 2:25 AM, Adam Bordelon a...@mesosphere.io
javascript:; wrote:
+1
Even better would be to address Unassigned issues marked Accepted (with
or without the 'newbie' label), since we've already acknowledged that
they're worth fixing, and you're more likely to get a quick review of your
patch.
The github.com/mesosphere/ org is for projects under the direction of the
company Mesosphere. Probably not the right place unless you want to donate
the code to Mesosphere.
github.com/mesos/ is the community repo, administered by Apache Mesos
committers, but not under the direct jurisdiction of
As far as I understand, hadoop-mesos is not an official Apache subproject
of the Apache Mesos project anymore, and is not managed by the Apache
Software Foundation. It started as a part of the original Mesos project
(even pre-Apache), but was later (post-Apache?) moved out to the 'mesos'
community
Colin, these /ec2 scripts haven't seen much love in a while, and we may
want to move them out of the main repo.
I'm not sure if it's worth keeping these up, but if you figure them out,
feel free to submit a patch.
The question of Mesos on AWS has come up before:
Jim was able to join after I opened the hangout.
Jim, I think you intended to send to d...@myriad.incubator.apache.org
On Wed, May 6, 2015 at 10:06 AM, Elizabeth Lingg elizab...@mesosphere.io
wrote:
I've heard rumors that there is a Core Mesos team meeting at this time. :)
That could be why
.
- Original Message -
From: Adam Bordelon a...@mesosphere.io
To: dev dev@mesos.apache.org, u...@mesos.apache.org
Sent: Tuesday, May 5, 2015 1:21:37 AM
Subject: [RESULT][VOTE] Release Apache Mesos 0.22.1 (rc6)
Hi all,
The vote for Mesos 0.22.1 (rc6) has passed with the following
Hi all,
The vote for Mesos 0.22.1 (rc6) has passed with the following votes.
+1 (Binding)
--
Timothy Chen
Niklas Nielsen
Vinod Kone
+1 (Non-binding)
--
Nikolay Borodachev
Elizabeth Lingg
Jörg Schad
Alexander Rojas
Tomas Barton
There were
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.22.1.
0.22.1 is a bug fix release and includes the following:
* [MESOS-1795] - Assertion failure in state abstraction crashes JVM.
*
In addition to a pool of IPs, we've also discussed other cluster-wide or
globally managed resources, like NAS/SAN bandwidth, site licenses, etc.
We'll be filing a JIRA on that soon, and we'd love to have your input.
As for allocator modules, the core functionality landed in MESOS-2160
/local/repositories/releases/content/org/apache/mesos/mesos/0.22.1-rc6/mesos-0.22.1-rc6.jar
On Tue, Apr 28, 2015 at 4:39 PM, Adam Bordelon a...@mesosphere.io wrote:
Looks like we've got a new blocker:
https://issues.apache.org/jira/browse/MESOS-2668
The patch is up for review already, and we'll cut
Looks like we've got a new blocker:
https://issues.apache.org/jira/browse/MESOS-2668
The patch is up for review already, and we'll cut a Mesos-0.22.1-rc6 once
it's in.
Any other patches that need to make it into rc6?
On Fri, Apr 24, 2015 at 5:56 PM, Adam Bordelon a...@mesosphere.io wrote:
Hi
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.22.1.
0.22.1 is a bug fix release and includes the following:
* [MESOS-1795] - Assertion failure in state abstraction crashes JVM.
*
on this? Is the spreadsheet
up-to-date?
On Wed, Apr 8, 2015 at 1:00 AM, Adam Bordelon
a...@mesosphere.io
wrote:
Hi Adam,
Yes, once we have finalized the scope of the point
release,
Niklas
will
send out an announcement of Mesos
Hi Adam,
Yes, once we have finalized the scope of the point release, Niklas will
send out an announcement of Mesos 0.22.1-rc1 (release candidate) which we
would love you to test any way you can. The email will contain instructions
for building the release candidate and voting in the thread. See
Hi Thomas,
You might be looking for a custom (external) containerizer. The
containerizer is what creates the container that the executor is run in, so
you should not have an executor launching another containerizer. If you
want to modify/control the docker run commands (besides specifying
+1 to moving these out to https://github.com/mesos/framework even if they
are used, in which case we should open an issue tracker for each separate
project and give write permissions to that repo to anyone willing to
maintain it.
On Mon, Apr 6, 2015 at 12:10 PM, Yan Xu y...@jxu.me wrote:
There
We do accept Pull-Requests https://github.com/apache/mesos/pulls for
small patches, especially (markdown) documentation patches; but for larger
code changes we prefer the issue tracking, multi-line comments, and
incremental diffs provided by ReviewBoard.
On Tue, Mar 31, 2015 at 10:55 AM, haosdent
Reminder: We're having another Mesos Developer Community Sync this
Thursday, April 2nd from 3-5pm Pacific.
Agenda:
https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing
To Join: follow the BlueJeans instructions from the recurring meeting
invite at the
In payment for asking such an obvious question, could we get a description
of how you are (or are considering) using Apache Mesos at EMC? If you're
already using Mesos in production, could we get permission to add you to
the Powered By Mesos
+1 (binding)
make check passes on Ubuntu 14.04 and Mac OS X (buildbot)
On Mon, Mar 23, 2015 at 3:44 PM, Elizabeth Lingg elizab...@mesosphere.io
wrote:
+1 (Tested with Chronos)
-Elizabeth
On Mon, Mar 23, 2015 at 3:40 PM, Ben Whitehead
ben.whiteh...@mesosphere.io wrote:
+1 (non-binding)
there be?
On Monday, March 23, 2015, Dario Rexin da...@mesosphere.io wrote:
+1 (non-binding)
tested with Marathon
On 24 Mar 2015, at 00:03, Adam Bordelon a...@mesosphere.io wrote:
+1 (binding)
make check passes on Ubuntu 14.04 and Mac OS X (buildbot)
On Mon, Mar 23, 2015 at 3:44 PM, Elizabeth
Mesos 0.22 will also support task labels
https://issues.apache.org/jira/browse/MESOS-2120
These could easily be tied to docker image/container labels as those are
launched as Mesos tasks.
This is in addition to the existing slave --attributes.
On Tue, Mar 17, 2015 at 7:21 AM, haosdent
There's also the previously discussed ResizeTask primitive:
https://issues.apache.org/jira/browse/MESOS-1279
Yifan wrote an initial proof-of-concept patch that could probably be
resurrected and cleaned up.
On Fri, Mar 13, 2015 at 2:28 PM, Tim St Clair tstcl...@redhat.com wrote:
fwiw - other
Added you as a contributor. Thanks for finding and fixing the bug!
You should ask around IRC/dev@ for a Shepherd (reviewer) for your fix.
On Wed, Mar 11, 2015 at 3:48 PM, Joseph Lee
joe.lee.three.thous...@gmail.com wrote:
Greetings!
I just filed
Agenda and running notes for this month's meeting are being collected in:
https://docs.google.com/document/d/1BMX7M54HXFxSbaURaM0PcRQoFiflRSDtnpQN0sW-_HM/edit?usp=sharing
Feel free to add any new agenda items at the bottom
On Thu, Mar 5, 2015 at 1:22 PM, Dave Lester d...@davelester.org wrote:
:18, Adam Bordelon a...@mesosphere.io wrote:
Looks like https://reviews.apache.org/r/26150/ was submitted with a
basic
libprocess benchmark.
See the source and tests (and `make bench` target) under
https://github.com/apache/mesos/tree/master/3rdparty/libprocess
On Fri, Feb 20, 2015 at 7
Looks like https://reviews.apache.org/r/26150/ was submitted with a basic
libprocess benchmark.
See the source and tests (and `make bench` target) under
https://github.com/apache/mesos/tree/master/3rdparty/libprocess
On Fri, Feb 20, 2015 at 7:16 AM, Atri Sharma atri.j...@gmail.com wrote:
Looks
Don't think anybody's actively working on it. See MESOS-314
https://issues.apache.org/jira/browse/MESOS-314 for cpuset
On Tue, Feb 10, 2015 at 11:39 PM, Chester Kuo chester@gmail.com wrote:
Hi dev,
Just checking with current Mesos and i didn't see it utilize NUMA
system of memory/CPU
Somebody recently pointed to the riak-debug [1] tool as another example.
[1] https://github.com/basho/riak/blob/develop/rel/files/riak-debug
On Mon, Feb 9, 2015 at 12:04 PM, Cody Maloney c...@mesosphere.io wrote:
It would be nice if we auto-packaged up backtraces so they could be easily
Added chesterkuo. You should be able to assign issues to yourself now.
On Wed, Feb 4, 2015 at 7:17 PM, Chester Kuo chester@gmail.com wrote:
Hi ,
Are there anyone can help to add me into contributor list so i can
work on this issue/feature ?
chesterkuo
Chester
On Fri, Jan 30, 2015
Also note that any unused resources from an offer passed to LaunchTasks
will be automatically declined (and potentially reoffered with a new
offerId).
Thus, you cannot do LaunchTasks(task1, offer1); LaunchTasks(task2,
offer1); since the remainder of offer1 will have been declined and any
future
Just make sure you only send one LaunchTasksMessage per slave, although
that message could contain multiple tasks launched on a collection of
offers from the same slave.
You mention that launching 1000s in the same message causes Mesos to crash.
Do you have a crash stack available for this?
You
(The JIRA:)
https://issues.apache.org/jira/browse/MESOS-2272
On Mon, Jan 26, 2015 at 10:50 PM, Kapil Arya ka...@mesosphere.io wrote:
PS: I have created a Jira and have published the following RRs:
1. https://reviews.apache.org/r/30294/
2. https://reviews.apache.org/r/30295/
3.
How about InternetAddressStorage (or just InternetAddress), since we don't
like abbreviations in our code?
(Or if 'in_ is short for something else, use it instead.)
On Mon, Jan 26, 2015 at 11:07 AM, Evelina Dumitrescu
evelina_dumitre...@yahoo.com.invalid wrote:
I renamed the IP::Address class
Confirmed. See https://reviews.apache.org/r/29887/ for a potential fix.
On Wed, Jan 14, 2015 at 11:24 AM, Vinod Kone vinodk...@gmail.com wrote:
I believe this is https://issues.apache.org/jira/browse/MESOS-2050.
@Till can you confirm?
On Wed, Jan 14, 2015 at 8:51 AM, Niklas Nielsen
FYI, Mesos wasn't actually considering TASK_ERROR a terminal state until
now (0.22). No impact if you weren't using it yet.
commit 1c80d845431a57dd8c20e636ab7fc313602e4b49
Author: Connor Doyle con...@mesosphere.io
Date: Wed Jan 7 13:33:16 2015 -0800
TASK_ERROR is terminal
TASK_ERROR
FYI: Mesosphere will be submitting a talk or two, but it'd be good to get
the rest of the community involved too!
-- Forwarded message --
From: Rich Bowen rbo...@rcbowen.com
Date: Mon, Jan 5, 2015 at 9:40 AM
Subject: ApacheCon North America 2015 Call For Papers
To: dev
You might not have `perf` installed. See
https://issues.apache.org/jira/browse/MESOS-2166
And the related thread starting at
http://www.mail-archive.com/user%40mesos.apache.org/msg01267.html
Ratnadeep,
Please see Tim StClair's writeup:
http://timothysc.github.io/blog/2014/09/08/mesos-breeze/
Looks like he's already all over that bugzilla issue, so I'll let him
follow up with you there.
On Sat, Dec 20, 2014 at 10:03 PM, Ratnadeep Debnath
rtn...@fedoraproject.org wrote:
Hi,
I am
We're definitely not going to get all of the Mesos frameworks migrated to
the Mesos github org, maybe not even all community
frameworks/modules/tools, but we should definitely welcome all willing to
contribute.
I also like the idea of a central registry for all
supported/experimental/proprietary
Great idea. I have been suggesting this to others when appropriate.
It's also worth pointing out the successful history of the Mesos GitHub
org:
Spark's pre-incubator github home was https://github.com/mesos/spark
Your project could be next!
On Fri, Dec 19, 2014 at 10:17 AM, Dave Lester
Here are some relevant JIRAs I found:
https://issues.apache.org/jira/browse/MESOS-934 - Mentions #1
https://issues.apache.org/jira/browse/MESOS-1521 - Mentions #2
On Thu, Nov 13, 2014 at 12:22 PM, Dave Lester daveles...@gmail.com wrote:
Contributions are welcome! The website is available on
+1 make distcheck on Ubuntu 14.04
On Thu, Nov 13, 2014 at 1:45 PM, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
+1
Thanks Ian! Compiles on Mac OS X 10.10 now, all tests pass.
On Thu, Nov 13, 2014 at 1:07 PM, Cosmin Lehene cleh...@adobe.com wrote:
Ian,
Are there rpms in some public
Those definitely do not belong in the Mesos cwiki.
Looks like they also live at
https://cwiki.apache.org/confluence/display/WW/Home
We should definitely remove them from Mesos, and we'd appreciate your help.
Thanks!
-Adam-
On Sun, Nov 9, 2014 at 10:28 PM, Dharmesh Kakadia dhkaka...@gmail.com
Fixed in 0.19: https://issues.apache.org/jira/browse/MESOS-1400
On Thu, Nov 6, 2014 at 7:59 PM, Timothy Chen t...@mesosphere.io wrote:
Hi Sharma,
Can you try out the latest master and see if you can repro it?
Tim
Sent from my iPhone
On Nov 6, 2014, at 7:41 PM, Sharma Podila
Also note, in addition to 'Support for Mesos modules' we also now allow
pluggable isolator modules.
On Thu, Nov 6, 2014 at 2:28 PM, Adam Bordelon a...@mesosphere.io wrote:
make check passed on LinuxMint16 (Ubuntu 13.10)
Would love to see the following two cherry-picked, especially
make check passed on LinuxMint16 (Ubuntu 13.10)
Would love to see the following two cherry-picked, especially the
configuration.md change before you update the website for the release blog
post.
d09478d73cb3ddd76c7b886bef691c8034fa6908 Updated docs/configuration.md.
As an alternate workaround, if you don't need the Java support (you're not
running a JVM framework like Spark/Hadoop/Marathon), then you could use
`configure --disable-java` to skip all the maven/pom build steps.
By disabling Java, you could at least check that the rest of Mesos builds
and runs
in the
codebase.
-- Ankur
On 1 Nov 2014, at 22:54, Adam Bordelon a...@mesosphere.io wrote:
Thank you Ankur. At first glance, it looks great. We'll do a more
thorough review of it very soon.
I know Tim St. Clair had some ideas for fixing MESOS-1711
https://issues.apache.org/jira/browse/MESOS
Olivier,
You should only need to create the /etc/mesos-slave/containerizers OR
specify --containerizers on the mesos-slave command-line. Either should
work.
- Is dockerd installed and running on the slave?
- You could be running into MESOS-1873
https://issues.apache.org/jira/browse/MESOS-1873.
:
On 10/22/2014 11:02 AM, Adam Bordelon wrote:
Olivier,
You should only need to create the /etc/mesos-slave/containerizers OR
specify --containerizers on the mesos-slave command-line. Either should
work.
- Is dockerd installed and running on the slave?
yes docker is running on slave
I'd also like to see more of the modules work land in 0.21, especially the
Authenticator module (MESOS-1889).
I expect it to land in less than a week, but I don't know what your
timeframe is for 0.21.
On Wed, Oct 22, 2014 at 11:22 AM, Ian Downes idow...@twitter.com.invalid
wrote:
Can someone
+1 This change has been a long time coming.
Anybody still using --checkpoint=false and need an official deprecation
cycle?
On Thu, Oct 2, 2014 at 12:25 PM, Cody Maloney c...@mesosphere.io wrote:
Per MESOS-444[1] I'd like to remove the checkpoint flag from slaves,
meaning that all slaves always
Hi Namrata, you can find the Mesos source code at
https://github.com/apache/mesos
Please also see
http://mesos.apache.org/documentation/latest/mesos-developers-guide/
I don't think we've specifically measured which .hpp's would benefit most
from moving code to .cpp's, but Isabel, Cody, and Joris
Hi all,
The vote for Mesos 0.20.1 (rc3) has passed with the following votes.
+1 (Binding)
--
*** Vinod Kone
*** Till Toenshoff
*** Niklas Nielsen
*** Jie Yu
+1 (Non-binding)
--
*** Tim Chen
*** Tom Arnfeld
There were no 0 or -1 votes.
at 9:10 PM, Vinod Kone vinodk...@gmail.com wrote:
+1 (binding)
make check passes on CentOS 5.5 w/ gcc 4.8.2.
On Wed, Sep 17, 2014 at 7:42 PM, Adam Bordelon a...@mesosphere.io
wrote:
Update: The vote is open until Mon Sep 22 10:00:00 PDT 2014 and passes
if a majority
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.20.1.
0.20.1 includes the following:
Minor bug fixes for docker integration, network isolation, build, etc.
The CHANGELOG for the release
Probably because they're building Mesos 0.21 and we haven't published
anything to the Maven repo for that yet.
Should either --disable-java or build a stable release like 0.20.
On Thu, Sep 18, 2014 at 5:33 PM, Vinod Kone vinodk...@gmail.com wrote:
-- Forwarded message --
From:
Commented. I'm now of the opinion that it was a bad apache-11.pom.
On Thu, Sep 18, 2014 at 6:28 PM, Vinod Kone vinodk...@gmail.com wrote:
makes sense. mind commenting on SO?
On Thu, Sep 18, 2014 at 6:25 PM, Adam Bordelon a...@mesosphere.io wrote:
Probably because they're building Mesos
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.20.1.
0.20.1 includes the following:
Minor bug fixes for docker integration, network isolation, etc.
The CHANGELOG for the release is
Update: The vote is open until Mon Sep 22 10:00:00 PDT 2014 and passes if a
majority of at least 3 +1 PMC votes are cast.
On Wed, Sep 17, 2014 at 6:27 PM, Adam Bordelon a...@mesosphere.io wrote:
Hi all,
Please vote on releasing the following candidate as Apache Mesos 0.20.1.
0.20.1
I can be the release manager, especially if Bhuvan wants to manage some of
the administrivia.
On Fri, Sep 12, 2014 at 12:23 PM, Tim St Clair tstcl...@redhat.com wrote:
I would like to, but this next month is going to be crazy for me. Perhaps
the next cycle.
Regards,
Tim
- Original
chime in here on how this fits into the task reconciliation
work that you've been leading?
On Wed, Sep 10, 2014 at 6:12 PM, Adam Bordelon a...@mesosphere.io wrote:
I agree with Niklas that if the executor has sent a terminal status
update
to the slave, then the task is done and the master
BenH has been calling these master reservations (globally control
reservations across all slaves through the master) and offer reservations
(I don't care which nodes it's on, as long as I get X cpu and Y RAM, or Z
sets of {X,Y}), and they're definitely on the roadmap.
On Wed, Sep 10, 2014 at 9:05
101 - 200 of 220 matches
Mail list logo
