It is a request from your browser session, not from the master that is
going to the slaves - so in order to view the sandbox you need to ensure
that the machine your browser is on can resolve and route to the masters
_and_ the slaves.
The master doesn't proxy the sandbox requests through itself
Thank you all, the master and slaves can resolve each others' hostname and
ssh login without password, firewalls have been switched off on all the
machines too.
So I'm confused what will block such a pull of info of slaves from UI?
Cheers,
Dan
2015-01-21 16:35 GMT-06:00 Cody Maloney
:
{
...
completed_frameworks: [
{
...
completed_executors: [
{
...
*container*: 26491475-9515-464d-bcd0-c72790489a85,
*directory*:
/tmp/mesos/0/slaves/20150122-175457-16777343-5050-18106-S0/frameworks/20150122-182305-16777343-5050-18833-
Hi all,
I created a JIRA to track the 0.22.0 release:
https://issues.apache.org/jira/browse/MESOS-2248
Feel free to add and mark JIRA tickets (major features and minor fixes) you
would like to go into this release.
We will mark the tickets as blockers when we have agreed on a reasonable
set of
we use the HAProxy configurator script bundled with marathon to bind
applications to ports :
https://github.com/mesosphere/marathon/blob/master/bin/
haproxy-marathon-bridge
Given the foregoing, can mesos-dns + mesos (possibly, mesosphere’s
marathon) + docker be configured to emulate
Schedulers can only use resources on slaves that are unused by and
unallocated to other schedulers. Therefore, schedulers cannot achieve this
unless you reserve slots on every slave for the scheduler. Seems kind of
a forced fit. An init like support would be more fundamental to Mesos
cluster
Thanks Ryan, yes, from the machine where the browser is on slave hostnames
could not be resolved, so that's why failure, but it can reach them by IP
address( I don't think sys admin would like to add those VMs entries to
/etc/hosts on the server). I tried to change masters and slaves of mesos
to
Try the --hostname parameters for master/slave. If you want to be extra
explicit about the IP (e.g. publish the public IP instead of the private
one in a cloud environment), you can also set the --ip parameter on
master/slave.
On Thu, Jan 22, 2015 at 8:43 AM, Dan Dong dongda...@gmail.com wrote:
On 01/21/2015 11:10 PM, Shuai Lin wrote:
OK, I'll take a look at the debian package.
thanks,
James
You can always write the init wrapper scripts for marathon. There is an
official debian package, which you can find in mesos's apt repo.
On Thu, Jan 22, 2015 at 4:20 AM, CCAAT
Hi,
My goal has been to develop multi-container docker applications locally and
expect their seamless introduction to production environments (wow.)
I have done a POC for my goal with fig and Kubernetes, and I enjoy that I can
depend on standard service ip/port environment variables to be
Just a thought looking forward...
Might be useful to define an init kind of feature in Mesos slaves.
Configuration can be defined in Mesos master that lists services that must
be run on all slaves. When slaves register, they get the list of services
to run all the time. Updates to the
Yes, --hostname solves the problem. Now I can see all files there like
stdout, stderr etc, but when I click on e.g stdout, it pops a new blank
window(pailer.html) without the content of the file(9KB size). Although it
provides a Download link beside, it would be much more convenient if one
can
If this was going to be used to allocate tasks outside of the schedulers
resource management, and for every slave, why not just use the OS provided
init system instead?
On 22 January 2015 at 19:40, Sharma Podila spod...@netflix.com wrote:
Schedulers can only use resources on slaves that are
13 matches
Mail list logo
