I was wondering how others are securing ZooKeeper on top of Mesos.
I'm running Mesos in HA mode on 3 AWS EC2 instances. A number of external
machines are set up as Mesos agents and SSL/authentication is enabled on
both ends (for Mesos and its frameworks). But to use HA mode the agents
have to
It was working for me with mesos 1.0.0-rc2. Now that I made the switch to
1.0.0 the feature is missing for user/pass prompt at the WebUI. Was another
flag added or was it decided that this feature wasn't necessary?
On Tue, Jul 12, 2016 at 6:26 PM, Douglas Nelson <itsbeh...@gmail.com> wrote:
it
> message there.
>
> See: https://issues.apache.org/jira/browse/MESOS-5854
>
> On Fri, Jul 29, 2016 at 5:57 PM, Douglas Nelson <itsbeh...@gmail.com>
> wrote:
>
>> It might be an issue with the mesos-init-wrapper? I'm using that to set
>> the flag via config
It might be an issue with the mesos-init-wrapper? I'm using that to set the
flag via config files. I'll have to look through it and see exactly what
it's doing when it sets the attributes flag.
On Fri, Jul 29, 2016 at 6:48 PM, Douglas Nelson <itsbeh...@gmail.com> wrote:
> I'm pretty s
ctory doesn't contain info from an
> agent started with different attributes (or no attributes).
>
> On Fri, Jul 29, 2016 at 5:31 PM, Douglas Nelson <itsbeh...@gmail.com>
> wrote:
>
>> When I set any attributes for the agent node it fails to run. No
>> mesos-slave.E
When I set any attributes for the agent node it fails to run. No
mesos-slave.ERROR log is created. I am using mesos 1.0.0 from the
mesosphere package, but I also tried building it and had the same issue.
As soon as I remove the --attributes flag the agent runs normally and
registers itself with
I have SSL enabled for mesos and for the most part everything seems to be
working fine. But when I stop a slave node for long enough that it shows up
with status LOST then I start up the slave again, registration with the
master fails:
I0718 15:51:45.646260 16791 master.cpp:5495] Authenticating
1.0.0, which is still going through release vote.
>
> Can you share which version of Mesos you are running?
>
> On Tue, Jul 12, 2016 at 5:18 PM, Douglas Nelson <itsbeh...@gmail.com>
> wrote:
>
>> With marathon you can enable basic access authentication to the WebUI
&g
With marathon you can enable basic access authentication to the WebUI with
the flag --http_credentials.
I expected something similar with the flag --authenticate_http in mesos but
when I hit the WebUI I'm not prompted to give a username/pass. Is that
feature not included in mesos or is there a
-master.sh ...)
>
> On Thu, Jul 7, 2016 at 11:53 AM, Douglas Nelson <itsbeh...@gmail.com>
> 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
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 <itsbeh...@gmail.com>
> wrote:
>
>> I rebuilt from scratch with SSL support and got no errors. I only set *export
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 <itsbeh...@gmail.com>
> wrote:
&
> 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:
&
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:
14 matches
Mail list logo
