VPC subnet definitions are overly restrictive about hpc-toolkit HOT 4 CLOSED

@brandenm-nag For now, I am confirming receipt of this issue report. I have a few suggestions that I think will be more effective for more "arbitrary" configurations but I want to test them before suggesting them. We are about to make a release and the features I want to suggest are new and do not yet have proper examples. I will report more later this week.

from hpc-toolkit.

Our plan is to fully expose all the settings in the Cloud Foundation Toolkit subnets module after v1.0 release of the Toolkit. i.e. have an input parameter to this module, probably named subnets, which has the same structure as the subnets parameter in the module linked above. This is already very nearly true, with the exception of CIDR ranges.

For users who do want to think about CIDR ranges, we will continue to enable the current behavior of providing the most compact set of subnets for a given number of desired IP addresses.

We will probably also enable more flexible firewall rule specification than is currently enabled.

from hpc-toolkit.

For record: we are designing a backwards-compatible solution for this extra functionality and have the implementation work planned as a high priority for the 1.x series of the Toolkit. We will update the schedule as we make progress.

from hpc-toolkit.

This has been incorporated on the develop branch of the HPC Toolkit and will be included in our next tagged release. Please see #392 for details.

We will leave this issue open until the fix is in a tagged release.

from hpc-toolkit.