[Pkg-xen-devel] Bug#674137: Bug#674137: xcp-xapi: default ports in xapi

Mike McClurg mike.mcclurg at gmail.com
Wed May 23 10:27:48 UTC 2012


On Wed, May 23, 2012 at 11:17 AM, Ritesh Raj Sarraf <rrs at debian.org> wrote:
> Package: xcp-xapi
> Severity: normal
> Tags: upstream
>
>
> Are there good reasons why xapi by default prefers to bidn to 80 and
> 443? This will lead to xapi installation/start failure on every server
> machine that might (and will probably) have apache installed.
>
> I know we can remove apache or change its port or change xapi's port
> (But I've had a hard time to easily find out where to specify the port),
> but 80/443 is owned by web servers and xapi is not a web server.

Well, technically it is a web server, since it speaks HTTP and serves
an XML-RPC based API ;) But yes, I see your point.

This is an artifact of xapi being from XenServer, where you would
never, ever want to put another web server in dom0. And still, even
with xapi on Debian, we still wouldn't recommend someone do this,
which is why xapi's binding ports aren't configurable.

It shouldn't be too hard make xapi configurable, so that you can
change a conf file setting and tell it to listen on a different port,
for both HTTP and HTTPS traffic. Is this something that is highly
desirable for Wheezy?

Mike





More information about the Pkg-xen-devel mailing list