lanefu

Those are totally awesome... The data sheets don't have enough information about the networking. Does the built in switch support LAG/LACP and VLAN trunking?

The firefly servers are quite ideal... although upfront cost is a little rough. TV boxes is a little too inelegant. My proposal lets you just have 1 wire into the board, and let you expand slowly.

I had to try 🤓

yeah just not enough gusto with A64 module... kind of DOA if you ask me... If they had an updated module it would be worth taking a look at... Would also be constraints by the single gigabit interface to the cluster board itself and the rest of your compute. When building out a big cluster of SBCs.. having POE is a HUGE win for cable management and sanity.... also you can reboot by just killing POE on the switch... https://dev.to/awwsmm/building-a-raspberry-pi-hadoop-spark-cluster-8b2#hardware N2+ is definitely top dog for brute force crunching. But just probably not the ideal device for purchasing and installing many. The RockPi 4C is probably the closest thing to ideal. As it supports a PoE HAT an EMMC. Would be nice to get the price point down by eliminating extra ports, and having POE and EMMC onboard.

I was trying to keep the Bill of Materials low but yeah a header or breakout or whatevs would be cool.

Suggestion for a (near future) product. We're still lacking a good SBC out in the wild for small clusters.. Recent SoC performance is good.. Currently all the homelab and k8s nerds are just using RPI4s because they have a header for POE support. We know there are better options. We had pitched this to orange pi but weren't receptive. Just sharing my idea here. A Lean SBC exclusively for server tasks. "The Ultimate Homelab SBC" Real 802.11at POE+ means only 1 cable for your compute node Use SPI flash for custom provisioning configuration Optimized for Compute "Ready for clustering and kubernetes" Has the Performance and Storage you need to easily deploy for clustered computing Suggested Reference Specs RK3399K or similar performant SoC Gigabit Ethernet 4G Dual Channel LPDDR4 16-32gig EMMC SPI flash 128mbit/16megabyte No Wifi No bluetooth No audio No CSI No HDMI USB 3 802.11af/at support or support for RPI4 style 6 pin POE hat All Ports in rear? holes for additional heatsink mounting options

@JMCC It's turtles all the way down for this https://statusgator.com/services/uptime-robot

https://status.uptimerobot.com lol

We have a realtime status page for primary Armbian web resources available here: https://status.armbian.com

Fair point

You should be able to enable the watchdog in systemd by uncommenting some lines in /etc/systemd/system.conf

Well we have a big arm server already configured as a github runner. I suppose we could chroot an armbian rootfs or place in a container So i guess something that can test armbian-config works as expected

oh neat...

what are you trying to solve? Most can use systemd and the hardware watchdog.

Id like to know more about this. Not sure if it’s enabled on all our kernels its possible you can disable via kernel arg in /boot/armbianEnv.txt

Follow some bash tutorials. Maybe the advanced bash scripting guide. then just use a text editor and mess with the code https://github.com/armbian/config

Id say it can be closed

I'm curious how the pine phone performs relative to your Galaxy 5.... Man Librem5 is kind of a tragedy.. at least you even got one.

Ansible is a fantastic tool for automating system config and installing stuff.... and its pluggable. Lots of existing "roles" out there we can start from for popular things https://galaxy.ansible.com Anyway..... to @TRS-80point... I wouldn't approach Armbian-config as a complete re-write.. there's lots of great functionality. I'd focus on improving the front-end's modularity, and then we can slow introduce ansible for some tasks.... again primarily I'm looking at software installation... as a place to start... Maybe there's one I should do an example on. Ansible is also great for for doing a lot of system config.. but again. this can be done in a measured way.

still trying to understand the proposal

fyi there's another PR for some SATA performance improvements that could use some testing on ebin https://git.io/JtEA

I second this... I run my home assistant via docker on my Armbian cluster....by far the sanest way

it would be nice if we could use it to just launch some ansible playbooks and roles.... a lot of the config and install code could be replaced by that. Main thing is we'd want to run it in a pyenv just to assure user land doesn't get goofed from ansible dependencies

Yep I like the idea of keeping the branch supported... Glad to help cherry-pick fixes etc as needed etc

Id focus on tuning your means of transfer to your helios4 rather disk tunning. SSH has never been good for raw throughput. You can tune ciphers and compression to get better performance. Native rsync rather than rsync over ssh is also more performant. With rsync there is also tuning opportunities. Given 4 drives. I recommed against raid6. Id choose raid5 for capacity or raid10 if you really intend to have a lot of concurrent disk IO. What type of data are you trying to protect. (If just large video files standard advise is to forgo raid and use snap raid instead) How often and how many devices do you expect writes?