@dragotin @darix @OpenCloud @opensuse

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

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

#openSUSE #OpenCloud #Ansible #vagrant #libvirt #hellyeah #packagerslife

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!

#OpenCloud #vagrant #libvirt #Ansible #filemanagement #selfhosting #hellyeah

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!

#OpenCloud #vagrant #libvirt #Ansible #container #Podman #quadlets #hellyeah

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.

#DevOps #Nginx #Ansible #vagrant #libvirt #podman #containers #hellyeah

The latest release of the #Chocolatey Test Environment as a VirtualBox #Vagrant box made me wonder how to use it in #VMware Workstation. This terrible guide that you should not use. Unless you need to. It works. But don't do it.

Using the Chocolatey Test Environment under QEMU
https://blog.pauby.com/post/convert-vagrant-virtualbox-vmdk-to-qemu-qcow2/

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!

#DevOps #Artifactory #vagrant #libvirt #Ansible

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!

#k8s #Kubernetes #Ansible #vagrant #libvirt #okd #microshift #microOKD #DevOps

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!

#DevOps #k8s #selfserviceportal #squest #hellyeah

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.

#vagrant #libvirt #Ansible #SemaphoreUI #Semaphore #OpenTofu #Terraform #DevOps #IaC

@a A #Vagrant environment is a life saver for that
One-use setup to try out the latest cool software in the blocks, and the production servers can stay as quiet and stable as they can

@swelljoe um.. #Vagrant called (*) to remind them they can destroy their image and spin up a fresh one without having to reinstall anything, let alone an Operating System. Even if they were dumb enough to delete the cached box, they should be able to re-provision from the code in the Vagrant file without having to do all that manual work. All this IaC makes it much easier for them to ignore that log file 🤣

* sure, this is an old metaphor, but Vagrant isn't exactly fresh either 😋

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

#secretmanagement #kms #devops

OK, I managed to improve lots of things in those setups and make the setup more reliable (even in case it takes really really long for everything to be up).

https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible

Now with four branches, one for Gitlab installed via helm chart and one using the Gitlab Operator.
And each of them with and without a Gitlab Runner being installed into the cluster.

#GitLab #Kubernetes #k3s #devops #Ansible #vagrant #libvirt #hellyeah

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

#Teleport #Ansible #vagrant #homelab #ssh

Here you are: Vagrant-Setup with Ansible deploying k3s and GitLab inside k3s.

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

Currently without the Runner, that comes next.

#GitLab #DevOps #k3s #kubernetes #Ansible #vagrant #hellyeah

@jwolynko When it comes to on-prem, GitLab still seems to be the preferred solution (GitHub enterprise seems to be deprecated, thank the universe for that). I personally am running Forgejo wherever possible.

But most of the customers I know do run some form of GitLab. And I wanted to make sure I had a working test setup, whenever I need one. Currently I wanted to do some testing for GitLab runners on Kubernetes.

The package based ones are pretty simple to setup (not talking about maintenance, of course).

https://codeberg.org/johanneskastl/gitlab_vagrant_libvirt_ansible
https://codeberg.org/johanneskastl/gitlab_and_runner_vagrant_libvirt_ansible

#GitLab #DevOps #Kubernetes #vagrant #Ansible

Here is a small Docker CLI plugin I did, that launches a Vagrant-managed VM using Parallels on macOS and sets up a Docker context for it. Useful if you want a lightweight, no-surprises alternative to Docker Desktop — works on Intel & ARM, with binfmt for cross-arch builds.

"docker vagrant up" and you're ready to go.

https://github.com/fpatz/docker-vagrant

#docker #vagrant #macos #cli #devtools

#Ubuntu no longer produce #vagrant box images for the current LTS (24.04).

I know bento do make a 24.04 image, but my developers and I often hit network issues with it.

Is it time to move away from vagrant and over to #docker?

Ansible-pull и GitLab CI/CD: когда лучше тянуть, чем толкать

Ansible — мощный инструмент автоматизации, но его push-модель не всегда удобна. Когда требуется централизованный контроль большого числа серверов, могут возникнуть проблемы: 📌 Нестабильные сети → клиент может быть недоступен во время обновления. 📌 Сложности с NAT → серверы находятся в закрытых "серых" сетях. 📌 Перемещаемые устройства → подключаются к сети только время от времени. Разбираемся, как ansible-pull решает эти проблемы на стенде , а также настраиваем CI/CD для тестирования и совместной разработки Ansible-ролей

https://habr.com/ru/articles/890276/

#ansiblelint #ansible #ansible_playbook #vagrant #docker #dockercompose #dockerfile #gitlab #git #cicd

@leyrer kennt jemand eine alternative zu #vagrant