Re: Marathon API and support for pods

[John Sirois]

+1, good info - wrong forum.

On Wed, Sep 21, 2016 at 11:07 AM, Zameer Manji  wrote:

> Hey,
>
> Have you considered sending this to your framework's mailing list? As a
> Mesos user, I don't think framework specific documents like this need to be
> shared with the entire community.
>
>
> On Wed, Sep 21, 2016 at 2:59 AM, James DeFelice 
> wrote:
>
>> Hi folks,
>>
>> First of all the Marathon team would like to thank those who provided
>> feedback on the v3 API proposal (linked below) that was circulated last
>> month. Developing a new API for Marathon is a big undertaking and getting
>> your feedback early in the process has been helpful.
>>
>> "A vision for pods in Marathon
>> [https://docs.google.com/document/d/1uPH58NWN_OuynptsqTOq8v5
>> qlkivq2mUb2M9J5jZTMU/edit#heading=h.sqydeepp9s4m]
>>
>> We've done some additional discovery over the several weeks and have made
>> some changes to our API roadmap. It takes time to get an API right and the
>> decisions we make now will have lasting impact for months/years to come;
>> let's ensure that we spend enough time now thinking through the long-term
>> implications of particular API design choices. We'd also like to facilitate
>> a deeper discussion with the community about what problems v3 should solve
>> before committing to API decisions. The current plan is to resume work on
>> the v3 API later this fall. Stay tuned for additional announcements
>> regarding v3 API proposals.
>>
>> Furthermore, the v3 API is about more than just pods. We, the team and
>> community at large, should ensure that a new API is conceptually consistent
>> across API types and satisfies not only our short-term goals, but is
>> forward-compatible with our long term roadmap.
>>
>> That said, we have customer demand for pods now! In order to deliver pods
>> functionality without committing to a v3 API the team has decided to
>> introduce pods via a new /v2/pods API endpoint. What does this mean for v2
>> API users?
>>
>> First, if your organization doesn't have an interest in pods then nothing
>> forces you to change. Additional support for pods in the Marathon v2 API
>> should not cause breakage for existing v2 API users.
>>
>> Second, by integrating with the existing v2 API and backend we'll be
>> minimizing overall architectural changes. Needless to say there will be
>> changes to backend components that had been previously optimized for single
>> tasks vs. task groups. But the overall architecture of the system will not
>> change. This is important in order to preserve the performance,
>> scalability, and stability gains that Marathon has recently made.
>>
>> In addition, introducing pods in v2 allows the Marathon team to gather
>> early feedback from the community and our customers about how the API does
>> and does not meet their needs. This is very valuable input that will help
>> to shape the future v3 API.
>>
>> Below is a link to a proposal for pods in the Marathon v2 API. This
>> initial implementation for pods support should be viewed as an MVP that
>> will be enhanced in coming releases. Your feedback is most welcome and
>> strongly encouraged. Please comment directly in the document with any
>> questions or concerns.
>>
>> "Marathon: Pods in v2"
>> [https://docs.google.com/document/d/1Zno6QK2yGF4koB8BYT88EtB
>> 2-T7t3aAYRQ27pUD76gw/edit#heading=h.ywxj299mstr7]
>>
>> Many thanks,
>>
>> the Marathon team.
>>
>
>

Re: Using Mesos?

[John Sirois]

Granted its not effusive, but follow the asfgit comment sha link to here:
https://github.com/apache/mesos/commit/377ece0c206d958c7384f7d59706aa0320812da0
You'll see the commit on master.

On Thu, Jun 30, 2016 at 3:11 PM, Jay Taylor  wrote:

> I just tried this but it appears my PR was closed without comment.
>
> https://github.com/apache/mesos/pull/119
>
> What am I missing here? :)
>
> On Thu, Jun 30, 2016 at 1:45 PM, Benjamin Mahler 
> wrote:
>
>> Just a reminder. If you're using Mesos and want to be featured in our
>> list of users, send a PR to get your organization added:
>>
>> https://github.com/apache/mesos/blob/master/docs/powered-by-mesos.md
>>
>> If you've built a framework, and would like it featured in our list of
>> frameworks, send a PR to get your framework listed:
>>
>> https://github.com/apache/mesos/blob/master/docs/frameworks.md
>>
>> Thanks!
>>
>> Ben
>>
>
>

Re: Mesos Security Recommendations

[John Sirois]

On Thu, Jun 4, 2015 at 5:58 PM, Kevin Sweeney kevi...@apache.org wrote:

 Jeff, have you succfessfully run stunnel with a Mesos cluster? I'd
 anticipate it to be a bit difficult due to the way that slaves dynamically
 discover masters via zookeeper. If I remember correctly, with stunnel you
 need to configure all the tunnels beforehand, which would mean that every
 master would need to enumerate every possible slave beforehand, and
 vice-versa.

 IMO that fairly severely limits the reliability of the system.

 By the way, is there a design doc for how TLS between slave and master is
 going to be implemented in 0.23.0?


Its not a design doc, but the issue breakdown spells out much:
https://issues.apache.org/jira/browse/MESOS-910



 On Thu, Jun 4, 2015 at 4:30 PM, Jeff Schroeder jeffschroe...@computer.org
  wrote:

 For securing insecure network communication you can use something like
 stunnel, then point the app at the local stunnel. It would be a fair bit of
 hoops to configure it all with any your config management system, but is
 totally doable.


 On Thursday, June 4, 2015, John Webb webbj1...@hotmail.com wrote:

 All,

 I'm looking for some recommendations on how to encrypt Mesos Slave 
 Framework communication to the Mesos Master until Mesos v0.23 is released
 which will include SSL support. I'm concerned about having the slave 
 framework user/password being sent across our network in clear text.

 I would especially like to hear from people who actually running Mesos
 in production environment.

 Thanks,
 John Webb



 --
 Text by Jeff, typos by iPhone