right now, withExistingVMs assumes a default backend to be created as needed at creation time or associates the VMs with the first backend found on the LB. This was the initial tentative logic. The proper way to do this though, now that backend infrastructure is supported is for each withExistingVMs call to create a separate backend right away for that set of VMs and remove the guesswork at creation time.
This also means an overload for withExistingVMs is needed that optionally takes a name for the new backend.
right now, withExistingVMs assumes a default backend to be created as needed at creation time or associates the VMs with the first backend found on the LB. This was the initial tentative logic. The proper way to do this though, now that backend infrastructure is supported is for each withExistingVMs call to create a separate backend right away for that set of VMs and remove the guesswork at creation time.
This also means an overload for withExistingVMs is needed that optionally takes a name for the new backend.