Le 20/12/2016 10:20, Chris Dent a écrit : > On Tue, 20 Dec 2016, Sylvain Bauza wrote: > >> Before moving forward and picking yet another port that could trample >> another service, I'd rather prefer first that Senlin jobs would >> temporarely disable the placement-* services so that the gate would be >> happy, while in the same time we try to identify a free port number that >> the placement API can safely bind. > > Another option here may be to not have the placement api bind to two > ports. The current set up binds 8778 with the API at /, but what's > registered in the service catalog is port 80 with the API at > /placement. > > So perhaps only use the http://1.2.3.4/placement and disable the > virtualhost that listens on 8778? > > I'd experiment with this myself but I'm going to be away from a > compute all day. If people think it is a good idea but nobody has a > chance to do it today I'll look into it tomorrow. >
Oh good catch. Since we register the service catalog with port 80, then there is no reason to consume an application port. Chris, don't worry, I'll play with that today. -Sylvain > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
