Re: Next steps for Mesos

2023-04-04 Thread Stephen Salinas
HubSpot is still also using mesos and I know we have at least 3 other
companies still using the open source version of our Singularity scheduler.
We are up to the 1.11.x release at this point. However, I don't know that
any of that crowd has been or will be active contributors.

-Stephen Salinas

On Mon, Mar 27, 2023 at 5:03 AM Qian Zhang  wrote:

> >
> > Qian, it might be worth having a more explicit email asking users to
> chime
> > in as this email was tailored more for contributors.
>
>
> Yes, we can have such email, but I think it does not affect whether we
> should move Mesos to attic or not, since the most important factor is
> whether we have enough active committers. Quoted from
> https://attic.apache.org/
> <https://attic.apache.org>
>
> When should a project move to the Attic?
>
> Projects whose PMC are unable to muster 3 votes for a release, who have no
> active committers or are unable to fulfill their reporting duties to the
> board are all good candidates for the Attic.
>
> I am happy to see there are still some companies using Mesos now, but in
> this mail thread, so far there are just several contributors interested in
> contributing to Mesos and only one committer Benjamin Mahler (no guaranteed
> time), I think that's not enough to keep this project going, so we may have
> to move Mesos to attic.
>
>
> Regards,
> Qian Zhang
>
>
> On Tue, Mar 21, 2023 at 2:56 AM Benjamin Mahler 
> wrote:
>
> > Also if you are still a user of mesos, please chime in.
> > Qian, it might be worth having a more explicit email asking users to
> chime
> > in as this email was tailored more for contributors.
> >
> > Twitter is still using mesos heavily, we upgraded from a branch based off
> > of 1.2.x to 1.9.x in 2021, but haven't upgraded to 1.11.x yet. We do
> have a
> > lot of patches carried on our branch that have not been upstreamed. I
> would
> > like to upstream them to avoid relying on many custom patches and to
> > get closer to HEAD, but it will take time and quite a bit of work, and
> it's
> > not a priority at the moment.
> >
> > On the contribution side, at this point if I were to continue
> contributing,
> > it would be on a volunteer basis, and I can't guarantee having enough
> time
> > to do so.
> >
> > On Fri, Mar 17, 2023 at 9:57 PM Qian Zhang  wrote:
> >
> > > Hi all,
> > >
> > > I'd like to restart the discussion around the future of the Mesos
> > project.
> > > As you may already be aware, the Mesos community has been inactive for
> > the
> > > last few years, there were only 3 contributors last year, that's
> > obviously
> > > not enough to keep the project moving forward. I think we need at
> least 3
> > > active committers/PMC members and some active contributors to keep the
> > > project alive, or we may have to move it to attic
> > > <https://attic.apache.org/
> <https://attic.apache.org/>
> >.
> > >
> > > Call for action: If you are the current committer/PMC member and still
> > > have the capacity to maintain the project, or if you are willing to
> > > actively contribute to the project as a contributor, please reply to
> this
> > > email, thanks!
> > >
> > >
> > > Regards,
> > > Qian Zhang
> > >
> >
>


Question on Docker Containerizer

2015-04-07 Thread Stephen Salinas
Hey Everyone,

  I have a question on using the docker containerizer. I have a feeling it
isn’t possible, but, is there a way to use the docker containerizer within
a custom executor? (ie. have it help translate commands to docker and
manage the containers within the wrapper of the custom executor).

  We know that we can launch a docker container as a task via the default
mesos executor, and we know that we can launch a docker container with a
custom executor, but we'd like our custom executor to be lauched *outside*
of the docker container we specify in the TaskInfo -- is this possible via
the docker containerizer?

-Stephen