Re: [openstack-dev] HTTPD Config

2015-03-06 Thread Adam Young
On 03/06/2015 01:29 PM, Matthias Runge wrote: On Fri, Mar 06, 2015 at 11:08:44AM -0500, Adam Young wrote: No matter what we do in devstack, this is something, horizon and keystone devs need to fix first. E.g. in Horizon, we still discover hard coded URLs here and there. To catch that kind of

Re: [openstack-dev] HTTPD Config

2015-03-06 Thread Rich Megginson
On 03/06/2015 12:37 AM, Matthias Runge wrote: On 05/03/15 19:49, Adam Young wrote: I'd like to drop port 5000 all-together, as we are using a port assigned to a different service. 35357 is also problematic as it is in the middle of the Ephemeral range. Since we are talking about running

Re: [openstack-dev] HTTPD Config

2015-03-06 Thread Adam Young
On 03/06/2015 02:37 AM, Matthias Runge wrote: On 05/03/15 19:49, Adam Young wrote: I'd like to drop port 5000 all-together, as we are using a port assigned to a different service. 35357 is also problematic as it is in the middle of the Ephemeral range. Since we are talking about running

Re: [openstack-dev] HTTPD Config

2015-03-06 Thread Matthias Runge
On Fri, Mar 06, 2015 at 11:08:44AM -0500, Adam Young wrote: No matter what we do in devstack, this is something, horizon and keystone devs need to fix first. E.g. in Horizon, we still discover hard coded URLs here and there. To catch that kind of things, I had a patch up for review, to easily

[openstack-dev] HTTPD Config

2015-03-05 Thread Adam Young
I'm trying to get a grip on what the HTTPD configuration should be for Horizon in order for it to use HTTPS. This rally should be the default, but the devstack and puppet choice of putting the Horizon config inside a Virtualhoat *:80 section in the config file makes it tricky. If I remove

Re: [openstack-dev] HTTPD Config

2015-03-05 Thread Matthias Runge
On 05/03/15 19:49, Adam Young wrote: I'd like to drop port 5000 all-together, as we are using a port assigned to a different service. 35357 is also problematic as it is in the middle of the Ephemeral range. Since we are talking about running everything in one web server anywya, using