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

ip-us.apache.org/repos/asf?p=mesos.git;a=blob_ >> > plain;f=CHANGELOG;hb=1.4.1-rc1 >> > >> > >> > >> > The candidate for Mesos 1.4.1 release is available at: >> > https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/mesos >> -1.4.1.tar.gz >> > >> > The tag to be voted on is 1.4.1-rc1: >> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit >> ;h=1.4.1-rc1 >> > >> > The MD5 checksum of the tarball can be found at: >> > https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/ >> > mesos-1.4.1.tar.gz.md5 >> > >> > The signature of the tarball can be found at: >> > https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/ >> > mesos-1.4.1.tar.gz.asc >> > >> > The PGP key used to sign the release is here: >> > https://dist.apache.org/repos/dist/release/mesos/KEYS >> > >> > The JAR is in a staging repository here: >> > https://repository.apache.org/content/repositories/orgapachemesos-1216 >> > >> > Please vote on releasing this package as Apache Mesos 1.4.1! >> > >> > The vote is open until Monday, November 13, 2017, 11:59 PM EST and >> passes >> > if a majority of at least 3 +1 PMC votes are cast. >> > >> > [ ] +1 Release this package as Apache Mesos 1.4.1 >> > [ ] -1 Do not release this package because ... >> > >> > Thanks, >> > Anand and Kapil >> > >> > > -- Anand Mazumdar

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

+1 (binding) make check passed on Ubuntu 16.04 -anand On Fri, Sep 15, 2017 at 2:12 PM, Kapil Arya wrote: > +1 (binding) > > Internal CI with Centos 6/7, Fedora 23, Debian 8, and Ubuntu 12/14/16. > > On Fri, Sep 15, 2017 at 5:08 PM, Vinod Kone wrote: > >> Ok. Looks like a test issue per https:

Mesos 1.4.0

Hello everyone, It's about time for Mesos 1.4.0 (somewhat late though, 1.3 rc1 was cut on 5/5) . Kapil would be the primary release manager and I would be the co-release manager. We expect to cut rc1 in the coming couple of weeks. Here's how you can help: - Set *Target Version = "1.4.0"* for anyt

Re: Plan for upgrading protobuf==3.2.0 in Mesos

d > to > > 1.3.0 first, then come back and upgrade your executors and schedulers. > > > > We understand this may expose inconvenience around updating the protobuf > > dependency, so please let us know if you have any concern or further > > questions. > > > > -- > > > > Cheers, > > > > Zhitao Li and Anand Mazumdar, >

Mesos 1.4.0 Release Manager(s)

1.4 is still some time away but I was wondering if there are any committers volunteering to be release managers? If not, me and Kevin would be happy to volunteer. Also, let us know if you would be interested to help us out in managing the release as a new committer. -anand

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

+1 (binding) make check passed on Ubuntu 16.04 with clang 3.6 -anand On Wed, May 3, 2017 at 10:01 AM, Vinod Kone wrote: > +1 (binding) > > *Revision*: 4154f66d6c6dde8fd2cf2bbf0bfa155f24ac55d4 > >- refs/tags/1.0.4-rc2 > > Configuration Matrix gcc clang > centos:7 --verbose --enable-libevent

Re: Plan for upgrading protobuf==3.2.0 in Mesos

us know if you have any concern or further > questions. > > -- > > Cheers, > > Zhitao Li and Anand Mazumdar,

[Design doc][RFC] Agent Lifecycle Management

Hello everyone, We are working on adding support for agent lifecycle management [1] that will provide a feedback mechanism for frameworks in case of agent node failures. The existing agent lost [2] signal is not sufficient for frameworks to ascertain that a given agent node isn't coming back. Her

Re: protbuf to json not compatible

Hi Tomek, Looks like we dropped the ball on MESOS-5995 (https://issues.apache.org/jira/browse/MESOS-5995). I assigned myself as the shepherd and would take a look next week. -anand On Thu, Mar 23, 2017 at 2:09 AM, Tomek Janiszewski wrote: > I have a similar problem with protobuf and json. In my

[Proposal] Media type for streaming requests/responses

Hello All, We recently added support for request streaming as part of the Debugging epic (MESOS-6460). As a follow up on that, we want your suggestions and feedback via comments on the proposal draft [1] around the media type to use for the 'Content-Type' header for streaming requests/responses.

[RESULT][VOTE] Release Apache Mesos 0.28.3 (rc1)

Hi all, The vote for Mesos 0.28.3 (rc1) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Vinod Kone Benjamin Mahler +1 (Non-binding) -- Greg Mann There were no 0 or -1 votes. Please find the release at: https://dist.apa

[VOTE] Release Apache Mesos 0.28.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.28.3. 0.28.3 includes the following: ** Bug * [MESOS-2043] - Framework auth fail with timeout error and never get authenticated * [MESO

Re: Mesos V1 Operator HTTP API - Java Proto Classes

We wanted to move the project away from officially supporting anything other than C++ and discuss more on if we should be responsible for publishing to the various language specific channels. However, for the time being, we had decided to include the v1 protobufs in the mesos JAR itself. (it alread

Re: mesos git commit: Added MESOS-6497 to CHANGELOG.

Neil, I had already committed it to master. There were some merge conflicts with the CHANGELOG for the 1.1.x branch. So, I had asked Till to resolve them and then commit it. -anand On Oct 28, 2016, at 1:23 PM, Neil Conway wrote: This commit should also appear in the master branch, not just 1.

Re: Protobuf long number JSON serialisation

Tomek, Thanks for reporting this. Looks like a bug in our JSON -> Protobuf parsing code. Mind filing a JIRA issue? -anand > On Aug 4, 2016, at 2:04 PM, Tomek Janiszewski wrote: > > Hi > > I have a problem with HTTP API. Proto2 does not specify JSON mappings but > Proto3 does and it recomme

[HTTP API] Client Libraries

Hi, We recently committed documentation around available client libraries for the Scheduler /Executor HTTP API’s. Link to doc: https://github.com/a

Re: how to debug HTTP API

Olivier, You are missing the “task_infos” key in your “ACCEPT” call. The master treats “Accept” operations with no launch tasks as declining offers implicitly. I would file a followup JIRA to ensure this is logged on the master (if not so). An example correct JSON: https://gist.github.com/hatr

Re: Status acknowledgements in MesosExecutor

Hi Evers, Thanks for taking this on. Vinod has agreed to shepherd this and I would be happy to be the initial reviewer for the patches. -anand > On Jun 1, 2016, at 10:27 AM, Evers Benno wrote: > > Some more context about this bug: > > We did some tests with a framework that does nothing but

Re: MESOS-3777: Looking for a shepherd

Hi Jose, Would you like to work on https://issues.apache.org/jira/browse/MESOS-5359 instead? It’s part of the Scheduler API v1 improvements epic. -anand > On May 19, 2016, at 12:40 PM, José G

Re: Status acknowledgements in MesosExecutor

Also, we would be modifying the agent to always acknowledge status updates from the executor. (MESOS-5262 ) Once, that is done, it should be sufficient for an executor to terminate itself on receiving an acknowledgment message from the agent, ins

Re: Change minimum supported version for GCC to 4.8.1

Are you referring to the spread sheet linked in MESOS-2604 ? AFAICT, it just shows that a particular variant of GCC 4.8+ is available on each of the supported distributions. So, this should not be an issue unless I am missing something? -anand

Change minimum supported version for GCC to 4.8.1

I would like to propose that we bump our minimum supported version for gcc from 4.8.0 to 4.8.1. The main motivation behind this is that there are at least 2 outstanding reviews on RB that want to use ref-qualifiers introduced i

Re: mesos git commit: Added documentation for API versioning.

che.org/repos/asf/mesos/tree/4568e584 >> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/4568e584 >> >> Branch: refs/heads/master >> Commit: 4568e584d15e2da68f777aff2570d6b0ceaa14fa >&g

Re: writing a scheduler against the v1 C++ API

James, Mesos 0.24 included experimental support for the Scheduler V1 API. So, it is indeed quite an reasonable thing to do and provide us feedback. :) - You can have a look at the C++ low level v1 scheduler library: https://github.com/apache/mesos/blob/master/include/mesos/v1/scheduler.hpp

[Design Doc] Executor HTTP API

Folks, The Scheduler HTTP API was introduced in Mesos 0.24. Building on that, we would like to propose a design document for the Executor HTTP API around agent-executor communication. The document is st

Re: Do we still need to add InverseOffer support to Scheduler API?

also > the Java/Python binding? Will we keep supporting them? Or they will be > eventually deprecated in future? > > > Regards, > Qian Zhang > > Anand Mazumdar ---09/15/2015 11:00:00---Hi Qian, We currently don’t intend to > move the old C++ Scheduler/Scheduler Driver

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi Qian, We currently don’t intend to move the old C++ Scheduler/Scheduler Driver Scheduler Driver interface to use the Mesos V1 API. If you want to use the new V

Re: [Breaking Change 0.24, MESOS 1988] Silently ignore launchTask/acceptOffers calls when disconnected

validation. The > disconnected case does not overlap with the master's validation logic, it > is an artifact of the driver implementation (the scheduler can't tell when > it's launch calls are enqueued behind a disconnected event). > > On Mon, Jun 22, 2015 at 5:23 PM,

[Breaking Change 0.24, MESOS 1988] Silently ignore launchTask/acceptOffers calls when disconnected

Hi All, We intend to introduce a breaking change [1] in the driver to silently ignore launchTasks/acceptOffers(…) calls when disconnected from the master in 0.24. The previous behavior was to send out “TASK_LOST” messages since there was no way to know that these task launches were dropped. How