So this is a quick guide on how I got Kubernetes installed and running on 5 nodes on a prototype SoPine clusterboard. This can also work on rock64's, pine64(+)/LTS or anything else really. I'm assuming you already know how to flash OS SD card images using your favourite host OS, and can configure a router, in particular assigning manual DHCP addresses to hosts.

This isn't step by step, and if you need clarification, then perhaps go learn about whatever it is first. This is not a beginner's guide.

Background:
I recently got the book "Kubernetes Up & Running" (KUAR) by Hightower, Burns & Beda from O'Reilly. It came out in September 2017 so it's fairly current, although with all tech books, there are some things already out of date.

I read the intro and chapter 1 - nice and informative.

Chapter 2 - "you may want to start expriementing" it suggested. Uhhm, yes. "You should use an online service offering" it advised. Uhmm, if I have to ... "If you're really want to set it up yourself ... appendix A has a guide" it revealed. I skipped the rest of Chapter 2 for now. Chapters 3 through Appendix A, I'll get back to later as well

NB* THIS IS SO FAR FROM PRODUCTION READY.

The steps that follow are a rough paraphrase of Appendix A in the KUAR book with a few changes (ie that out of date already stuff)

Step 1- Get hardware.

• Two or more sopines
  
• sopine clusterboard (cheats power cabling, network cabling (has built in  GigE ethernet switch), cable management and all the other hassles of DIY clusters)
  

• I used an armbian 5.37 BSP xenial server build, any xenial build should work but stick with the minimal builds as you won't need most of what's in minimal, nevermind anything else
  

• Rather than installing DHCP tools on the host node, I just plugged them in an booted each sopine up sequentially, and assinged them hosts sopine[0..4] and on my router gave them IP addresses nnn.nnn.nnn.200 through 204 (where n is whatever subnet used on your router. eg 192.168.1.200 or 10.10.10.200)
  
• The book assumes the cluster will be isolated and hidden from the world so there are some extra network forwarding steps and configs I completely ignored as the clusterboard has it's own switch directly connected to the 'net and all nodes can see the world. Again this is *not* a production ready setup, where you'd likely have one exposed node, and all your worker nodes hidden/protected in a vlan or simiar. (Have I mentioned this is *not* a production ready setup?)
  

• (optional) install cssh(X) - Cluster SSH lets you blow up numerous systems at once by ssh'ing into all of them simultaneously and running things all at once. Since I haven't bothered (yet) with config management to setup the sopines, this is even more efficient #BadDevOps than ssh'ing into them individually way of doing things. (Thank you Xalius for introducing this to me!) (csshX is the OSX brew version)
  
• install docker.io - this is the default container engine
  
• install kubernetes package encryption key:
  
  Code:

  curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
• Add repo to your repo's list
  
  Code:

  echo "deb http://apt.kubernetes.io/ kubernetes-xenial main" >> /etc/apt/sources.list.d/kubernetes.list
• Update and upgrade the nodes
  
• install actual kubernetes stuff
  
  Code:

  apt install -y kubelet kubeadm kubectl kubernetes-cni
• this installed version 1.9 on my sopines
  

• On the master node (sopine0 in my case) 
  
  Code:

  kubeadm init --pod-network-cidr 192.168.1.0/24 --apiserver-advertise-address 192.168.1.200
• Make sure to use the correct network range as you may not be using the same subnet as I. This will take a while. It will also generate the <token> you need to initialise the slave nodes and will actually print out the command for the slave nodes to join the cluster
  
• on the slave nodes (sopine[1..n])
  
  Code:

  kubeadm join --token=<token> 192.168.1.200:6443 --discovery-token-ca-cert-hash sha256:<hash>
• if it all played nice then to see your embryonic Kubernetes cluster details
  
  Code:

  kubectl get nodes

Hi folks, just doing some hunting around for information...

I note that the GPIO on the Rock64 is supposed to be capable of emulating Pi2.
I also note that some of the pins are not mapped the same way.

I was using a Pi2 with a Parallel RGB (DPI Mode 2) display. This makes use of pins 11, 29, and 31 which are all "NC" pins on the Rock64.

I am therefore assuming the Rock64 is incapable of interfacing with a RGB 16Bit 565 type display ?

Cheers
Ben

Hi guys,

First of: love the Rock64 so far, very happy running the ayufan Xenial minimal.

I was a bit hesistant about buying the Rock64 due to it being a relatively new device, but was convinced due to what seems like a vibrant user community being built here. The community pages proved to be very helpful in setting up the device, thanks for that!

I did a search in the forum on my specific issue and could not find a direct solution - apologies in advance if it turns out to be a rookie / easy mistake. I have working knowledge from tinkering with Linux over the past 15 years, but am definitely not an expert.

My setup:

- Rock 64 on the official power supply (running on a US to EU power converter however).

- Running Ayufan Xenial minimal on a 16GB micro SD card.

- Aukey USB powered hub: https://www.amazon.de/dp/B00QM89U4G/ref=...11_TE_dp_1

- Three Seagate Expansion Portable 4TB drives linked to the USB hub: https://www.amazon.de/dp/B017KE8OG0/ref=...11_TE_dp_1

- Very limited software installed (Docker, vsftp)

What happened:

I tried setting up my three external harddrives in RAID 0, following this tutorial:
https://forum.pine64.org/showthread.php?tid=5231

In the middle of the tutorial, the device crashed (no error message on screen through putty).

I connected the Rock64 to a monitor (figured at first there was a problem with the network connection) and saw it crashing in 'real time' (while I was not taking any user actions). I took a few pictures (attached to this post). I looked at syslog and the last error there is from a few hours before the crashed. Happy to post any other logs.

In essence, it seems there are a few read/write errors on my external disks and then the device crashed. I plugged out the USB hub and the crashing stopped, so the error is likely connected to the drives.

I took a good look at one of the overview forum posts (https://forum.pine64.org/showthread.php?tid=4760) and I think my issue might be linked to undervoltage. Is there any way to check that? I thought my powered HUB was strong enough to handle all three drives, but please correct me if I'm wrong.

Logs:





Any help appreciated!

Dear All,
 
I integrate the EMMC Driver(USDHC2) and PWM Backlight Driver
I want to test the EMMC Driver(USDHC2), PWM Backlight Driver and I want to check the result.
Please provide the user guide for EMMC Driver(USDHC2) and PWM Backlight Driver.
 
 
Regards,
VinothS

Hello, everyone!
Merry Christmas and Happy New Year!

I'm looking for a device for music streaming.
I'd like to output sound via HDMI port to my AVR.
Can anybody confirm, that HighRes and surround sound are output correctly using any of the supported distribution? Ubuntu/Debian, LibreELEC, Volumio?
Maybe someone can post outputs of aplay -l command, or even try to do speaker-test with different samplerates and channel numbers?
Does your AVR shows correct samplerate and channels? Are the channels mapped correctly?

I've tried such streaming using HDMI output of my HP ProBook 4530s with Ubuntu 16.04.
Installed upmpdcli and mpd and everything works as expected. AVR indicates correct sample rates and channel number with any source I throw to it. 44.1/48/88.2/96/176.4/192kHz, 2ch or 6ch.


I also have CubieBoard2 and Tanix TX5 Pro devices.
Both devices can only output 2 or 8ch, which is not perfect. I have to do channel assignments via asound.conf, and as a result sound is always output as 8ch.
RPi 3 cannot output anything higher, than 2ch/48kHz.

Rock64 is my last hope to have small small music network streaming device =)

Thanks for your help!

So it look like I have a failing module

   

They're in order from right to left 0 through 4, and sopine1 is running stupidly hot despite not doing anything as confirmed by the terminal screen cap. The outside modules are the coolest, while 2 and 3 are taking some extra heat.

   

Fans and forced air are on the way. Heatsinks are at the office, but sopine1 looks like it's toast (sic)

I recently purchased and am awaiting both a Pine64-LTS and a ROCK64, both with emmc modules. After purchasing, I realized that I had not purchased the emmc to usb adapter. This is my fault, but I have been looking into my options in the meantime.

Here is the information that I have gathered, though I may have gotten some things wrong(that is the first part of my question, and leads directly to the second.)

1. On the LTS, there are images I can write to SD, and then install to emmc.
2. These installers are not available on the ROCK(if they are, my question basically ends here, as I can install to emmc without needing to wait for the adapter.)

The second part of my question, which assumes #2 above is true, is whether I can put the emmc into the LTS, write a ROCK image, and just put the emmc into the ROCK?

Is the following LED panel compatible with the Pine A64+ 2 GB?


https://www.dfrobot.com/product-1644.html

I have been using my Pinebook just fine for several months and yesterday it did something odd. The screen appeared to have interference like you were looking at it thru a screen door. At the same time I noticed the current temp was missing from the clock area in the upper right (I am using the latest version of Mate). So I restarted it, but it never came back after the restart. I had been using it plugged in and the battery was over 70% charged when this happened.

I can long press the power button and force it off. I have powered it back on and the green power led comes on, it appears the back light to the screen comes on, but that's it, no Pinebook boot-up screen or anything. I thought maybe the install got hosed up so I tried to boot-up from MicroSD, but it won't do that either. I pulled the back off and disconnected the battery for a while, plugged it back in and same results. I tried this several times. Also I carefully re-seated the cable connectors on the mainboard and re-seated the EMMC itself.

I left it powered off and unplugged over night. Plugged it in this morning and the red led by the power connector came on for a while. After about 2 hours I tried to power it on and the same thing happened. It looks like it will be powering up as the back light for the screen comes on and the green led comes on. but nothing ever happens after that. No Pinebook boot-up screen or anything.

Did my Pinebook die?

Thanks in advance for the advice.

Hello,

I tested android 6.0 but hdmi output display still 1 min delayed. 
And I think it seem to be not stable.

So I tested android 5.1 and it works that I wanted.

Then I want to get android 5.1 PINE64-LTS source, but i could not find infomation about source of android 5.1(PINE64-LTS, SOPINE)

How to get & compile Android 5.1 for PINE64-LTS ?
(I want 1.1 stable version same as download image site "http://wiki.pine64.org/index.php/SOPINE_Software_Release#Android_5.1.1_.5B20160630.5D")

I visited "https://github.com/ayufan-pine64/android-5.1" but DEPRECATED