On Tue, Sep 27, 2016, at 02:58 PM, Clark Boylan wrote: > Once multinode testing has tls-proxy enabled the next thing I think we > should be talking about is enabling this by default in devstack. As > mentioned before ironic doesn't work due to IPA images not trusting > glance's cert. Swift's functional tests don't currently work against > https keystone as they assume http as well. All this to say if you have > a devstack plugin or testing that depends on devstack now would be a > great time to turn on tls-proxy and see if your things work with it > (easy mode is depends-on 373219). I think that if we can identify places > where it doesn't work and fixing it would require a lot of effort we > should just proactively disable it in the jobs. That way we can turn it > on by default for the default vanilla case.
I forgot to mention here that devstack + tls-proxy + CentOS 7 is also non functional. Something about apache restarts and reloads is different here than on Fedora24, Ubuntu Trusty, and Ubuntu Xenial. Would be great if someone that knows a lot more about CentOS were to take a look at this. Clark __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
