Does Galaxy need multi-regionality? about cloudbridge

[afgane]

To make the behavior of default_zone more explicit, let's require the default_zone parameter when creating a Google provider in CloudBridge.

[afgane]

Nuwan and I had a chat about this just now and feel that a better solution would be to keep the interface as is; namely, require the zone to be supplied as a parameter when creating a Subnet. Then, internal to the GCE provider, the region to which the supplied zone belongs to can be extracted and used in the request. For example, OpenStack implementation adheres to the interface but simply ignores the zone argument.

Another point that came up while looking at this is use of provider.default_zone in several places in the GCE implementation (e.g., instance reboot method). Using default_zone in methods that don't create resources, including the provider should be removed. This is because if, for example, a zone was specified when creating an instance yet that zone is different from the default_zone, the query won't work as expected. Instead, the resource zone should be extracted from the selfLink.
The only place this won't work right away is in the InstanceTypeService, instance_data method because there is no local resource object. Instead, it looks like using aggregatedList method instead of the list method would do the trick and not require a zone to be specified.

[afgane]

I just looked at the use of default_zone throughout the GCE implementation and I think the issue we identified in the previous comment has been corrected at this point. I feel the only potential issue with the use of that parameter may come up in the Snapshot.create method where the snapshot is being created in the default_zone. Instead, maybe we should be creating it in the volume.zone_id zone. And it's a big maybe (as in probably not) because the volumes.list method will return only the volumes from the current default region so in principle a given CloudBridge session should not even see the volumes outside the default_zone.

Unless I'm missing something here, I move we close this issue.