Now the production is "isolated" behind the firewall, all the services are not directly accessible for the VPN environments.
The team needs access to the production services to test the behavior of the developments with real data.
What is needed :
for staging and production networks, access to
Network
| services | staging | production |
|---|---|---|
| read-only storage | [x] webapp.internal.staging.swh.network:5002 [1] | [x] webapp1:5002 / [x] moma:5002 |
| read-only indexer_storage [2] | [x] storage1.internal.staging.swh.network:5007 | [x] saam:5007 |
| read-only-search [2] | [x] webapp.internal.staging.swh.network:5010 [1] | [x] webapp1:5010 / [x] moma:5010 |
| read-only-scheduler [2] | [x] scheduler0.internal.staging.swh.network:5008 | [x] saatchi:5008 |
| graph backend [3] | N/A | graph.internal.softwareheritage.org:5009 |
[1] The service is not deployed on this environment and needs to be configured
[2] There is no existing read-only mode for this module. To not slow down the team, the access will be opened as before the network migration until a read-only mode is developed
[3] The main instance is read-only. No staging instance available.