STT really helped me. Plus then you can search for key words!

Now my eye sight is worse and TTS is useful lol

Fair. Maybe a separate repo makes sense for the wild West of vibe apps, but flathub is really more focused on end users whom will absolutely commit a murder if they find out the documentation they have been using and failing to do what they want was just gas lighting them.

Also not to be confused with charasmatic cannible Sweeny Todd

Again same vibe

I mean it’s already for Java what more indication do you need to not use it? /S

Good to see AMD fighting as hard as they always do to avoid winning against Nvidia. Adoption of their tool that makes their products useful too high? Better put the stop to that lmao

Because the network effect is the primary reason GitHub is the defacto forge. There some pretty large FOSS orgs on gitlab though, but it’s inherently splintered without federation.

From an enterprise standpoint, there are a surprising amount of organizations so big they have several gitlabs running, but tons of friction again because of the splintered nature that takes up.

They did care, then AI became the time sink.

Have the filesystem compress by default and ship that?

I know you can do it with zfs. Export a snapshot of a fs with compression enabled. I’m less sure if you can do it with a btrfs, lvm, or xfs though. I know they support fs level compression though.

Heck every conference I go to I pester Gitlab about it. It’s always “ehh it’s on the road map”. Honestly it really is the solution to that problem space

That’s fair it has loss leaders and network effects more so. The vendor lock in is non-git, non-ci side. So issues, orgs, etc. Actually you can see where they embraced opensource vs extending solely by the degree it is vendor locked.

If they stole it, it’s a loss leader, if they made it, it’s vendor locked.

Well there used to be an island where the majority of folks involved in these kind of deals went to, but the owner landed in some legal trouble and decided to hang somewhere else instead

Honestly if I had one wish is that government would be banned for saying any rental agreement was an investment.

It’s so frustrating, and brings me hope to see it change, that RnD and infrastructure investment funds got put into software rental agreement for windows and VMware and more recently into proprietary Cloud ecosystems.

Like you own nothing from that. That money is gone from the public good. It’s not an investment. I didn’t invest in an apartment, I rented, I don’t have any value left from that agreement I had my wants and needs temporally satisfied.

That is just the constant issue these people put in the public trust are learning but have to held to task to.

Its perfectly adequate generating simple scripts if you know what it’s doing or complex programs IF.you have a “harness” which is to say tones of well defined scopes, design docs, coding guidelines, and a dev and test environment with written and automatic unit and integration tests.

Basically every devs wish lists. You get adequate complex coding results.

Pair programing with a mentor shouldn’t be a day to day thing. Like why waste the time and put so much pressure on the trainee like that anyways?

Vim unless I can neovim.

Being able to change configs on headless systems was my gateway, now I just prefer it

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

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?