[ 
https://issues.apache.org/jira/browse/WHIRR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Bayer updated WHIRR-120:
-------------------------------

    Attachment: WHIRR-120.patch

Second draft of patch - I switched to always using iptables and security 
groups, rather than having a flag, and I also added a few other tweaks:
- Storing every ip and hostname in the cluster in /etc/hosts on each host in 
the cluster - this is particularly needed with GoGrid, as their 
reverse-resolved hostnames for their public IPs all actually resolve to/are 
aliases for www.gogrid.com, so...yeah, that's problematic. I actually had to 
add all my GoGrid IPs to my own /etc/hosts to get tests working. Fun! But I 
can't imagine this causing problems elsewhere - in fact, it may well clean up a 
number of problems.
- Adding iptables rules to allow each (public and private) IP in the cluster 
full access to every other host in the cluster. This is needed because on EC2, 
security groups allow traffic between the hosts in the security group, but when 
we're stuck in iptables-land, we don't have that. So here we're emulating it.
                
> 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
>
>   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

Reply via email to