Can't find a vagrant image fedora/42-cloud-base

41 is present anyone knows why 42 is absent?

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...
https://codeberg.org/johanneskastl/writefreely_vagrant_libvirt_ansible
https://github.com/johanneskastl/writefreely_vagrant_libvirt_ansible

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...).

https://download.fedoraproject.org/pub/fedora/linux/releases/42/Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-libvirt-42-1.1.x86_64.vagrant.libvirt.box

(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.

https://codeberg.org/johanneskastl/ghost_vagrant_libvirt_ansible
https://github.com/johanneskastl/ghost_vagrant_libvirt_ansible

Have a lot of fun...

Another day, another vagrant-libvirt setup.

This time for MariaDB, with a server VM and a client VM. As usual, vagrant, libvirt and Ansible do the heavy lifting.

https://codeberg.org/johanneskastl/mariadb_vagrant_libvirt_ansible
https://github.com/johanneskastl/mariadb_vagrant_libvirt_ansible

Have a lot of fun...

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.

https://codeberg.org/johanneskastl/traefik_gateway-api_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/traefik_gateway-api_on_k3s_vagrant_libvirt_ansible

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

Have a lot of fun.

Dear all,

for playing around with the Ghost CMS / blog system I put together yet another vagrant-libvirt setup using Ansible and Podman Quadlets

https://codeberg.org/johanneskastl/ghost_podman_vagrant_libvirt_ansible
https://github.com/johanneskastl/ghost_podman_vagrant_libvirt_ansible

Have a lot of fun.

Just added Rocky Linux 10 (STG) to the Vagrant box collection for ARM64 systems. Have fun on your Mac, Devs! Happy coding!

Box: https://portal.cloud.hashicorp.com/services/vagrant/registries/gyptazy/boxes/rocky10.0-arm64
Collection: https://portal.cloud.hashicorp.com/services/vagrant/registries/gyptazy

I continued playing around with @OpenCloud and translated the Quickstart script into an Ansible playbook. As usual, here is the vagrant-libvirt setup to try that yourself:

https://codeberg.org/johanneskastl/opencloud_quickstart_vagrant_libvirt_ansible
https://github.com/johanneskastl/opencloud_quickstart_vagrant_libvirt_ansible

Have a lot of fun!

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:

https://codeberg.org/johanneskastl/opencloud_tronde_vagrant_libvirt_ansible
https://github.com/johanneskastl/opencloud_tronde_vagrant_libvirt_ansible

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

Have a lot of fun!

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...

https://codeberg.org/johanneskastl/nginx_reverse_proxy_podman_vagrant_libvirt_ansible
https://github.com/johanneskastl/nginx_reverse_proxy_podman_vagrant_libvirt_ansible

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.

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:
https://codeberg.org/johanneskastl/artifactory_vagrant_libvirt_ansible
https://github.com/johanneskastl/artifactory_vagrant_libvirt_ansible

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!

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.

https://codeberg.org/johanneskastl/microshift_okd_vagrant_libvirt_ansible
https://github.com/johanneskastl/microshift_okd_vagrant_libvirt_ansible

Have a lot of fun!

I found Squest (https://github.com/HewlettPackard/squest/) 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:
https://codeberg.org/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/squest_on_k3s_vagrant_libvirt_ansible

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

Have a lot of fun!

I had time to polish up my vagrant-libvirt setup for playing around with SemaphoreUI (https://semaphoreui.com/). Have a lot of fun!

https://codeberg.org/johanneskastl/semaphore_vagrant_libvirt_ansible
https://github.com/johanneskastl/semaphore_vagrant_libvirt_ansible

Currently only one VM with Semaphore. But I am working on another setup with a runner and a VM that can be managed by Semaphore.

....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.
https://codeberg.org/johanneskastl/openbao_vagrant_libvirt_ansible

I had time to update my old #Teleport #vagrant setup to work with the current @opensuse packages maintained by yours truly.

https://codeberg.org/johanneskastl/teleport_with_vagrant_libvirt

Also some roles were cleaned up, tested and are now fully compliant to #AnsibleLint...