You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm testing bamboo on a 1 master/3 slaves mesos cluster. Marathon, zk, mesos master, haproxy and bamboo are all on master server.
When I scale up or down a app in Marathon, I have to clic on "update" button in bamboo ui for bamboo to update haproxy configuration. The number of instances is reflected correctly, but the log does not show anything, and haproxy is not reconfigured.
Here is the production.json:
{
"Marathon": {
"Endpoint": "http://localhost:8080",
"Zookeeper": {
"Host": "localhost:2181",
"Path": "/marathon/state",
"ReportingDelay": 5
}
},
Hello.
I'm testing bamboo on a 1 master/3 slaves mesos cluster. Marathon, zk, mesos master, haproxy and bamboo are all on master server.
When I scale up or down a app in Marathon, I have to clic on "update" button in bamboo ui for bamboo to update haproxy configuration. The number of instances is reflected correctly, but the log does not show anything, and haproxy is not reconfigured.
Here is the production.json:
{
"Marathon": {
"Endpoint": "http://localhost:8080",
"Zookeeper": {
"Host": "localhost:2181",
"Path": "/marathon/state",
"ReportingDelay": 5
}
},
"Bamboo": {
"Endpoint": "http://localhost:8000",
"Zookeeper": {
"Host": "localhost",
"Path": "/marathon-haproxy/state",
"ReportingDelay": 5
}
},
"HAProxy": {
"TemplatePath": "/root/gopath/src/github.com/QubitProducts/bamboo/config/haproxy_template.cfg",
"OutputPath": "/usr/local/etc/haproxy/haproxy.cfg",
"ReloadCommand": "read PIDS < /var/run/haproxy.pid; haproxy -f /usr/local/etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid -sf $PIDS && while ps -p $PIDS; do sleep 0.2; done"
},
"StatsD": {
"Enabled": false,
"Host": "localhost:8125",
"Prefix": "bamboo-server.development."
}
}
Is there any other configuration to debug te (marathon | zk) /bamboo communication?
Thanks.
The text was updated successfully, but these errors were encountered: