kylechase · August 8, 2025 13:18 · May 2, 2025 · May 2, 2025 · Apr 29, 2025 · Apr 29, 2025
diff --git a/proxmox.md b/proxmox.md
@@ -35,7 +35,7 @@ Also made ceph take a hard dependecy on frr service being started - this may hel
    - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing Mesh (old)~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
    - Optional: [Enable VMs to access ceph mesh](/dbbe5483f2779228ff743c5f333effe0)
    - Optional: [Enable LAN clients to access mesh](/c0df83c269c5f5c192cb8a08a0d4a559)
-   - Optional: [cephFS Clients - mount remote cephFS volume])/61b38c47cb2c79db279ee1cbb6f31772)
+   - Optional: [cephFS Clients - mount remote cephFS volume](/61b38c47cb2c79db279ee1cbb6f31772)
 4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -35,6 +35,7 @@ Also made ceph take a hard dependecy on frr service being started - this may hel
    - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing Mesh (old)~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
    - Optional: [Enable VMs to access ceph mesh](/dbbe5483f2779228ff743c5f333effe0)
    - Optional: [Enable LAN clients to access mesh](/c0df83c269c5f5c192cb8a08a0d4a559)
+   - Optional: [cephFS Clients - mount remote cephFS volume])/61b38c47cb2c79db279ee1cbb6f31772)
 4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -15,6 +15,13 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 <h4 align="center">The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.</h4>
 
 
+Update as of 2025.04.29
+- Added some more tweaks to the thunderbolt setup, mesh setup
+- added way to get VMs to access ceph mesh (no you cant bridge en05 and en06 - it breaks if you do that)
+- added way to get any machine on LAN to access ceph mesh
+- todo: bind my docker swarm VMs to mesh, mount ceph isnide vm (coming soon as gist)
+
+
 Updates as of 2025.04.20
 Been running great, still had issues with IPv4 dual fabric.  Have refactored that with some great suggestions from commenters.  Now need to see if longhaul tests prove out if these have helped.
 

diff --git a/proxmox.md b/proxmox.md
@@ -27,6 +27,7 @@ Also made ceph take a hard dependecy on frr service being started - this may hel
    - [Enable Dual Stack IPv4 / IPv4) Openfabric Routing Mesh (new)](/58b5cd9a18e1f5846048aabd4b152564)
    - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing Mesh (old)~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
    - Optional: [Enable VMs to access ceph mesh](/dbbe5483f2779228ff743c5f333effe0)
+   - Optional: [Enable LAN clients to access mesh](/c0df83c269c5f5c192cb8a08a0d4a559)
 4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -26,7 +26,7 @@ Also made ceph take a hard dependecy on frr service being started - this may hel
    - [Prepare Thunderbolt-Net cables and interface setup](/67fdc9a517faefa68f730f82d7fa3570)
    - [Enable Dual Stack IPv4 / IPv4) Openfabric Routing Mesh (new)](/58b5cd9a18e1f5846048aabd4b152564)
    - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing Mesh (old)~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
-   - Optional: [Enable Bridge for VM access to mesh](/dbbe5483f2779228ff743c5f333effe0)
+   - Optional: [Enable VMs to access ceph mesh](/dbbe5483f2779228ff743c5f333effe0)
 4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -22,9 +22,11 @@ Also made ceph take a hard dependecy on frr service being started - this may hel
 
 ## Outcomes
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)
-2. [Thunderbolt Mesh Networking Setup](/67fdc9a517faefa68f730f82d7fa3570)
-3. [v2 - Enable Dual Stack IPv4 / IPv4) Openfabric Routing Mesh](/58b5cd9a18e1f5846048aabd4b152564)
-   - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing on Mesh Network~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
+2. Thunderbolt Netwokring Setup 
+   - [Prepare Thunderbolt-Net cables and interface setup](/67fdc9a517faefa68f730f82d7fa3570)
+   - [Enable Dual Stack IPv4 / IPv4) Openfabric Routing Mesh (new)](/58b5cd9a18e1f5846048aabd4b152564)
+   - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing Mesh (old)~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
+   - Optional: [Enable Bridge for VM access to mesh](/dbbe5483f2779228ff743c5f333effe0)
 4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -18,6 +18,8 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 Updates as of 2025.04.20
 Been running great, still had issues with IPv4 dual fabric.  Have refactored that with some great suggestions from commenters.  Now need to see if longhaul tests prove out if these have helped.
 
+Also made ceph take a hard dependecy on frr service being started - this may help some scenarios, but not if the thunderbolt interfaces are down, still not sure how to help folks there (this applies mostly to MS-101 users, see commnts sections of indidual gists, esp old deprecated openfrabric mesh gist) 
+
 ## Outcomes
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)
 2. [Thunderbolt Mesh Networking Setup](/67fdc9a517faefa68f730f82d7fa3570)

diff --git a/proxmox.md b/proxmox.md
@@ -15,14 +15,8 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 <h4 align="center">The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.</h4>
 
 
-Updates as of 9/30/2023
-This cluster is no longer a PoC and is my production cluster for all my VMs and docker containers (in VM based swarm).  
-
-All my initial objectives have been achivied and then some.  All VMs migrated from Hyper-V and working - despite some stupidty on my part - though i learnt a lot!)
-
-I will update if and when i make major changes, redesign or add new capabilities, but to be clear i now consider this gist set complete for my needs and have no more edits planned.
-
-If you spot a critical type let me know and I can change but as as these are notes for me (not a tutorial) i make no promises :-) 
+Updates as of 2025.04.20
+Been running great, still had issues with IPv4 dual fabric.  Have refactored that with some great suggestions from commenters.  Now need to see if longhaul tests prove out if these have helped.
 
 ## Outcomes
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)

diff --git a/proxmox.md b/proxmox.md
@@ -1,5 +1,3 @@
-## dont buy ASUS motherboard for this topology - many of their motherboard do not implement full SW Connection Manager required for full spec USB4 / TB4 required for this topology and they are unable to articulate which motherboard do and do not have the required features and keep saying 20Gbp/s is the max speed of connection on intel NUCS - this is wrong. 13th and 14th Gen NUCs that implement a SW connection manager for USB4 / TB4 will work fine..
-
 # ProxMox Cluster - Soup-to-Nutz
 aka what i did to get from nothing to done.
 

diff --git a/proxmox.md b/proxmox.md
@@ -34,6 +34,7 @@ If you spot a critical type let me know and I can change but as as these are not
 4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)
+   - [cephFS - virtiofs passthrough to docker swarm VMs](/1b526c38b9c7f7dca58ca71052653820)
 7. [Setup HA Windows Server VM + TPM](/054c153defe3acbbe3a61d6fe08704d4)
 8. [How to migrate Gen2 Windows VM from Hyper-V to Proxmox](/e9cf5df1100edfdfb3a6104d6b288a1d)
 
@@ -56,9 +57,7 @@ If you spot a critical type let me know and I can change but as as these are not
 - maybe send syslog to my syslog server (securely)
 - figure out ceph public/cluster running on different networks - unclear its needed for this size of install
 - get all nodes listening to my network UPS and shut down before power runs out
-- For the docker VMs implement both cephfs via virtiofs for and a cephs docker volume and test which i like best in a swarm
-      - using [this ceph volume guide](https://gist.github.com/Drallas/6069c5fc96f3570a9c8d573fc9c6d44c) and this [mounting guide](https://gist.github.com/Drallas/7e4a6f6f36610eeb0bbb5d011c8ca0be) by Drallas
-      - using one of these three ceph volume plugins [Brindster/docker-plugin-cephfs](https://github.com/Brindster/docker-plugin-cephfs) [flaviostutz/cepher](https://github.com/flaviostutz/cepher) [n0r1sk/docker-volume-cephfs](https://gitlab.com/n0r1sk/docker-volume-cephfs) each has different strengths and weaknesses (i will like choose either the n0r1sk or the Brindster one).
+- using one of these three ceph volume plugins [Brindster/docker-plugin-cephfs](https://github.com/Brindster/docker-plugin-cephfs) [flaviostutz/cepher](https://github.com/flaviostutz/cepher) [n0r1sk/docker-volume-cephfs](https://gitlab.com/n0r1sk/docker-volume-cephfs) each has different strengths and weaknesses (i will like choose either the n0r1sk or the Brindster one) - until i figure out ceph networking more this is dead in the water as ceph isn't reachable from LAN or docker swarm VMs - so using virtiofs linked in main items above.
 
 ## Purpose of cluster
 I have been using Hyper-V for my docker swarm cluster VM hosts ([see other gists](/f4624361c4e8c3be2aad9b3f0073c7f9)).  Original intenttion was to try and get Thunderbolt Networking for a Hyper-V cluster going and clustered storage for the VMs.  This turns out to be super hard when using NUCs as cluster nodes due to too few disks.  I looked at solar winds as alternative but this was both complex and not pervasive.

diff --git a/proxmox.md b/proxmox.md
@@ -30,12 +30,12 @@ If you spot a critical type let me know and I can change but as as these are not
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)
 2. [Thunderbolt Mesh Networking Setup](/67fdc9a517faefa68f730f82d7fa3570)
 3. [v2 - Enable Dual Stack IPv4 / IPv4) Openfabric Routing Mesh](/58b5cd9a18e1f5846048aabd4b152564)
-4. ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing on Mesh Network~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
-5. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
-6. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
-7. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)
-8. [Setup HA Windows Server VM + TPM](/054c153defe3acbbe3a61d6fe08704d4)
-9. [How to migrate Gen2 Windows VM from Hyper-V to Proxmox](/e9cf5df1100edfdfb3a6104d6b288a1d)
+   - ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing on Mesh Network~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
+4. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
+5. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
+6. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)
+7. [Setup HA Windows Server VM + TPM](/054c153defe3acbbe3a61d6fe08704d4)
+8. [How to migrate Gen2 Windows VM from Hyper-V to Proxmox](/e9cf5df1100edfdfb3a6104d6b288a1d)
 
    1. [Notes on migrating my real world domain controller #2 ](/scyto/f8b0a1b06ae62f03db3182f8bd23abda)
    2. [Notes on migrating my real world domain controller #1 (FSMO holder, AAD Sync and CA server) ](/scyto/ef59d3799c089338cfb32b83306f9396)

diff --git a/proxmox.md b/proxmox.md
@@ -29,8 +29,8 @@ If you spot a critical type let me know and I can change but as as these are not
 ## Outcomes
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)
 2. [Thunderbolt Mesh Networking Setup](/67fdc9a517faefa68f730f82d7fa3570)
-3. ~Enable OSPF Routing On Mesh network~ - deprecated -  [old gist here](/629c61d36af07b5ee45adfb172e25384)
-4. [Enable Dual Stack (IPv4 and IPv6) Openfabric Routing on Mesh Network](/4c664734535da122f4ab2951b22b2085)
+3. [v2 - Enable Dual Stack IPv4 / IPv4) Openfabric Routing Mesh](/58b5cd9a18e1f5846048aabd4b152564)
+4. ~Enable Dual Stack (IPv4 and IPv6) Openfabric Routing on Mesh Network~ deprecated - [Old gist here](/4c664734535da122f4ab2951b22b2085)
 5. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 6. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 7. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -1,4 +1,4 @@
-## dont buy ASUS motherboard for this topology - many of their motherboard do not implement full SW Connection Manager required for full specy USB4 / TB4 required for this topology and they are unable to articulate which motherboard do and don not have the required features and keep saying 20Gbp/s is the max speed of connection on intel NUCS - this is wrong. 13th and 14th Gen NUCs that implement a SW connection manager for USB4 / TB4 will work fine..
+## dont buy ASUS motherboard for this topology - many of their motherboard do not implement full SW Connection Manager required for full spec USB4 / TB4 required for this topology and they are unable to articulate which motherboard do and do not have the required features and keep saying 20Gbp/s is the max speed of connection on intel NUCS - this is wrong. 13th and 14th Gen NUCs that implement a SW connection manager for USB4 / TB4 will work fine..
 
 # ProxMox Cluster - Soup-to-Nutz
 aka what i did to get from nothing to done.

diff --git a/proxmox.md b/proxmox.md
@@ -1,4 +1,4 @@
-## dont buy ASUS motherboard for this topology - many of their motherboard do not implement full SW Connection Manager required for full specy USB4 / TB4 required for this topology.
+## dont buy ASUS motherboard for this topology - many of their motherboard do not implement full SW Connection Manager required for full specy USB4 / TB4 required for this topology and they are unable to articulate which motherboard do and don not have the required features and keep saying 20Gbp/s is the max speed of connection on intel NUCS - this is wrong. 13th and 14th Gen NUCs that implement a SW connection manager for USB4 / TB4 will work fine..
 
 # ProxMox Cluster - Soup-to-Nutz
 aka what i did to get from nothing to done.

diff --git a/proxmox.md b/proxmox.md
@@ -1,3 +1,5 @@
+## dont buy ASUS motherboard for this topology - many of their motherboard do not implement full SW Connection Manager required for full specy USB4 / TB4 required for this topology.
+
 # ProxMox Cluster - Soup-to-Nutz
 aka what i did to get from nothing to done.
 

diff --git a/proxmox.md b/proxmox.md
@@ -9,7 +9,7 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 
 
 <p align="center">
-<img width="400" alt="image" src="https://user-images.githubusercontent.com/11369180/273477686-3462588e-2f3a-4f52-9a5a-2c01dcae92e1.png">
+<img width="400" alt="image" src="https://user-images.githubusercontent.com/11369180/273478752-90462127-d65c-4c7d-b418-e7efbd2bd2fc.jpg">
 </p>
 
 <h4 align="center">The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.</h4>

diff --git a/proxmox.md b/proxmox.md
@@ -12,10 +12,7 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 <img width="400" alt="image" src="https://user-images.githubusercontent.com/11369180/273477686-3462588e-2f3a-4f52-9a5a-2c01dcae92e1.png">
 </p>
 
-
-
-<p style="text-align: center;">The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.
-</p>
+<h4 align="center">The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.</h4>
 
 
 Updates as of 9/30/2023

diff --git a/proxmox.md b/proxmox.md
@@ -11,7 +11,11 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 <p align="center">
 <img width="400" alt="image" src="https://user-images.githubusercontent.com/11369180/273477686-3462588e-2f3a-4f52-9a5a-2c01dcae92e1.png">
 </p>
-The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.
+
+
+
+<p style="text-align: center;">The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.
+</p>
 
 
 Updates as of 9/30/2023

diff --git a/proxmox.md b/proxmox.md
@@ -8,10 +8,10 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 [Required Outomces of cluster project](/76e94832927a89d977ea989da157e9dc#goals-of-cluster)
 
 
-
-1. dd ![my_cluster (Large)](https://user-images.githubusercontent.com/11369180/273477686-3462588e-2f3a-4f52-9a5a-2c01dcae92e1.png)
-
-
+<p align="center">
+<img width="400" alt="image" src="https://user-images.githubusercontent.com/11369180/273477686-3462588e-2f3a-4f52-9a5a-2c01dcae92e1.png">
+</p>
+The first 3 NUCs are the new proxmox cluster, the second set of 3 NUCs is the old Hyper-V nodes.
 
 
 Updates as of 9/30/2023

diff --git a/proxmox.md b/proxmox.md
@@ -8,6 +8,12 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 [Required Outomces of cluster project](/76e94832927a89d977ea989da157e9dc#goals-of-cluster)
 
 
+
+1. dd ![my_cluster (Large)](https://user-images.githubusercontent.com/11369180/273477686-3462588e-2f3a-4f52-9a5a-2c01dcae92e1.png)
+
+
+
+
 Updates as of 9/30/2023
 This cluster is no longer a PoC and is my production cluster for all my VMs and docker containers (in VM based swarm).  
 

diff --git a/proxmox.md b/proxmox.md
@@ -35,7 +35,7 @@ If you spot a critical type let me know and I can change but as as these are not
 9. [Migrate HomeAssistant VM from Hyper-V](/96ee39f432f18a43ea3b95697c3f398e)
 10. [Migrate my debian VM based docker swarm from Hyper-V to proxmox](/042c8c41b23bd5ddb31d1e4e38156dff)
 11. Extra Credit (optional):
-    1. [Enable vGPU Passthrough](/e4e3de35ee23fdb4ae5d5a3b85c16ed3)
+    1. [Enable vGPU Passthrough (+windows guest, CT guest configs](/e4e3de35ee23fdb4ae5d5a3b85c16ed3)
     2. [Install Lets Encrypt Cert (CloudFlare as DNS Provder](/7a67e48ae2c6b1cffdefb8f984734b5d)
     3. [Azure Active Directory Auth](/038b35c913018ee1cbd4dc62e49a6355)
     4. [Install Proxmox Backup Server (PBS) on synology with CIFS backend](/61dcfff1d0128d9df85cf57b756c599c)

diff --git a/proxmox.md b/proxmox.md
@@ -33,7 +33,7 @@ If you spot a critical type let me know and I can change but as as these are not
    3. [Notes on migrating my windows (server 2019) admin center VM](/3ebe199d718b25a2927294dbf3d74a97)
 
 9. [Migrate HomeAssistant VM from Hyper-V](/96ee39f432f18a43ea3b95697c3f398e)
-10. [Migrate my debian VM based docker swarm to proxmox](/042c8c41b23bd5ddb31d1e4e38156dff) - in progess 9/27/23
+10. [Migrate my debian VM based docker swarm from Hyper-V to proxmox](/042c8c41b23bd5ddb31d1e4e38156dff)
 11. Extra Credit (optional):
     1. [Enable vGPU Passthrough](/e4e3de35ee23fdb4ae5d5a3b85c16ed3)
     2. [Install Lets Encrypt Cert (CloudFlare as DNS Provder](/7a67e48ae2c6b1cffdefb8f984734b5d)

diff --git a/proxmox.md b/proxmox.md
@@ -21,7 +21,7 @@ If you spot a critical type let me know and I can change but as as these are not
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)
 2. [Thunderbolt Mesh Networking Setup](/67fdc9a517faefa68f730f82d7fa3570)
 3. ~Enable OSPF Routing On Mesh network~ - deprecated -  [old gist here](/629c61d36af07b5ee45adfb172e25384)
-4. [Enable Openfabric Routing on Mesh Network](/4c664734535da122f4ab2951b22b2085)
+4. [Enable Dual Stack (IPv4 and IPv6) Openfabric Routing on Mesh Network](/4c664734535da122f4ab2951b22b2085)
 5. [Setup Cluster](/645193291b9a81eb3cb6ebefe68274ae)
 6. [Setup Ceph and High Availability](/8c652f3eab61ed1fa2f980d02a484c35)
 7. [Create CephFS and storage for ISOs and CT Templates](/941b24efd1ac0bf9b3cd30c3fb1e5341)

diff --git a/proxmox.md b/proxmox.md
@@ -9,7 +9,9 @@ _note: these are designed to be primarily a re-install guide for myself (writing
 
 
 Updates as of 9/30/2023
-This cluster is no longer a PoC and is my production cluster for my two dommain controllers.  All my initial objectives achivied and then some.  All VMs migrated from Hyper-V and working - despite some stupidty on my part - though i learnt a lot!)
+This cluster is no longer a PoC and is my production cluster for all my VMs and docker containers (in VM based swarm).  
+
+All my initial objectives have been achivied and then some.  All VMs migrated from Hyper-V and working - despite some stupidty on my part - though i learnt a lot!)
 
 I will update if and when i make major changes, redesign or add new capabilities, but to be clear i now consider this gist set complete for my needs and have no more edits planned.
 

diff --git a/proxmox.md b/proxmox.md
@@ -1,20 +1,19 @@
 # ProxMox Cluster - Soup-to-Nutz
 aka what i did to get from nothing to done.
 
+_note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so).  YMMV_  
+
 [Purpose of Proxmox cluster project](/76e94832927a89d977ea989da157e9dc#purpose-of-cluster)
 
 [Required Outomces of cluster project](/76e94832927a89d977ea989da157e9dc#goals-of-cluster)
 
-Start Date - First week of August 2023
 
-End Date - none
+Updates as of 9/30/2023
+This cluster is no longer a PoC and is my production cluster for my two dommain controllers.  All my initial objectives achivied and then some.  All VMs migrated from Hyper-V and working - despite some stupidty on my part - though i learnt a lot!)
 
-Updates as of 9/27/2023
-This cluster is no longer a PoC and is my production cluster for my two dommain controllers, home assistant, 2 of 3 docker VM host nodes
-
-_note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so).  YMMV_  
+I will update if and when i make major changes, redesign or add new capabilities, but to be clear i now consider this gist set complete for my needs and have no more edits planned.
 
-I will regularly update until all outcomes and todo's are achieved.
+If you spot a critical type let me know and I can change but as as these are notes for me (not a tutorial) i make no promises :-) 
 
 ## Outcomes
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)

diff --git a/proxmox.md b/proxmox.md
@@ -12,7 +12,9 @@ End Date - none
 Updates as of 9/27/2023
 This cluster is no longer a PoC and is my production cluster for my two dommain controllers, home assistant, 2 of 3 docker VM host nodes
 
-_note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so).  YMMV_  i will regularly update until all outcomes and todo's are achieved.
+_note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so).  YMMV_  
+
+I will regularly update until all outcomes and todo's are achieved.
 
 ## Outcomes
 1. [Hardware and Base Proxmox Install](/cd1a8cdd9904f43e319e438551d7f92c)

diff --git a/proxmox.md b/proxmox.md
@@ -1,9 +1,9 @@
 # ProxMox Cluster - Soup-to-Nutz
-### aka what i did to get from nothing to done.
+aka what i did to get from nothing to done.
 
-[Purpose of Proxmox Cluster Project](/76e94832927a89d977ea989da157e9dc#purpose-of-cluster)
+[Purpose of Proxmox cluster project](/76e94832927a89d977ea989da157e9dc#purpose-of-cluster)
 
-[goal of cluster](/76e94832927a89d977ea989da157e9dc#goals-of-cluster)
+[Required Outomces of cluster project](/76e94832927a89d977ea989da157e9dc#goals-of-cluster)
 
 Start Date - First week of August 2023
 

diff --git a/proxmox.md b/proxmox.md
@@ -2,6 +2,7 @@
 ### aka what i did to get from nothing to done.
 
 [Purpose of Proxmox Cluster Project](/76e94832927a89d977ea989da157e9dc#purpose-of-cluster)
+
 [goal of cluster](/76e94832927a89d977ea989da157e9dc#goals-of-cluster)
 
 Start Date - First week of August 2023
No results found