@withenoughcoffee.com loved the shout-out for George Washington Carver during the episode! I grew up in SW Missouri, visiting the national park and hearing about all the things he discovered. He is an excellent example of curiosity and persistent determination.

After I got OpenBao running in my home lab, I moved on to standing up an OpenFGA instance so that I could eventually integrate it with Incus, then after I got that in place I realized I also needed Keycloak… so after OpenFGA, I setup Keycloak. At some point I need to actually integrate it with Incus

This is the full command I've used:
whisper \
--model large \
--language Turkish \
--task translate \
--compression_ratio_threshold 2.4 \
--logprob_threshold -1.0 \
--no_speech_threshold 0.6 \
--condition_on_previous_text False \
--verbose True \
--threads 6 \
--fp16 False \
input/video_file.mp4

I think most of my success eliminating the looping was from adjusting these options:
--compression_ratio_threshold 2.4 \
--no_speech_threshold 0.6 \

I found a bit of information about what some of the options do here: github.com/openai/whisp...

It seems to do this more on long form content I think where there are long periods of silence or something. I’ve had a bit of success by tweaking some of the command line arguments to produce transcripts that don’t get stuck in loops myself.

I was able to get OpenBao working in my home lab earlier this week. I wanted to replicate the functionality I have used Google Secret Manager or AWS Secret Manager for in the public cloud and have something similar in my home cloud. It's working great. #openbao #ansible #opentofu #incus

In the latest episode of Fork Around and Find Out we ask Brian Grant what's next for Infrastructure as Code and why it has reached its limits for usefulness.

Listen now: https://www.fafo.fm/2

My JetKVM arrived today, had it set up in seconds remotely controlling another system, set a DHCP reservation for it on my network, and added a DNS entry. Now I can move it to any device in my homelab. Thank you @jetkvm.bsky.social for such a great job on this product! #homelab #jetkvm

It turns out you can add a filter config setting to the host lvm config file so that the host will ignore the guest devices that show up as ZFS volumes on the host. This seems to have fixed my issues in some initial testing.

So many things happened with Incus in 2024 (stgraber.org/2025/01/04/i...), and I now have 4 different systems set up as standalone hosts. I have 2 mini-pc x86 systems, and 2 Raspberry Pis with NVMe storage. I'm still working on trying to get a cluster of 3 other mini-pcs functional.

On the guest `lvm pvs` displays the attached disk in the guest VM (/dev/nvme0n1), but on the host `lvm pvs` displays the zfs volume (/dev/zd240) that was assigned to the VM. I'm still trying to make sense of what's going on here and why.

I found that this somehow relates to lvm, and in the guest machines there is a configuration task for bootstrapping a Ceph OSD with a command `ceph-volume lvm create` and this is applied to an entire attached disk. On the host if I remove the volume groups it lets me destroy the test cluster.

I've been working on incus-deploy (github.com/lxc/incus-de...) and ran into this issue where when destroying the test cluster, it would fail to destroy the attached disk because it said the zfs volumes were busy, even if I shut down the systems first.

When money talks, sticking to your morals can be tough.

Kelsey Hightower joins us on the first-ever episode of the FAFO Podcast to talk about the delicate balance between personal principles and paychecks for aspiring tech professionals:

https://buff.ly/40jhzAD