This is a second post of the series on minimal Linux VMs deployments on SmartOS hypervisor. Same as in case of Gentoo I decided to go with systemd and btrfs for system & service management and main/only filesystem respectively.

I wanted to have a small, “minimalistic” VMs on my hypervisor, so they would have very little footprint on resources. I decided to go with systemd and btrfs for system & service management and main/only filesystem respectively.

The only considered distributions up for that task (at least from my point of view) were Debian and Gentoo. I decided to start with the latter as I had less experience with it and wanted to learn my ways around.

Recently I’ve been migrating to new infrastructure – I will most definitely write about it more in separate post(s) – and I found myself in need of some centralized log server. I played a bit with different tools and eventually settled with graylog2. Current setup looks as follows:

• First node: graylog2-server + elasticsearch + mongodb
• Second node: graylog2-web

Eventually I’d love to put Elasticsearch and MongoDB on separate machine(s) and add one more node for graylog2-radio and RabbitMQ (though preferably having both on separate boxes too), but this can wait and I needed working solution as fast as possible. Speaking of which, what seems to be the…

Awhile back I decided to finally publish my dotfiles. It turned out that it’s not necessarily such good idea to split config files into so many small chunks — it’s harder to maintain when they are split like that. Few days ago I stubmled upon GitHub ❤ ~/ where I learned about rcm.

Since I’m going to write more about LVM, I decided to start with quick summary of what I’ve already posted awhile back:

• Repartitioning LUKS-crypted LVM on Debian
• Extending LVM & FS online with new disk
• Updating GRUB device.map file after adding a new disk
• Migrating to new Logical Volume
• Extend LV & FS on-line with one command

Stay tuned cause more is coming soon! (: