I was talking to a homeless man a few years back that was a brick layer, his wife got into drugs and took his kids from him. He fought in court for them but lost (they, the kids, wanted to stay with their mom) and got slapped with pretty alimony. He eventually just quit caring, quite going to work, and decided to just live on the streets. He panhandles and saves up to get a hotel room every few weeks, cleans up, and goes to the bars to pick up chicks.
At least all according to him while we were chatting
There is an ironically a huge opportunity for upheaval of corporations because they are actually giving up huge amounts of control and leverage on their part.
Like at what point is their essentially company who's sole job being brand making and management of contracts going to be side stepped?
For public facing companies I kind of prefer this tbh. It also makes sense from a raising funds perspective (more owners to pay in). Employees should have voting rights and Coop or not, the union needs to exist to protect their interest too
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
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.
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!
I was talking to a homeless man a few years back that was a brick layer, his wife got into drugs and took his kids from him. He fought in court for them but lost (they, the kids, wanted to stay with their mom) and got slapped with pretty alimony. He eventually just quit caring, quite going to work, and decided to just live on the streets. He panhandles and saves up to get a hotel room every few weeks, cleans up, and goes to the bars to pick up chicks.
At least all according to him while we were chatting