Github user mikezaccardo commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/98#discussion_r73239082
--- Diff: guide/ops/locations/_AWS.md ---
@@ -111,3 +125,15 @@ You can then deploy blueprints to the subnet, allowing
VPC hardware instance typ
by specifying the subnet ID as the `networkName` in your YAML blueprint.
This is covered in the previous section, "Using Subnets".
+
+### Tidying up after jclouds
+
+Security groups are not always deleted by jclouds. This is due to a
limitation in AWS (see
+https://issues.apache.org/jira/browse/JCLOUDS-207). In brief, AWS prevents
the security group
+being deleted until there are no VMs using it. However, there is eventual
consistency for
+recording which VMs still reference those security groups: after deleting
the VM, it can sometimes
+take several minutes before the security group can be deleted. jclouds
retries for 3 seconds, but
+does not block for longer.
+
+There is utility written by Cloudsoft for deleting these unused resources:
+http://www.cloudsoftcorp.com/blog/2013/03/tidying-up-after-jclouds.
--- End diff --
Does that mean we've lost all blog posts before
[http://www.cloudsoft.io/blog/2015/01/gitlab-flow-ftw]?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
