Re: Setting up SSL for mesos

[Kamil Wokitajtis]

You don't have to build it on every machine.
Just install checkinstall tool, build it on one machine and create package.
When building, after make command don't run make install, instead run:

checkinstall --install=no --pkgname=mesos --pkgversion=0.28.2 -y

I am using Ubuntu, so in my case it will create deb package.
Just copy it over to every node and do:

dpkg -i 

With this approach, it is very easy to update mesos to the most recent
version.


2016-07-08 1:56 GMT+02:00 Douglas Nelson :

> Inlining the environment variable fixed it! I had to use sudo to run
> mesos, so I either needed to inline it or use -E. *Facepalm*
>
> On the note of building mesos, is there any chance in the future that
> mesosphere would create a prebuilt mesos package with ssl included? It
> would be nice to avoid building on each machine I want to run mesos on.
> Also, it would be great to have the convenience of using config files,
> having automatic startup, etc with a simple apt-get install mesos-ssl. Is
> that something that's been considered?
>
> Thanks!
>
> On Thu, Jul 7, 2016 at 1:14 PM, Joseph Wu  wrote:
>
>> Can you double-check if your master is linking to openssl?
>>
>> From your build folder, you should get something like:
>> ldd src/.libs/mesos-master | grep ssl
>> libevent_openssl-2.0.so.5 => /lib64/libevent_openssl-2.0.so.5
>> libssl.so.10 => /lib64/libssl.so.10
>> libssl3.so => /lib64/libssl3.so
>>
>> There doesn't seem to be anything wrong with your configure/build steps.
>> And your environment variables setup should work on any sane Unix shell.
>> (Perhaps inline the environment variable?  SSL_ENABLED=true
>> ./mesos-master.sh ...)
>>
>> On Thu, Jul 7, 2016 at 11:53 AM, Douglas Nelson 
>> wrote:
>>
>>> I rebuilt from scratch with SSL support and got no errors. I only set 
>>> *export
>>> SSL_ENABLED=true* and then I ran the mesos-master.
>>>
>>> No errors were thrown and I can see the web UI via HTTP. I double
>>> checked that I was running the .sh from the build folder I created. Is
>>> mesos not connecting with the environment variable I set for some reason?
>>>
>>>
>>>
>>> On Wed, Jul 6, 2016 at 2:20 PM, Joseph Wu  wrote:
>>>
 If you can see the WebUI via HTTP, without downgrade support, you might
 be inadvertently running a different version of Mesos than the one you
 built.

 You can quickly sanity check this by removing either SSL_KEY_FILE or
 SSL_CERT_FILE and starting your master.  If your build has SSL support, it
 should immediately exit with an error message.


 On Wed, Jul 6, 2016 at 12:33 PM, Douglas Nelson 
 wrote:
 >
 > I attempted to set up SSL following this guide:
 http://mesos.apache.org/documentation/latest/ssl/
 >
 > I'm able to hit the WebUI with http but using https gives me nothing.
 I must be missing something. Here are the steps I'm taking:
 >
 > I downloaded 0.28.2 from here:
 https://github.com/apache/mesos/releases
 > I ran ./configure --enable-libevent --enable-ssl
 > Then I ran make and make install
 > I set the following environment variables:
 >
 > export SSL_ENABLED=1
 > export SSL_SUPPORT_DOWNGRADE=0
 > export SSL_KEY_FILE=
 > export SSL_CERT_FILE=
 >
 > Finally, I ran ./bin/mesos-master.sh --ip=127.0.0.1
 --work_dir=/var/lib/mesos
 >
 > I can provide any additional information if needed. Thanks!
 >
 > Also, I read that SSL would be included in mesosphere's nightly
 builds: https://open.mesosphere.com/downloads/mesos-nightly/
 >
 > How stable are those builds and has SSL already been included?
 >
 > -Doug Nelson


>>>
>>
>

Re: Setting up SSL for mesos

[Kamil Wokitajtis]

If you only set *SSL_ENABLED=true, *mesos would not start and throw error
that certificate and key variables are not exported.
So I assume mesos does not see SSL_ENABLED env variable in your case.
Do you run mesos from the same shell as you do the variables export ?


2016-07-07 20:53 GMT+02:00 Douglas Nelson :

> I rebuilt from scratch with SSL support and got no errors. I only set *export
> SSL_ENABLED=true* and then I ran the mesos-master.
>
> No errors were thrown and I can see the web UI via HTTP. I double checked
> that I was running the .sh from the build folder I created. Is mesos not
> connecting with the environment variable I set for some reason?
>
>
>
> On Wed, Jul 6, 2016 at 2:20 PM, Joseph Wu  wrote:
>
>> If you can see the WebUI via HTTP, without downgrade support, you might
>> be inadvertently running a different version of Mesos than the one you
>> built.
>>
>> You can quickly sanity check this by removing either SSL_KEY_FILE or
>> SSL_CERT_FILE and starting your master.  If your build has SSL support, it
>> should immediately exit with an error message.
>>
>>
>> On Wed, Jul 6, 2016 at 12:33 PM, Douglas Nelson 
>> wrote:
>> >
>> > I attempted to set up SSL following this guide:
>> http://mesos.apache.org/documentation/latest/ssl/
>> >
>> > I'm able to hit the WebUI with http but using https gives me nothing. I
>> must be missing something. Here are the steps I'm taking:
>> >
>> > I downloaded 0.28.2 from here: https://github.com/apache/mesos/releases
>> > I ran ./configure --enable-libevent --enable-ssl
>> > Then I ran make and make install
>> > I set the following environment variables:
>> >
>> > export SSL_ENABLED=1
>> > export SSL_SUPPORT_DOWNGRADE=0
>> > export SSL_KEY_FILE=
>> > export SSL_CERT_FILE=
>> >
>> > Finally, I ran ./bin/mesos-master.sh --ip=127.0.0.1
>> --work_dir=/var/lib/mesos
>> >
>> > I can provide any additional information if needed. Thanks!
>> >
>> > Also, I read that SSL would be included in mesosphere's nightly builds:
>> https://open.mesosphere.com/downloads/mesos-nightly/
>> >
>> > How stable are those builds and has SSL already been included?
>> >
>> > -Doug Nelson
>>
>>
>

Re: Setting up SSL for mesos

[Kamil Wokitajtis]

export SSL_ENABLED=true
export SSL_KEY_FILE=/etc/mesos/ssl/key.pem
export SSL_CERT_FILE=/etc/mesos/ssl/cert.pem

2016-07-06 23:05 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:

> For SSL support on 0.28.2 I am exporting only three variables and it works
> like charm:
>
>
> 2016-07-06 21:33 GMT+02:00 Douglas Nelson <itsbeh...@gmail.com>:
>
>> I attempted to set up SSL following this guide:
>> http://mesos.apache.org/documentation/latest/ssl/
>>
>> I'm able to hit the WebUI with http but using https gives me nothing. I
>> must be missing something. Here are the steps I'm taking:
>>
>>
>>1. I downloaded 0.28.2 from here:
>>https://github.com/apache/mesos/releases
>>2. I ran ./configure --enable-libevent --enable-ssl
>>3. Then I ran make and make install
>>4. I set the following environment variables:
>>   - export SSL_ENABLED=1
>>   - export SSL_SUPPORT_DOWNGRADE=0
>>   - export SSL_KEY_FILE=
>>   - export SSL_CERT_FILE=
>>5. Finally, I ran ./bin/mesos-master.sh --ip=127.0.0.1
>>--work_dir=/var/lib/mesos
>>
>> I can provide any additional information if needed. Thanks!
>>
>> Also, I read that SSL would be included in mesosphere's nightly builds:
>> https://open.mesosphere.com/downloads/mesos-nightly/
>>
>> How stable are those builds and has SSL already been included?
>>
>> -Doug Nelson
>>
>
>

Re: Setting up SSL for mesos

[Kamil Wokitajtis]

For SSL support on 0.28.2 I am exporting only three variables and it works
like charm:


2016-07-06 21:33 GMT+02:00 Douglas Nelson :

> I attempted to set up SSL following this guide:
> http://mesos.apache.org/documentation/latest/ssl/
>
> I'm able to hit the WebUI with http but using https gives me nothing. I
> must be missing something. Here are the steps I'm taking:
>
>
>1. I downloaded 0.28.2 from here:
>https://github.com/apache/mesos/releases
>2. I ran ./configure --enable-libevent --enable-ssl
>3. Then I ran make and make install
>4. I set the following environment variables:
>   - export SSL_ENABLED=1
>   - export SSL_SUPPORT_DOWNGRADE=0
>   - export SSL_KEY_FILE=
>   - export SSL_CERT_FILE=
>5. Finally, I ran ./bin/mesos-master.sh --ip=127.0.0.1
>--work_dir=/var/lib/mesos
>
> I can provide any additional information if needed. Thanks!
>
> Also, I read that SSL would be included in mesosphere's nightly builds:
> https://open.mesosphere.com/downloads/mesos-nightly/
>
> How stable are those builds and has SSL already been included?
>
> -Doug Nelson
>

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

Thanks, that was the case. I wonder why I didn't have to run ldconfig in
the first place after 0.28.1 install.
Anyway, another lesson learnt.

2016-06-06 14:51 GMT+02:00 Stephen Gran <stephen.g...@piksel.com>:

> Hi,
>
> Run ldconfig after install?
>
> Cheers,
>
> On 06/06/16 13:21, Kamil Wokitajtis wrote:
> > For 0.28.1:
> > root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> > | grep libmesos
> > libmesos-0.28.1.so <http://libmesos-0.28.1.so/> =>
> > /usr/local/lib/libmesos-0.28.1.so
> > <http://libmesos-0.28.1.so/> (0x7fbf522b6000)
> >
> > For 0.28.2, as expected, library not found:
> > root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> > | grep libmesos
> > libmesos-0.28.2.so <http://libmesos-0.28.2.so/> => not found
> >
> > After exporting LD_LIBRARY_PATH, libmesos is found as expected:
> > root@pltr-app-pl02:~#export LD_LIBRARY_PATH=/usr/local/lib
> > root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> > | grep mesos
> > libmesos-0.28.2.so <http://libmesos-0.28.2.so/> =>
> > /usr/local/lib/libmesos-0.28.2.so
> > <http://libmesos-0.28.2.so/> (0x7f219a8c1000)
> >
> > Looks like exporting LD_LIBRARY_PATH should help. But exporting this
> > variable in mesos startup scripts doesn't seem to solve issue.
> >
> >
> > 2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com
> > <mailto:gyliu...@gmail.com>>:
> >
> > You can check what is the output of `ldd mesos-docker-executor` to
> > see if the libmesos-xxx is in the right location.
> >
> > [root@dcos001 mesosphere]# ldd
> >
>  
> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
> > | grep libmesos
> > libmesos-0.28.1.so <http://libmesos-0.28.1.so> =>
> >
>  /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
> libmesos-0.28.1.so
> > <http://libmesos-0.28.1.so> (0x7f5cf1cb1000)
> >
> > Thanks,
> >
> > Guangya
> >
> > On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis
> > <wokitaj...@gmail.com <mailto:wokitaj...@gmail.com>> wrote:
> >
> > Hi,
> >
> > I have upgraded my mesos env from 0.28.1 to 0.28.2.
> > On 0.28.1 everything worked just fine.
> > Now agents are unable to start docker images, mesos throws:
> >
> > mesos-docker-executor: error while loading shared libraries:
> > libmesos-0.28.2.so <http://libmesos-0.28.2.so/>: cannot open
> > shared object file: No such  file or directory
> >
> > Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
> > /usr/local/lib
> > There is also symlink libmesos.so -> libmesos-0.28.2.
> > /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
> > I have also tried exporting LD_LIBRARY_PATH in startup scripts,
> > no luck.
> >
> > Thanks,
> > Kamil
> >
> >
> >
>
> --
> Stephen Gran
> Senior Technical Architect
>
> picture the possibilities | piksel.com
>

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

I have solved this issue by adding env variable to marathon app deployment
json:

"env": {
  "LD_LIBRARY_PATH" : "/usr/local/lib"
}

Maybe someone could shed light, why 0.28.2 is unable to locate libmesos
without exporting LD_LIBRARY_PATH?



2016-06-06 14:21 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:

> For 0.28.1:
> root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.1.so => /usr/local/lib/libmesos-0.28.1.so
>  (0x7fbf522b6000)
>
> For 0.28.2, as expected, library not found:
> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.2.so => not found
>
> After exporting LD_LIBRARY_PATH, libmesos is found as expected:
> root@pltr-app-pl02:~# export LD_LIBRARY_PATH=/usr/local/lib
> root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor
> | grep mesos
> libmesos-0.28.2.so => /usr/local/lib/libmesos-0.28.2.so
>  (0x7f219a8c1000)
>
> Looks like exporting LD_LIBRARY_PATH should help. But exporting this
> variable in mesos startup scripts doesn't seem to solve issue.
>
>
> 2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com>:
>
>> You can check what is the output of `ldd mesos-docker-executor` to see if
>> the libmesos-xxx is in the right location.
>>
>> [root@dcos001 mesosphere]# ldd
>> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
>> | grep libmesos
>> libmesos-0.28.1.so =>
>> /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
>> libmesos-0.28.1.so (0x7f5cf1cb1000)
>>
>> Thanks,
>>
>> Guangya
>>
>> On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis <wokitaj...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have upgraded my mesos env from 0.28.1 to 0.28.2.
>>> On 0.28.1 everything worked just fine.
>>> Now agents are unable to start docker images, mesos throws:
>>>
>>> mesos-docker-executor: error while loading shared libraries:
>>> libmesos-0.28.2.so: cannot open shared object file: No such  file or
>>> directory
>>>
>>> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
>>> /usr/local/lib
>>> There is also symlink libmesos.so -> libmesos-0.28.2.
>>> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
>>> I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.
>>>
>>> Thanks,
>>> Kamil
>>>
>>>
>>
>

Re: 0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

For 0.28.1:
root@pltr-app-pl01:~# ldd /usr/local/libexec/mesos/mesos-docker-executor |
grep libmesos
libmesos-0.28.1.so => /usr/local/lib/libmesos-0.28.1.so
 (0x7fbf522b6000)

For 0.28.2, as expected, library not found:
root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor |
grep libmesos
libmesos-0.28.2.so => not found

After exporting LD_LIBRARY_PATH, libmesos is found as expected:
root@pltr-app-pl02:~# export LD_LIBRARY_PATH=/usr/local/lib
root@pltr-app-pl02:~# ldd /usr/local/libexec/mesos/mesos-docker-executor |
grep mesos
libmesos-0.28.2.so => /usr/local/lib/libmesos-0.28.2.so
 (0x7f219a8c1000)

Looks like exporting LD_LIBRARY_PATH should help. But exporting this
variable in mesos startup scripts doesn't seem to solve issue.


2016-06-06 13:50 GMT+02:00 Guangya Liu <gyliu...@gmail.com>:

> You can check what is the output of `ldd mesos-docker-executor` to see if
> the libmesos-xxx is in the right location.
>
> [root@dcos001 mesosphere]# ldd
> ./packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/libexec/mesos/mesos-docker-executor
> | grep libmesos
> libmesos-0.28.1.so =>
> /opt/mesosphere/packages/mesos--0335ca0d3700ea88ad8b808f3b1b84d747ed07f0/lib/
> libmesos-0.28.1.so (0x7f5cf1cb1000)
>
> Thanks,
>
> Guangya
>
> On Mon, Jun 6, 2016 at 6:38 PM, Kamil Wokitajtis <wokitaj...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I have upgraded my mesos env from 0.28.1 to 0.28.2.
>> On 0.28.1 everything worked just fine.
>> Now agents are unable to start docker images, mesos throws:
>>
>> mesos-docker-executor: error while loading shared libraries:
>> libmesos-0.28.2.so: cannot open shared object file: No such  file or
>> directory
>>
>> Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
>> /usr/local/lib
>> There is also symlink libmesos.so -> libmesos-0.28.2.
>> /etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
>> I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.
>>
>> Thanks,
>> Kamil
>>
>>
>

0.28.2 - mesos-docker-executor - libmesos not found

[Kamil Wokitajtis]

Hi,

I have upgraded my mesos env from 0.28.1 to 0.28.2.
On 0.28.1 everything worked just fine.
Now agents are unable to start docker images, mesos throws:

mesos-docker-executor: error while loading shared libraries:
libmesos-0.28.2.so: cannot open shared object file: No such  file or
directory

Just like for Mesos 0.28.1 where it works, libmesos-0.28.2 is in
/usr/local/lib
There is also symlink libmesos.so -> libmesos-0.28.2.
/etc/ld.so.conf.d/libc.conf contains /usr/local/lib entry.
I have also tried exporting LD_LIBRARY_PATH in startup scripts, no luck.

Thanks,
Kamil

Re: How to install marathon-lb

[Kamil Wokitajtis]

Did you try to run docker from command line?
You need to paste marathon and mesos logs, answer is probably there ;)

2016-05-03 10:54 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:

> Hi kamil
>
> I tried to replace that hostname with the one related to one random slave.
> And it does not work.
> I tried also to change the private IP od the marathon instance with the
> public, but i still have problem.
> I'm also running Mesos-DNS this should be a problem?
>
>
> 2016-05-02 21:52 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>
>> Did you try to run docker command from shell? Does it work for you?
>> Do you have also slave running on 131.154.96.27?
>> In my case entry was "constraints": [["hostname", "CLUSTER",
>> "master-1"]], because on host master-1 I have both master and slave running.
>> If you don't have slave running on 131.154.96.27, update this entry to
>> point to one of your slave hosts.
>>
>>
>> 2016-05-02 19:03 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>
>>> Here it is:
>>>
>>> {
>>>
>>>   "id": "marathon-lb",
>>>
>>>   "volumes": [],
>>>
>>>   "cpus": 1,
>>>
>>>   "mem": 512,
>>>
>>>   "instances": 1,
>>>
>>>   "container": {
>>>
>>> "type": "DOCKER",
>>>
>>> "docker": {
>>>
>>> "image": "mesosphere/marathon-lb",
>>>
>>> "network": "HOST",
>>>
>>> "parameters": [
>>>
>>> { "key": "env", "value": "PORTS=9090" }
>>>
>>> ],
>>>
>>> "portMappings": [
>>>
>>>   {
>>>
>>>"containerPort": 80,
>>>
>>> "hostPort": 80,
>>>
>>> "servicePort": 10004,
>>>
>>> "protocol": "tcp"
>>>
>>>   },
>>>
>>>   {
>>>
>>>"containerPort": 9090,
>>>
>>> "hostPort": 9090,
>>>
>>> "servicePort": 10005,
>>>
>>> "protocol": "tcp"
>>>
>>>   }
>>>
>>> ]},
>>>
>>> "privileged": false
>>>
>>>   },
>>>
>>>   "args": [
>>>
>>>   "sse",
>>>
>>>   "--marathon", "http://192.168.100.54:8080;,
>>>
>>>   "--group", "external"
>>>
>>>   ],
>>>
>>>   "forcePullImage": true,
>>>
>>>   "constraints": [["hostname", "CLUSTER", "131.154.96.27"]]
>>>
>>> }
>>>
>>>
>>> where:
>>> 192.168.100.54 is the private IP there marathon is running.
>>>
>>> 131.154.96.27: is the hostname i set in /etc/mesos-master/hostname and
>>> /etc/mesos-master/ip files.
>>>
>>>
>>>
>>> 2016-05-02 17:20 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>>>
>>>> Please paste your modified marathon-lb.json file.
>>>> Can you see any error messages in the marathon and mesos logs ?
>>>> We are mapping ports 80, 9090,10004,10005, those need to be open.
>>>>
>>>> Docker command is as follows:
>>>>
>>>> docker run --privileged -e PORTS=9090 --net=host -p 80:80 -p 9090:9090
>>>> mesosphere/marathon-lb sse --marathon http://192.168.33.20:8080
>>>> --group "external"
>>>>
>>>> 2016-05-02 17:07 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>
>>>>> Can you please tell me which is the correspondent marathon-lb.json
>>>>> docker command?
>>>>>
>>>>> 2016-05-02 16:55 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>>
>>>>>> All those ports must be open? Because i am on openstack environment
>>>>>> and i need to know if there is something to open
>>>>>>
>>>>>> 2016-05-02 15:52 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>>>

Re: How to install marathon-lb

[Kamil Wokitajtis]

Did you try to run docker command from shell? Does it work for you?
Do you have also slave running on 131.154.96.27?
In my case entry was "constraints": [["hostname", "CLUSTER", "master-1"]],
because on host master-1 I have both master and slave running.
If you don't have slave running on 131.154.96.27, update this entry to
point to one of your slave hosts.


2016-05-02 19:03 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:

> Here it is:
>
> {
>
>   "id": "marathon-lb",
>
>   "volumes": [],
>
>   "cpus": 1,
>
>   "mem": 512,
>
>   "instances": 1,
>
>   "container": {
>
> "type": "DOCKER",
>
> "docker": {
>
> "image": "mesosphere/marathon-lb",
>
> "network": "HOST",
>
> "parameters": [
>
> { "key": "env", "value": "PORTS=9090" }
>
> ],
>
> "portMappings": [
>
>   {
>
>"containerPort": 80,
>
> "hostPort": 80,
>
> "servicePort": 10004,
>
> "protocol": "tcp"
>
>   },
>
>   {
>
>"containerPort": 9090,
>
> "hostPort": 9090,
>
> "servicePort": 10005,
>
> "protocol": "tcp"
>
>   }
>
> ]},
>
> "privileged": false
>
>   },
>
>   "args": [
>
>   "sse",
>
>   "--marathon", "http://192.168.100.54:8080;,
>
>   "--group", "external"
>
>   ],
>
>   "forcePullImage": true,
>
>   "constraints": [["hostname", "CLUSTER", "131.154.96.27"]]
>
> }
>
>
> where:
> 192.168.100.54 is the private IP there marathon is running.
>
> 131.154.96.27: is the hostname i set in /etc/mesos-master/hostname and
> /etc/mesos-master/ip files.
>
>
>
> 2016-05-02 17:20 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>
>> Please paste your modified marathon-lb.json file.
>> Can you see any error messages in the marathon and mesos logs ?
>> We are mapping ports 80, 9090,10004,10005, those need to be open.
>>
>> Docker command is as follows:
>>
>> docker run --privileged -e PORTS=9090 --net=host -p 80:80 -p 9090:9090
>> mesosphere/marathon-lb sse --marathon http://192.168.33.20:8080 --group
>> "external"
>>
>> 2016-05-02 17:07 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>
>>> Can you please tell me which is the correspondent marathon-lb.json
>>> docker command?
>>>
>>> 2016-05-02 16:55 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>
>>>> All those ports must be open? Because i am on openstack environment and
>>>> i need to know if there is something to open
>>>>
>>>> 2016-05-02 15:52 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>
>>>>> i changed all but i see waiting app.
>>>>>
>>>>> 2016-05-02 15:26 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>>>>>
>>>>>> I am using private docker registry (https://docs.docker.com/registry/
>>>>>> ).
>>>>>> In my case I can pull image from local repository installed on node
>>>>>> master-1 (master-1:5000/marathon-lb):
>>>>>>  "image": "master-1:5000/marathon-lb"
>>>>>>
>>>>>> If you don't have private registry, you have to pull image from the
>>>>>> docker hub (mesosphere/marathon-lb):
>>>>>>  "image": "mesosphere/marathon-lb"
>>>>>>
>>>>>> Basically, for many reasons I want all my images to be hosted locally.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2016-05-02 15:10 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>>>
>>>>>>> Thanks your your answer.
>>>>>>> I understood what you are telling me, just a thing, what you mean
>>>>>>> with docker registry?
>>>>>>>
>>>>>>> 2016-05-02 13:31 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>>>>>>>
>>>>>>>> Hi,
>>>>>&g

Re: How to install marathon-lb

[Kamil Wokitajtis]

Please paste your modified marathon-lb.json file.
Can you see any error messages in the marathon and mesos logs ?
We are mapping ports 80, 9090,10004,10005, those need to be open.

Docker command is as follows:

docker run --privileged -e PORTS=9090 --net=host -p 80:80 -p 9090:9090
mesosphere/marathon-lb sse --marathon http://192.168.33.20:8080 --group
"external"

2016-05-02 17:07 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:

> Can you please tell me which is the correspondent marathon-lb.json docker
> command?
>
> 2016-05-02 16:55 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>
>> All those ports must be open? Because i am on openstack environment and i
>> need to know if there is something to open
>>
>> 2016-05-02 15:52 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>
>>> i changed all but i see waiting app.
>>>
>>> 2016-05-02 15:26 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>>>
>>>> I am using private docker registry (https://docs.docker.com/registry/
>>>> ).
>>>> In my case I can pull image from local repository installed on node
>>>> master-1 (master-1:5000/marathon-lb):
>>>>  "image": "master-1:5000/marathon-lb"
>>>>
>>>> If you don't have private registry, you have to pull image from the
>>>> docker hub (mesosphere/marathon-lb):
>>>>  "image": "mesosphere/marathon-lb"
>>>>
>>>> Basically, for many reasons I want all my images to be hosted locally.
>>>>
>>>>
>>>>
>>>> 2016-05-02 15:10 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>
>>>>> Thanks your your answer.
>>>>> I understood what you are telling me, just a thing, what you mean with
>>>>> docker registry?
>>>>>
>>>>> 2016-05-02 13:31 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Fastest way is to run marathon-lb docker image.
>>>>>> You have to update marathon-lb.json code below with yours (or public)
>>>>>> docker registry, IPs and hostnames.
>>>>>> When you add application to marathon and you want it to be load
>>>>>> balanced via marathon-lb,
>>>>>> you have to add labels section eg.:
>>>>>>
>>>>>>  "labels": {
>>>>>> "HAPROXY_GROUP":"external",
>>>>>> "HAPROXY_0_VHOST":"service.mesosphere.com"
>>>>>>   }
>>>>>>
>>>>>>
>>>>>> Reading documentation on github was enough for me, specially "issues"
>>>>>> tab ;)
>>>>>> https://github.com/mesosphere/marathon-lb
>>>>>>
>>>>>>
>>>>>> Below code works for me, but I think you can change "network" mode
>>>>>> from BRIDGE to HOST and remove line : { "key": "net", "value": "host" }.
>>>>>>
>>>>>> marathon-lb.json:
>>>>>>
>>>>>> {
>>>>>>   "id": "marathon-lb",
>>>>>>   "volumes": [],
>>>>>>   "cpus": 0.5,
>>>>>>   "mem": 256.0,
>>>>>>   "instances": 1,
>>>>>>   "container": {
>>>>>> "type": "DOCKER",
>>>>>> "docker": {
>>>>>> "image": "master-1:5000/marathon-lb",
>>>>>> "network": "BRIDGE",
>>>>>> "parameters": [
>>>>>> { "key": "env", "value": "PORTS=9090" },
>>>>>> { "key": "net", "value": "host" }
>>>>>> ],
>>>>>> "portMappings": [
>>>>>>   {
>>>>>> "containerPort": 80,
>>>>>> "hostPort": 80,
>>>>>> "servicePort": 10004,
>>>>>> "protocol": "tcp"
>>>>>>   },
>>>>>>   {
>>>>>> "containerPort": 9090,
>>>>>> "hostPort": 9090,
>>>>>> "servicePort": 10005,
>>>>>> "protocol": "tcp"
>>>>>>   }
>>>>>> ]},
>>>>>> "privileged": false
>>>>>>   },
>>>>>>   "args": [
>>>>>>   "sse",
>>>>>>   "--marathon", "http://192.168.33.20:8080;,
>>>>>>   "--group", "external"
>>>>>>   ],
>>>>>>   "forcePullImage": true,
>>>>>>   "constraints": [["hostname", "CLUSTER", "master-1"]]
>>>>>> }
>>>>>>
>>>>>> 2016-05-02 11:08 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>>>>>
>>>>>>> Hello all
>>>>>>>
>>>>>>> I'm not using DC/OS, and i would like to know how to install
>>>>>>> marathon-lb on my mesos cluster. Is there any tutorial that does not
>>>>>>> involve dcos instructions?
>>>>>>>
>>>>>>> Thanks for replies.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: How to install marathon-lb

[Kamil Wokitajtis]

I am using private docker registry (https://docs.docker.com/registry/).
In my case I can pull image from local repository installed on node
master-1 (master-1:5000/marathon-lb):
 "image": "master-1:5000/marathon-lb"

If you don't have private registry, you have to pull image from the docker
hub (mesosphere/marathon-lb):
 "image": "mesosphere/marathon-lb"

Basically, for many reasons I want all my images to be hosted locally.



2016-05-02 15:10 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:

> Thanks your your answer.
> I understood what you are telling me, just a thing, what you mean with
> docker registry?
>
> 2016-05-02 13:31 GMT+02:00 Kamil Wokitajtis <wokitaj...@gmail.com>:
>
>> Hi,
>>
>> Fastest way is to run marathon-lb docker image.
>> You have to update marathon-lb.json code below with yours (or public)
>> docker registry, IPs and hostnames.
>> When you add application to marathon and you want it to be load balanced
>> via marathon-lb,
>> you have to add labels section eg.:
>>
>>  "labels": {
>> "HAPROXY_GROUP":"external",
>> "HAPROXY_0_VHOST":"service.mesosphere.com"
>>   }
>>
>>
>> Reading documentation on github was enough for me, specially "issues" tab
>> ;)
>> https://github.com/mesosphere/marathon-lb
>>
>>
>> Below code works for me, but I think you can change "network" mode from
>> BRIDGE to HOST and remove line : { "key": "net", "value": "host" }.
>>
>> marathon-lb.json:
>>
>> {
>>   "id": "marathon-lb",
>>   "volumes": [],
>>   "cpus": 0.5,
>>   "mem": 256.0,
>>   "instances": 1,
>>   "container": {
>> "type": "DOCKER",
>> "docker": {
>> "image": "master-1:5000/marathon-lb",
>> "network": "BRIDGE",
>> "parameters": [
>> { "key": "env", "value": "PORTS=9090" },
>> { "key": "net", "value": "host" }
>> ],
>> "portMappings": [
>>   {
>> "containerPort": 80,
>> "hostPort": 80,
>> "servicePort": 10004,
>> "protocol": "tcp"
>>   },
>>   {
>> "containerPort": 9090,
>> "hostPort": 9090,
>> "servicePort": 10005,
>> "protocol": "tcp"
>>   }
>> ]},
>> "privileged": false
>>   },
>>   "args": [
>>   "sse",
>>   "--marathon", "http://192.168.33.20:8080;,
>>   "--group", "external"
>>   ],
>>   "forcePullImage": true,
>>   "constraints": [["hostname", "CLUSTER", "master-1"]]
>> }
>>
>> 2016-05-02 11:08 GMT+02:00 Stefano Bianchi <jazzist...@gmail.com>:
>>
>>> Hello all
>>>
>>> I'm not using DC/OS, and i would like to know how to install marathon-lb
>>> on my mesos cluster. Is there any tutorial that does not involve dcos
>>> instructions?
>>>
>>> Thanks for replies.
>>>
>>
>>
>

Re: How to install marathon-lb

[Kamil Wokitajtis]

Hi,

Fastest way is to run marathon-lb docker image.
You have to update marathon-lb.json code below with yours (or public)
docker registry, IPs and hostnames.
When you add application to marathon and you want it to be load balanced
via marathon-lb,
you have to add labels section eg.:

 "labels": {
"HAPROXY_GROUP":"external",
"HAPROXY_0_VHOST":"service.mesosphere.com"
  }


Reading documentation on github was enough for me, specially "issues" tab ;)
https://github.com/mesosphere/marathon-lb


Below code works for me, but I think you can change "network" mode from
BRIDGE to HOST and remove line : { "key": "net", "value": "host" }.

marathon-lb.json:

{
  "id": "marathon-lb",
  "volumes": [],
  "cpus": 0.5,
  "mem": 256.0,
  "instances": 1,
  "container": {
"type": "DOCKER",
"docker": {
"image": "master-1:5000/marathon-lb",
"network": "BRIDGE",
"parameters": [
{ "key": "env", "value": "PORTS=9090" },
{ "key": "net", "value": "host" }
],
"portMappings": [
  {
"containerPort": 80,
"hostPort": 80,
"servicePort": 10004,
"protocol": "tcp"
  },
  {
"containerPort": 9090,
"hostPort": 9090,
"servicePort": 10005,
"protocol": "tcp"
  }
]},
"privileged": false
  },
  "args": [
  "sse",
  "--marathon", "http://192.168.33.20:8080;,
  "--group", "external"
  ],
  "forcePullImage": true,
  "constraints": [["hostname", "CLUSTER", "master-1"]]
}

2016-05-02 11:08 GMT+02:00 Stefano Bianchi :

> Hello all
>
> I'm not using DC/OS, and i would like to know how to install marathon-lb
> on my mesos cluster. Is there any tutorial that does not involve dcos
> instructions?
>
> Thanks for replies.
>

Mesos 0.28 SSL in official packages

[Kamil Wokitajtis]

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