Re: Introducing `support/mesos-build.sh`

[Michael Park]

The first run looks good! https://builds.apache.org/job/Mesos-Buildbot/4890/

[image: Screen Shot 2018-02-07 at 10.30.51 PM.png]
On Wed, Feb 7, 2018 at 8:39 PM Michael Park  wrote:

> Yep, Just landed! Waiting for https://builds.apache.org/job/Mesos-Buildbot to
> pick it up.
>
> On Wed, Feb 7, 2018 at 8:27 PM Vinod Kone  wrote:
>
>> Yay, thanks MPark! Has the change landed already?
>>
>> On Wed, Feb 7, 2018 at 8:23 PM, Michael Park  wrote:
>>
>> > Many of you probably know that we currently have
>> `support/docker-build.sh`
>> > to power our CI for our various configurations. One of the problems for
>> us
>> > has been that we create a `Dockerfile` ad-hoc and invoke `docker build`
>> > with it. This is very inefficient and also leads to flaky issues around
>> > `apt-get install`.
>> >
>> > I've introduced `support/mesos-build.sh` which operates off of docker
>> > images hosted on Dockerhub instead, and should aid in bringing us faster
>> > and more stable CI results!
>> >
>> > As a bonus, we now also test Clang on the CentOS 7!
>> >
>> > Thanks,
>> >
>> > MPark
>> >
>>
>

Re: Introducing `support/mesos-build.sh`

[Michael Park]

Yep, Just landed! Waiting for https://builds.apache.org/job/Mesos-Buildbot to
pick it up.

On Wed, Feb 7, 2018 at 8:27 PM Vinod Kone  wrote:

> Yay, thanks MPark! Has the change landed already?
>
> On Wed, Feb 7, 2018 at 8:23 PM, Michael Park  wrote:
>
> > Many of you probably know that we currently have
> `support/docker-build.sh`
> > to power our CI for our various configurations. One of the problems for
> us
> > has been that we create a `Dockerfile` ad-hoc and invoke `docker build`
> > with it. This is very inefficient and also leads to flaky issues around
> > `apt-get install`.
> >
> > I've introduced `support/mesos-build.sh` which operates off of docker
> > images hosted on Dockerhub instead, and should aid in bringing us faster
> > and more stable CI results!
> >
> > As a bonus, we now also test Clang on the CentOS 7!
> >
> > Thanks,
> >
> > MPark
> >
>

Re: The state of our CI

[Vinod Kone]

Thanks for the reminder MPark. And also huge thanks (to you and others who
chipped in) for digging into the blocking fd issue plaguing our CI and
fixing it!

Please please make sure keeping our CI green is among your top priorities.
It's the responsibility of all of us.

For new contributors and committers, the emails from CI go to
bui...@mesos.apache.org. Please subscribe to that list if you haven't
already.

On Wed, Feb 7, 2018 at 8:13 PM, Michael Park  wrote:

> Last week I noticed that our CI (
> https://builds.apache.org/job/Mesos-Buildbot) has been failing for some
> time (I've heard somewhere between 2 weeks and a month). It seems like none
> of us (including me of course) are paying much attention to the
> builds.apache.org emails. Hard to blame ourselves for filtering these
> emails and not paying much attention to the failures given the history of
> flaky tests.
>
> However, I would like to point out that Alex Rukletsov has done a fantastic
> job over the last 4 months or so of trying to keep our CI in a sane state.
> He's been identifying, tracking, and keeping authors accountable of the
> flaky tests and there has been great progress. I would love it if we can
> reap the benefits of his (and others!) efforts simply by us keeping a
> closer eye on our CI.
>
> Thanks,
>
> MPark
>

Re: Introducing `support/mesos-build.sh`

[Vinod Kone]

Yay, thanks MPark! Has the change landed already?

On Wed, Feb 7, 2018 at 8:23 PM, Michael Park  wrote:

> Many of you probably know that we currently have `support/docker-build.sh`
> to power our CI for our various configurations. One of the problems for us
> has been that we create a `Dockerfile` ad-hoc and invoke `docker build`
> with it. This is very inefficient and also leads to flaky issues around
> `apt-get install`.
>
> I've introduced `support/mesos-build.sh` which operates off of docker
> images hosted on Dockerhub instead, and should aid in bringing us faster
> and more stable CI results!
>
> As a bonus, we now also test Clang on the CentOS 7!
>
> Thanks,
>
> MPark
>

Introducing `support/mesos-build.sh`

[Michael Park]

Many of you probably know that we currently have `support/docker-build.sh`
to power our CI for our various configurations. One of the problems for us
has been that we create a `Dockerfile` ad-hoc and invoke `docker build`
with it. This is very inefficient and also leads to flaky issues around
`apt-get install`.

I've introduced `support/mesos-build.sh` which operates off of docker
images hosted on Dockerhub instead, and should aid in bringing us faster
and more stable CI results!

As a bonus, we now also test Clang on the CentOS 7!

Thanks,

MPark

The state of our CI

[Michael Park]

Last week I noticed that our CI (
https://builds.apache.org/job/Mesos-Buildbot) has been failing for some
time (I've heard somewhere between 2 weeks and a month). It seems like none
of us (including me of course) are paying much attention to the
builds.apache.org emails. Hard to blame ourselves for filtering these
emails and not paying much attention to the failures given the history of
flaky tests.

However, I would like to point out that Alex Rukletsov has done a fantastic
job over the last 4 months or so of trying to keep our CI in a sane state.
He's been identifying, tracking, and keeping authors accountable of the
flaky tests and there has been great progress. I would love it if we can
reap the benefits of his (and others!) efforts simply by us keeping a
closer eye on our CI.

Thanks,

MPark

Re: Soliciting Hackathon Ideas

[Andrew Schwartzmeyer]

Thanks all for the ideas! (And keep them coming if you have more, it's 
not for another couple weeks.) I'll make sure to put together a list and 
run it by a few of you before I fly out.


On 02/07/2018 3:22 pm, Benjamin Mahler wrote:

-list to bcc

Hey Tim! Sorry that this fell through the cracks, Vinod and I can 
shepherd

this.

What time zone are you in? We can set up a hangout to go over it.

Ben

On Wed, Feb 7, 2018 at 8:13 AM, Timothy Anderegg 
 wrote:

>
>
> > On Feb 6, 2018, at 11:21 PM, Benjamin Mahler 
wrote:
> >
> > +1 Versioned documentation would be heroic!
>
> Based on https://reviews.apache.org/r/52064/ ?
>
> >
> > On Tue, Feb 6, 2018 at 5:49 PM Vinod Kone  wrote:
> >
> >> Versioned documentation!
> >>
> >> Sent from my iPhone
> >>
> >>> On Feb 6, 2018, at 4:37 PM, Benjamin Mahler 
> wrote:
> >>>
> >>> A couple of ideas from the performance related working group:
> >>>
> >>> -Use protobuf arenas for all non-trivial outbound master messages
> (easy)
> >>> This can be done piecemeal.
> >>> -Use move semantics (take a Message&&) in all of the master message
> >>> handlers to reduce copying (medium) This one can be done piecemeal.
For
> >>> example Master::statusUpdate would be a good one to start with.
> >>> -Audit the Registrar code to use move semantics to reduce copying
> >> (medium)
> >>>
> >>> If there are any UI programmers:
> >>>
> >>> -Consider a webui "refresh", try to find a new set of fonts and
style,
> >>> could be fun.
> >>>
> >>> On Fri, Feb 2, 2018 at 12:47 PM, Andrew Schwartzmeyer <
> >>> and...@schwartzmeyer.com> wrote:
> >>>
>  Hello all,
> 
>  Next month I'll be attending HackIllinois (
https://hackillinois.org/)
> >> as
>  an open-source mentor. It's a huge student-run hackathon at the
> >> University
>  of Illinois at Urbana-Champaign, running from February 23rd to the
> 25th.
>  Students from a multitude of schools will be attending (they even
bus
> >> them
>  in). The hackathon has an open-source focus, and while there will be
> >> many
>  projects for the students to work on, I want to make sure Mesos gets
> >> some
>  attention too.
> 
>  I am asking you all for open issues and new ideas for small,
>  beginner-friendly projects that could fit a two-day Hackathon
project.
> >> For
>  Mesos, I'm looking through our open issues labeled "easyfix",
> >> "beginner",
>  or "newbie", which actually returns 74 results! If you have anything
> in
>  particular that you think would be a good fit, please let me know.
I'd
> >> like
>  to go with a list of vetted issues so I don't accidentally start
some
>  students in on a giant can of worms. Our excellent new Beginner
> >> Contributor
>  Guide will be a huge help too.
> 
>  Thanks,
> 
>  Andy
> 
>  P.S. If any of you also want to attend, let me know, and I'll get
you
> in
>  touch with their director.
> 
> >>
>
>

Re: Soliciting Hackathon Ideas

[Timothy Anderegg]

Sorry to threadjack this :)  The Hackathon sounds cool, good luck!  BTW I
finally finished the Broken Earth trilogy, it was incredible!

Hope you're doing well,

Tim

On Fri, Feb 2, 2018 at 3:47 PM Andrew Schwartzmeyer <
and...@schwartzmeyer.com> wrote:

> Hello all,
>
> Next month I'll be attending HackIllinois (https://hackillinois.org/) as
> an open-source mentor. It's a huge student-run hackathon at the
> University of Illinois at Urbana-Champaign, running from February 23rd
> to the 25th. Students from a multitude of schools will be attending
> (they even bus them in). The hackathon has an open-source focus, and
> while there will be many projects for the students to work on, I want to
> make sure Mesos gets some attention too.
>
> I am asking you all for open issues and new ideas for small,
> beginner-friendly projects that could fit a two-day Hackathon project.
> For Mesos, I'm looking through our open issues labeled "easyfix",
> "beginner", or "newbie", which actually returns 74 results! If you have
> anything in particular that you think would be a good fit, please let me
> know. I'd like to go with a list of vetted issues so I don't
> accidentally start some students in on a giant can of worms. Our
> excellent new Beginner Contributor Guide will be a huge help too.
>
> Thanks,
>
> Andy
>
> P.S. If any of you also want to attend, let me know, and I'll get you in
> touch with their director.
>

Re: Implicit reconcile "pauses" offer stream in large cluster

[Benjamin Mahler]

Following up, did you gather any perf data for this?

On Sat, Dec 30, 2017 at 8:15 AM, Meghdoot bhattacharya <
meghdoo...@yahoo.com.invalid> wrote:

> Zhitao any further updates on this?
>
> Thx
>
> > On Dec 13, 2017, at 1:02 PM, Benjamin Mahler  wrote:
> >
> > You can check the diff, for example:
> > https://github.com/apache/mesos/compare/1.3.0...1.4.0
> >
> > I didn't notice any changes that look like they would cause this.
> >
> > What do the master logs show during the time frame?
> > Have you profiled what the master and scheduler are doing during this
> time
> > frame?
> >
> >> On Tue, Dec 12, 2017 at 10:46 AM, Zhitao Li 
> wrote:
> >>
> >> Hi,
> >>
> >> We have seen some potential problems when trying to upgrading Mesos from
> >> 1.3 to 1.4: when an implicit reconciliation happened for a large
> framework
> >> (Aurora) , the scheduler would not see any offer for several minutes.
> >> Strangely this does not show up once we revert back to 1.3.
> >>
> >> A couple of questions:
> >>
> >> 1) Is there any between 1.3 and 1.4 which can make this slower?
> >> 2) FWICT by reading code of implicit reconcile, Mesos master sends back
> >> status for all active and pending tasks for the framework (which has
> 70k+
> >> in our cluster right now) in batch before yielding to any other
> messages.
> >> Has anyone thought about supporting some kind of "pagination": i.e,
> master
> >> would only send back N status updates, then delay for S seconds, then
> send
> >> back next batch of N updates, until all active tasks are handled. This
> is
> >> pretty much how Aurora triggers explicit reconcile to Mesos, and we
> don't
> >> see any issue when processing it this way.
> >>
> >> Thanks!
> >>
> >>
> >> --
> >> Cheers,
> >>
> >> Zhitao Li
> >>
>

[Containerization WG] Sync tomorrow

[Jie Yu]

Hi folks,

During the sync tomorrow, we'll be doing a grooming for all the
containerization related bugs and issues in Mesos JIRA:
Bugs: https://issues.apache.org/jira/issues/?filter=12343087
All issues: https://issues.apache.org/jira/issues/?filter=12343086

Please join us if you're interested.

If you want to discuss anything else, please add to the agenda
https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit#

Thanks!
- Jie

Re: Soliciting Hackathon Ideas

[Benjamin Mahler]

-list to bcc

Hey Tim! Sorry that this fell through the cracks, Vinod and I can shepherd
this.

What time zone are you in? We can set up a hangout to go over it.

Ben

On Wed, Feb 7, 2018 at 8:13 AM, Timothy Anderegg  wrote:

> I've been looking for a new shepherd for that for a while, if there are any
> takers I'm happy to rebase against the latest code!
>
> Tim
>
> On Wed, Feb 7, 2018 at 11:10 AM James Peach  wrote:
>
> >
> >
> > > On Feb 6, 2018, at 11:21 PM, Benjamin Mahler 
> wrote:
> > >
> > > +1 Versioned documentation would be heroic!
> >
> > Based on https://reviews.apache.org/r/52064/ ?
> >
> > >
> > > On Tue, Feb 6, 2018 at 5:49 PM Vinod Kone  wrote:
> > >
> > >> Versioned documentation!
> > >>
> > >> Sent from my iPhone
> > >>
> > >>> On Feb 6, 2018, at 4:37 PM, Benjamin Mahler 
> > wrote:
> > >>>
> > >>> A couple of ideas from the performance related working group:
> > >>>
> > >>> -Use protobuf arenas for all non-trivial outbound master messages
> > (easy)
> > >>> This can be done piecemeal.
> > >>> -Use move semantics (take a Message&&) in all of the master message
> > >>> handlers to reduce copying (medium) This one can be done piecemeal.
> For
> > >>> example Master::statusUpdate would be a good one to start with.
> > >>> -Audit the Registrar code to use move semantics to reduce copying
> > >> (medium)
> > >>>
> > >>> If there are any UI programmers:
> > >>>
> > >>> -Consider a webui "refresh", try to find a new set of fonts and
> style,
> > >>> could be fun.
> > >>>
> > >>> On Fri, Feb 2, 2018 at 12:47 PM, Andrew Schwartzmeyer <
> > >>> and...@schwartzmeyer.com> wrote:
> > >>>
> >  Hello all,
> > 
> >  Next month I'll be attending HackIllinois (
> https://hackillinois.org/)
> > >> as
> >  an open-source mentor. It's a huge student-run hackathon at the
> > >> University
> >  of Illinois at Urbana-Champaign, running from February 23rd to the
> > 25th.
> >  Students from a multitude of schools will be attending (they even
> bus
> > >> them
> >  in). The hackathon has an open-source focus, and while there will be
> > >> many
> >  projects for the students to work on, I want to make sure Mesos gets
> > >> some
> >  attention too.
> > 
> >  I am asking you all for open issues and new ideas for small,
> >  beginner-friendly projects that could fit a two-day Hackathon
> project.
> > >> For
> >  Mesos, I'm looking through our open issues labeled "easyfix",
> > >> "beginner",
> >  or "newbie", which actually returns 74 results! If you have anything
> > in
> >  particular that you think would be a good fit, please let me know.
> I'd
> > >> like
> >  to go with a list of vetted issues so I don't accidentally start
> some
> >  students in on a giant can of worms. Our excellent new Beginner
> > >> Contributor
> >  Guide will be a huge help too.
> > 
> >  Thanks,
> > 
> >  Andy
> > 
> >  P.S. If any of you also want to attend, let me know, and I'll get
> you
> > in
> >  touch with their director.
> > 
> > >>
> >
> >
>

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

[Andrew Schwartzmeyer]

+1 (binding)

Passed internal CI and hand tests (debug and release builds). Only 
failure was due to a CI configuration only compatible with 1.6.


On 02/06/2018 4:19 pm, Andrew Schwartzmeyer wrote:

+0 (binding)

We're putting 1.5.0-rc2 through a hybrid DC/OS cluster end-to-end test
suite, but the results won't be back until tomorrow. If we could delay
a day, that'd be great.

On 02/05/2018 9:24 pm, Chun-Hung Hsiao wrote:

+1 (non-binding)

Tested with `make distcheck` with grpc disabled and enabled on mac.
Tested with `make distcheck DISTCHECK_CONFIGURE_FLAGS='--enable-grpc'` 
on

centos 7.

On Mon, Feb 5, 2018 at 8:33 PM, Vinod Kone  
wrote:



+1 (binding)

Tested on ASF CI. The red builds were known flaky tests regarding
checks/health checks.

*Revision*: f7e3872b0359c6095f8eeaefe408cb7dcef5bb83

   - refs/tags/1.5.0-rc2

Configuration Matrix gcc clang
centos:7 --verbose --enable-libevent --enable-ssl autotools
[image: Failed]

[image: Not run]
cmake
[image: Success]

[image: Not run]
--verbose autotools
[image: Failed]

[image: Not run]
cmake
[image: Success]

[image: Not run]
ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
[image: Success]

[image: Success]

cmake
[image: Success]

[image: Success]

--verbose autotools
[image: Success]

[image: Success]

cmake
[image: Success]

[image: Success]


On Sat, Feb 3, 2018 at 11:11 AM, Zhitao Li  
wrote:


> +1 (non-binding)
>
> Tested with running all tests on Debian/jessie server on AWS.
>
> On Fri, Feb 2, 2018 at 3:25 PM, Jie Yu  wrote:
>
>> +1
>>
>> Verified in our internal CI that `sudo make check` passed in CentOS 6,
>> CentOS7, Debian 8, Ubuntu 14.04, Ubuntu 16.04 (both w/ or w/o SSL
>> enabled).
>>
>>
>> On Thu, Feb 1, 2018 at 5:36 PM, Gilbert Song 
wrote:
>>

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

[James Peach]

+1 (binding)

Tested on Fedora 27

> On Feb 1, 2018, at 5:36 PM, Gilbert Song  wrote:
> 
> Hi all,
> 
> Please vote on releasing the following candidate as Apache Mesos 1.5.0.
> 
> 1.5.0 includes the following:
> 
>  * Support Container Storage Interface (CSI).
>  * Agent reconfiguration policy.
>  * Auto GC docker images in Mesos Containerizer.
>  * Standalone containers.
>  * Support gRPC client.
>  * Non-leading VOTING replica catch-up.
> 
> 
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.5.0-rc2
> 
> 
> The candidate for Mesos 1.5.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.5.0-rc2/mesos-1.5.0.tar.gz
> 
> The tag to be voted on is 1.5.0-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.5.0-rc2
> 
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.5.0-rc2/mesos-1.5.0.tar.gz.md5
> 
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.5.0-rc2/mesos-1.5.0.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-1222
> 
> Please vote on releasing this package as Apache Mesos 1.5.0!
> 
> The vote is open until Tue Feb  6 17:35:16 PST 2018 and passes if a
> majority of at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Mesos 1.5.0
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> Jie and Gilbert

Re: Soliciting Hackathon Ideas

[Timothy Anderegg]

I've been looking for a new shepherd for that for a while, if there are any
takers I'm happy to rebase against the latest code!

Tim

On Wed, Feb 7, 2018 at 11:10 AM James Peach  wrote:

>
>
> > On Feb 6, 2018, at 11:21 PM, Benjamin Mahler  wrote:
> >
> > +1 Versioned documentation would be heroic!
>
> Based on https://reviews.apache.org/r/52064/ ?
>
> >
> > On Tue, Feb 6, 2018 at 5:49 PM Vinod Kone  wrote:
> >
> >> Versioned documentation!
> >>
> >> Sent from my iPhone
> >>
> >>> On Feb 6, 2018, at 4:37 PM, Benjamin Mahler 
> wrote:
> >>>
> >>> A couple of ideas from the performance related working group:
> >>>
> >>> -Use protobuf arenas for all non-trivial outbound master messages
> (easy)
> >>> This can be done piecemeal.
> >>> -Use move semantics (take a Message&&) in all of the master message
> >>> handlers to reduce copying (medium) This one can be done piecemeal. For
> >>> example Master::statusUpdate would be a good one to start with.
> >>> -Audit the Registrar code to use move semantics to reduce copying
> >> (medium)
> >>>
> >>> If there are any UI programmers:
> >>>
> >>> -Consider a webui "refresh", try to find a new set of fonts and style,
> >>> could be fun.
> >>>
> >>> On Fri, Feb 2, 2018 at 12:47 PM, Andrew Schwartzmeyer <
> >>> and...@schwartzmeyer.com> wrote:
> >>>
>  Hello all,
> 
>  Next month I'll be attending HackIllinois (https://hackillinois.org/)
> >> as
>  an open-source mentor. It's a huge student-run hackathon at the
> >> University
>  of Illinois at Urbana-Champaign, running from February 23rd to the
> 25th.
>  Students from a multitude of schools will be attending (they even bus
> >> them
>  in). The hackathon has an open-source focus, and while there will be
> >> many
>  projects for the students to work on, I want to make sure Mesos gets
> >> some
>  attention too.
> 
>  I am asking you all for open issues and new ideas for small,
>  beginner-friendly projects that could fit a two-day Hackathon project.
> >> For
>  Mesos, I'm looking through our open issues labeled "easyfix",
> >> "beginner",
>  or "newbie", which actually returns 74 results! If you have anything
> in
>  particular that you think would be a good fit, please let me know. I'd
> >> like
>  to go with a list of vetted issues so I don't accidentally start some
>  students in on a giant can of worms. Our excellent new Beginner
> >> Contributor
>  Guide will be a huge help too.
> 
>  Thanks,
> 
>  Andy
> 
>  P.S. If any of you also want to attend, let me know, and I'll get you
> in
>  touch with their director.
> 
> >>
>
>

Re: Soliciting Hackathon Ideas

[James Peach]

> On Feb 6, 2018, at 11:21 PM, Benjamin Mahler  wrote:
> 
> +1 Versioned documentation would be heroic!

Based on https://reviews.apache.org/r/52064/ ?

> 
> On Tue, Feb 6, 2018 at 5:49 PM Vinod Kone  wrote:
> 
>> Versioned documentation!
>> 
>> Sent from my iPhone
>> 
>>> On Feb 6, 2018, at 4:37 PM, Benjamin Mahler  wrote:
>>> 
>>> A couple of ideas from the performance related working group:
>>> 
>>> -Use protobuf arenas for all non-trivial outbound master messages (easy)
>>> This can be done piecemeal.
>>> -Use move semantics (take a Message&&) in all of the master message
>>> handlers to reduce copying (medium) This one can be done piecemeal. For
>>> example Master::statusUpdate would be a good one to start with.
>>> -Audit the Registrar code to use move semantics to reduce copying
>> (medium)
>>> 
>>> If there are any UI programmers:
>>> 
>>> -Consider a webui "refresh", try to find a new set of fonts and style,
>>> could be fun.
>>> 
>>> On Fri, Feb 2, 2018 at 12:47 PM, Andrew Schwartzmeyer <
>>> and...@schwartzmeyer.com> wrote:
>>> 
 Hello all,
 
 Next month I'll be attending HackIllinois (https://hackillinois.org/)
>> as
 an open-source mentor. It's a huge student-run hackathon at the
>> University
 of Illinois at Urbana-Champaign, running from February 23rd to the 25th.
 Students from a multitude of schools will be attending (they even bus
>> them
 in). The hackathon has an open-source focus, and while there will be
>> many
 projects for the students to work on, I want to make sure Mesos gets
>> some
 attention too.
 
 I am asking you all for open issues and new ideas for small,
 beginner-friendly projects that could fit a two-day Hackathon project.
>> For
 Mesos, I'm looking through our open issues labeled "easyfix",
>> "beginner",
 or "newbie", which actually returns 74 results! If you have anything in
 particular that you think would be a good fit, please let me know. I'd
>> like
 to go with a list of vetted issues so I don't accidentally start some
 students in on a giant can of worms. Our excellent new Beginner
>> Contributor
 Guide will be a huge help too.
 
 Thanks,
 
 Andy
 
 P.S. If any of you also want to attend, let me know, and I'll get you in
 touch with their director.
 
>>