This is a followup from T419996: cloudcumin not able to communicate with openstack.eqiad1.wikimediacloud.org:25000 anymore to enhance cumin's openstack backend to be able to use an http proxy to talk to the openstack APIs. Note that the proxy in this case will apply to the openstack backend, as cumin already supports having a proxy for all requests.
Description
Details
Related Objects
Event Timeline
Change #1260082 had a related patch set uploaded (by Volans; author: Volans):
[operations/software/cumin@master] openstack backend: add support for a proxy
Change #1260082 merged by jenkins-bot:
[operations/software/cumin@master] openstack backend: add support for a proxy
Change #1266885 had a related patch set uploaded (by Volans; author: Volans):
[operations/puppet@production] webproxies: allow cloudcumin to openstack
Change #1266885 merged by Volans:
[operations/puppet@production] webproxies: allow cloudcumin to openstack
Change #1266956 had a related patch set uploaded (by Volans; author: Volans):
[operations/puppet@production] cumin: use webproxy to connect to openstack APIs
Change #1266963 had a related patch set uploaded (by Volans; author: Volans):
[operations/homer/public@master] Revert "cr-cloud: allow cumin/cloudcumin traffic"
Change #1266956 merged by Volans:
[operations/puppet@production] cumin: use webproxy to connect to openstack APIs
Change #1266963 merged by jenkins-bot:
[operations/homer/public@master] Revert "cr-cloud: allow cumin/cloudcumin traffic"
The cloudcumin hosts are now using the webproxies to connect to the openstack APIs and the firewall rule has been reverted. Resolving.