| 2015-10-02 07:26:41 |
Peter Sabaini |
description |
In bug #1398182 the ability to set the hostname portion of public Openstack service endpoints was added. However, it is a) not possible to choose the scheme (http / https) and b) not possible to choose the service port for those endpoints
a) implies that in order to set a public frontend with https, I now also have to set up ssl for the internal urls -- this may not always be desirable or even possible. Moreover for this to work I now need two different ssl certs, one for internal and one for external use.
b) implies that I have to use the same ports internally and externally; given firewalling / filtering requirements of clients this may not always be possible. |
[update: the scheme part is being worked on in bug #1500635]
In bug #1398182 the ability to set the hostname portion of public Openstack service endpoints was added. However, it is a) not possible to choose the scheme (http / https) and b) not possible to choose the service port for those endpoints
a) implies that in order to set a public frontend with https, I now also have to set up ssl for the internal urls -- this may not always be desirable or even possible. Moreover for this to work I now need two different ssl certs, one for internal and one for external use.
b) implies that I have to use the same ports internally and externally; given firewalling / filtering requirements of clients this may not always be possible. |
|
