AniNIX/Kapisi
1
0
Fork 0
Code Issues 31 Pull Requests 1 Projects 1 Releases Wiki Activity

Revising Geth README; commenting Geth2-5 for staging

Browse Source
This commit is contained in:
DarkFeather
2026-07-31 15:50:37 -05:00
parent 51b1f00fb2
commit 311eb69d33
2 changed files with 37 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
examples/msn0.yml
+22 -21
View File
@@ -95,38 +95,39 @@ all:
active_vms: active_vms:
- Yggdrasil - Yggdrasil
Geth: Geth:
vars:
primary: Geth0
hosts: hosts:
Geth0: Geth0:
ipinterface: eth0 ipinterface: eth0
ip: 10.0.1.9 ip: 10.0.1.9
mac: b8:27:eb:09:a1:a0 mac: b8:27:eb:09:a1:a0
static: true static: true
k3s_primary: true
Geth1: Geth1:
ipinterface: eth0 ipinterface: eth0
ip: 10.0.1.10 ip: 10.0.1.10
mac: e4:5f:01:01:ff:9c
static: true
Geth2:
ipinterface: eth0
ip: 10.0.1.11
mac: e4:5f:01:01:ff:d5 mac: e4:5f:01:01:ff:d5
static: true static: true
Geth3: # Geth2:
ipinterface: eth0 # ipinterface: eth0
ip: 10.0.1.12 # ip: 10.0.1.11
mac: e4:5f:01:01:ff:96 # mac: e4:5f:01:01:ff:9c
static: true # static: true
Geth4: # Geth3:
ipinterface: eth0 # ipinterface: eth0
ip: 10.0.1.13 # ip: 10.0.1.12
mac: e4:5f:01:01:ff:e4 # mac: e4:5f:01:01:ff:96
static: true # static: true
Geth5: # Geth4:
ipinterface: eth0 # ipinterface: eth0
ip: 10.0.1.14 # ip: 10.0.1.13
mac: b8:27:eb:81:f5:4b # mac: e4:5f:01:01:ff:e4
static: true # static: true
# Geth5:
# ipinterface: eth0
# ip: 10.0.1.14
# mac: b8:27:eb:81:f5:4b
# static: true
virtual: # 10.0.1.16/28 virtual: # 10.0.1.16/28
vars: vars:
hosts: hosts:
roles/Geth/README.md
+15 -11
View File
@@ -1,20 +1,24 @@
Geth is a complete automation suite for homes and interaction with the physical world. However, it is not a automatic process, and as such you will need to install it manually. Geth is a collective ecosystem for aggregating compute across many cheap nodes for small tasks.
# Etymology=The [http://masseffect.wikia.com/wiki/Geth Geth] are a fictional race in the Mass Effect universe. Geth are individual processes running on many platforms. The more devices, the smarter the collective or gestalt consciousness of the entity becomes. Thanks to NetworkChuck's [tutorial](https://www.youtube.com/watch?v=X9fSMGkjtug) for helping to get this started and the Antsle nano models for the hardware to run this.
# Etymology
The [Geth](http://masseffect.wikia.com/wiki/Geth) are a fictional race in the Mass Effect universe. Geth are individual processes running on many platforms. The more devices, the smarter the collective or gestalt consciousness of the entity becomes.
# Relevant Files and Software # Relevant Files and Software
You can install Geth with [https://aninix.net/foundation/ConfigPackages ConfigPackages]'s Geth Makefile and configuration.
A number of devices can be controlled under the gestalt -- see [[Geth/Hardware]] for our experiments with Geth hardware platforms. The configuration.yaml format used by the underlying home-assistant package is very simple, and as such we don't prescriptively install one over the base version. Instead, we include snippets for you to define your own structure. This is a Rancher orchestration of Kubernetes. This allows us to centrally manage a lot of small processes, such as CTF images, without the weight of managing full virtual machines.
We are also considering features such as integrating smart lights with Shadowfeed presence detection and timeslots and requiring wireless presence for RFC door unlocks. Note: containers make it easier to isolate dependencies, especially for less-maintained apps or when we want to set up an isolated network ecosystem. However, they do introduce performance overhead. This is helpful for micro-services, but it's not helpful for heavy, oft-used or data-intensive applications. Some articles with tracking on the wasted compute using containers are below.
* https://pythonspeed.com/articles/docker-performance-overhead/
[file:///var/lib/hass/ Geth configuration] can be tested with the following: <pre> hass --script check_config -c /var/lib/hass</pre> * https://www.torizon.io/blog/containers-in-linux-and-performance-impact
# Available Clients # Available Clients
See [[WebServer#Clients|this list of clients]] for tools to access this system. The Shadowfeed NAT rules will need to be updated to allow access outside the network, and make sure to follow [https://home-assistant.io/getting-started/securing/ the security checkpoints] before publishing. This system does not have a client itself, but the containers managed in it may provide SSH or Web clients.
# Equivalents or Competition # Equivalents or Competition
Most home-automation systems are DIY at the moment, though the [https://nest.com/ NEST] system is one commercial offering.
<!--|ref=REFERENCE-->}} There are many ways to run containers other than Rancher/k3s:
[[Category:SSL]] * Self-hosted: RedHat OpenShift, [Antsle antMan](https://antsle.com), and raw Docker
* Cloud: [Containers on Azure](https://azure.microsoft.com/en-us/products/category/containers/), [AWS Containers](https://aws.amazon.com/containers/)