Re: [VOTE] Accept Aurora for Apache Incubation
+1 (non-binding) On Sat, Sep 28, 2013 at 9:39 AM, Andy Konwinski andykonwin...@gmail.comwrote: +1 On Sep 26, 2013 11:08 AM, Dave Lester d...@ischool.berkeley.edu wrote: Since discussion about the Aurora proposal has calmed and the team recently published a snapshot of the their source code on github ( https://github.com/twitter/aurora), I'd like to call a vote for Aurora to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/AuroraProposal Let's keep this vote open for three business days, closing the voting on Tuesday 10/1. [ ] +1 Accept Aurora into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Aurora because... Dave = Abstract = Aurora is a service scheduler used to schedule jobs onto Apache Mesos. = Proposal = Aurora is a scheduler that provides all of the primitives necessary to quickly deploy and scale stateless and fault tolerant services in a datacenter. Aurora builds on top of Apache Mesos and provides common features that allow any site to run large scale production applications. While the project is currently used in production at Twitter, we wish to develop a community to increase contributions and see it thrive in the future. = Background = The initial development of Aurora was done at Twitter, and its codebase was recently open sourced. This proposal is for Aurora to join the Apache Incubator. = Rationale = While the Apache Mesos core focuses on distributing individual tasks across nodes in a cluster, typical services consist of dozens or hundreds of replicas of tasks. As a service scheduler, Aurora provides the abstraction of a job to bundle and manage these tasks. Aurora provides many key functionalities centered around a job, including: definition, the concept of an instance and the serverset, deployment and scheduling, health checking, and introspection. It also allows cross-cutting concerns to be handled like observability and log collection. = Current Status = == Meritocracy == By submitting this incubator proposal, we’re expressing our intent to build a diverse developer community around Aurora that will conduct itself according to The Apache Way and use meritocratic means of accepting contributions. Several members of the Aurora team overlap with Apache Mesos, which successfully graduated from the Incubator and has embraced a meritocratic model of governance; we plan to follow a similar path forward with Aurora and believe that a synergy between both projects will make this even easier. == Community == Aurora is currently being used internally at Twitter. By open sourcing the project, we hope to extend our contributor base significantly and create a vibrant community around the project. == Core Developers == Aurora is currently being developed by a team of seven engineers at Twitter. == Alignment == The ASF is a natural choice to host the Aurora project, given the goal of open sourcing the project and fostering a community to grow and support the software. Additionally, Aurora integrates with Apache Mesos, and Apache ZooKeeper for service discovery. We believe that inclusion within Apache will build stronger ties between these projects, and create further alignment between their goals and communities. = Known Risks = == Orphaned Products == The core developers plan to continue working full time on the project, and there is very little risk of Aurora being abandoned since it is running hundreds of services as part of Twitter’s infrastructure. Additionally, members of the Mesos community beyond Twitter have expressed interest in an advanced scheduler like Aurora (see “Interested Parties” section); we believe that need will drive some of the community involvement necessary for the project to incubate successfully. == Inexperience with Open Source == Initial Aurora committers have varying levels of experience using and contributing to Open Source projects, however by working with our mentors and the Apache community we believe we will be able to conduct ourselves in accordance with Apache Incubator guidelines. The close relationship between the Aurora team and Apache Mesos means there is an awareness of the incubation process and a willingness to embrace The Apache Way. == Homogenous Developers == The initial set of committers are from a single organization, however we expect that once approved for incubation the project will attract contributors from more organizations. We have already had conversations with other companies who have expressed an interest in Aurora. == Reliance on Salaried Developers == Initial Aurora committers are salaried developers at Twitter, however shortly after open sourcing the code we plan to diversify the project’s core committers and
[RESULT] [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
The vote to release mesos-0.12.0-incubating has passed with 3 IPMC binding +1s and 5 non-binding +1s. IPMC Binding Votes: Alex Karasulu Chris Mattman Tom White Non-Binding Votes: Vinod Kone Deepal Jayasinghe Brenden Matthews Yan Xu Andy Konwinski Thanks all! -- Forwarded message -- From: Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov Date: Mon, Jun 17, 2013 at 6:04 PM Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) To: Benjamin Mahler benjamin.mah...@gmail.com, mesos-...@incubator.apache.org mesos-...@incubator.apache.org, general@incubator.apache.org general@incubator.apache.org Hey Ben, Looks like we got a 3rd +1 from Tom W -- woot -- so we can proceed :) Way to put a cherry on top since we're pushing on graduating now too! Great work guys. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Benjamin Mahler benjamin.mah...@gmail.com Date: Monday, June 17, 2013 12:12 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org, general@incubator.apache.org general@incubator.apache.org, jpluser chris.a.mattm...@jpl.nasa.gov Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) +chris Hey Chris, looks like we're stalled on releasing again. What are the rules for a lack of IPMC participation in the 72 hour window? Can we proceed? On Fri, Jun 14, 2013 at 11:09 AM, Benjamin Mahler bmah...@twitter.com wrote: Unfortunately 0.12.0 was at a point where we had flaky tests, we're in much better shape these days! (0.13.0 and later) Alright, just one additional binding vote needed!! Hopefully we can get that quickly and start preparing to release 0.13.0. On Thu, Jun 13, 2013 at 11:27 PM, Andy Konwinski andykonwin...@gmail.com wrote: Yeah, after running the tests a few more times I saw a couple different tests fail and eventually in one run of `make check` they all passed. Here's the play-by-play: I ran the tests again and they hung here for at least 10 min: MacbookAir:build andyk$ make check Making check in . make[1]: Nothing to be done for `check-am'. Making check in third_party make check-recursive Making check in libprocess Making check in third_party make check-am make libgmock.la http://libgmock.la make[6]: `libgmock.la http://libgmock.la' is up to date. Making check in . make tests make[5]: `tests' is up to date. make check-TESTS Then again, and a different test failed in libprocess after a few seconds: MacbookAir:build andyk$ cat third_party/libprocess/test-suite.log ... [ RUN ] Statistics.truncate ../../../third_party/libprocess/src/tests/statistics_tests.cpp:58: Failure Expected: (Clock::now()) = (values.get().begin()-first.secs()), actual: 1.37119e+09 vs 1.37119e+09 ../../../third_party/libprocess/src/tests/statistics_tests.cpp:71: Failure Expected: (Clock::now()) = (values.get().begin()-first.secs()), actual: 1.37128e+09 vs 1.37128e+09 [ FAILED ] Statistics.truncate (1 ms) Then they all passed! Glad to know the flakey tests are known issues and being worked on in a future release. +1 (non-binding) from me on this release. Andy On Thu, Jun 13, 2013 at 10:38 PM, Vinod Kone vinodk...@gmail.com wrote: is this test always failing or just flaky? we've fixed a bunch of our flaky tests in 0.13.0. On Thu, Jun 13, 2013 at 10:13 PM, Andy Konwinski andykonwin...@gmail.com wrote: I downloaded the tarball and it builds fine for me but `make check` doesn't succeed on OS X 10.8.3. Is this a known issue? I'll attach the test suite output and paste the output from the failing test below. Andy -- [ RUN ] ZooKeeperTest.MasterDetectorExpireSlaveZKSessionNewMaster 2013-06-13 22:07:44,372:5033(0x11747b000):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-4, errno=64(Host is down): failed while receiving a server response 2013-06-13 22:07:44,375:5033(0x11726f000):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-4, errno=64(Host is down): failed while receiving a server response 2013-06-13 22:07:44,377:5033(0x11726f000):ZOO_ERROR@handle_socket_error_msg@1621: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-112, errno=70(Stale NFS file handle): sessionId=0x13f41150633 has expired. E0613 22:07:44.377506 220274688 detector.cpp:477] Master detector ((755)@ 192.168.1.104:51358 http://192.168.1.104:51358) failed to get masters
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Unfortunately 0.12.0 was at a point where we had flaky tests, we're in much better shape these days! (0.13.0 and later) Alright, just one additional binding vote needed!! Hopefully we can get that quickly and start preparing to release 0.13.0. On Thu, Jun 13, 2013 at 11:27 PM, Andy Konwinski andykonwin...@gmail.comwrote: Yeah, after running the tests a few more times I saw a couple different tests fail and eventually in one run of `make check` they all passed. Here's the play-by-play: I ran the tests again and they hung here for at least 10 min: MacbookAir:build andyk$ make check Making check in . make[1]: Nothing to be done for `check-am'. Making check in third_party make check-recursive Making check in libprocess Making check in third_party make check-am make libgmock.la make[6]: `libgmock.la' is up to date. Making check in . make tests make[5]: `tests' is up to date. make check-TESTS Then again, and a different test failed in libprocess after a few seconds: MacbookAir:build andyk$ cat third_party/libprocess/test-suite.log ... [ RUN ] Statistics.truncate ../../../third_party/libprocess/src/tests/statistics_tests.cpp:58: Failure Expected: (Clock::now()) = (values.get().begin()-first.secs()), actual: 1.37119e+09 vs 1.37119e+09 ../../../third_party/libprocess/src/tests/statistics_tests.cpp:71: Failure Expected: (Clock::now()) = (values.get().begin()-first.secs()), actual: 1.37128e+09 vs 1.37128e+09 [ FAILED ] Statistics.truncate (1 ms) Then they all passed! Glad to know the flakey tests are known issues and being worked on in a future release. +1 (non-binding) from me on this release. Andy On Thu, Jun 13, 2013 at 10:38 PM, Vinod Kone vinodk...@gmail.com wrote: is this test always failing or just flaky? we've fixed a bunch of our flaky tests in 0.13.0. On Thu, Jun 13, 2013 at 10:13 PM, Andy Konwinski andykonwin...@gmail.com wrote: I downloaded the tarball and it builds fine for me but `make check` doesn't succeed on OS X 10.8.3. Is this a known issue? I'll attach the test suite output and paste the output from the failing test below. Andy -- [ RUN ] ZooKeeperTest.MasterDetectorExpireSlaveZKSessionNewMaster 2013-06-13 22:07:44,372:5033(0x11747b000):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:51504] zk retcode=-4, errno=64(Host is down): failed while receiving a server response 2013-06-13 22:07:44,375:5033(0x11726f000):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:51504] zk retcode=-4, errno=64(Host is down): failed while receiving a server response 2013-06-13 22:07:44,377:5033(0x11726f000):ZOO_ERROR@handle_socket_error_msg@1621: Socket [127.0.0.1:51504] zk retcode=-112, errno=70(Stale NFS file handle): sessionId=0x13f41150633 has expired. E0613 22:07:44.377506 220274688 detector.cpp:477] Master detector ((755)@ 192.168.1.104:51358) failed to get masters: session expired ../../src/tests/zookeeper_tests.cpp:441: Failure Mock function called more times than expected - returning directly. Function call: newMasterDetected(@0x10d211c00 (758)@ 192.168.1.104:51358) Expected: to be called once Actual: called twice - over-saturated and active 2013-06-13 22:07:47,707:5033(0x11747b000):ZOO_ERROR@handle_socket_error_msg@1621: Socket [127.0.0.1:51504] zk retcode=-112, errno=70(Stale NFS file handle): sessionId=0x13f411506330002 has expired. [ FAILED ] ZooKeeperTest.MasterDetectorExpireSlaveZKSessionNewMaster (3459 ms) On Thu, Jun 13, 2013 at 8:59 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Ben, +1 from me (binding) SIGS pass (minor nit: your GPG key should probably be made available at id.apache.org, which will in turn make it available here http://people.apache.org/keys/group/mesos.asc) I was able to import Ben's key: [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Can't check signature: No public key [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% gpg --keyserver pgpkeys.mit.edu --recv-key D141A5B6 gpg: requesting key D141A5B6 from hkp server pgpkeys.mit.edu gpg: key D141A5B6: public key Benjamin Mahler benjamin.mah...@gmail.com imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) [chipotle:~/tmp/apache-mesos-0.12.0] mattmann% $HOME/bin/verify_gpg_sigs Verifying Signature for file mesos-0.12.0-incubating.tar.gz.asc gpg: Signature made Mon Jun 10 16:22:16 2013 PDT using RSA key ID D141A5B6 gpg: Good signature from Benjamin Mahler benjamin.mah...@gmail.com gpg: WARNING: This key is not certified with a trusted signature! gpg
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
72 hours has passed and we have the following +1's: Binding (2 more needed): Alex Karasulu Non-Binding: Vinod Kone Deepal jayasinghe Brenden Matthews Yan Xu Could some IPMC members please take a look? It would be greatly appreciated! Ben On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler benjamin.mah...@gmail.comwrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
[VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1)
Correction on the tag link: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=5332ade3c403b4d9fcdcd9194ee86d3fa99eca17 On Mon, Jun 10, 2013 at 5:05 PM, Benjamin Mahler benjamin.mah...@gmail.comwrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC2)
+1 (non binding) Tested on CentOS 5.5 On Tue, Dec 18, 2012 at 11:42 PM, Brian McCallister bri...@skife.orgwrote: +1 On Tue, Dec 11, 2012 at 12:56 PM, Benjamin Hindman b...@berkeley.edu wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.10.0. This will be the second incubator release for Mesos in Apache. The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incubating-RC2 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.10.0-incubating! The vote is open until Friday, December 14th at 5:00 pm (PST) and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.10.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://www.mesosproject.org .
