Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: drigodwin <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-98-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-98-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #98: Improve location docs
Content-Type: text/plain
Message-Id: <20160802125209.8A3BCE0007@git1-us-west.apache.org>
Date: Tue,  2 Aug 2016 12:52:09 +0000 (UTC)
archived-at: Tue, 02 Aug 2016 12:52:11 -0000

Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/98#discussion_r73148373
  
    --- 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 --
    
    This URL is no longer valid


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---