Oh what’s the name of that conference? That would be very cool to listen for insights from for sure!
Oh what’s the name of that conference? That would be very cool to listen for insights from for sure!


I really enjoy the pikvm and the switcher for my home lab. Redfish support gets fishy with a switcher if that is a concern though.
I do love a good mesh for a cluster block though. My next next next project is using KubeOVN to turn my cluster block into a switch with “out” connections to connection other devices (wifi, laptop, cameras, etc) to it as my network router and of course upstream from the modem and hotspot for Internet connection.


I would recommend 4-5 nodes. 5 if you want true high availability. 4 still requires some intervention in case of failure.
Just because it’s bare metal. Got to think of your Mean Time to Repair (MTTR) which is to say if a whole node goes bust how long will it take to potentially order and install a new one.
If you go kubernetes (k8s) I would recommend rke2 or k3s. They are really straightforward setups and pretty enterprise ready out of the box.
If you have a hard requirement for Ceph I would recommend doing Rook-Ceph which makes deploying and management a lot easier by letting k8s handle it. For simpler but less performant (in my testing) persistent volumes (PVs) like ceph Longhorn is really easy to deploy and manage.
For backups Velero is really nice for apps in your cluster, since it can be done per namespace and include PV data too. Rke2/k3s both have nice etcd (the backend data base for k8s) snapshoting and backup tools too for full disaster recovery.
Rke2/k3s both have ways to auto deploying charts from the filesystem too https://docs.rke2.io/add-ons/helm
This is a good stepping stone for GitOps imho. If that matters to you at all. Starting with just having a git dir for these files, then later doing some like ArgoCD
I would also recommend, since you are looking at hyper converged storage have dedicated network lines for it is generally recommended. So create a bond of two ports per node just for storage, tag them with their own vlan, and in your setup of rook or longhorn specific that vlan interface as the device for data to flow.
Pxe boot is also nice at this scale, either setup on your router (OpenWrt has decent support), you maintance laptop/machine, and/or do something like Tinkerbell (cloud native pxe from your k8s cluster!). It’s just nice to be able to blow away a node and rebuild if you are tinkering a lot.
Remember cattle not pets, and welcome to the range cowpoke!


The pikvm and pikvm switch are really fun tbh


Huh cool. So Declaritive programming like kube manifests but for a given interpreter or meta-programmer instead of the k8s API or operator?


I mean even more options there like Longhorn or Rook-Ceph


I mean yeah. This was the very reason to dump a ton into “the metaverse” in order to maximize possible data collection
It’s crazy because ethenol COULD be just a byproduct from food production. Talking to farmers about a decade ago that what they were aiming for. Basically a step before just tilling it or burning it back into the field if it was misshappen (consumers don’t buy ugly veggies) or worse infested/rotting.
The subsidy structure messed that up apparently. The subsidized crop insurance made it not worth it, plus the ethanol subsidies required dedicated fields.
I 100% would rather see solar over dedicated ethanol fields and all of the water usage and pollution they represent.
That’s how I felt with autism for sure. Not formally diagnosed but to go “oh most people actually naturally and subconsciously are aware of other peoples micro expressions and do not have to conciously decide to “turn on” that part of themselves when talking to other people” and explaining some of the biggest hurdles of my developmental life was a huge relief.
Like I was getting pretty misanthropic for a bit because 1 I was getting bullied by kids and adults alike for not “just getting it” and 2 thinking most people consciously sat down and choose to be jerks and inconsiderate.


That would be the second. The first would cover the right to share information about building your own uncensored 3d printer and designs and plans for legal arms.
I actually prefer that visual metaphor more. The locked box makes me unsure about what unlocks it, just seeing the wrong tool leaves more options open.


Or “we poorly implemented security controls for a system, it must have been so smart to have data leakage”


There are cases of but also on going programs.
Their building a Prison System ™️ regardless, open source (e.g. Linux) just offers SOME protections.
We have to do more regardless, but it’s still all part of the good fight in my book


I wonder what entails “fully protected”. Encryption? What kind? Etc


Bad form. Breaks SLSA some. Breaks some CVE tracking tools too.
If the patch introduces a vulnerabilty or breaking issue how would it be tracked?


Cars are useful where rual living makes sense. The sense breaks down fast if you dont need to pass acres of fields.


Because IF it is superuseful tool and you are being paid to dev then you will have to explain why. Like if a framer showed up to a construction site and refused to use power tools


Honestly zfs, btrfs, and lvm really do this so well i forget that traditional partitions exists
I’m very biased towards thinking we need better systems thinking. Treat each patient like a the ecosystem we are, you know?
Mostly out of frustration on how as a sysadmin and a gardener I seemed to take more time to consider how various systems and components interacted with each other we making changes or addressing problems then most my life time of medical experiences. Those have been largely problem-fix type thinking, where you try to as fast as possible bandaid a problem and move it to “solved” as fast as possible.
To give you an example what that would look like to me (and my biases). Patient Bob comes in saying his ear hurts. You process him in, check his vitals, run some basic diags related to his ear canals, sinuses, etc. Cross reference his past health data. Cross reference public health data related to where he is and has been. If additional tests to help narrorow it down, get those done. Start a treatment plan.
That is unchanged largely. This is where the difference happens. His case is now on the backlog to follow up on. If this is an chronic condition then the doctor should follow up with specialists and work on a long term care plan and hospital reach back out to them when they need more information or have some more information on the long term plan.
This is true for ANY chronic condition or worrying diag result, until they are resolved.
If this comes down to “known issue, no solution” problem then a team that interfaces with Universities, pharmasuticals, medical equipment manufacturers, etc should be signaling to them they need to start researching/making something etc