Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)

The list of patches to include in 0.28.0-rc2 are now being tracked by a JIRA: https://issues.apache.org/jira/browse/MESOS-4915 On Thu, Mar 10, 2016 at 3:51 PM, Vinod Kone wrote: > I'll cut it first thing tomorrow. Whatever from kevin's list ablove gets in > by tonight will

Re: mesos git commit: Add 'name' field into NetworkInfo.

Done, please review, thanks Neil and Jie. https://reviews.apache.org/r/44696/ Thanks, Qian Zhang On Fri, Mar 11, 2016 at 3:13 AM, Jie Yu wrote: > Good catch. > > + Qian, could you please send a patch for that? Thanks! > > - Jie > > On Thu, Mar 10, 2016 at 11:08 AM, Neil

Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)

I'll cut it first thing tomorrow. Whatever from kevin's list ablove gets in by tonight will get into rc2. On Thu, Mar 10, 2016 at 6:28 PM, Daniel Osborne < daniel.osbo...@metaswitch.com> wrote: > Kevin, > > When are you planning on cutting? > > I'm very keen to seeing 4370 get merged. It just

RE: [VOTE] Release Apache Mesos 0.28.0 (rc1)

Kevin, When are you planning on cutting? I'm very keen to seeing 4370 get merged. It just needs some final fixes to get past "Fix it, then ship it". Thanks, Dan -Original Message- From: Kevin Klues [mailto:klue...@gmail.com] Sent: Thursday, March 10, 2016 11:46 AM To: user

Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)

Updated list of patches to include in 0.28.0-rc2. We are cutting the release candidate today, so make sure your patches land soon if they haven't already. Did I miss any? Committed: Added documentation about container image support. commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b

Re: mesos git commit: Add 'name' field into NetworkInfo.

Good catch. + Qian, could you please send a patch for that? Thanks! - Jie On Thu, Mar 10, 2016 at 11:08 AM, Neil Conway wrote: > Should we also update docs/networking-for-mesos-managed-containers.md? > It contains a version of the NetworkInfo message definition. > >

Re: mesos git commit: Add 'name' field into NetworkInfo.

Should we also update docs/networking-for-mesos-managed-containers.md? It contains a version of the NetworkInfo message definition. Neil On Thu, Mar 10, 2016 at 11:05 AM, wrote: > Repository: mesos > Updated Branches: > refs/heads/master 57a574fc9 -> 2a436e02f > > > Add

Re: [VOTE] Release Apache Mesos 0.24.2 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. All tests pass. I was also able to successfully test a simple upgrade scenario from 0.23.1 to 0.24.2-rc2 using the script found here: https://reviews.apache.org/r/44229/ Cheers, Greg On Tue, Mar 8,

Re: Executors no longer inherit environment variables from the agent

Alex, See my response inlined: First, does this change include the executor library? We currently use > environment variables to propagate various config values from an agent to > executors. If it does, what is the alternative? Any environment variables generated by Mesos (i.e., MESOS_,

Re: [VOTE] Release Apache Mesos 0.25.1 (rc2)

Thanks Greg! On 10 March 2016 at 12:34, Greg Mann wrote: > +1 (non-binding) > > Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. > > The following tests failed during the first test run: > ContainerizerTest.ROOT_CGROUPS_BalloonFramework >

Re: [VOTE] Release Apache Mesos 0.26.1 (rc2)

Thanks Greg! On 10 March 2016 at 12:32, Greg Mann wrote: > +1 (non-binding) > > Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL > enabled. All tests pass. > > I was also able to successfully test a simple upgrade scenario from > 0.25.1-rc2 to 0.26.1-rc2

Re: [VOTE] Release Apache Mesos 0.25.1 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. The following tests failed during the first test run: ContainerizerTest.ROOT_CGROUPS_BalloonFramework MemoryPressureMesosTest.CGROUPS_ROOT_Statistics MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery

Re: [VOTE] Release Apache Mesos 0.26.1 (rc2)

+1 (non-binding) Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled. All tests pass. I was also able to successfully test a simple upgrade scenario from 0.25.1-rc2 to 0.26.1-rc2 using the script found here: https://reviews.apache.org/r/44229/ Cheers, Greg On Tue, Mar

Re: Negative durations

Duration and TimePoint were introduced to map to the types in C++ ( http://en.cppreference.com/w/cpp/chrono). Duration is negative so as not to surprise users when they do TimePoints A - B and end up with a positive duration when B > A. You could imagine a user of these writing code to check if

RE: Compile failure

The problem was solved when I removed all related subversion packages and then installed the 1.9 one. Before the 1.9 install I had to run rpm -ivh /tmp/epel-release-7-5.noarch.rpm All fine now, I'm able to compile! Walter -Original Message- From: Alexander Rojas

Re: Compile failure

Hi Walter, I once had the same problem. The solution is to move to subversion 1.8, so as super user try: # Change version in the repository sed -i "s/1.9/1.8/g" /etc/yum.repos.d/wandisco-svn.repo # Remove cache files rm -rf /var/cache/yum/x86_64/7Server/WANdiscoSVN/* # Rebuild the cache yum

Re: Executors no longer inherit environment variables from the agent

Not that I know a lot about this project, but I think for the command executor we can use the `Environment` message. Perhaps we can extend the container info to have something similar? > On 10 Mar 2016, at 12:50, Alex Rukletsov wrote: > > I have two questions. > >

Re: Executors no longer inherit environment variables from the agent

I have two questions. First, does this change include the executor library? We currently use environment variables to propagate various config values from an agent to executors. If it does, what is the alternative? Second, what will be the preferred way to pass config values to executors? It

Re: Questions about Docker related tests in Mesos

Hi Zhiwei, I was thinking about this as well, but for different reasons: Pulling in Docker images for tests is not the ideal solution. Sure, testing a `sleep 1000` should work, but testing an executor leaves some questions on how to handle changes/deprecation of the interfaces. It's not a

Questions about Docker related tests in Mesos

Hi all, The Docker related test cases that hardcoded "alpine" as the Docker image which caused test cases failed on IBM Power platform, since the Docker image "alpine" is not compatible with IBM Power platform. And I saw an inline comment by Timothy: "// TODO(tnachen): Use local image to test if