gitlab and IPv6

I’m working on setting up a new server running Debian GNU/Linux and libvirt/kvm. One of the first VMs I set up was a GITLAB server.

Two thinks to remeber:

1. You can’t install GITLAB from an IPv6 only server because their servers don’t have IPV6 (well it’s only 2017).

2. The gilab Debian package brings it’s own data base and and Webserver (ngnix). In the default setup ngnix will onyl listen to IPv4. You have to edit /opt/gitlab/etc/gitlab/gitlab.rb and edit the nginx['listen_addresses'] = line.

libvirt, virt-install and Arch Linux

For years I’m using a shell script wrapper around virt-install to setup VMs. Recently I was asked to setup several VMs on Arch Linux for a training. Whatever I did, I wasn’t able to install a VM. The Console was always showing that no boot device could be found. It took some time to find out that something from qemu-arch-extra was missing. After installing this package everything worked as expected.


At DENOG8 I’ve seen several marketing only presentations marked CONFIDENTIAL.

From my point of view I think that this is only marketing: “You are our potential customers. Look how much we trust you already. We are sharing confidential marketing bullshit with you!”

v6 only

Some people may not be able to read this post because this blog as no A record anymore. I don’t care if you don’t have IPv6. It’s 2016.

For those of you who can read this: I’ll try to write some technical posts about Icinga2, libvirt/kvm and other stuff in the future.

I’m old

I just update my bio on the Froscon website an noticed that I’m getting paid for system and network administration for 20 year.

BTW: I’m giving a presentation at this years Froscon about automating Icinga2 (e.g. using Ansible/Puppet for deployment and the API for managing your monitoring config).

The Phoenix Project

The advantage of not having a project right now is that I can catch up on my reading.

A couple of day ago I finished The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.

Bill Palmer is freshly promoted head of IT operations. He runs into many problems most of you will know: People not talking to each other, processes that and tools that are too complicated to use, people just doing what they think is is right, gurus with no time to document things.

The book shows Bills way from total chaos to a productive work

BTW: I started using Kanban for myself two weeks ago (again). I’ll add a post about this after a month of using it.