Re: Build failed in Jenkins: mesos-reviewbot #6201
On Jun 4, 2015, at 12:50 PM, Vinod Kone vinodk...@apache.org wrote: On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: checking for C++ compiler version... 4.8.2 checking for C++ compiler vendor... (cached) gnu configure: error: GCC 4.8 or higher required (found 4.8.2) hmm. this looks weird. Is this the bug in my autoconf patch that Ben fixed with 2b2618f855a9f377111ad0460fc4a6e9db4d3755?
Re: Introduction - Aditi
Hi Aditi, Please feel free to add me as a reviewer for these patches. I contributed part of Phase 1, and ended up looking ahead as to what would be required for the further phases. I'd be happy to review your patches! Joris On Thu, Jun 4, 2015 at 11:00 AM, Aditi Dixit aditi96di...@gmail.com wrote: Hi all, I'm Aditi and I'm currently interning at Outreachy. Apache Mesos is an amazing piece of software and I'm really excited to work on it. This is my first time contributing to an open source software, so any advice you may have for me is welcome! The project that I would be working on is Updating the Framework Info. The goal of this project is to develop a way to allow frameworks to update their FrameworkInfo without having to restart all the slaves, tasks or master(s) and reconcile the FrameworkInfo. The project is quite nicely described by Vinod Kone in the Confluence link here https://cwiki.apache.org/confluence/display/MESOS/Design+doc%3A+Updating+Framework+Info . Right now, I'm working on starter tickets to get familiar with the Mesos codebase, but I hope to start working on the project soon. Regards, Aditi
Re: Build failed in Jenkins: mesos-reviewbot #6201
JPeach: That's correct. You had it right in the top level project, but the comparison was wrong in the libprocess check. Probably just a copy paste error, all fixed now! :-) Thanks for helping us move to more general macros! Joris On Thu, Jun 4, 2015 at 10:51 PM, James Peach jor...@gmail.com wrote: On Jun 4, 2015, at 12:50 PM, Vinod Kone vinodk...@apache.org wrote: On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: checking for C++ compiler version... 4.8.2 checking for C++ compiler vendor... (cached) gnu configure: error: GCC 4.8 or higher required (found 4.8.2) hmm. this looks weird. Is this the bug in my autoconf patch that Ben fixed with 2b2618f855a9f377111ad0460fc4a6e9db4d3755?
Re: Build failed in Jenkins: mesos-reviewbot #6201
Looks like ben pushed a fix ~ 5 hours ago. On Thu, Jun 4, 2015 at 12:50 PM, Vinod Kone vinodk...@apache.org wrote: On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: checking for C++ compiler version... 4.8.2 checking for C++ compiler vendor... (cached) gnu configure: error: GCC 4.8 or higher required (found 4.8.2) hmm. this looks weird.
Re: Build failed in Jenkins: mesos-reviewbot #6201
On Thu, Jun 4, 2015 at 7:48 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: checking for C++ compiler version... 4.8.2 checking for C++ compiler vendor... (cached) gnu configure: error: GCC 4.8 or higher required (found 4.8.2) hmm. this looks weird.
Re: soliciting shepherds for auto tools changes
Took care of MESOS-2666 as well James. There was a bug I had to fix. ;-) Please take a look at the reviews where I left some comments. It looks like Cody still has some questions around semantics for https://reviews.apache.org/r/33752, please address that and then we can get it committed. Thank you thank you thank you for reaching out for a shepherd too! On Thu, Jun 4, 2015 at 7:00 AM Benjamin Hindman b...@eecs.berkeley.edu wrote: I just took a look and shipped the reviews associated with MESOS-2659. I'll take a look at MESOS-2666 next. Thanks for the contributions James! On Thu, Jun 4, 2015 at 5:54 AM Jake Farrell jfarr...@apache.org wrote: I can only help review, not a Mesos committer -Jake On Wed, Jun 3, 2015 at 11:47 PM, James Peach jor...@gmail.com wrote: On Jun 3, 2015, at 10:25 AM, Jake Farrell jfarr...@apache.org wrote: Happy to help review and provide feedback on these patches Thanks Jake, does that mean you are shepherding too, or just reviewing? -Jake On Wed, Jun 3, 2015 at 12:21 PM, James Peach jor...@gmail.com wrote: On May 18, 2015, at 10:52 AM, Vinod Kone vinodk...@apache.org wrote: Tim and Cody. Do any of you have cycles to shepherd these? If there's no takers, should I just close the tickets? On Fri, May 15, 2015 at 3:19 PM, Vinod Kone vinodk...@gmail.com wrote: -- Vinod -- Forwarded message -- From: James Peach jpe...@apache.org Date: Fri, May 15, 2015 at 9:28 AM Subject: soliciting shepherds for auto tools changes To: benjamin.mah...@gmail.com, c...@mesosphere.io, tstcl...@redhat.com, benjamin.hind...@gmail.com, vinodk...@gmail.com, mcyp...@gmail.com Hi all, I have the following tickets: https://issues.apache.org/jira/browse/MESOS-2537 https://issues.apache.org/jira/browse/MESOS-2659 https://issues.apache.org/jira/browse/MESOS-2666 with corresponding reviews at: https://reviews.apache.org/r/33755/ https://reviews.apache.org/r/33754/ https://reviews.apache.org/r/33753/ https://reviews.apache.org/r/33752/ https://reviews.apache.org/r/33850/ https://reviews.apache.org/r/33849/ Is anyone able to act as shepherd for these? thanks, James
Re: soliciting shepherds for auto tools changes
On Jun 4, 2015, at 8:31 AM, Benjamin Hindman b...@eecs.berkeley.edu wrote: Took care of MESOS-2666 as well James. There was a bug I had to fix. ;-) Please take a look at the reviews where I left some comments. Thanks Ben! It looks like Cody still has some questions around semantics for https://reviews.apache.org/r/33752, please address that and then we can get it committed. Ok, I'll look at that today. Thank you thank you thank you for reaching out for a shepherd too! On Thu, Jun 4, 2015 at 7:00 AM Benjamin Hindman b...@eecs.berkeley.edu wrote: I just took a look and shipped the reviews associated with MESOS-2659. I'll take a look at MESOS-2666 next. Thanks for the contributions James! On Thu, Jun 4, 2015 at 5:54 AM Jake Farrell jfarr...@apache.org wrote: I can only help review, not a Mesos committer -Jake On Wed, Jun 3, 2015 at 11:47 PM, James Peach jor...@gmail.com wrote: On Jun 3, 2015, at 10:25 AM, Jake Farrell jfarr...@apache.org wrote: Happy to help review and provide feedback on these patches Thanks Jake, does that mean you are shepherding too, or just reviewing? -Jake On Wed, Jun 3, 2015 at 12:21 PM, James Peach jor...@gmail.com wrote: On May 18, 2015, at 10:52 AM, Vinod Kone vinodk...@apache.org wrote: Tim and Cody. Do any of you have cycles to shepherd these? If there's no takers, should I just close the tickets? On Fri, May 15, 2015 at 3:19 PM, Vinod Kone vinodk...@gmail.com wrote: -- Vinod -- Forwarded message -- From: James Peach jpe...@apache.org Date: Fri, May 15, 2015 at 9:28 AM Subject: soliciting shepherds for auto tools changes To: benjamin.mah...@gmail.com, c...@mesosphere.io, tstcl...@redhat.com, benjamin.hind...@gmail.com, vinodk...@gmail.com, mcyp...@gmail.com Hi all, I have the following tickets: https://issues.apache.org/jira/browse/MESOS-2537 https://issues.apache.org/jira/browse/MESOS-2659 https://issues.apache.org/jira/browse/MESOS-2666 with corresponding reviews at: https://reviews.apache.org/r/33755/ https://reviews.apache.org/r/33754/ https://reviews.apache.org/r/33753/ https://reviews.apache.org/r/33752/ https://reviews.apache.org/r/33850/ https://reviews.apache.org/r/33849/ Is anyone able to act as shepherd for these? thanks, James
Re: soliciting shepherds for auto tools changes
I just took a look and shipped the reviews associated with MESOS-2659. I'll take a look at MESOS-2666 next. Thanks for the contributions James! On Thu, Jun 4, 2015 at 5:54 AM Jake Farrell jfarr...@apache.org wrote: I can only help review, not a Mesos committer -Jake On Wed, Jun 3, 2015 at 11:47 PM, James Peach jor...@gmail.com wrote: On Jun 3, 2015, at 10:25 AM, Jake Farrell jfarr...@apache.org wrote: Happy to help review and provide feedback on these patches Thanks Jake, does that mean you are shepherding too, or just reviewing? -Jake On Wed, Jun 3, 2015 at 12:21 PM, James Peach jor...@gmail.com wrote: On May 18, 2015, at 10:52 AM, Vinod Kone vinodk...@apache.org wrote: Tim and Cody. Do any of you have cycles to shepherd these? If there's no takers, should I just close the tickets? On Fri, May 15, 2015 at 3:19 PM, Vinod Kone vinodk...@gmail.com wrote: -- Vinod -- Forwarded message -- From: James Peach jpe...@apache.org Date: Fri, May 15, 2015 at 9:28 AM Subject: soliciting shepherds for auto tools changes To: benjamin.mah...@gmail.com, c...@mesosphere.io, tstcl...@redhat.com, benjamin.hind...@gmail.com, vinodk...@gmail.com, mcyp...@gmail.com Hi all, I have the following tickets: https://issues.apache.org/jira/browse/MESOS-2537 https://issues.apache.org/jira/browse/MESOS-2659 https://issues.apache.org/jira/browse/MESOS-2666 with corresponding reviews at: https://reviews.apache.org/r/33755/ https://reviews.apache.org/r/33754/ https://reviews.apache.org/r/33753/ https://reviews.apache.org/r/33752/ https://reviews.apache.org/r/33850/ https://reviews.apache.org/r/33849/ Is anyone able to act as shepherd for these? thanks, James
Re: [DISCUSS] Renaming Mesos Slave
-1 master/worker -1 master/agent -1 leader/follower +1 master/slave; no change needed There's no technical benefit **at all** to a terminology change at this point. If people want to change the names in their client presentations that's fine. Master/slave conveys specific meaning that is lost otherwise. In this context of this project (and elsewhere in Engineering-related fields) the terms are technical jargon and have no social implications within such context. On Thu, Jun 4, 2015 at 9:53 AM, Till Toenshoff toensh...@me.com wrote: 1. Mesos Worker [node/host/machine] 2. Mesos Worker [process] 3. No, master/worker seems to address the issue with less changes. 4. Begin using the new name ASAP, add a disambiguation to the docs, and change old references over time. Fixing the official name, even before changes are in place, would be a good first step. +1 -- James DeFelice 585.241.9488 (voice) 650.649.6071 (fax)
Re: [DISCUSS] Renaming Mesos Slave
1. Mesos Worker [node/host/machine] 2. Mesos Worker [process] 3. No, master/worker seems to address the issue with less changes. 4. Begin using the new name ASAP, add a disambiguation to the docs, and change old references over time. Fixing the official name, even before changes are in place, would be a good first step. +1
Mesos 0.23 Release Planning Guidelines (Proposal)
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, Dynamic Reservations). Once these blockers are resolved, we will start deferring unresolved issues by Priority and Status until we are ready to make the first cut. For details, guidelines, and helpful links, see https://docs.google.com/document/d/1WNvZqdoPn2SDIA_EMvTMn4DFkzrNC2t2xoDfDee7etA/edit Feel free to leave comments on that doc. We can discuss more at the next Developer Sync. TL;DR: Set Target Version to 0.23, update Priority, Status. Find/be a Shepherd. Release JIRA: https://issues.apache.org/jira/browse/MESOS-2727 Dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326227
Introduction - Aditi
Hi all, I'm Aditi and I'm currently interning at Outreachy. Apache Mesos is an amazing piece of software and I'm really excited to work on it. This is my first time contributing to an open source software, so any advice you may have for me is welcome! The project that I would be working on is Updating the Framework Info. The goal of this project is to develop a way to allow frameworks to update their FrameworkInfo without having to restart all the slaves, tasks or master(s) and reconcile the FrameworkInfo. The project is quite nicely described by Vinod Kone in the Confluence link here https://cwiki.apache.org/confluence/display/MESOS/Design+doc%3A+Updating+Framework+Info. Right now, I'm working on starter tickets to get familiar with the Mesos codebase, but I hope to start working on the project soon. Regards, Aditi
RE: [DISCUSS] Renaming Mesos Slave
+1 to Itamar. I'd be interested to hear any case studies of how this has been handled in other OS projects with master/slave namings if anyone can give examples? From: Itamar Ostricher [ita...@yowza3d.com] Sent: 04 June 2015 05:38 To: u...@mesos.apache.org Cc: dev Subject: Re: [DISCUSS] Renaming Mesos Slave Strong -1 for changing the name (either master or slave). From a community stand point, if dev resources are diverted to renaming efforts, then the community and the user base both lose meaningful functionality that isn't being worked on. From a using organization stand point, as well as framework developer perspective, I follow mesos releases pretty closely, and I'm confident that the version that deprecates backward compatibility with the current names will be a version I will not be able to adopt for months, if at all... So please don't do that, or if you do, consider leaving in a configuration option to keep the current names for sane upgrades. On Thu, Jun 4, 2015, 06:42 Benjamin Staffin b...@folsomlabs.commailto:b...@folsomlabs.com wrote: 1. Mesos Worker (or just Mesos node) 2. Mesos Worker 3. No, but if we do then Leader or Director or Controller 4. Deprecation cycle, documentation, etc. Provide aliases for a release or two. Thanks for raising this topic; it's been on my mind for a while. As for why I think this matters: http://en.wikipedia.org/wiki/Microaggression_theory On Mon, Jun 1, 2015 at 2:18 PM, Adam Bordelon a...@mesosphere.iomailto:a...@mesosphere.io wrote: 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 draft a proposal from the discussion and call for a VOTE. Here are the questions I would like us to answer: 1. What should we call the Mesos Slave node/host/machine? 2. What should we call the mesos-slave process (could be the same)? 3. Do we need to rename Mesos Master too? Another topic worth discussing is the deprecation process, but we don't necessarily need to decide on that at the same time as deciding the new name(s). 4. How will we phase in the new name and phase out the old name? Please voice your thoughts and opinions below. Thanks! -Adam- P.S. My personal thoughts: 1. Mesos Worker [Node] 2. Mesos Worker or Agent 3. No 4. Carefully
Re: Introduction - Aditi
Thanks for the information Adam. This really helps! Yes, Vinod is my mentor for the duration of my internship. My JIRA id is aditidixit Thanks, Aditi On Thu, Jun 4, 2015 at 2:56 PM, Adam Bordelon a...@mesosphere.io wrote: 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 that Phase1 was completed in MESOS-2614 https://issues.apache.org/jira/browse/MESOS-2614. Let us know what your JIRA id is so we can add you as a contributor and you can have tickets assigned to you. On Thu, Jun 4, 2015 at 2:00 AM, Aditi Dixit aditi96di...@gmail.com wrote: Hi all, I'm Aditi and I'm currently interning at Outreachy. Apache Mesos is an amazing piece of software and I'm really excited to work on it. This is my first time contributing to an open source software, so any advice you may have for me is welcome! The project that I would be working on is Updating the Framework Info. The goal of this project is to develop a way to allow frameworks to update their FrameworkInfo without having to restart all the slaves, tasks or master(s) and reconcile the FrameworkInfo. The project is quite nicely described by Vinod Kone in the Confluence link here https://cwiki.apache.org/confluence/display/MESOS/Design+doc%3A+Updating+Framework+Info . Right now, I'm working on starter tickets to get familiar with the Mesos codebase, but I hope to start working on the project soon. Regards, Aditi
Re: Introduction - Aditi
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 that Phase1 was completed in MESOS-2614 https://issues.apache.org/jira/browse/MESOS-2614. Let us know what your JIRA id is so we can add you as a contributor and you can have tickets assigned to you. On Thu, Jun 4, 2015 at 2:00 AM, Aditi Dixit aditi96di...@gmail.com wrote: Hi all, I'm Aditi and I'm currently interning at Outreachy. Apache Mesos is an amazing piece of software and I'm really excited to work on it. This is my first time contributing to an open source software, so any advice you may have for me is welcome! The project that I would be working on is Updating the Framework Info. The goal of this project is to develop a way to allow frameworks to update their FrameworkInfo without having to restart all the slaves, tasks or master(s) and reconcile the FrameworkInfo. The project is quite nicely described by Vinod Kone in the Confluence link here https://cwiki.apache.org/confluence/display/MESOS/Design+doc%3A+Updating+Framework+Info . Right now, I'm working on starter tickets to get familiar with the Mesos codebase, but I hope to start working on the project soon. Regards, Aditi
Re: soliciting shepherds for auto tools changes
On Jun 4, 2015, at 9:33 AM, James Peach jor...@gmail.com wrote: On Jun 4, 2015, at 8:31 AM, Benjamin Hindman b...@eecs.berkeley.edu wrote: Took care of MESOS-2666 as well James. There was a bug I had to fix. ;-) Please take a look at the reviews where I left some comments. Thanks Ben! It looks like Cody still has some questions around semantics for https://reviews.apache.org/r/33752, please address that and then we can get it committed. Ok, I'll look at that today. After reviewing the way the bundled packages selection works, I posted https://reviews.apache.org/r/35084/. This changes the behavior of the build somewhat, but allows consistent and fine-grained selection of which bundled packages to use. For example, you can now choose to disable all bundled packages except zookeeper, which might be a reasonable choice on CentOS 7, ./configure --disable-bundled --with-zookeeper=bundled. Currently, you would have to do something like ./configure --enable-bundled --with-glog=/ --with-gmock=/ --with-leveldb=/ --with-protobuf=/ etc ... J
Re: soliciting shepherds for auto tools changes
I can only help review, not a Mesos committer -Jake On Wed, Jun 3, 2015 at 11:47 PM, James Peach jor...@gmail.com wrote: On Jun 3, 2015, at 10:25 AM, Jake Farrell jfarr...@apache.org wrote: Happy to help review and provide feedback on these patches Thanks Jake, does that mean you are shepherding too, or just reviewing? -Jake On Wed, Jun 3, 2015 at 12:21 PM, James Peach jor...@gmail.com wrote: On May 18, 2015, at 10:52 AM, Vinod Kone vinodk...@apache.org wrote: Tim and Cody. Do any of you have cycles to shepherd these? If there's no takers, should I just close the tickets? On Fri, May 15, 2015 at 3:19 PM, Vinod Kone vinodk...@gmail.com wrote: -- Vinod -- Forwarded message -- From: James Peach jpe...@apache.org Date: Fri, May 15, 2015 at 9:28 AM Subject: soliciting shepherds for auto tools changes To: benjamin.mah...@gmail.com, c...@mesosphere.io, tstcl...@redhat.com, benjamin.hind...@gmail.com, vinodk...@gmail.com, mcyp...@gmail.com Hi all, I have the following tickets: https://issues.apache.org/jira/browse/MESOS-2537 https://issues.apache.org/jira/browse/MESOS-2659 https://issues.apache.org/jira/browse/MESOS-2666 with corresponding reviews at: https://reviews.apache.org/r/33755/ https://reviews.apache.org/r/33754/ https://reviews.apache.org/r/33753/ https://reviews.apache.org/r/33752/ https://reviews.apache.org/r/33850/ https://reviews.apache.org/r/33849/ Is anyone able to act as shepherd for these? thanks, James
