[
https://issues.apache.org/jira/browse/WHIRR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453313#comment-13453313
]
Andrew Bayer commented on WHIRR-120:
------------------------------------
Ok, so I should have run the unit tests first. =) A number of tests are
expecting nothing to be run in the configure phase other than what's explicitly
specified, so I'm moving the iptables-for-cluster logic behind the same flag as
adding all the cluster hosts to /etc/hosts - we'll still do iptables for
explicit firewall rules, but not for the security group-internal emulation
unless it's requested (via the /etc/hosts flag).
> support deployment to the GoGrid cloud
> --------------------------------------
>
> Key: WHIRR-120
> URL: https://issues.apache.org/jira/browse/WHIRR-120
> Project: Whirr
> Issue Type: New Feature
> Components: new provider
> Affects Versions: 0.3.0
> Reporter: Adrian Cole
> Assignee: Andrew Bayer
> Attachments: WHIRR-120.patch, WHIRR-120.patch, WHIRR-120.patch,
> WHIRR-120.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> GoGrid is supported in jclouds as the "gogrid" provider. Support should be
> fairly straightforward with the exception that we'll need to manipulate
> iptables to expose services like hadoop.
> Here's an example of a iptables rule that works in gogrid, and authorizes
> port 8080:
> iptables -I RH-Firewall-1-INPUT 1 -p tcp --dport 8080 -j ACCEPT
> iptables-save
--
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
