linux
rook
linux | rook | |
---|---|---|
73 | 51 | |
10,759 | 11,978 | |
1.5% | 1.0% | |
10.0 | 9.9 | |
7 days ago | 6 days ago | |
C | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
linux
-
Argon mini fan starts at 55°C but never stops
Fan control generally involves hysteresis. This means a cooling fan turns on at one temperature, and then turns off once temperature has fallen to another lower temperature. This avoids cycling the fan on and off too much. The difference between those two temperatures is hysteresis. The default hysteresis is 10°C and maybe the fan never manages to cool the CPU to 45°C. A parameter has been added to change hysteresis: https://github.com/raspberrypi/linux/commit/fa390133fd17f2cc6aa5a7d2e472c073a1115fe1
-
Raspberry Pi 5
I see that the PR against the Raspberry Pi linux repo is out [0]. Interestingly they are introducing a BCM2712 defconfig with a 64k default page size.
[0] - https://github.com/raspberrypi/linux/pull/5618
-
[RPi4] classic install or GenPi64
and can grab their patched kernel source here ( use the dtbs and overlays and kernel from your compiled version)
-
24 SPI displays on one ESP32?
Also was your pi issue related to this? https://github.com/raspberrypi/linux/issues/3381 or what do you mean jittery, unstable?
-
Issues with Raspberry Pi Zero W and Camera Module - bullseye and buster errors.
Could be related to the driver load order/blacklisting (https://github.com/raspberrypi/linux/issues/435) Or couple of people report configuring the dtoverlay=imx477 in the boot config helped (https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README)
-
RaspberryOS & Sense Hat v1
thanks, I also found this: https://github.com/raspberrypi/linux/issues/5398
- Vulkan not starting on RPi4
-
How Brompton Bicycle uses Raspberry Pi technology to improve production [video]
And ready! :)
> It is the most basic task for Linux computer...
Well, it depends for whom. Also, you need adequate software and hardware. About wireless, the chipset in an RPi4 is designed for clients, not APs, and its capabilities on having multiple clients are quite limited:
https://github.com/raspberrypi/linux/issues/3010
Routers like the Omnia Turris, Mikrotik, PC Engines... use specific mini PCIe cards that can be as expensive as a full Raspberry Pi 4, just for the wireless.
https://www.discomp.eu/wireless-minipci-cards_c14501412.html
- How can I fix this?
- Display Backlight not turning off
rook
-
Ceph: A Journey to 1 TiB/s
I have some experience with Ceph, both for work, and with homelab-y stuff.
First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes.
For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines.
Also, Ceph does prefer physical access to disks (similar to ZFS).
And you do need decent networking connectivity - I think that's the main thing people think of, when they think of high hardware requirements for Ceph. Ideally 10Gbe at the minimum - although more if you want higher performance - there can be a lot of network traffic, particularly with things like backfill. (25Gbps if you can find that gear cheap for homelab - 50Gbps is a technological dead-end. 100Gbps works well).
But honestly, for a homelab, a cheap mini PC or NUC with 10Gbe will work fine, and you should get acceptable performance, and it'll be good for learning.
You can install Ceph directly on bare-metal, or if you want to do the homelab k8s route, you can use Rook (https://rook.io/).
Hope this helps, and good luck! Let me know if you have any other questions.
-
Running stateful workloads on Kubernetes with Rook Ceph
Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case of a disaster.
-
People who run Nextcloud in Docker: Where do you store your data/files? In a Docker volume, or on a remote server/NAS?
This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself.
-
Rook/Ceph with VM nodes on research cluster?
The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:
-
Asking for recommendation on remote Kubernetes storage for a small cluster and databases
Have you looked at Rook?
-
Want advice on planned evolution: k3os/Longhorn --> Talos/Ceph, plus Consul and Vault
I've briefly run ceph in an external mode, you can actually use a rook deployment to manage it (sort of). Here is the documentation for doing that. For me it didn't pass my testing phase because I need better networking equipment before I can try that.
-
ATARI is still alive: Atari Partition of Fear
This article explains the data corruption issue happened in Rook in 2021. The root cause lies in an unexpected place and can also occurs in all Ceph environment. It's interesting that Rook had started to encounter this problem recently even though this problem has existed for a long time. It's due to a series of coincidences. I wrote this article because the word "Atari" used in a non-historical context in 2021.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
Rook (this is a nice article for Rook NFS)
-
Running on-premise k8s with a small team: possible or potential nightmare?
Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc
-
My completely automated Homelab featuring Kubernetes
I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.
What are some alternatives?
zen-kernel - Zen Patched Kernel Sources
longhorn - Cloud-Native distributed storage built on and for Kubernetes
FUZIX - FuzixOS: Because Small Is Beautiful
ceph-csi - CSI driver for Ceph
LibreELEC.tv - Just enough OS for KODI
velero - Backup and migrate Kubernetes applications and their persistent volumes
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
zfs - OpenZFS on Linux and FreeBSD
Ceph - Ceph is a distributed object, block, and file storage platform
cacule-cpu-scheduler - The CacULE CPU scheduler is based on interactivity score mechanism. The interactivity score is inspired by the ULE scheduler (FreeBSD scheduler).
hub-feedback - Feedback and bug reports for the Docker Hub