Senlin-api fails to bind to bind_host
Having learned that the Senlin installation instructions mean what they say :) I've also learned that I made an error installing Senlin, which I think I've cleared up. Now when I open a new console and launch senlin-api, it fails to bind to 0.0.0.0:8778. I understand the 0.0.0.0 to be interpreted as "whatever my IP address is just now". So I ran 'lsof' and discovered there are many listeners on 8778. Where is the best place to look for the cause of that failure?
Not only does senlin-api fail as described, but none of the "openstack cluster ..." commands are recognized. If Apache is listening on 8778, should I even be trying to run the senlin-api command?
Bug 1743959 (https://bugs.launchpad.net/senlin/+bu...) seems to relate to this. Can I just pick another port for Senlin? I'm not too proud to replace the 32 occurrences of '8778' with, say '8779'. I'm on the Stein release. Is there any advice available on this question?
After discovering that this is a two-year-old problem, I modified the Apache placement-api.conf file to use port 8780. Now Senlin binds just fine and there seems to be a periodic GET in the senlin-api console window. Now to pursue the question of why the "openstack cluster ..." commands don't work