Earlier quoted context omitted.
Simply for not having to deal with all the usb-c adaptors and cables. It's also pretty cool being able to turn the pis on or off by cycling the switch port from your network control plane (Unifi in my case) You could even do it dynamically via the api for a "bare-metal autoscaling" type workflow.
> Simply for not having to deal with all the usb-c adaptors and cables. You can get one large 5V PSU and go directly to the pins on the Pi. No need to bother with individual USB adaptors...
Turing Pi: Kubernetes Cluster on Your Desk
61–65 of 65 posts
Re: Turing Pi: Kubernetes Cluster on Your Desk
#62Earlier quoted context omitted.
Yes, a single ryzen node running multiple VMs.
So, you don't see a difference between clustering on physically separated nodes and VM?
I think it's far more realistic to choose a hypervisor (KVM, raise the roof) install it and configure it, run N virtual machines on a single machine, provisioning and slicing the hardware, setting up and managing the network between them, having disks run in a raid so the VMs don't starve for I/O and data is replicated, and then running kubernetes (or whatever personal hell you want) within your "virtual cluster." That's the whole "running a cluster" part all of these Pi Kubernetes things miss because they're running on consumer grade hardware.
Your hosting provider is surely not using thousands of small under-powered machines running bare metal installs of your applications.
Want to find out how resilient your cluster is? Just fucking kill one of the VMs. Boom. Instant feedback. Now try that with a PI, you'll have to unplug it, and then wait five minutes for it to boot. It becomes tedious fast.
Clustering and distributed systems are extremely complex and difficult... just having physical machines doesn't really even begin to scratch that problems you'll face, just my two cents.
Re: Turing Pi: Kubernetes Cluster on Your Desk
#63The main idea behind Turing Pi is to deliver compute to the edge. If we look at cases where some compute will run low latency, highly available and internet independent apps to automate processes, and often in a hard to reach places, then the classic servers, not a solution. Turing Pi is an early version of edge computers with cloud-native architecture. Why it's important? Because if you are a business with some services running in the cloud and you want your edge computing organically to coexist with your cloud stack, then edge clusters could be a great choice. The speed to innovate and deploy your code into production to both cloud and the edge environment could be a critical component.
The existing Turing Pi model more oriented at forward-thinking developers who want to learn and push cloud-native to the edge. Why Raspberry Pi computers? They are not the most powerful computers, but they definitely can lower the entry point for developers by offering a huge and well-documented software ecosystem.
Re: Turing Pi: Kubernetes Cluster on Your Desk
#64There is also the https://www.pine64.org/clusterboard/ for $99 which takes these modules https://www.pine64.org/sopine/ at $29 a piece, which are quad-core ARM Cortex A53 with 2GB LPDDR3. This is their wiki: https://wiki.pine64.org/index.php/PINE_A64-LTS/SOPine
Re: Turing Pi: Kubernetes Cluster on Your Desk
#65There is also the https://www.pine64.org/clusterboard/ for $99 which takes these modules https://www.pine64.org/sopine/ at $29 a piece, which are quad-core ARM Cortex A53 with 2GB LPDDR3. This is their wiki: https://wiki.pine64.org/index.php/PINE_A64-LTS/SOPine
75W 5v bricks can't be that easy to come by were as 12 or even 19v we're usually tripping over.