We have too many variables to describe the same thing:

• SUBNET_RANGE
• MACHINES_SUBNET_v4_RANGE
• and MACHINES_SUBNET_RANGE that we pass via the ${SHARED_DIR}

They're all only used on openstack platform, so I propose that we make things consistent.

If we need a different subnet range for the dualstack job, we should pass it as a variable via the job definition like we do for example here.

If we need a different machine subnet because of the cloud where the job runs, we should instead consider make it part of openstack-conf-resourcenames-commands.sh.