Skip to content

Open redis access so the counters pods can access the redis backend

Antoine R. Dumont requested to merge open-redis-access into production

Redis is currently listening on 127.0.0.1 because services are running on that node. Services are currently getting migrated to pod in staging. But they will need access to this redis backend which will stay on that node. So open access so they can communicate.

This keeps the 127.0.0.1 address access too.

swh-octodiff counters0.staging 
*** Running octocatalog-diff on host counters0.internal.staging.swh.network
I, [2023-12-11T15:33:40.538192 #2953308]  INFO -- : Catalogs compiled for counters0.internal.staging.swh.network
I, [2023-12-11T15:33:40.917351 #2953308]  INFO -- : Diffs computed for counters0.internal.staging.swh.network
diff origin/production/counters0.internal.staging.swh.network current/counters0.internal.staging.swh.network
*******************************************
  File[/etc/redis/redis.conf.puppet] =>
   parameters =>
     content =>
      @@ -56,5 +56,5 @@
       # It is possible to listen to just one or multiple selected interfaces using
       # the "bind" configuration directive, followed by one or more IP addresses.
      -bind 127.0.0.1
      +bind 127.0.0.1 192.168.130.95
      _
       # Specify the path for the unix socket that will be used to listen for
*******************************************
  Redis::Instance[default] =>
   parameters =>
     bind =>
      - 127.0.0.1
      + ["127.0.0.1", "192.168.130.95"]
*******************************************
*** End octocatalog-diff on counters0.internal.staging.swh.network

Refs. swh/infra/sysadm-environment#5179 (closed)

Edited by Antoine R. Dumont

Merge request reports