osapi_port/osapi_listen_port and ec2_port/ec2_listen_port

[Brian Lamar]

The following flags need to be properly documented:

ec2_port
ec2_listen_port
ec2_host
ec2_listen

osapi_port
osapi_listen_port
osapi_host
osapi_listen

http://docs.openstack.org/cactus/openstack-compute/admin/content/reference-for-flags-in-nova-conf.html

[Vish Ishaya (vishvananda)]

There are two versions of the flags because the host:port used by clients is different from the host:port that the server is listening on when you are doing load balancing. So you need to be able to specify a host / port for clients and a listen_ host /port for the server.

So i think the actual bug here is just better documentation.

[Brian Lamar (blamar)]

Ugh, this is more complicated than I thought :)

I'm really curious how this is going to work out in a production environment. I don't like that the API services need to have information about how they're being load-balanced/proxied. Are you sure this is necessary? Not doubting, I just don't see why the API needs this knowledge.

Thanks!

[Thierry Carrez (ttx)]

ISTR it needs it to advertise the endpoints correctly. It's listening to private IP/port combo but advertises a public combo to the client as endpoint.

[Brian Waldon (bcwaldon)]

Should this bug move to openstack-manuals?

[Thierry Carrez (ttx)]

done