Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subnet CIDR customization in Schematics #14

Open
sam-andaluri opened this issue Dec 22, 2022 · 2 comments
Open

Subnet CIDR customization in Schematics #14

sam-andaluri opened this issue Dec 22, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@sam-andaluri
Copy link

The subnet CIDR defaults to VPC default which creates a new CIDR block of /18 for each zone. So I cannot install 2 LSF clusters in the same zone Or I if my on-prem network had the same CIDR as LSF default then the overlap would not allow me to connect them together.

ibm_is_subnet module uses VPC default but the module allows specifying a custom CIDR. It wouldn't be difficult to expose or accept a custom CIDR via terraform variables such Schematics can pick up and let customer choose default or a custom CIDR.

@AugieMena3
Copy link
Contributor

hi @sam-andaluri yes, we acknowledge that the CIDR block overlap issue when trying to establish communication between LSF clusters needs to be addressed. We will look at allowing the user to specify a custom CIDR in a future release. Thanks for taking the time to provide this feedback.

@AugieMena3 AugieMena3 added the enhancement New feature or request label Aug 1, 2023
@AugieMena3
Copy link
Contributor

The capability to specify a custom CIDR has been implemented in our Symphony solution: https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-deployment-values. However, it still needs to be implemented in the LSF solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants