[
https://issues.apache.org/jira/browse/WHIRR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667149#comment-13667149
]
Andrew Bayer commented on WHIRR-725:
------------------------------------
Oooooh yeah, now I remember: since jclouds currently doesn't have an
API-agnostic interface for managing security groups (though it really should,
and that is on my plate to implement), we have special casing for ec2 and
OpenStack security groups in Whirr - see
https://github.com/apache/whirr/blob/trunk/core/src/main/java/org/apache/whirr/service/FirewallManager.java#L284.
It shouldn't be hard to add CloudStack support at all - I'll have a patch up
today or tomorrow.
> Security Group rules don't get created on CloudStack 4.0.2 provider
> -------------------------------------------------------------------
>
> Key: WHIRR-725
> URL: https://issues.apache.org/jira/browse/WHIRR-725
> Project: Whirr
> Issue Type: Bug
> Components: new provider, service/hadoop
> Affects Versions: 0.8.2
> Environment: Running Whirr 0.8.2 on OSX 10.8.2, compiled from source.
> Using a cloudstack 4.0.2 cloud.
> Reporter: sebastien goasguen
>
> Trying to deploy a cdh cluster, the instances start, nodes get configured.
> But the security groups rules don't get created/added to the SG. No errors in
> the whirr.log file.
> Adding the rules by hand, out of band from whirr fixes the issue. Instances
> get a working hadoop (at least hadoop fs -ls / works).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
