senlin-api and placement-api have same default port

[Jonathan Mills]

It appears that senlin-api and placement-api are both trying to claim port 8778 as their default port. I noticed this when I upgraded from Mitaka to Pike, and had to stand up the Placement api for the first time. It couldn't possibly have escaped others' notice, but I don't see any open bugs on it.

[Qiming Teng (tengqim)]

Unfortunately, yes. This issue has been identified last year and the solution was to have every service deployed using service path on a single port on the web server. However, later on, RDO insists it will continue to use port based service deployment and they want nova placement API to use 8778 port...

[Jonathan Mills (jonmills-t)]

So what is the plan for Senlin API port? Your response is ambiguous in that you acknowledge the issue and also make no commitment to address it. Should I read your response as "won't fix"?

[Qiming Teng (tengqim)]

No. I was trying to give you a brief background on this. We haven't got cycles to (re-)solve it so far. The plan is to debug senlin service so that it doesn't rely on a particular port. By that I mean enabling users to access senlin service at a url like this:

http://controller-ip/clustering/v1

[miaoyuliang (mylaliang)]

Then，what is the future plan? Senlin and placement default port is still 8778