eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

217
active users

#libvirt

0 posts0 participants0 posts today

So I have been playing with the WriteFreely blog system. To check out if this would work for the use case I was asked about.

I built a vagrant-libvirt setup (using the usual vagrant/libvirt/Ansible approach) as well as a package for openSUSE. The setup uses my package on Leap and Tumbleweed or the upstream binary on a third branch. Another branch will set this up behind a Nginx reverse proxy.

I'll give the package a decent spin and then send it to a devel project to get it into Tumbleweed.

Here you are, have a lot of fun...
codeberg.org/johanneskastl/wri
github.com/johanneskastl/write

Codeberg.orgwritefreely_vagrant_libvirt_ansibleVagrant-libvirt setup with a VM that runs WriteFreely

Hey @fedora,

are there any plans to release the #Vagrant box for #Fedora42 to app.vagrantup.com?

There is already a box available on the Fedora server, but without metadata (which makes updates hard...).

download.fedoraproject.org/pub

(I know Vagrant is no longer used widely and Hashicorp messed up with the whole licensing trouble, but having an existing box available easiy would really be appreciated nontheless...)

Have a nice day, everyone!

Having fun with the Ghost CMS.

The installation is only supported on Ubuntu. And is tailored to Ubuntu and thus does not recognized Nginx installations on other operating systems.

I put together a vagrant-libvirt setup using Ansible that does the tricky bits itself. Currently supporting AlmaLinux 10, openSUSE Tumbleweed and Fedora 41, see the different branches.

This is a "production" setup of Ghost, i.e. using a MariaDB database instead of sqlite3.

codeberg.org/johanneskastl/gho
github.com/johanneskastl/ghost

Have a lot of fun...

Codeberg.orgghost_vagrant_libvirt_ansibleVagrant-libvirt setup with a VM running the Ghost CMS

In case you want to get your hands dirty with Traefik, Kubernetes and the new GatewayAPI, I got you covered.

Here is another vagrant-libvirt setup that has #k3s, #Traefik and a #Nginx deployment. Instead of using a #Kubernetes #ingress or a Traefik ingressroute, this setup uses the #GatewayAPI resources like Gateways and HTTPRoutes.

codeberg.org/johanneskastl/tra
github.com/johanneskastl/traef

As usual, #Ansible does the heavy lifting and deploys everything in the cluster.

Have a lot of fun.

Codeberg.orgtraefik_gateway-api_on_k3s_vagrant_libvirt_ansibleVagrant-libvirt setup with k3s, Traefik and Nginx, reachable by using the Kubernetes Gateway API resources
#k8s#DevOps#vagrant
Replied in thread

@dragotin @darix @OpenCloud @opensuse

Here is the vagrant-libvirt setup I currently use to test the new package:
codeberg.org/johanneskastl/ope
github.com/johanneskastl/openc

Most boilerplate and surrounding things are fine, the executable runs, but currently the setup is broken due to missing assets / assets not being created.

As stated in the README, work in progress under heavy development... :-)

Codeberg.orgopencloud_opensuse_vagrant_libvirt_ansibleVagrant-libvirt setup running OpenCloud in a VM using the openSUSE package (I am currently working on...)

Aaaaand another one:

I played around with @Tronde's #OpenCloud #Ansible collection.

Easy to use, feature-rich and very nice in general. Get up and running with a OpenCloud container via Podman in a matter of minutes.

Here is a vagrant-libvirt setup using that Ansible collection:

codeberg.org/johanneskastl/ope
github.com/johanneskastl/openc

(Actually, it is using a fork that contains some fixes, links to the pull requests are in the README).

Have a lot of fun!

Codeberg.orgopencloud_tronde_vagrant_libvirt_ansibleVagrant-libvirt setup that runs OpenCloud in a VM with Podman, using tronde's nice Ansible collection

New treat incoming: I played around with #Podman and #Nginx as a #ReverseProxy. And as usual I ended up creating a new vagrant-libvirt setup...

codeberg.org/johanneskastl/ngi
github.com/johanneskastl/nginx

One container running as a server (with a very valuable index.html...) and another container as reverse proxy.

Two branches, one with quadlets (where everything worked out of the box) and another running "normal" containers.

Codeberg.orgnginx_reverse_proxy_podman_vagrant_libvirt_ansibleVagrant-libvirt setup that runs a Nginx reverse proxy in a VM using Podman

In in the last two week I tried to get the vagrant-libvirt setup for #Artifactory up and running.

I now have a kind-of-working setup:
codeberg.org/johanneskastl/art
github.com/johanneskastl/artif

This #vagrant setup creates a VM and installs the official Artifactory OSS version. It works kind of well in my tests. However, I deem the official systemd unit broken by design (separate toot following). So this setup installs a new unit that worked better in my tests (but not perfect, which I think is caused by the official startup scripts).

Have fun!

Codeberg.orgartifactory_vagrant_libvirt_ansibleVagrant-libvirt setup that creates a VM and installs Artifactory (OSS)

The #okd project has released a version of #microshift based on OKD, so of course I had to try it out.

For those not familiar with it, OKD is a kubernetes distribution and is the "upstream" of RedHat's OpenShift.

Here is a single-VM vagrant-libvirt setup that installs, configures and starts the Kubernetes cluster using #Ansible.

codeberg.org/johanneskastl/mic
github.com/johanneskastl/micro

Have a lot of fun!

Codeberg.orgmicroshift_okd_vagrant_libvirt_ansibleVagrant-libvirt setup that creates a VM and installs a Microshift (micro-okd) kubernetes cluster

I found Squest (github.com/HewlettPackard/sque) recently, which is a self-service portal built on top of #AWX #RedHat #AAP (Ansible Automation Platform). Of course I had to try this out...

@christianhuth put together a Helm chart, while I tried to get upstream's way of deploying to work (they are using an #Ansible playbook-role construct to install this into #Kubernetes).

Here is the first result, the helm-based #vagrant #libvirt setup:
codeberg.org/johanneskastl/squ
github.com/johanneskastl/sques

(The ansible branch using upstream's deployment will follow, once I get it working with vagrant-libvirt...)

Have a lot of fun!

GitHubGitHub - HewlettPackard/squest: Service request portal on top of Ansible Tower/AWXService request portal on top of Ansible Tower/AWX - HewlettPackard/squest

....aaaaaand #OpenBao (the fork of #Hashicorp #Vault) is on its way to @opensuse #Tumbleweed in the latest version 2.2.1. Since 2.2.0 the webui is included in OpenBao, so this can be a full replacement for Vault!

Looking forward to doing more testing with it!

In case you want to try it out, here is a #vagrant #libvirt setup using #Ansible to prepare an OpenBao server VM and a client using a secret.
codeberg.org/johanneskastl/ope

Codeberg.orgopenbao_vagrant_libvirt_ansibleVagrant-libvirt setup with an OpenBao Server and a client VM running the OpenBao Agent (and a PostgreSQL database)
Continued thread

As an update, I could not reproduce it on Fedora 40, but I could on #OpenSUSE Tumbleweed and #Ubuntu 25.04.

However, it seems that it's reproducible in KubeVirt 1.2.2 but Fedora 42 does not have this issue with KubeVirt v1.3.1. For reference, Harvester 1.4.1 with Kubevirt 1.2.2 came out in January of this year and Harvester 1.4.2 with 1.3.1 came out in March of this year.

I'm seeing a nasty virtio network regression with the 6.14 Linux kernel on Fedora 41, 42, and OpenSUSE Tumbleweed. "bad gso: type 4" and http traffic crawling to ISDN speeds. Specifically http/s, somehow iperf tcp performance is fine, but dnf, curl, wget, etc, are affected. Trying to gather what info I can and I'll file a bug about it soon unless someone beats me to it.