mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

9.1K
active users

#vagrant

4 posts2 participants0 posts today

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!

Summary card of repository johanneskastl/opencloud_tronde_vagrant_libvirt_ansible
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.

Summary card of repository johanneskastl/nginx_reverse_proxy_podman_vagrant_libvirt_ansible
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!

Summary card of repository johanneskastl/artifactory_vagrant_libvirt_ansible
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!

Summary card of repository johanneskastl/microshift_okd_vagrant_libvirt_ansible
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!

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

@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

Replied in thread

@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.
codeberg.org/johanneskastl/ope

Summary card of repository johanneskastl/openbao_vagrant_libvirt_ansible
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

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

codeberg.org/johanneskastl/git

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.

Summary card of repository johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
Codeberg.orggitlab_on_k3s_vagrant_libvirt_ansibleVagrant-libvirt setup that creates a VM with k3s and installs GitLab in the cluster
Replied in thread

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

codeberg.org/johanneskastl/git
codeberg.org/johanneskastl/git

Summary card of repository johanneskastl/gitlab_vagrant_libvirt_ansible
Codeberg.orggitlab_vagrant_libvirt_ansibleVagrant-libvirt setup with a VM that is running a Gitlab instance

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

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

habr.com/ru/articles/890276/

ХабрAnsible-pull и GitLab CI/CD: когда лучше тянуть, чем толкать👋 Привет! Меня зовут Андрей, я специалист по управлению IT-инфраструктурой с опытом работы с Windows- и Linux-системами. Современная IT-инфраструктура — это живой организм, состоящий из множества...

Uuuuuuuh, #OpenBao (the open source fork of #Hashicorp #Vault) just released version 2.2.0 and now includes the UI, that was missing so far.

The package for @opensuse was adapted, tested and worked out fine. Will soon be available in #Tumbleweed!

If you want to test this out, feel free to use this vagrant-libvirt setup of mine:
codeberg.org/johanneskastl/ope

Summary card of repository johanneskastl/openbao_vagrant_libvirt_ansible
Codeberg.orgopenbao_vagrant_libvirt_ansibleVagrant-libvirt setup with an OpenBao Server and a client VM running the OpenBao Agent (and a PostgreSQL database)