hi @danbroudy I think it is still an issue. Basically the current code creates too many (identical) firewalls if I deploy multiple VMs in the same network. In fact, if the I ask for 10 nodes with specific inboundPorts, multiple firewalls with the same rules are created inside the network for the group of nodes.
This PR was an attempt to reduce the creation of the firewalls, given that there is a quota on that resource. In particular, FirewallTagNamingConvention doesn't look terribly helpful here and the PR was replacing it with templateOptions.getNetworkName(), falling back to the group name if that is empty. Please give us your thoughts on that, if you have a better idea. Thanks --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/20#issuecomment-67072020
