I heartily agree on both points. While I've found Mesosphere's documentation very helpful, it is often mixed up with the DCOS commercial offering. That may be something we're interested in down the road, but right now we are trying to stand up a relatively small cluster using straight Mesos/Marathon/Chronos, etc., and finding good documentation is very challenging due to the overlap with DCOS.
The Apache documentation also, I think, is suffering precisely because Mesosphere has been serving up better materials on their own. It's certainly useful, but I'm a bit uncomfortable with that arrangement. Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Tue, Apr 12, 2016 at 7:04 AM, Paul Bell <[email protected]> wrote: > FWIW, I quite agree with Zameer's point. > > That said, I want to make abundantly clear that in my experience the folks > at Mesosphere are wonderfully helpful. > > But what happens if down the road Mesosphere is acquired or there occurs > some other event that could represent, if not a conflict of interest, then > simply a different strategic direction? > > My 2 cents. > > -Paul > > On Mon, Apr 11, 2016 at 5:19 PM, Zameer Manji <[email protected]> wrote: > >> I have suggested this before and I will suggest it again here. >> >> I think the Apache Mesos project should build and distribute packages >> instead of relying on the generosity of a commercial vendor. The Apache >> Aurora project does this already with good success. As a user of Apache >> Mesos I don't care about Mesosphere Inc and I feel uncomfortable that the >> project is so dependent on its employees. >> >> Doing this would allow users to contribute packaging fixes directly to >> the project, such as enabling SSL. >> >> On Mon, Apr 11, 2016 at 3:02 AM, Adam Bordelon <[email protected]> >> wrote: >> >>> Hi Kamil, >>> >>> Technically, there are no "official" Apache-built packages for Apache >>> Mesos. >>> >>> At least once company (Mesosphere) chooses to build and distribute >>> Mesos packages, but does not currently offer SSL builds. It wouldn't >>> be hard to add an SSL build to our regular builds, but it hasn't been >>> requested enough to prioritize it. >>> >>> cc: Joris, Kapil >>> >>> On Thu, Apr 7, 2016 at 7:42 AM, haosdent <[email protected]> wrote: >>> > Hi, ssl didn't enable default. You need compile it by following this >>> doc >>> > http://mesos.apache.org/documentation/latest/ssl/ >>> > >>> > On Thu, Apr 7, 2016 at 10:04 PM, Kamil Wokitajtis < >>> [email protected]> >>> > wrote: >>> >> >>> >> This is my first post, so Hi everyone! >>> >> >>> >> Is SSL enabled in official packages (CentOS in my case)? >>> >> I can see libssl in ldd output, but I cannot see libevent. >>> >> I had to compile mesos from sources to run it over ssl. >>> >> I would prefer to install it from packages. >>> >> >>> >> Regards, >>> >> Kamil >>> > >>> > >>> > >>> > >>> > -- >>> > Best Regards, >>> > Haosdent Huang >>> >>> -- >>> Zameer Manji >>> >>> >
