Re: Poland, Warsaw User Group

2016-01-11 Thread Niklas Nielsen
You can see the removal here: http://svn.apache.org/viewvc/mesos/site/publish/community/user-groups/index.html?r1=1711312=1720526=1720526 On Mon, Jan 11, 2016 at 10:14 AM, Niklas Nielsen wrote: > Sorry about that, Piotr! I will have taken a stab at this by tomorrow. > > Niklas > >

Re: Poland, Warsaw User Group

2016-01-11 Thread Niklas Nielsen
Sorry about that, Piotr! I will have taken a stab at this by tomorrow. Niklas On Mon, Jan 11, 2016 at 9:15 AM, Piotr Szwed wrote: > Hi Niklas, > > I just found out that we disappeared from the site, could you fix that? > > URL: http://www.meetup.com/Warsaw-Mesos-User-Group/ >

Re: Linking mesos tasks to Docker containers

2016-01-11 Thread haosdent
is containerid here. On Tue, Jan 12, 2016 at 10:36 AM, Shuai Lin wrote: > Take a look at > https://github.com/scrapinghub/marathon-apps-collectd-plugin, basically > it works like this: > > - there is a custom collectd (https://github.com/collectd/collectd) > plugin,

Re: Linking mesos tasks to Docker containers

2016-01-11 Thread haosdent
could you found it in slave state http endpoint? I remember the hierarchy should be framework->executors->container. On Tue, Jan 12, 2016 at 10:41 AM, haosdent wrote: > is containerid here. > > On Tue, Jan 12, 2016 at 10:36 AM, Shuai Lin > wrote: >

Re: Managing Secrets

2016-01-11 Thread Alexandre Mclean
Hashicorp's Vault seems to be the most promising solution for this. Mantl has integrated it with Mesos and Marathon already, so I would look at their stack to see how it all fits together: https://mantl.io On Mon, Jan 11, 2016 at 10:21 AM, Luke Amdor wrote: > We've been

Re: Linking mesos tasks to Docker containers

2016-01-11 Thread Qian Zhang
I think slave state endpoint has the info you need: ... "executors": [ { "container": "b824a7ad-35c6-48ab-9378-b180ed431fb5", <- this is ... "tasks": [ {

Managing Secrets

2016-01-11 Thread Erb, Stephan
Hi everyone, I'd like to explore mechanisms to provide secrets to applications deployed on Mesos (e.g. via Marathon or Apache Aurora). The classical workflow of having the passwords encrypted in the local git repository and only decrypted during deployment (for example via ansible vault)

Re: Managing Secrets

2016-01-11 Thread Robert Vežnaver
Hi, We give each app a private/public key pair, and let the developers encrypt any environment variable with their app's public key (we also base64 encode the ciphertext). Then instead of calling the usual "/bin/sh", we call a small bash wrapper script which decrypts the desired environment

Linking mesos tasks to Docker containers

2016-01-11 Thread Scott Rankin
Hi all, I’m trying to put together a monitoring system for our Marathon/Mesos/Docker app infrastructure, and I’m having some trouble linking between Mesos and Docker. Mesos has a task ID (like app_auth.6fb24412-af26-11e5-9900-02d62c7c9807), but the only place that shows up in the Docker