Ok, an little update on the PiZero Cluster Front:
\nNow, that OTG is compiled directly into the \"next\" kernel of RPi, we can use the OTG USB Virtual Ethernet directly - which makes it a lot easier. So I updated this :).<\/p>\n
0. Preparing Minibian Jessie Image apt-get install -y rpi-update sudo rpi-update # Create Default User pi # Disable root login or - and default RPi Jessie Image.<\/p>\n 1. Building mpich 3 # Make MPICH 3.2 # Create SSH on Master, distribute to Slaves 2. PiZero on Virtual Ethernet # This is required in the config.txt # Regarding the readme this is applied automatically for a pi zero (and yes it works without) - so not really needed # Only use this, if the new kernel causes sd card errors # permanently add the g_ether (or any other) module, add it to \/etc\/modules # Add settings to network interfaces # Some additional tweaks: # Turn HDMI Off # Turn ACT LED Off on Pi Zero to your \/etc\/rc.local before exit 0 to turn off the HDMI Interface on boot, This was enough to create an Pi Zero Slave Image. On the Master Machine, I did following changes: # Allow Ipv4 Forward # Install iptables # Define NATing rules # Save NAT rules \/ load iptables on interface up Add #After that, I shutdown the RPi via Then I attached the Pi Zero to the Hub of Pi B via an Micro USB Cable by using the Micro USB OTG Slot on the Pi Zero, connecting it to the Hub of the Pi Modell B. Next, I powered up the Pi B - and both booted.<\/p>\n I pinged 192.168.7.2 - which was the IP of the Pi Zero - and it answered. Now I only had to use cat ~\/.ssh\/id_rsa.pub | ssh pi@192.168.7.2 \"mkdir .ssh;cat >> .ssh\/authorized_keys\" from Section 0 to get the SSH Key, created in Step 0 onto the Pi Zero and could use that to automatically login in into the Pi Zero. Now, I need to get more Pi Zeros - I plan on using an Modell B as Master with an big active USB Hub to support 4 Pi Zeros - or an Modell B+ with an REALLY BEFFY USB Supply to work them all the same RPi - but that would come down to trying this... And I got only one Pi Zero - so I need some more time (or some sponsors?) to get me more RPi Zeros to try and see, whether this approach does scale ;)!<\/p>\n Best thing: This can also be used to try the awesome work of http:\/\/blog.hypriot.com<\/a>\/ to build an Docker Cluster from that - cool, ain't it?<\/p>\n
\nI used some old Appliance Image I created from an Minibian Wheezy Image (https:\/\/minibianpi.wordpress.com\/<\/a>) earlier this year - for the 1.) section on the RPi Modell B pre 2.0 and RPi Modell A+. For the 2.) section, I used an special Appliance Image I made from an Minibian Jessie Image. However, I will document needed changes here, to get it running from any source. I recommend the Minibian Jessie Image as starting point, with this changes:<\/p>\n
\napt-get update
\napt-get install -y raspi-config keyboard-configuration
\nraspi-config
\n# Default Configuration and Expand Filesystem using raspi-config
\n# Enter Finish and press Yes on Reboot the Device<\/p>\n
\napt-get -y dist-upgrade
\nreboot<\/p>\n
\nreboot<\/p>\n
\nadduser pi
\n# Enter Password as wanted, i.e. raspberry
\n# Add user to default groups
\nusermod -a -G pi,adm,dialout,cdrom,audio,video,plugdev,games,users pi
\n# Add sbin Paths to pi
\necho 'export PATH=\"$PATH:\/sbin:\/usr\/sbin:usr\/local\/sbin\"' >> \/home\/pi\/.bashrc
\n# Add user to sudo
\nvisudo
\n# Add under
\n# # User privilege specification
\n# root ALL=(ALL:ALL) ALL
\npi ALL=(ALL:ALL) ALL
\n# Save and Exit
\nreboot<\/p>\n
\nsudo passwd -l root
\n<\/code><\/p>\n
\n
\n# Update and Install Dependencies, then reboot
\nsudo apt-get update
\nsudo apt-get -y dist-upgrade
\nsudo apt-get install -y build-essential
\nsudo reboot<\/p>\n
\ncd ~
\nwget http:\/\/www.mpich.org\/static\/downloads\/3.2\/mpich-3.2.tar.gz
\ntar -xvzf mpich-3.2.tar.gz
\ncd mpich-3.2
\n# This will take some time
\nsudo .\/configure --disable-fortran
\n# This will take several cups of tea ;)
\nsudo make
\nsudo make install
\n<\/code><\/p>\n
\n
\ncd ~
\nssh-keygen -t rsa \u2013C \"raspberrypi\"
\n<\/code>
\nDefault location should be set to \/home\/pi\/.ssh\/id_rsa if you're using the standard user pi. Then choose this command to distribute the key to all your \"slave maschines\":
\ncat ~\/.ssh\/id_rsa.pub | ssh pi@IP_OF_SLAVES \"mkdir .ssh;cat >> .ssh\/authorized_keys\"
\n( Was taken from http:\/\/www.southampton.ac.uk\/~sjc\/raspberrypi\/<\/a> - he was the original father of the RPi Clusters and his work inspired me already years ago - so please read and support his work :)! Additional infos can be found at http:\/\/westcoastlabs.blogspot.co.uk\/2012\/06\/parallel-processing-on-pi-bramble.html<\/a>)
\nYou could also just
\ncat ~\/.ssh\/id_rsa.pub >> ~\/.ssh\/authorized_keys
\nto your own authorized files, shutdown your Master Pi after that and clone the card several times for all your Clients. This way, you would only need to do the work once - however, maybe you should release the keys in ~\/.ssh\/ so that only your Master Pi could command the slaves<\/p>\n
\nI build my MPICH as mentioned in 1) on an Minibian Jessie image (SDCard running on an RPi B). Then I installed the new RPi Kernel and prepared the image for OTG Ethernet, using the new information provided by NicoHood<\/a>:<\/p>\n
\n#install new kernel with OTG support
\nsudo BRANCH=next rpi-update<\/p>\n
\necho \"device_tree=bcm2708-rpi-zero.dtb\" | sudo tee -a \/boot\/config.txt<\/p>\n
\n# echo \"dtoverlay=dwc2\" | sudo tee -a \/boot\/config.txt<\/p>\n
\n# echo \"dtoverlay=mmc\" | sudo tee -a \/boot\/config.txt<\/p>\n
\necho \"dwc2\" | sudo tee -a \/etc\/modules
\necho \"g_ether\" | sudo tee -a \/etc\/modules<\/p>\n
\necho '
\nallow-hotplug usb0
\niface usb0 inet static
\naddress 192.168.7.2
\nnetmask 255.255.255.0
\nnetwork 192.168.7.0
\nbroadcast 192.168.7.255
\ngateway 192.168.7.1
\ndns-nameservers 8.8.8.8' | sudo tee --append \/etc\/network\/interfaces<\/p>\n
\nAdd<\/p>\n
\n\/usr\/bin\/tvservice -o
\n# Turn HDMI Back On
\n#\/usr\/bin\/tvservice -p<\/p>\n
\necho none | tee \/sys\/class\/leds\/led0\/trigger
\necho 1 | tee \/sys\/class\/leds\/led0\/brightness
\n<\/code><\/p>\n
\nas well as the LED of the Pi Zero to use less energy. Found on:
\nhttp:\/\/www.midwesternmac.com\/blogs\/jeff-geerling\/raspberry-pi-zero-conserve-energy<\/a> and http:\/\/www.midwesternmac.com\/blogs\/jeff-geerling\/controlling-pwr-act-leds-raspberry-pi<\/a><\/p>\n
\nShutdown the RPi now with
\n
\nsudo shutdown -h now
\n<\/code>
\nremove the Power and insert the SDcard into your Pi Zero.<\/p>\n
\n
\n# Add settings to network interfaces
\necho '
\nallow-hotplug usb0
\niface usb0 inet static
\naddress 192.168.7.1
\nnetmask 255.255.255.0
\nnetwork 192.168.7.0
\nbroadcast 192.168.7.255' | sudo tee --append \/etc\/network\/interfaces<\/p>\n
\necho 'net.ipv4.ip_forward=1' | sudo tee --append \/etc\/sysctl.conf<\/p>\n
\nsudo apt-get install -y iptables<\/p>\n
\nsudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
\nsudo iptables -A FORWARD -i eth0 -o usb0 -m state --state RELATED,ESTABLISHED -j ACCEPT
\nsudo iptables -A FORWARD -i usb0 -o eth0 -j ACCEPT<\/p>\n
\nsudo touch \/etc\/iptables_masq.rules
\nsudo chown pi:pi \/etc\/iptables_masq.rules
\nsudo iptables-save > \/etc\/iptables_masq.rules<\/p>\n
\npre-up iptables-restore < \/etc\/iptables_masq.rules\nunder the eth0 section in the network interfaces\n\nsudo vi \/etc\/network\/interfaces\n\ni.e.\nauto eth0\niface eth0 inet dhcp\n pre-up iptables-restore < \/etc\/iptables_masq.rules\n\n( Info taken from: http:\/\/serverfault.com\/questions\/405628\/routing-traffic-on-ubuntu-to-give-raspberry-pi-internet-access<\/a> ) <\/p>\n
\nsudo shutdown -h now
\n#removed power from it.
\n<\/code><\/p>\n
\nWith the new IP of the RPi B and Pi Zero in the machinefile of mpich I could then use my both RPis with higher speed and nearly zero costs for cabeling and power :)!
\nThe clou: I don't need an additional powersupply for the Pi Zero - nor network adapters, RJ45 cabling, an switch - only one USB A to USB Micro cable per Pi Zero - and maybe an big, active USB Hub ;)!<\/p>\n