Open parker20121 opened 8 years ago
Does the marathon has any tasks deployed?
On 9 Dec 2015, at 18:23, Matt Parker notifications@github.com wrote:
this is what the query produces. I'm running marathon 0.13.0 and mesos 0.25
curl -i http://10.105.0.15:8000/api/services HTTP/1.1 200 OK Content-Type: application/json Date: Wed, 09 Dec 2015 18:17:07 GMT Content-Length: 2
{}
— Reply to this email directly or view it on GitHub.
116 instances
any logs from Bamboo being able to identity changes?
Can bamboo communicate with Marathon?
On 9 Dec 2015, at 19:10, Matt Parker notifications@github.com wrote:
116 instances
— Reply to this email directly or view it on GitHub.
I'm assuming so since the bamboo interface lists every instance (see graphic in first post)
core@r105u21 ~ $ docker logs bamboo
/usr/lib/python2.7/dist-packages/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2015-12-09 18:39:10,333 CRIT Supervisor running as root (no user in config file)
2015-12-09 18:39:10,333 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2015-12-09 18:39:10,442 INFO RPC interface 'supervisor' initialized
2015-12-09 18:39:10,442 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-12-09 18:39:10,442 INFO supervisord started with pid 10
2015-12-09 18:39:11,446 INFO spawned: 'bamboo' with pid 13
2015-12-09 18:39:11,573 DEBG 'bamboo' stdout output:
2015/12/09 18:39:11 Using environment override MARATHON_ENDPOINT=http://10.105.0.1,http://10.105.0.3,http://10.105.0.5,http://10.105.0.7,http://10.105.0.9
2015/12/09 18:39:11 Using environment override BAMBOO_ENDPOINT=http://bamboo:8000
2015/12/09 18:39:11 Using environment override BAMBOO_ZK_HOST=zk://10.105.0.1:2181,10.105.0.3:2181,10.105.0.5:2181,10.105.0.7:2181,10.105.0.9:2181
2015/12/09 18:39:11 Using environment override BAMBOO_ZK_PATH=/bamboo
2015/12/09 18:39:11 Environment variable not set: STATSD_ENABLED
2015/12/09 18:39:11 Starting update loop
2015-12-09 18:39:11,635 DEBG 'bamboo' stdout output:
2015/12/09 18:39:11 bamboo_startup => 2015-12-09T18:39:11Z
2015/12/09 18:39:11 Queuing an haproxy update.
2015-12-09 18:39:11,678 DEBG 'bamboo' stdout output:
2015/12/09 18:39:11 Exec cmd: PIDS=`pidof haproxy`; haproxy -f /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -sf $PIDS && while ps -p $PIDS; do sleep 0.2; done
2015-12-09 18:39:11,899 DEBG 'bamboo' stdout output:
[martini] listening on :8000 (development)
2015-12-09 18:39:12,273 DEBG 'bamboo' stdout output:
2015/12/09 18:39:12 HAProxy: Configuration updated
2015-12-09 18:39:13,274 INFO success: bamboo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Does each service need to be configured individually to make it available through bamboo/haproxy? Or should they be available by default?
Depends which template you use. We mostly use host based routing with DNS. But if you use path based, the default template support it already without adding new entry in Bamboo API or UI.
We don't often use path based because some applications may need special treatment to render properly (some apps can't deal with paths correctly)
On 9 Dec 2015, at 19:27, Matt Parker notifications@github.com wrote:
Does each service need to be configured individually to make it available through bamboo/haproxy? Or should they be available by default?
— Reply to this email directly or view it on GitHub.
I started Bamboo on Mesos & DockerHUb's milk/bamboo:latest-port across our mesos slaves.
But when I try to list services using
curl -i http://X.X.X.X:8000/api/services
I get an empty JSON response
this is what the query produces. I'm running marathon 0.13.0 and mesos 0.25
curl -i http://10.105.0.15:8000/api/services HTTP/1.1 200 OK Content-Type: application/json Date: Wed, 09 Dec 2015 18:17:07 GMT Content-Length: 2
{}