This is what the repo looked like before i refactored it

total 128
-rw-rw-r--  1 reachableceo reachableceo  6311 Jul 30 23:27 AGENTS.md
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 29 19:28 awx
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 29 19:32 console
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 28 11:33 dns-cluster-setup
drwxrwxr-x  4 reachableceo reachableceo  4096 Jul 29 05:01 docs
drwxrwxr-x  4 reachableceo reachableceo  4096 Jul 29 04:59 k8s
-rw-rw-r--  1 reachableceo reachableceo 33962 Jul 28 11:22 LICENSE
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 28 11:22 logs
drwxrwxr-x  3 reachableceo reachableceo  4096 Jul 29 19:28 netinfra
-rw-rw-r--  1 reachableceo reachableceo     0 Aug  1 15:31 nextprompt
drwxrwxr-x  3 reachableceo reachableceo  4096 Jul 28 20:01 perf
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 28 19:46 powerman
drwxrwxr-x 10 reachableceo reachableceo  4096 Jul 30 08:47 provisioning
drwxrwxr-x  3 reachableceo reachableceo  4096 Jul 29 05:01 proxmox
-rw-rw-r--  1 reachableceo reachableceo  2251 Jul 30 09:33 README.md
drwxrwxr-x  5 reachableceo reachableceo  4096 Jul 30 22:52 returned-logs
-rw-r--r--  1 reachableceo reachableceo 12514 Jul 30 23:03 STATUS.md
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 30 23:01 switches
drwxrwxr-x  5 reachableceo reachableceo  4096 Jul 30 08:41 tests
drwxrwxr-x  2 reachableceo reachableceo  4096 Jul 30 11:40 ups
drwxrwxr-x  3 reachableceo reachableceo  4096 Jul 28 11:22 vendor

Here is what it looks like now

total 112
-rw-rw-r-- 1 reachableceo reachableceo  6311 Jul 30 23:27 AGENTS.md
drwxrwxr-x 4 reachableceo reachableceo  4096 Aug  1 15:34 archive
drwxrwxr-x 2 reachableceo reachableceo  4096 Jul 29 19:28 awx
drwxrwxr-x 4 reachableceo reachableceo  4096 Aug  1 15:34 dcinfra
drwxrwxr-x 4 reachableceo reachableceo  4096 Jul 29 04:59 k8s
-rw-rw-r-- 1 reachableceo reachableceo 33962 Jul 28 11:22 LICENSE
drwxrwxr-x 2 reachableceo reachableceo  4096 Jul 28 11:22 logs
drwxrwxr-x 5 reachableceo reachableceo  4096 Aug  1 15:34 netinfra
-rw-rw-r-- 1 reachableceo reachableceo  1426 Aug  1 15:31 nextprompt
drwxrwxr-x 4 reachableceo reachableceo  4096 Aug  1 15:33 proxmox
-rw-rw-r-- 1 reachableceo reachableceo  2251 Jul 30 09:33 README.md
drwxrwxr-x 5 reachableceo reachableceo  4096 Jul 30 22:52 returned-logs
-rw-r--r-- 1 reachableceo reachableceo 12514 Jul 30 23:03 STATUS.md
drwxrwxr-x 5 reachableceo reachableceo  4096 Jul 30 08:41 tests
drwxrwxr-x 2 reachableceo reachableceo  4096 Jul 30 11:40 ups
drwxrwxr-x 3 reachableceo reachableceo  4096 Jul 28 11:22 vendor

I move the top level directories into more of a sub project/module type setup

I moved the provisioning directory to archive, because its replaced by the KNELIAC repository/project (located at: /home/reachableceo/projects/KNELIAC

As far as the servers/data center itself, I have made many changes to :

- deployed virtual machines (tsys-umbrel, tsys-sipwise)
- location of virtual machine disks
- amount of ram/cpu allocated to virtual machines
- LACP between core and r3-stor is fixed
- pfv-k8s-wnode fleet changes
- removed tctc vm 
- added all domains to uptime kuma
- added all systems/services to uptime kuma
- ssd/nvme disks are formatted and in use on pfv-tsys5

Unfortuantely during my storage moves, I accidently wiped out pfv-netinfra-02 . Can you turn it back into a redundant node? Its setup with the ssh pub key/passwordless sudo like before

Also, the default /dev/shm allocated to pihole was too small, i fixed that in compose live on the server, as it was a production outage. Can you fold that fix in? Also can you add a docker compose healthcheck for gravity.db issues? I had to manually fix gravitydb (move it out of way, bounce container, pihole auto recreates it). 

In general, re-orient yourself to this repo, to the servers/viritual machines (via lldp/snmpwalk/ssh/nmap)

oh a note about the 4gbps lacp and concerns about mismatch. 

Heres my thinking (re single flow/link saturation due to mismatched lacp and/or lack of layer4 option on core switch)....

pfv-tsys6/7 will both have 1gbps to pfv-tsys4/5 right? so thats ok
the indiviual vms (doing k8s chatter, mpi interconnect, clustered whatever) will all have 1gbps (because unique ip/mac)

So, as long as, every single endpoint has 1gbps to every other endpoint over the vlan 1000 network , I am happy. 

The 4gbps was more about ensuring adequate overall capacity for all the different sessions.  I am very open to more iperf testing, fio testing on the vms and generally properly performance benchmarking/analyzing the whole proxmox/k8s cluster before any workloads are put onto them. Also cpu/ram benchmarking as well. Lets see what this cluster can do.