jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-207) Key Pair and Security Groups created by jclouds are not removed when the node is destroyed (via Jclouds)
Date Tue, 02 Aug 2016 21:12:20 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404801#comment-15404801
] 

ASF GitHub Bot commented on JCLOUDS-207:
----------------------------------------

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

    https://github.com/apache/brooklyn-docs/pull/98#discussion_r73238552
  
    --- 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
    --- End diff --
    
    "...prevents the security group *+from* being 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)

Mime
View raw message