Why opsman IP is hardcoded?!!

Question

Why opsman IP is hardcoded?!!

Closed this issue 7 years ago · 5 comments

https://github.com/pivotal-cf/pcf-pipelines/blob/f8e5b5793729278d9c9a5c13d2c8d4d9be4d640a/install-pcf/azure/terraform/c0-azure-base/ops_manager.tf#L16

Answer 1 · 2018-01-13T10:25:59.000Z

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

Answer 2 · 2018-01-17T17:48:15.000Z

Hi @kamoljan, thanks for this and your pull request. Prioritised for engineer review.

Answer 3 · 2018-01-25T20:04:57.000Z

@kamoljan Thanks for the issue. Do you have a use case to make this address configurable?

Answer 4 · 2018-01-26T00:27:15.000Z

@kcboyle yes.
You have params to configure IPs,
if you change it (e.g. from 192.168.0.0/20 to 10.0.0.0/20), the pipeline deployment will fail.

Also, we need this address spaces to be configurable to avoid IP clashing in vnet peering (Azure case) or VPN connections.

Answer 5 · 2018-02-07T21:05:01.000Z

Hi @kamoljan, thanks, the team's implemented a fix for the issue you have raised. We will be releasing pcf-pipelines v23.1 with this fix at some point soon. Thanks again.