RE: Openstack in HTTPD URL Scheme

[Matt Domsch]

NameVirtualHost localhost?

-----Original Message-----
From: Adam Young [[e-mail]]
Sent: Friday, April 27, 2012 04:36 PM Central Standard Time
To: [e-mail]
Subject: Re: Openstack in HTTPD URL Scheme

On 04/27/2012 05:33 PM, Christian Berendt wrote:
> Hello Adam.
>
> On 04/27/2012 11:25 PM, Adam Young wrote:
> > #should this be keystone or identity?
>
> I would prefer using always the development name of the project, in
> this case keystone.
>
> Regards, Christian.

Thanks, Christian.  I suspect that will work better with documentation
as well.

Pete Zaitcev also has pointed out that Swift probably won't play nicely
with this,  as the URL scheme is pretty much driven by Amazon, and it
assumes a top level URL along the lines of

http://test-1235163301.kvm-rei.zaitcev.lan/testdata
https://s3.amazonaws.com/test-1235163301/testdata
http://kvm-rei.zaitcev.lan/test-1235163301/testdata

_______________________________________________
cloud mailing list
[e-mail]
https://admin.fedoraproject.org/mailman/listinfo/cloud

Openstack in HTTPD URL Scheme

[Adam Young]

On 04/27/2012 06:21 PM, [e-mail] wrote:
> NameVirtualHost localhost?

We can use Virtual hosts to distinguish but that implies either  
separate ports or DNS support.  I'd like to stay away from multiple 
ports due to the SELinux port assignments clashing with the ones the 
OPenstack tends to use,  but named virtual hosts will work fine.
> -----Original Message-----
> *From: *Adam Young [[e-mail] ]
> *Sent: *Friday, April 27, 2012 04:36 PM Central Standard Time
> *To: *[e-mail]
> *Subject: *Re: Openstack in HTTPD URL Scheme
>
> On 04/27/2012 05:33 PM, Christian Berendt wrote:
> > Hello Adam.
> >
> > On 04/27/2012 11:25 PM, Adam Young wrote:
> > > #should this be keystone or identity?
> >
> > I would prefer using always the development name of the project, in
> > this case keystone.
> >
> > Regards, Christian.
>
> Thanks, Christian.  I suspect that will work better with documentation
> as well.
>
> Pete Zaitcev also has pointed out that Swift probably won't play nicely
> with this,  as the URL scheme is pretty much driven by Amazon, and it
> assumes a top level URL along the lines of
>
> http://test-1235163301.kvm-rei.zaitcev.lan/testdata
> https://s3.amazonaws.com/test-1235163301/testdata
> http://kvm-rei.zaitcev.lan/test-1235163301/testdata
>
> cloud mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/cloud

Openstack in HTTPD URL Scheme

[Daniel P. Berrange]

On Fri, Apr 27, 2012 at 07:46:48PM -0400, Adam Young wrote:
> On 04/27/2012 06:21 PM, [e-mail] wrote:
> > NameVirtualHost localhost?
>
> We can use Virtual hosts to distinguish but that implies either
> separate ports or DNS support.  I'd like to stay away from multiple
> ports due to the SELinux port assignments clashing with the ones the
> OPenstack tends to use,  but named virtual hosts will work fine.

Is HTTPS support for NamedVirtualHosts widespread enough these
days ? I know there have been issues with this in the past, and
even today it is much harder (and more expensive) to get x509
certs from real authorities for multi-hostnames / wildcards.

Daniel