andreaturli commented on this pull request.


>           } catch (Exception ex) {
             logger.warn(ex, "Error cleaning up resources for node %s", 
deadNode);
          }
+
+         List<SecurityGroup> securityGroups = 
cleanupResources.findOrphanedSecurityGroups(regionAndId.regionId(), 
deadNode.getGroup());
+         for (SecurityGroup securityGroup : securityGroups) {
+            logger.debug(">> destroying security group %s ...", 
securityGroup.id());
+            if 
(cleanupResources.cleanupSecurityGroupIfOrphaned(regionAndId.regionId(), 
securityGroup.id())) {
+               logger.debug(">> security group: (%s) has been deleted.", 
securityGroup.id());
+            } else {
+               logger.warn(">> security group: (%s) has not been deleted.", 
securityGroup.id());
+            }
+         }
+
+         // FIXME not sure it is correct to always delete vSwitch and VPC

flaky, indeed!

>From the doc:
- costs: I think it's usage is for free
- Maximum number of VPCs per region: 10 (Submit a ticket to apply for more 
quota)
- other concerns: although fast, creating/destroying VPC adds a delay, but not 
crucial





-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/443#discussion_r208855282

Reply via email to