"Porting Mesos on Power" (Mesos 4312) was one of the near term projects in
the first version, but now is removed. I would like to add it back, however
failed. I have an account there but seem still cannot edit it.

Besides, how does Mesos support Swarm on Mesos after "Deprecate Docker
containerizer"? In current Swarm on Mesos, Swarm has to talk to Docker
daemon as Mesos does not support all the Docker APIs yet. Once we have a
JIRA for it, I would like to raise the issue there.

Thanks,

Yong

On Thu, Apr 21, 2016 at 10:54 PM, haosdent <[email protected]> wrote:

> Just added the links, you could update by create a account in
> https://cwiki.apache.org :-)
>
> On Fri, Apr 22, 2016 at 9:24 AM, Joris Van Remoortere <[email protected]
> >
> wrote:
>
> > That is the plan, I think it just hasn't been done yet :-)
> >
> > —
> > *Joris Van Remoortere*
> > Mesosphere
> >
> > On Thu, Apr 21, 2016 at 9:20 PM, Qian Zhang <[email protected]> wrote:
> >
> > > In that wiki, can we also put the corresponding JIRA ticket link there
> so
> > > that folks can take a close look at the projects they are interested
> in?
> > >
> > >
> > > Thanks,
> > > Qian Zhang
> > >
> > > On Fri, Apr 22, 2016 at 8:20 AM, haosdent <[email protected]> wrote:
> > >
> > > > I would like to know more details about
> > > >
> > > > >Deprecate Docker containerizer (in favor of Unified containerizer w/
> > > > Docker support)
> > > >
> > > > Is there any jira issue about this?
> > > >
> > > > On Fri, Apr 22, 2016 at 7:48 AM, Greg Mann <[email protected]>
> wrote:
> > > >
> > > > > Hello all!
> > > > > Today we had another Mesos community sync meeting; find the notes
> > > pasted
> > > > > below. Of particular interest is our new roadmap document
> > > > > <
> > https://cwiki.apache.org/confluence/display/MESOS/%5BDRAFT%5D+Roadmap
> > > >,
> > > > > which outlines items planned for development within the next six
> > > months.
> > > > >
> > > > > For future sync meeting times, see the community calendar
> > > > > <http://mesos.apache.org/community/>on the Mesos website.
> > > > >
> > > > > Cheers,
> > > > > Greg
> > > > >
> > > > >
> > > > >
> > > > > April 21, 2016
> > > > >
> > > > > Time: 3pm PST
> > > > >
> > > > > Location: Mesosphere HQ
> > > > >
> > > > > Attendees:
> > > > >
> > > > >    -
> > > > >
> > > > >    Mesosphere: Greg, Vinod, Joris, Joseph, Jie, Gilbert, Avinash,
> > > Kevin,
> > > > >    MPark, Kapil, Jojy, Artem
> > > > >    -
> > > > >
> > > > >    Apple: Yan Xu
> > > > >
> > > > >
> > > > > Agenda/Notes:
> > > > >
> > > > >    -
> > > > >
> > > > >    Review of action items from last meeting
> > > > >    -
> > > > >
> > > > >       MPark set up a system to automatically notify him before
> > > community
> > > > >       syncs, and he can forward this message to the mailing lists.
> > > Don’t
> > > > yet have
> > > > >       a fully automatic method for sending these notifications.
> > > > >       -
> > > > >
> > > > >       Jie: Wiki page of release features has been updated
> > > > >       -
> > > > >
> > > > >       Vinod: draft roadmap has been created, see link below
> > > > >
> > > > >
> > > > >    -
> > > > >
> > > > >    3rdparty flattening and module dependency installation
> > > > >    -
> > > > >
> > > > >       Review chain starting at https://reviews.apache.org/r/46514/
> > > > >       -
> > > > >
> > > > >       Key points for 3rdparty flattening:
> > > > >       -
> > > > >
> > > > >          Added --with-stout to libprocess configure
> > > > >          -
> > > > >
> > > > >          Added --with-libprocess/stout to top-level configure
> > > > >          -
> > > > >
> > > > >          Moved 3rdparty/libprocess/3rdparty/* to 3rdparty/
> > > > >          -
> > > > >
> > > > >          Stop using libprocess/stout configure scripts; use
> top-level
> > > > >          configure instead
> > > > >          -
> > > > >
> > > > >       Module dependency installation:
> > > > >       -
> > > > >
> > > > >          Added --enable-install-module-dependencies
> > > > >          -
> > > > >
> > > > >          Boost, glog, protobuf, and picojson are installed in
> > > > >          ${libdir}/mesos/3rdparty
> > > > >          -
> > > > >
> > > > >          Appropriate flags added mesos.pc
> > > > >          -
> > > > >
> > > > >       No direct effect on distro packaging
> > > > >       -
> > > > >
> > > > >    Roadmap!!
> > > > >    -
> > > > >
> > > > >       https://cwiki.apache.org/confluence/display/MESOS/Roadmap
> > > > >       -
> > > > >
> > > > >    Docker image issues: using Alpine images in the tests causes
> > > > >    difficulties for some users on the Power platform.
> > > > >    -
> > > > >
> > > > >       Additionally, it would be great to eliminate the dependency
> on
> > > > >       internet access for running the tests
> > > > >       -
> > > > >
> > > > >       One solution: use `docker load` to load a small image into
> the
> > > > >       local cache, from which it can be used by the Docker runtime
> > > > >       -
> > > > >
> > > > >       Another solution: establish a Mesos account on the Docker Hub
> > and
> > > > >       place images for testing there. This would require internet
> > > access
> > > > for
> > > > >       tests.
> > > > >
> > > > >
> > > > > Action Item
> > > > >
> > > > >    -
> > > > >
> > > > >    Joris will review Kapil’s 3rdparty patches
> > > > >    -
> > > > >
> > > > >    MPark, Joris and AlexC will help with the CMake path
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best Regards,
> > > > Haosdent Huang
> > > >
> > >
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Reply via email to