From 31976e17a5e0a74782c4730521b4ef01c5d90bd8a6c59ed1e1ef6280fa825392 Mon Sep 17 00:00:00 2001 From: mue Date: Sun, 29 Dec 2024 23:25:06 +0100 Subject: [PATCH] README: Improve formatting --- README.md | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index 1bcd301..6a125dd 100644 --- a/README.md +++ b/README.md @@ -51,21 +51,21 @@ S3 compat layer provided by Ceph as one option [Ceph Stretch](https://docs.ceph.com/en/latest/rados/operations/stretch-mode/) Needs 3 zones (arbiter versus data zones) with a maximum of 700ms latency Ceph Stretch is a solution to specifically cater for higher latencies -because its use case is to span over several geographically seperated data centers -Possibly [rook](https://rook.io/docs/rook/v1.9/ceph-storage.html) as provider -[OpenEBS](https://openebs.io/) -[Longhorn](https://longhorn.io/) +because its use case is to span over several geographically seperated data centers +Possibly [rook](https://rook.io/docs/rook/v1.9/ceph-storage.html) as provider +[OpenEBS](https://openebs.io/) +[Longhorn](https://longhorn.io/) ### Problems -etcd latency -Network bandwith and latencies not predictable for the individual participant's connections -Low bandwith, not symmetric with regard to bandwith +etcd latency +Network bandwith and latencies not predictable for the individual participant's connections +Low bandwith, not symmetric with regard to bandwith ### What we did _not_ discuss -What kind of SBC to use or support +What kind of SBC to use or support The more RAM the better. Many SBCs are low on RAM, typically only up to 4GB and while SBCs with much more RAM exist they might not be as well supported by Linux -or not as well available like the more common ones +or not as well available like the more common ones An interesting candidate seems to the [Raxda Rock 3-5](https://wiki.radxa.com/Rock3) with up to 32GB of RAM While there is no immediate or inherent reason to restrict that, @@ -76,15 +76,15 @@ and / or run their own system image for their SBC ## What we have ### Hardware -Pine64 -Pine ROCKPro64 -Raspberry Pi +Pine64 +Pine ROCKPro64 +Raspberry Pi ### Software Talos on Pine64 ## Next steps -Please add your name, mail address, notes and thoughts to this README -Decide on and set up communication infrastructure -Decide on cluster endpoint / entry point solution -Explore Talos more in-depth +Please add your name, mail address, notes and thoughts to this README +Decide on and set up communication infrastructure +Decide on cluster endpoint / entry point solution +Explore Talos more in-depth