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: 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: Catching the webui up to features

[Timothy Anderegg]

We have a similar scenario using an actual proxy (Apache in this case) in
front of a firewalled VLAN, that also does Kerberos authentication against
the endpoints.  This currently works fine for external API requests but the
WebUI is only partially functional, since I haven't looked into the newer
Mesos features to support proxying that Ben mentioned.  I will try to
implement those and see if I can get it all working as it should.  Is there
documentation on those features?  If not I will figure it out and submit
some :)

YARN handles this differently (like Aaron thought Mesos would), such that
the web UI has its own proxy that allows access to some of the services
running on it without having to do more complex standalone proxy
configurations or service discovery, but implementing that for Mesos would
certainly increase the complexity of Mesos' web UI.  This does enable some
nice features such as being able to access the Spark UI automatically via
the Yarn UI, without having to worry about where the driver is running or
what port it is on.

- Tim

On Wed, Oct 18, 2017 at 1:11 PM Aaron Wood  wrote:

> In this case localhost is my host (OSX) and u64 is my guest (Ubuntu VM).
> What I was doing was viewing the Mesos UI from my host by making use of
> port mapping in my VM. Port 10050 on my host maps to 5050 inside my VM. So
> in a way this is like viewing the UI with a proxy in the middle. What I was
> expecting was that I could view the UI served from the master and not have
> to worry about reaching the agents directly for their information. I'm not
> using DC/OS at all here, just my own builds of Apache Mesos.
>
> I was thinking that if the master was able to handle the communication with
> the agents (and other masters if the leader changes) that people would be
> able to use the UI in situations like mine, or more realistically, in
> situations where you have some sort of cluster that you need to tunnel into
> in order to reach Mesos. For example, Mesos is not exposed outside of our
> cluster directly since the cluster has its own private internal network.
> You have to tunnel in using our defined node(s) that are on both the
> external and internal network.
>
> I hope that helps explain the scenario!
>
> Thanks,
> Aaron
>
> On Tue, Oct 17, 2017 at 3:05 PM, Benjamin Mahler 
> wrote:
>
> > What does localhost vs u64 represent for you there in terms of your
> actual
> > cluster?
> >
> > Are you expecting to be able to publicly access the masters and agents?
> Or
> > are you running a proxy (like DC/OS's adminrouter)?
> > We recently made some changes that makes it easier to patch the UI to
> work
> > with a proxy.
> >
> > Would be great to understand how you'd like it to work.
> >
> > Ben
> >
> > On Tue, Sep 26, 2017 at 9:15 AM, Aaron Wood 
> wrote:
> >
> > > You're right about the slaves section in 0.28.x. There are no error
> > > messages or modals that pop up but looking at the requests after you
> > click
> > > on a slave in the slaves section shows these obvious failures (u64 is
> the
> > > hostname of my VM which won't be resolved from the host):
> > >
> > > Request URL:
> > > http://u64:5051/slave(1)/state?jsonp=angular.callbacks._6
> > > Request URL:
> > > http://u64:5051/metrics/snapshot?jsonp=angular.callbacks._7
> > > Request URL:
> > > http://u64:5051/monitor/statistics?jsonp=angular.callbacks._8
> > >
> > > What does work in 0.28.x (and doesn't in 1.0.x) is the main page which
> > has
> > > AJAX calls on an interval. These are successfully completed every 10
> > > seconds or so:
> > >
> > > Request URL:
> > > http://localhost:10050/master/state
> > > Request URL:
> > > http://localhost:10050/metrics/snapshot
> > >
> > > In the newer versions of Mesos these requests are a bit different and
> > fail:
> > >
> > > Request URL:
> > > http://u64:5050/master/state?jsonp=angular.callbacks._2
> > > Request URL:
> > > http://u64:5050/metrics/snapshot?jsonp=angular.callbacks._3
> > >
> > > This is what causes the error modal to pop up on every interval tick of
> > > these AJAX requests.
> > >
> > > Thanks,
> > > Aaron
> > >
> > > On Mon, Sep 25, 2017 at 7:47 PM, Benjamin Mahler 
> > > wrote:
> > >
> > > > 0.28.x UI is working for you even when you click into an agent?
> > > >
> > > > Can you show us which requests are being made in the old UI vs the
> new
> > UI
> > > > and which ones do not work for you? (use chrome's built-in debugging
> > > tools)
> > > >
> > > > On Mon, Sep 25, 2017 at 3:38 PM, Aaron Wood 
> > > wrote:
> > > >
> > > > > I just built Mesos 0.28.x and tried out this scenario. It seems
> that
> > > this
> > > > > issue presents itself only in 1.0.x and up. I also found out that
> > DCOS
> > > > > hides this issue if someone uses
> https://github.com/dcos/adminrouter
> > > > >
> > > > > I have not dug through the 0.28.x code enough to pinpoint the exact
> > > area
> > > > > for where 

Re: Refactoring configuration docs

[Timothy Anderegg]

+1

On Mon, Oct 2, 2017 at 1:14 PM James Peach  wrote:

>
> > On Oct 2, 2017, at 10:12 AM, Andrew Schwartzmeyer <
> and...@schwartzmeyer.com> wrote:
> >
> > I'm going to assume everyone said "go for it!"
>
> Go for it!
>
> >
> > Cheers,
> >
> > Andrew Schwartzmeyer
> >
> > On 09/28/2017 9:18 am, Andrew Schwartzmeyer wrote:
> >> Hi all,
> >> I'm going through and updating the CMake docs, and that brought me to
> >> our docs/configuration.md file. This file is huge! In the style of
> >> Jie's refactor of the isolator docs, I'd like to create a
> >> docs/configuration folder, and split these files into mesos.md,
> >> master.md, agent.md, libprocess.md, autotools.md, and cmake.md within
> >> that folder.
> >> I think this important for discoverability, especially considering
> >> that we lack a table of contents. After re-organizing, I would suggest
> >> that docs/configuration.md become a table of contents with relative
> >> links into the configuration folder.
> >> Any objections / ongoing work I might interfere with?
> >> Thanks,
> >> Andrew Schwartzmeyer
>
>

Re: Two important tickets for improving documentation

[Timothy Anderegg]

So a few days turned into a few months, but Mesos-3011 (versioned
documentation on the website) is ready for review if anyone has time,
thanks!  https://issues.apache.org/jira/browse/MESOS-3011

-Tim

On Thu, Jun 30, 2016 at 9:43 PM Timothy Anderegg <timothy.ander...@gmail.com>
wrote:

> Yep, thanks Vinod!
>
> On Thu, Jun 30, 2016, 9:24 PM Benjamin Mahler <bmah...@apache.org> wrote:
>
>> Looks like Vinod will shepherd, thanks Vinod!
>>
>> On Tue, Jun 28, 2016 at 4:38 PM, Timothy Anderegg <
>> timothy.ander...@gmail.com> wrote:
>>
>> > I picked it up as part of the website working group, but don't have a
>> > shepherd yet.
>> >
>> > On Tue, Jun 28, 2016, 7:06 PM Benjamin Mahler <bmah...@apache.org>
>> wrote:
>> >
>> > > Thanks a lot Timothy!
>> > >
>> > > Do you have a shepherd or do you still need one?
>> > >
>> > > On Tue, Jun 28, 2016 at 7:19 AM, Timothy Anderegg <
>> > > timothy.ander...@gmail.com> wrote:
>> > >
>> > > > Hi Ben - I'm actually almost done with Mesos-3011, will open a
>> review
>> > > > request in the next few days.  Only a few last issues to resolve.
>> > > >
>> > > > On Mon, Jun 27, 2016, 11:20 PM Benjamin Mahler <bmah...@apache.org>
>> > > wrote:
>> > > >
>> > > > > Just wanted to highlight two tickets that would be of great help
>> to
>> > the
>> > > > > community.
>> > > > >
>> > > > > (1) The first is to publish documentation on the website for each
>> > > > release.
>> > > > > We currently publish periodically off of master, and so it's a
>> pain
>> > for
>> > > > > users because the documentation does not reflect the version they
>> are
>> > > > > running:
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/MESOS-3011
>> > > > >
>> > > > > Once we have the tooling we can publish the documentation for
>> > previous
>> > > > > releases.
>> > > > >
>> > > > > (2) The second is to automate the generation of docs/
>> > configuration.md.
>> > > > As
>> > > > > far as I know, we're still generating this manually, which makes
>> it a
>> > > > huge
>> > > > > pain and consequently it becomes stale:
>> > > > >
>> > > > > https://issues.apache.org/jira/browse/MESOS-3019
>> > > > >
>> > > > > This would be done in a similar way to how Kevin Klues added a
>> > support
>> > > > > script for generating the help endpoint documentation.
>> > > > >
>> > > > > Vinod, looks like we need to do an update of configuration.md for
>> > 1.0?
>> > > > >
>> > > > > Ben
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: Two important tickets for improving documentation

[Timothy Anderegg]

Yep, thanks Vinod!

On Thu, Jun 30, 2016, 9:24 PM Benjamin Mahler <bmah...@apache.org> wrote:

> Looks like Vinod will shepherd, thanks Vinod!
>
> On Tue, Jun 28, 2016 at 4:38 PM, Timothy Anderegg <
> timothy.ander...@gmail.com> wrote:
>
> > I picked it up as part of the website working group, but don't have a
> > shepherd yet.
> >
> > On Tue, Jun 28, 2016, 7:06 PM Benjamin Mahler <bmah...@apache.org>
> wrote:
> >
> > > Thanks a lot Timothy!
> > >
> > > Do you have a shepherd or do you still need one?
> > >
> > > On Tue, Jun 28, 2016 at 7:19 AM, Timothy Anderegg <
> > > timothy.ander...@gmail.com> wrote:
> > >
> > > > Hi Ben - I'm actually almost done with Mesos-3011, will open a review
> > > > request in the next few days.  Only a few last issues to resolve.
> > > >
> > > > On Mon, Jun 27, 2016, 11:20 PM Benjamin Mahler <bmah...@apache.org>
> > > wrote:
> > > >
> > > > > Just wanted to highlight two tickets that would be of great help to
> > the
> > > > > community.
> > > > >
> > > > > (1) The first is to publish documentation on the website for each
> > > > release.
> > > > > We currently publish periodically off of master, and so it's a pain
> > for
> > > > > users because the documentation does not reflect the version they
> are
> > > > > running:
> > > > >
> > > > > https://issues.apache.org/jira/browse/MESOS-3011
> > > > >
> > > > > Once we have the tooling we can publish the documentation for
> > previous
> > > > > releases.
> > > > >
> > > > > (2) The second is to automate the generation of docs/
> > configuration.md.
> > > > As
> > > > > far as I know, we're still generating this manually, which makes
> it a
> > > > huge
> > > > > pain and consequently it becomes stale:
> > > > >
> > > > > https://issues.apache.org/jira/browse/MESOS-3019
> > > > >
> > > > > This would be done in a similar way to how Kevin Klues added a
> > support
> > > > > script for generating the help endpoint documentation.
> > > > >
> > > > > Vinod, looks like we need to do an update of configuration.md for
> > 1.0?
> > > > >
> > > > > Ben
> > > > >
> > > >
> > >
> >
>

Re: Two important tickets for improving documentation

[Timothy Anderegg]

I picked it up as part of the website working group, but don't have a
shepherd yet.

On Tue, Jun 28, 2016, 7:06 PM Benjamin Mahler <bmah...@apache.org> wrote:

> Thanks a lot Timothy!
>
> Do you have a shepherd or do you still need one?
>
> On Tue, Jun 28, 2016 at 7:19 AM, Timothy Anderegg <
> timothy.ander...@gmail.com> wrote:
>
> > Hi Ben - I'm actually almost done with Mesos-3011, will open a review
> > request in the next few days.  Only a few last issues to resolve.
> >
> > On Mon, Jun 27, 2016, 11:20 PM Benjamin Mahler <bmah...@apache.org>
> wrote:
> >
> > > Just wanted to highlight two tickets that would be of great help to the
> > > community.
> > >
> > > (1) The first is to publish documentation on the website for each
> > release.
> > > We currently publish periodically off of master, and so it's a pain for
> > > users because the documentation does not reflect the version they are
> > > running:
> > >
> > > https://issues.apache.org/jira/browse/MESOS-3011
> > >
> > > Once we have the tooling we can publish the documentation for previous
> > > releases.
> > >
> > > (2) The second is to automate the generation of docs/configuration.md.
> > As
> > > far as I know, we're still generating this manually, which makes it a
> > huge
> > > pain and consequently it becomes stale:
> > >
> > > https://issues.apache.org/jira/browse/MESOS-3019
> > >
> > > This would be done in a similar way to how Kevin Klues added a support
> > > script for generating the help endpoint documentation.
> > >
> > > Vinod, looks like we need to do an update of configuration.md for 1.0?
> > >
> > > Ben
> > >
> >
>

Re: Two important tickets for improving documentation

[Timothy Anderegg]

Hi Ben - I'm actually almost done with Mesos-3011, will open a review
request in the next few days.  Only a few last issues to resolve.

On Mon, Jun 27, 2016, 11:20 PM Benjamin Mahler  wrote:

> Just wanted to highlight two tickets that would be of great help to the
> community.
>
> (1) The first is to publish documentation on the website for each release.
> We currently publish periodically off of master, and so it's a pain for
> users because the documentation does not reflect the version they are
> running:
>
> https://issues.apache.org/jira/browse/MESOS-3011
>
> Once we have the tooling we can publish the documentation for previous
> releases.
>
> (2) The second is to automate the generation of docs/configuration.md. As
> far as I know, we're still generating this manually, which makes it a huge
> pain and consequently it becomes stale:
>
> https://issues.apache.org/jira/browse/MESOS-3019
>
> This would be done in a similar way to how Kevin Klues added a support
> script for generating the help endpoint documentation.
>
> Vinod, looks like we need to do an update of configuration.md for 1.0?
>
> Ben
>

Re: Conceptual question Task Container

[Timothy Anderegg]

The same is true with all frameworks I've used, such as Marathon - each
executor manages one task (although it can have multiple "runs").

On Mon, Jun 27, 2016 at 9:49 AM haosdent  wrote:

> Hi, @Dave If you use mesos-executor or mesos-docker-executor. It only would
> launch one Task during executor lifecycle, so your problem does not exist.
>
> On Mon, Jun 27, 2016 at 5:38 PM, Dave Webb  wrote:
>
> > Hi,
> >
> > I'm currently familiarizing myself with the Mesos source code and have a
> > conceptual question about executors, tasks and the containerizer.
> > Basically, each executor gets its own container (and thus its own cgroup
> > subtree ".../mesos/executor0" when using cgroup isolation). This achieves
> > isolation between different executors.
> >
> > However, all Tasks which are eligible for the same executor, are just
> > assigned to it and the corresponding executor is "enlarged".
> > Yet, the individual tasks do not get their own container (and therefore
> no
> > cgroup subtree ".../mesos/executor0/task0" is created).
> >
> > From my understanding, this behavior implies that tasks within the same
> > executor are not isolated at all (at least when using cgroups).
> > Also when implementing your own executor, the API does not offer the
> > possibility to create individual containers for tasks.
> >
> > I find this quite inconsistent:
> > Tasks contain information about their assigned resources, but this
> > information has different meaning depending on the executors.
> > If a task has its own executor, its resources are isolated. But if there
> > are multiple tasks within one executor, the sum of all resources is
> shared
> > within these tasks.
> >
> > Have I missed anything or why was this behavior chosen?
> > Wouldn't it be more consistent if resource were assigned to executors
> > instead of tasks?
> >
> > Thank you very much!
> > Dave
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Re: Slack as the canonical chat channel

[Timothy Anderegg]

+1 to Slack

On Fri, Jun 17, 2016 at 6:46 PM Michael Park  wrote:

> +1 for Slack for me as well, but is it possible/feasible?
>
> On 17 June 2016 at 18:07, tommy xiao  wrote:
>
> > +1 Slack!
> >
> > 2016-06-18 4:54 GMT+08:00 Vinod Kone :
> >
> > > -benh, jake : so that they don't get spammed by reply-alls :)
> > >
> > > On Fri, Jun 17, 2016 at 1:50 PM, Kapil Arya 
> wrote:
> > >
> > > > +1 Slack!
> > > >
> > > > On Fri, Jun 17, 2016 at 4:37 PM, Yan Xu  wrote:
> > > >
> > > > > +1 Slack.
> > > > >
> > > > > On Friday, June 17, 2016, José Guilherme Vanz <
> > guilherme@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > +1 Slack
> > > > > >
> > > > > > On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere <
> > > jo...@mesosphere.io
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > +1 Slack
> > > > > > >
> > > > > > > —
> > > > > > > *Joris Van Remoortere*
> > > > > > > Mesosphere
> > > > > > >
> > > > > > > On Fri, Jun 17, 2016 at 10:04 PM, Vinod Kone <
> > vinodk...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Looks like people have jumped the gun here before I sent the
> > > email
> > > > :)
> > > > > > > >
> > > > > > > > Here is the context. During the community sync we discussed
> > about
> > > > > using
> > > > > > > > *Slack* or *HipChat* as our official chat channel instead of
> > our
> > > > > > current
> > > > > > > > #mesos IRC channel on freenode.
> > > > > > > >
> > > > > > > > The main reasons for using Slack/Hipchat are
> > > > > > > >
> > > > > > > >- In-client chat history
> > > > > > > >- Discoverability of work group specific channels
> > > > > > > >- Email notifications when offline
> > > > > > > >- Modern UX and clients
> > > > > > > >
> > > > > > > > During the sync most people preferred the move to *Slack*. I
> > > wanted
> > > > > to
> > > > > > > get
> > > > > > > > a sense from other community members as well through this
> > email.
> > > > > Please
> > > > > > > let
> > > > > > > > us know what you think.
> > > > > > > >
> > > > > > > > Note that even if we move to Slack, we will make sure people
> > can
> > > > > still
> > > > > > > > connect using IRC clients and that the chat history is
> publicly
> > > > > > available
> > > > > > > > (per ASF guidelines). During the transition period, we might
> > > mirror
> > > > > > > > messages from Slack channel to IRC and vice-versa.
> > > > > > > >
> > > > > > > > Thoughts?
> > > > > > > >
> > > > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia <
> > > > > vinitmahe...@gmail.com
> > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 Slack.
> > > > > > > > >
> > > > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo <
> > > > > guojian...@cn.ibm.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > +1 Slack!
> > > > > > > > > >
> > > > > > > > > > /J
> > > > > > > > > >
> > > > > > > > > > Vaibhav Khanduja  wrote on
> > > > 06/16/2016
> > > > > > > > > 22:26:27:
> > > > > > > > > >
> > > > > > > > > > > From: Vaibhav Khanduja 
> > > > > > > > > > > To: dev@mesos.apache.org
> > > > > > > > > > > Date: 06/16/2016 22:26
> > > > > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun
> > 16,
> > > > 2016
> > > > > > 3pm
> > > > > > > > > > > - 4pm (Apache Mesos)
> > > > > > > > > > >
> > > > > > > > > > > + 1 slack
> > > > > > > > > > >
> > > > > > > > > > > Sent from my iPhone. Please excuse for typos and
> brevity
> > of
> > > > > this
> > > > > > > > > message.
> > > > > > > > > > >
> > > > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent <
> > > haosd...@gmail.com>
> > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > +1 For Slack.
> > > > > > > > > > > >
> > > > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann <
> > > > > > g...@mesosphere.io>
> > > > > > > > > > wrote:
> > > > > > > > > > > >>
> > > > > > > > > > > >> Hello all,
> > > > > > > > > > > >> Here are the notes from our community sync meeting
> > this
> > > > > > > afternoon:
> > > > > > > > > > > >>
> > > > > > > > > > > >> Attendees:
> > > > > > > > > > > >>
> > > > > > > > > > > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph,
> Kapil,
> > > > Anand,
> > > > > > > > > Gilbert,
> > > > > > > > > > > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark
> > > > > > > > > > > >>
> > > > > > > > > > > >> Uber: Zhitao Li
> > > > > > > > > > > >>
> > > > > > > > > > > >> Agenda/Note:
> > > > > > > > > > > >>
> > > > > > > > > > > >>   -
> > > > > > > > > > > >>
> > > > > > > > > > > >>   Reviewing the list of maintainers on
> > > > > > > > > > > >>
> > > > http://mesos.apache.org/documentation/latest/committers/
> > > > > > > > > > > >>   -
> > > > > > > > > > > >>
> > > > > > > > > > > >>  Add components for
> > > > > > > > > > > >>  -
> > > > > > > > > > > >>
> > > > > > > > > > > >> 

Re: [WEBSITE] Website refresh

[Timothy Anderegg]

I'll do Mesos-3011 if Joerg can't get to it.

On Tue, May 17, 2016, 7:33 PM Vinod Kone <vinodk...@apache.org> wrote:

> I looked at the open issues for the website
> <
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MESOS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Accepted)%20AND%20component%20%3D%20%22project%20website%22%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC
> >
> .
>
> These look like something we can tackle in the short term:
>
> MESOS-3690 <https://issues.apache.org/jira/browse/MESOS-3690> -- Looks
> like
> a PR from Freddy is already open <https://github.com/apache/mesos/pull/75
> >.
> Any one care to review it?
>
> MESOS-3011 <https://issues.apache.org/jira/browse/MESOS-3011> -- Users
> will
> thank you for this.
>
> MESOS-1495 <https://issues.apache.org/jira/browse/MESOS-1495> --
> Committers
> will thank you for this.
>
> Any takers?
>
> On Tue, May 17, 2016 at 3:50 PM, Tomek Janiszewski <jani...@gmail.com>
> wrote:
>
> > JIRA: https://issues.apache.org/jira/browse/MESOS-5402
> > PR: https://reviews.apache.org/r/47499/
> >
> > wt., 17.05.2016 o 22:30 użytkownik Timothy Anderegg <
> > timothy.ander...@gmail.com> napisał:
> >
> > > Happy to help review the change
> > >
> > > On Tue, May 17, 2016, 4:26 PM Vinod Kone <vinodk...@apache.org> wrote:
> > >
> > > > Great. Can you file tickets for these and submit patches? I can help
> > > commit
> > > > them. Would be great if people with front-end experience can review
> the
> > > > changes though.
> > > >
> > > > On Tue, May 17, 2016 at 1:23 PM, Tomek Janiszewski <
> jani...@gmail.com>
> > > > wrote:
> > > >
> > > > > Currently only issue I spotted on mobile is text that is not
> > wrapped. I
> > > > > checked in devtools and adding *@media only screen and
> > > (max-width:985px)*
> > > > >  above .container
> > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/apache/mesos/blob/4d2b1b793e07a9c90b984ca330a3d7bc9e1404cc/site/source/assets/css/main.css#L28
> > > > > >
> > > > > solve
> > > > > this but add another issues
> > > > > 1. Missing left padding in jumbotron – minor issue but it really
> > > doesn't
> > > > > look good
> > > > > 2. links in navbar hides on small screens due to hardcoded height
> > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/apache/mesos/blob/4d2b1b793e07a9c90b984ca330a3d7bc9e1404cc/site/source/assets/css/main.css#L103
> > > > > >
> > > > >
> > > > > 3. Tables still need scrolling but IMO it's OK
> > > > > There could be other issues I haven't noticed, but on the first
> sight
> > > > > making site mobile friendlier doesn't look hard.
> > > > >
> > > > > wt., 17.05.2016 o 21:19 użytkownik Vinod Kone <
> vinodk...@apache.org>
> > > > > napisał:
> > > > >
> > > > > > On Tue, May 17, 2016 at 10:18 AM, Tomek Janiszewski <
> > > jani...@gmail.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > In short term we could make it mobile friendly
> > > > > >
> > > > > >
> > > > > > Can this be done easily? What needs to change?
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [WEBSITE] Website refresh

[Timothy Anderegg]

Happy to help review the change

On Tue, May 17, 2016, 4:26 PM Vinod Kone  wrote:

> Great. Can you file tickets for these and submit patches? I can help commit
> them. Would be great if people with front-end experience can review the
> changes though.
>
> On Tue, May 17, 2016 at 1:23 PM, Tomek Janiszewski 
> wrote:
>
> > Currently only issue I spotted on mobile is text that is not wrapped. I
> > checked in devtools and adding *@media only screen and (max-width:985px)*
> >  above .container
> > <
> >
> https://github.com/apache/mesos/blob/4d2b1b793e07a9c90b984ca330a3d7bc9e1404cc/site/source/assets/css/main.css#L28
> > >
> > solve
> > this but add another issues
> > 1. Missing left padding in jumbotron – minor issue but it really doesn't
> > look good
> > 2. links in navbar hides on small screens due to hardcoded height
> > <
> >
> https://github.com/apache/mesos/blob/4d2b1b793e07a9c90b984ca330a3d7bc9e1404cc/site/source/assets/css/main.css#L103
> > >
> >
> > 3. Tables still need scrolling but IMO it's OK
> > There could be other issues I haven't noticed, but on the first sight
> > making site mobile friendlier doesn't look hard.
> >
> > wt., 17.05.2016 o 21:19 użytkownik Vinod Kone 
> > napisał:
> >
> > > On Tue, May 17, 2016 at 10:18 AM, Tomek Janiszewski  >
> > > wrote:
> > >
> > > > In short term we could make it mobile friendly
> > >
> > >
> > > Can this be done easily? What needs to change?
> > >
> >
>

Re: [WEBSITE] Website refresh

[Timothy Anderegg]

I think that doing a once-over of the documentation (and perhaps some
thought on big picture restructuring of that content, possibly adding in a
few use-case specific "guides" that might act as tutorials on specific
common tasks), would be quite beneficial to existing and new users, but
probably not feasible before MesosCon.  +1 to starting with the home page
for now.

On Tue, May 17, 2016 at 12:49 PM Vinod Kone  wrote:

> Hi,
>
> What's the minimum we could do to spruce up the website for MesosCon?
>
> Given the time, I think improving the home page would be a good start? I
> had some discussions with Mesosphere's design team and they kindly agreed
> to help out here. Once they have the design doc for the home page update
> ready, I will share it with the community and we can review it.
>
> Is there anything else we could do in the short-term? Content
> re-organization seems like the most beneficial thing we could do but that
> might take a lot more time.
>
> Thanks,
> Vinod
>

Looking for Shepherd for Mesos-3402

[Timothy Anderegg]

Hi folks -

https://issues.apache.org/jira/browse/MESOS-3402

This change adds support for framework authentication to the mesos-execute
command line utility, to make it easier to conduct integration testing.
It's a fairly small change code-wise, please let me know if you could help
review/shepherd, thanks!

Tim

Re: Mesos Developer Community Design Discussions

[Timothy Anderegg]

Live stream for folks who won't be there would be great, thanks!

Tim

On Mon, Aug 10, 2015 at 7:09 PM, Benjamin Hindman b...@eecs.berkeley.edu
wrote:

 The spreadsheet has been updated, sorry about that!

 Dave: we didn't want to pull people away from the hackathon and all the
 other times were taken, so we figured we'd do the best we can! Enough
 people have chatted with me about talking about future features that it
 made sense to put something together for anyone in the community to join.
 We'll try and get live streaming set up for folks that aren't flying in
 until Wednesday (or at all).

 On Mon, Aug 10, 2015 at 3:01 PM Dave Lester d...@davelester.org wrote:

  Hi Ben,
 
  It looks like the spreadsheet/google form isn't public outside your
  organization, you may need to revise the permissions.
 
  I'm curious, why this particular day? It's a bit unfortunate that only 8
  day notice is being given, since I imagine most people have their
  flights for MesosCon already booked and will not likely be in
  attendance.
 
  Best,
  Dave
 
  On Mon, Aug 10, 2015, at 02:52 PM, Benjamin Hindman wrote:
   We've had great developer community meetings over Google Hangouts, but
   MesosCon is right around the corner and we'd like to do it in person!
  
   I'd like to invite everyone to attend an in person developer community
   meeting on Tuesday, August 18th in Seattle. The focus will be for Mesos
   committers and contributors to get together to discuss big ticket
   features to work on during the next 6 to 12 months. I will be joining
   many
   other committers at this event and we all look forward to discussing
 new
   features with everyone!
  
   There is a limited amount of space so please submit your RSVP here:
   http://bit.ly/mesosdesignsummit
  
   We look forward to seeing you in Seattle! And don't forget to register
   for
   MesosCon
   http://events.linuxfoundation.org/events/mesoscon/attend/register if
   you haven't already!
 

Re: Mesos Contribution Request

[Timothy Anderegg]

Yeah, I thought it was a good place to start :)  Thanks again!

Tim

On Wed, Aug 5, 2015 at 12:47 PM, Marco Massenzio ma...@mesosphere.io
wrote:

 eh, contributing to documentation is the surest way of being loved by *any*
 OSS community :)

 There's a lot of activity currently around authentication/authorization, so
 I'm sure you'll have no trouble in finding stuff to contribute to.
 Thanks, Tim!

 *Marco Massenzio*
 *Distributed Systems Engineer*

 On Wed, Aug 5, 2015 at 9:35 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
  wrote:

  Great, thanks Marco!  Ultimately I'm interested in helping with Kerberos
  authentication (would help with adoption of Mesos for us), but I'm
 planning
  to tackle some simpler things first as you suggest.  Right now I'm
 writing
  some of the authentication documentation, since that's missing currently
  (MESOS-1838), and will help prep me for more substantial work.
 
  -Tim
 
  On Wed, Aug 5, 2015 at 12:25 PM, Marco Massenzio ma...@mesosphere.io
  wrote:
 
   Hi Tim,
  
   I've added you to the Contributors list, welcome to Apache Mesos and
   looking forward to your contributions!
   I assume you've obviously already looked up the Contributing page on
   mesos.apache.org and joined our Review Board (reviews.apache.org); the
   other one thing to look out for are tickets marked as 'newbie'; they
 are
   usually a gentler introduction to our code base.
  
   Any other questions, please feel free to ask!
   Thanks for joining.
  
   *Marco Massenzio*
   *Distributed Systems Engineer*
  
   On Wed, Aug 5, 2015 at 7:57 AM, Timothy Anderegg 
   timothy.ander...@gmail.com
wrote:
  
Hello, I would like to get involved with the development of Mesos, my
   JIRA
username is tanderegg, could I be added to the contributors list?
   Thanks,
and let me know if you need any more info.
   
Tim
   
  
 

Re: Mesos Contribution Request

[Timothy Anderegg]

Thanks Vinod, I did see that, looks like a solid approach.  I'll continue
to dig in and see where I can help.

Tim

On Wed, Aug 5, 2015 at 2:08 PM, Vinod Kone vinodk...@gmail.com wrote:

 Welcome Tim.

 This doc
 
 https://docs.google.com/document/d/1kM3_f7DSqXcE2MuERrLTGp_XMC6ss2wmpkNYDCY5rOM/edit#heading=h.bbxx6wwg3tpe
 
 might
 help you get a sense of the current state of authN and where it is going.

 On Wed, Aug 5, 2015 at 9:53 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
  wrote:

  Yeah, I thought it was a good place to start :)  Thanks again!
 
  Tim
 
  On Wed, Aug 5, 2015 at 12:47 PM, Marco Massenzio ma...@mesosphere.io
  wrote:
 
   eh, contributing to documentation is the surest way of being loved by
  *any*
   OSS community :)
  
   There's a lot of activity currently around
 authentication/authorization,
  so
   I'm sure you'll have no trouble in finding stuff to contribute to.
   Thanks, Tim!
  
   *Marco Massenzio*
   *Distributed Systems Engineer*
  
   On Wed, Aug 5, 2015 at 9:35 AM, Timothy Anderegg 
   timothy.ander...@gmail.com
wrote:
  
Great, thanks Marco!  Ultimately I'm interested in helping with
  Kerberos
authentication (would help with adoption of Mesos for us), but I'm
   planning
to tackle some simpler things first as you suggest.  Right now I'm
   writing
some of the authentication documentation, since that's missing
  currently
(MESOS-1838), and will help prep me for more substantial work.
   
-Tim
   
On Wed, Aug 5, 2015 at 12:25 PM, Marco Massenzio 
 ma...@mesosphere.io
wrote:
   
 Hi Tim,

 I've added you to the Contributors list, welcome to Apache Mesos
 and
 looking forward to your contributions!
 I assume you've obviously already looked up the Contributing page
  on
 mesos.apache.org and joined our Review Board (reviews.apache.org);
  the
 other one thing to look out for are tickets marked as 'newbie';
 they
   are
 usually a gentler introduction to our code base.

 Any other questions, please feel free to ask!
 Thanks for joining.

 *Marco Massenzio*
 *Distributed Systems Engineer*

 On Wed, Aug 5, 2015 at 7:57 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
  wrote:

  Hello, I would like to get involved with the development of
 Mesos,
  my
 JIRA
  username is tanderegg, could I be added to the contributors list?
 Thanks,
  and let me know if you need any more info.
 
  Tim