Evans, do the current commands work on all other operating systems, or does it need to be checked against other OSes, too? I am thinking we could use "systemctl status iptables" command to check whether iptables is running or not on CentOS, and "systemctl status firewalld" to check for firewalld - so we don't need to rely on the version number. But I'm not familiar with Ubuntu (I don't think it uses systemd?), so we could just run the current commands as default on all other OSes (if they indeed work everywhere else).
By the way, how do you guys (what is the best way) copy files to HDFS on your Vagrant-based VMs? Do you use Hue, do you use shared folders on the VM, any other method? --David On Mon, Nov 23, 2015 at 4:11 AM, Evans Ye <[email protected]> wrote: > Hi David, > > Nothing special we deal with the firewall issue. We just turn it off. > You can find the following shell code in vagrant-puppet-vm/Vagrantfile: > > 69 service iptables stop > 70 chkconfig iptables off > > We don't do firewall setting in Puppet because that's much more related to > infrastructure instead of Hadoop. > If you have managed firewall device across the whole DC, then we don't > need iptables. > > Now, for the patch, It seems that we need to determine the OS before > taking action. > I suggest you refer to bigtop/bigtop_toolchain/bin/puppetize.sh, which did > a great job on that. > > Evans > > > 2015-11-23 5:06 GMT+08:00 David Starina <[email protected]>: > >> Thank you! I updated the wiki for now, until we fix this. >> >> --David >> >> On Sun, Nov 22, 2015 at 9:10 PM, Konstantin Boudnik <[email protected]> >> wrote: >> >>> On Sun, Nov 22, 2015 at 09:06PM, David Starina wrote: >>> > I don't think I have the right to edit the wiki. >>> >>> Please send me your wiki account name I will fix the permissions. >>> >>> > What would the patch do? I'm not familiar with the way Vagrant and >>> Puppet >>> > work together, so I'm mostly guessing, please correct me if I'm wrong >>> ... >>> > I'm guessing simply disabling the firewall won't do - it would be fine >>> for >>> > running a Vagrant box, but Vagrant is using Puppet to configure stuff, >>> and >>> > the same Puppet configurations are used to set physical machines (this >>> is >>> > all guessing). So the patch would require to correctly configure >>> firewall >>> > (not turn it off :-) via Puppet configuration (still guessing). >>> >>> I will leave this to Evans to address, as I like yourself aren't prolific >>> enough with this framework. >>> >>> Cos >>> >>> > On Sun, Nov 22, 2015 at 6:06 PM, Konstantin Boudnik <[email protected]> >>> wrote: >>> > >>> > > Either way: wiki update or opening a JIRA snd submitting a patch as >>> Evans >>> > > suggested. Perhaps the latter is even better considering that it >>> fixes the >>> > > issue instead of just describing it. >>> > > >>> > > Regards, >>> > > Cos >>> >> >> >
