[
https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403909#comment-15403909
]
ASF GitHub Bot commented on JCLOUDS-207:
----------------------------------------
Github user drigodwin commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/98#discussion_r73148099
--- 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
--- End diff --
"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"
"Whilst there is eventual consistency for recording which VMs still
reference security groups, after deleting a VM, it can sometimes take several
minutes before the security group can be deleted"
> Key Pair and Security Groups created by jclouds are not removed when the node
> is destroyed (via Jclouds)
> --------------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-207
> URL: https://issues.apache.org/jira/browse/JCLOUDS-207
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.6.0
> Reporter: Eugen Paraschiv
> Labels: ec2
>
> Simply stated, the problem is that the nodes that are created in EC2 via
> jclouds leave a key-pair and a security group each, after they're deleted
> (also via jclouds).
> This issue is described in much more detail here:
> http://www.cloudsoftcorp.com/blog/tidying-up-after-jclouds/
> Hopefully it's an easy fix and the operation of first creating and then
> destroying the node will leave no unnecessary artifacts on the EC2 account.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
