home.social

#hellyeah — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #hellyeah, aggregated by home.social.

  1. To whom it may concern:

    I have started testing the fish shell. It looks promising and has lot of things built-in. But I have a very large and long grown bashrc with aliases and whatnot. Might take a while to port it over completely.

    #Shell #Linux #fish #HellYeah

  2. OK, so I took the plunge and finally (after ~7 years of thinking about it and being distracted by other things) started playing around with OpenStack and kolla-ansible.

    The quick start guide makes it sound simple and it really is. After some fiddling with the proper kolla-ansible versions I had a working installation (single node, but still impressive).

    Encountered some bugs on the way (and reported them), which is to be expected by using a not-yet-released version (stable/2026.1 git branch).

    Next step is trying to find documentation on how to use it to do a multi-machine installation where things like storage get important and interesting.

    I'll keep you posted. If you do not hear from me again, you know why... :-)

    #OpenStack #kolla-ansible #HomeLab #HellYeah #Virtualization #Cloud

  3. OK, so I took the plunge and finally (after ~7 years of thinking about it and being distracted by other things) started playing around with OpenStack and kolla-ansible.

    The quick start guide makes it sound simple and it really is. After some fiddling with the proper kolla-ansible versions I had a working installation (single node, but still impressive).

    Encountered some bugs on the way (and reported them), which is to be expected by using a not-yet-released version (stable/2026.1 git branch).

    Next step is trying to find documentation on how to use it to do a multi-machine installation where things like storage get important and interesting.

    I'll keep you posted. If you do not hear from me again, you know why... :-)

    #OpenStack #kolla-ansible #HomeLab #HellYeah #Virtualization #Cloud

  4. OK, so I took the plunge and finally (after ~7 years of thinking about it and being distracted by other things) started playing around with OpenStack and kolla-ansible.

    The quick start guide makes it sound simple and it really is. After some fiddling with the proper kolla-ansible versions I had a working installation (single node, but still impressive).

    Encountered some bugs on the way (and reported them), which is to be expected by using a not-yet-released version (stable/2026.1 git branch).

    Next step is trying to find documentation on how to use it to do a multi-machine installation where things like storage get important and interesting.

    I'll keep you posted. If you do not hear from me again, you know why... :-)

    #OpenStack #kolla-ansible #HomeLab #HellYeah #Virtualization #Cloud

  5. OK, so I took the plunge and finally (after ~7 years of thinking about it and being distracted by other things) started playing around with OpenStack and kolla-ansible.

    The quick start guide makes it sound simple and it really is. After some fiddling with the proper kolla-ansible versions I had a working installation (single node, but still impressive).

    Encountered some bugs on the way (and reported them), which is to be expected by using a not-yet-released version (stable/2026.1 git branch).

    Next step is trying to find documentation on how to use it to do a multi-machine installation where things like storage get important and interesting.

    I'll keep you posted. If you do not hear from me again, you know why... :-)

    #OpenStack #kolla-ansible #HomeLab #HellYeah #Virtualization #Cloud

  6. OK, so I took the plunge and finally (after ~7 years of thinking about it and being distracted by other things) started playing around with OpenStack and kolla-ansible.

    The quick start guide makes it sound simple and it really is. After some fiddling with the proper kolla-ansible versions I had a working installation (single node, but still impressive).

    Encountered some bugs on the way (and reported them), which is to be expected by using a not-yet-released version (stable/2026.1 git branch).

    Next step is trying to find documentation on how to use it to do a multi-machine installation where things like storage get important and interesting.

    I'll keep you posted. If you do not hear from me again, you know why... :-)

    #OpenStack #kolla-ansible #HomeLab #HellYeah #Virtualization #Cloud

  7. I think I could solve this, after some more fiddling.

    I tried this again once I was home and could check from both sides more easily.

    TL;DR Damn you, providers handing our DNS answers even if they are not existing...

    Long story:

    The client's connection request went via IPv6, as apparently it got a valid AAAA DNS answer, even though the Wireguard server's hostname only has an A record in the authoritative DNS server. Seems like some provider inbetween messed with this or did the "not found, here is a page full of ads..." thingy.

    After restricting the client to only use IPv4, everything was fine. Pings worked from both client and server, networks behind the server were reachable.

    #Wireguard #Linux #VPN #HomeLab #SelfHosting #Debugging #Network #AdminLife #HellYeah

  8. I think I could solve this, after some more fiddling.

    I tried this again once I was home and could check from both sides more easily.

    TL;DR Damn you, providers handing our DNS answers even if they are not existing...

    Long story:

    The client's connection request went via IPv6, as apparently it got a valid AAAA DNS answer, even though the Wireguard server's hostname only has an A record in the authoritative DNS server. Seems like some provider inbetween messed with this or did the "not found, here is a page full of ads..." thingy.

    After restricting the client to only use IPv4, everything was fine. Pings worked from both client and server, networks behind the server were reachable.

    #Wireguard #Linux #VPN #HomeLab #SelfHosting #Debugging #Network #AdminLife #HellYeah

  9. I think I could solve this, after some more fiddling.

    I tried this again once I was home and could check from both sides more easily.

    TL;DR Damn you, providers handing our DNS answers even if they are not existing...

    Long story:

    The client's connection request went via IPv6, as apparently it got a valid AAAA DNS answer, even though the Wireguard server's hostname only has an A record in the authoritative DNS server. Seems like some provider inbetween messed with this or did the "not found, here is a page full of ads..." thingy.

    After restricting the client to only use IPv4, everything was fine. Pings worked from both client and server, networks behind the server were reachable.

    #Wireguard #Linux #VPN #HomeLab #SelfHosting #Debugging #Network #AdminLife #HellYeah

  10. I think I could solve this, after some more fiddling.

    I tried this again once I was home and could check from both sides more easily.

    TL;DR Damn you, providers handing our DNS answers even if they are not existing...

    Long story:

    The client's connection request went via IPv6, as apparently it got a valid AAAA DNS answer, even though the Wireguard server's hostname only has an A record in the authoritative DNS server. Seems like some provider inbetween messed with this or did the "not found, here is a page full of ads..." thingy.

    After restricting the client to only use IPv4, everything was fine. Pings worked from both client and server, networks behind the server were reachable.

    #Wireguard #Linux #VPN #HomeLab #SelfHosting #Debugging #Network #AdminLife #HellYeah

  11. I think I could solve this, after some more fiddling.

    I tried this again once I was home and could check from both sides more easily.

    TL;DR Damn you, providers handing our DNS answers even if they are not existing...

    Long story:

    The client's connection request went via IPv6, as apparently it got a valid AAAA DNS answer, even though the Wireguard server's hostname only has an A record in the authoritative DNS server. Seems like some provider inbetween messed with this or did the "not found, here is a page full of ads..." thingy.

    After restricting the client to only use IPv4, everything was fine. Pings worked from both client and server, networks behind the server were reachable.

    #Wireguard #Linux #VPN #HomeLab #SelfHosting #Debugging #Network #AdminLife #HellYeah

  12. Chad Gray (Mudvayne/HELLYEAH) Played His First Solo Show Last Night, Setlist & Footage Available

    Last night (April 24th) saw Mudvayne/HELLYEAH vocalist Chad Gray play his first ‘30 Years Of Madness” solo show.…
    #NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Music #chadgray #Entertainment #HELLYEAH #Mudvayne
    newsbeep.com/us/606903/

  13. Chad Gray (Mudvayne/HELLYEAH) Played His First Solo Show Last Night, Setlist & Footage Available

    Last night (April 24th) saw Mudvayne/HELLYEAH vocalist Chad Gray play his first ‘30 Years Of Madness” solo show.…
    #NewsBeep #News #US #USA #UnitedStates #UnitedStatesOfAmerica #Music #chadgray #Entertainment #HELLYEAH #Mudvayne
    newsbeep.com/us/606903/

  14. Reshelving at the zine library today and my zac efron fanzine was in the pile #hellyeah

  15. Reshelving at the zine library today and my zac efron fanzine was in the pile #hellyeah

  16. Reshelving at the zine library today and my zac efron fanzine was in the pile #hellyeah

  17. Reshelving at the zine library today and my zac efron fanzine was in the pile #hellyeah

  18. Two things I noticed:

    The microshift-olm package provices the Operator Lifecycle Manager, but apparently only a very limited subset. I could not get it working at all.
    github.com/openshift/microshif

    There are packages for ArgoCD, called microshift-gitops. Those install a part of ArgoCD. You get the repo-server, redis and the application-controller. But no WebUI. I have not found out yet, if I can still use the argocd CLI to connect to the cluster and e.g. sync an application, as it normally (AFAIK) relies on the web component being exposed via ingress, loadbalancer or port-forward. I'll report back if I get it working. Other than the missing WebUI, it does what ArgoCD is supposed to do: sync stuff into the cluster. Nice.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  19. Two things I noticed:

    The microshift-olm package provices the Operator Lifecycle Manager, but apparently only a very limited subset. I could not get it working at all.
    github.com/openshift/microshif

    There are packages for ArgoCD, called microshift-gitops. Those install a part of ArgoCD. You get the repo-server, redis and the application-controller. But no WebUI. I have not found out yet, if I can still use the argocd CLI to connect to the cluster and e.g. sync an application, as it normally (AFAIK) relies on the web component being exposed via ingress, loadbalancer or port-forward. I'll report back if I get it working. Other than the missing WebUI, it does what ArgoCD is supposed to do: sync stuff into the cluster. Nice.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  20. Two things I noticed:

    The microshift-olm package provices the Operator Lifecycle Manager, but apparently only a very limited subset. I could not get it working at all.
    github.com/openshift/microshif

    There are packages for ArgoCD, called microshift-gitops. Those install a part of ArgoCD. You get the repo-server, redis and the application-controller. But no WebUI. I have not found out yet, if I can still use the argocd CLI to connect to the cluster and e.g. sync an application, as it normally (AFAIK) relies on the web component being exposed via ingress, loadbalancer or port-forward. I'll report back if I get it working. Other than the missing WebUI, it does what ArgoCD is supposed to do: sync stuff into the cluster. Nice.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  21. Two things I noticed:

    The microshift-olm package provices the Operator Lifecycle Manager, but apparently only a very limited subset. I could not get it working at all.
    github.com/openshift/microshif

    There are packages for ArgoCD, called microshift-gitops. Those install a part of ArgoCD. You get the repo-server, redis and the application-controller. But no WebUI. I have not found out yet, if I can still use the argocd CLI to connect to the cluster and e.g. sync an application, as it normally (AFAIK) relies on the web component being exposed via ingress, loadbalancer or port-forward. I'll report back if I get it working. Other than the missing WebUI, it does what ArgoCD is supposed to do: sync stuff into the cluster. Nice.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  22. Two things I noticed:

    The microshift-olm package provices the Operator Lifecycle Manager, but apparently only a very limited subset. I could not get it working at all.
    github.com/openshift/microshif

    There are packages for ArgoCD, called microshift-gitops. Those install a part of ArgoCD. You get the repo-server, redis and the application-controller. But no WebUI. I have not found out yet, if I can still use the argocd CLI to connect to the cluster and e.g. sync an application, as it normally (AFAIK) relies on the web component being exposed via ingress, loadbalancer or port-forward. I'll report back if I get it working. Other than the missing WebUI, it does what ArgoCD is supposed to do: sync stuff into the cluster. Nice.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  23. Dear Openshift and Kubernetes users,

    after my single-node OpenShift cluster broke for the third time (pods not coming up, no idea what went wrong this time), I reinstalled the machine and tried MicroShift.

    I overlooked the tiny detail in the documentation that there are subscription repos for RHEL10, but only packages for RHEL9. So I had to reinstall my machine after trying RHEL10 first.

    In general microshift seems to be an easy way to get a OpenShift-like "cluster" running on a single machine. I'll report back once I did some more thorough testing.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  24. Dear Openshift and Kubernetes users,

    after my single-node OpenShift cluster broke for the third time (pods not coming up, no idea what went wrong this time), I reinstalled the machine and tried MicroShift.

    I overlooked the tiny detail in the documentation that there are subscription repos for RHEL10, but only packages for RHEL9. So I had to reinstall my machine after trying RHEL10 first.

    In general microshift seems to be an easy way to get a OpenShift-like "cluster" running on a single machine. I'll report back once I did some more thorough testing.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  25. Dear Openshift and Kubernetes users,

    after my single-node OpenShift cluster broke for the third time (pods not coming up, no idea what went wrong this time), I reinstalled the machine and tried MicroShift.

    I overlooked the tiny detail in the documentation that there are subscription repos for RHEL10, but only packages for RHEL9. So I had to reinstall my machine after trying RHEL10 first.

    In general microshift seems to be an easy way to get a OpenShift-like "cluster" running on a single machine. I'll report back once I did some more thorough testing.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  26. Dear Openshift and Kubernetes users,

    after my single-node OpenShift cluster broke for the third time (pods not coming up, no idea what went wrong this time), I reinstalled the machine and tried MicroShift.

    I overlooked the tiny detail in the documentation that there are subscription repos for RHEL10, but only packages for RHEL9. So I had to reinstall my machine after trying RHEL10 first.

    In general microshift seems to be an easy way to get a OpenShift-like "cluster" running on a single machine. I'll report back once I did some more thorough testing.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting

  27. Dear Openshift and Kubernetes users,

    after my single-node OpenShift cluster broke for the third time (pods not coming up, no idea what went wrong this time), I reinstalled the machine and tried MicroShift.

    I overlooked the tiny detail in the documentation that there are subscription repos for RHEL10, but only packages for RHEL9. So I had to reinstall my machine after trying RHEL10 first.

    In general microshift seems to be an easy way to get a OpenShift-like "cluster" running on a single machine. I'll report back once I did some more thorough testing.

    #OpenShift #MicroShift #Kubernetes #DevOps #Linux #RHEL #HellYeah #SelfHosting