README: Improve formatting
This commit is contained in:
parent
f30b5cd9f2
commit
31976e17a5
32
README.md
32
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/)
|
[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
|
Needs 3 zones (arbiter versus data zones) with a maximum of 700ms latency
|
||||||
Ceph Stretch is a solution to specifically cater for higher latencies
|
Ceph Stretch is a solution to specifically cater for higher latencies
|
||||||
because its use case is to span over several geographically seperated data centers
|
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
|
Possibly [rook](https://rook.io/docs/rook/v1.9/ceph-storage.html) as provider
|
||||||
[OpenEBS](https://openebs.io/)
|
[OpenEBS](https://openebs.io/)
|
||||||
[Longhorn](https://longhorn.io/)
|
[Longhorn](https://longhorn.io/)
|
||||||
|
|
||||||
### Problems
|
### Problems
|
||||||
etcd latency
|
etcd latency
|
||||||
Network bandwith and latencies not predictable for the individual participant's connections
|
Network bandwith and latencies not predictable for the individual participant's connections
|
||||||
Low bandwith, not symmetric with regard to bandwith
|
Low bandwith, not symmetric with regard to bandwith
|
||||||
|
|
||||||
### What we did _not_ discuss
|
### 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
|
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
|
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
|
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,
|
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
|
## What we have
|
||||||
### Hardware
|
### Hardware
|
||||||
Pine64
|
Pine64
|
||||||
Pine ROCKPro64
|
Pine ROCKPro64
|
||||||
Raspberry Pi
|
Raspberry Pi
|
||||||
|
|
||||||
### Software
|
### Software
|
||||||
Talos on Pine64
|
Talos on Pine64
|
||||||
|
|
||||||
## Next steps
|
## Next steps
|
||||||
Please add your name, mail address, notes and thoughts to this README
|
Please add your name, mail address, notes and thoughts to this README
|
||||||
Decide on and set up communication infrastructure
|
Decide on and set up communication infrastructure
|
||||||
Decide on cluster endpoint / entry point solution
|
Decide on cluster endpoint / entry point solution
|
||||||
Explore Talos more in-depth
|
Explore Talos more in-depth
|
||||||
|
Loading…
Reference in New Issue
Block a user