[
https://issues.apache.org/jira/browse/WHIRR-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189158#comment-13189158
]
Evan Pollan commented on WHIRR-482:
-----------------------------------
I do -- when running whirr from the same machine (the steady-state production
case). In this case, we were running multiple instances of whirr on multiple
machines. The cluster name is baked into the default product config.
Normally, this name is tweaked if an additional whirr "controller" machine is
built and deployed for some test case, however this step was skipped in this
particular case.
Since the cluster name is baked into the cluster properties file, we elected to
leave a recognizable name latent in that file as it ships with the application.
This helps with EC2 instance recognition (since it appears there's no way to
effect an instance name assignment via whirr), and has the added benefit of
having the cluster reuse the named security group (in case the security group
has had out-of-band firewall rules modified on it).
I could easily modify my application to tack on some type of unique(ish) token
to the end of the cluster name to prevent this from happening, but it still
seems like relatively dangerous default behavior for whirr.
> destroy-cluster in EC2 terminates any instance belonging to the cluster's
> security group, even if it's not a member of the cluster
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WHIRR-482
> URL: https://issues.apache.org/jira/browse/WHIRR-482
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Evan Pollan
>
> I had three different whirr-created clusters running in EC2, 2 of which
> shared the same cluster name (and, thus, the same security group). They were
> all created from different machines -- i.e. the ~/.whirr/<cluster>/instances
> files were all on different instances. I invoked destroy-cluster from one of
> the "initiating" machines that had created one of the two identically named
> clusters, and the destruction process terminated all of the instances in the
> cluster "owned" by the machine running the destroy-cluster command, as well
> as all of the instances of the other cluster sharing that name.
> Since whirr writes an inventory of all the instances it creates to
> ~/.whirr/<cluster>/instances, shouldn't it use that manifest to drive it's
> instance termination behavior?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
