Re: [2/2] mesos git commit: Added documentation for labeled reserved resources.

Any plans to support labels for static reservations? Are we intentionally not supporting ReservationInfo for static reservations? Or is this just outside of the initial scope? On Fri, Feb 12, 2016 at 1:18 AM, wrote: > Added documentation for labeled reserved resources. > >

Re: Slave Terminology Rename Proposal

> On Feb 11, 2016, at 2:14 PM, Vinod Kone wrote: > > What do you mean by keeping the old symbols? I mean, will there be a period where you keep the old names as well as the new names? > For example, in the case of the `Allocator::addSlave()`, are you suggesting > that

Re: [2/2] mesos git commit: Added documentation for labeled reserved resources.

Hi Ben, On Fri, Feb 12, 2016 at 2:34 AM, Benjamin Mahler wrote: > Any plans to support labels for static reservations? > > Are we intentionally not supporting ReservationInfo for static > reservations? Or is this just outside of the initial scope? Labels for static

Re: Shepherd for MESOS-3486

Hi Michael, Thanks for taking this on! Joris Van Remoortere will shepherd, but please also include me in the review request. Thanks, Neil On Thu, Feb 11, 2016 at 5:21 PM, Michael Browning wrote: > Hello, > > I've picked a small issue off of the newbie issues stack to

Shepherd Request

Can anyone shepherd the following issue for me? https://issues.apache.org/jira/browse/MESOS-4631 Thanks. -Disha

Re: Mesos binaries and shared library dependencies.

To be clear, I'm actually a bit torn both ways on this. On the one hand, including the rpath makes it easy for those who don't know anything about LD_LIBRARY_PATH, the ldcache, etc. to simply pass their paths to their external dependencies at configure time and then run their binaries without

Precision of scalar resources

tl;dr: If you use resource values with more than three decimal digits of precision (e.g., you are launching a task that uses 2.5001 CPUs), please speak up! Mesos uses floating point to represent scalar resource values, such as the number of CPUs in a resource offer or dynamic reservation.

Re: Mesos binaries and shared library dependencies.

Maybe have an opt-in (say —with-rpath)? -Jojy > On Feb 12, 2016, at 2:19 PM, Kevin Klues wrote: > > To be clear, I'm actually a bit torn both ways on this. > > On the one hand, including the rpath makes it easy for those who don't > know anything about LD_LIBRARY_PATH, the

Mesos binaries and shared library dependencies.

Hi all, A discussion came up recently around including rpaths in our mesos binaries to help resolve any shared library dependencies that don't exist in standard library paths (e.g. /lib, /usr/local/lib, etc.). By default, there are no shared library dependencies that exist in non-standard paths,

Re: Mesos binaries and shared library dependencies.

I like that idea. Don't set rpath by default, but allow people to specify that it should be set via a flag. How does --set-rpath-for-external-libs sound for a name. Too long? I don't like just --with-rpath, because it's not descriptive enough in my opinion. On Fri, Feb 12, 2016 at 2:34 PM,

Re: Mesos binaries and shared library dependencies.

Playing with this a bit more, I came up with a solution that bridges the gap between the two alternatives I proposed before. Basically, I found a way to get the wrapper script to set the rpath when running the binary from the build directory, but leave the rpath of the actual binary unchanged.

Re: [2/2] mesos git commit: Added documentation for labeled reserved resources.

Neil, I think what you want to show for setting reservationInfo for static reservation is https://issues.apache.org/jira/browse/MESOS-4476 On Sat, Feb 13, 2016 at 2:16 AM, Neil Conway wrote: > Hi Ben, > > On Fri, Feb 12, 2016 at 2:34 AM, Benjamin Mahler