1. AWS migration

    About a year ago I attended the AWSome Day at Mechelen. Back then I wrote a first draft article about it, but it got out of my sight unfortunately. I reviewed it and decided to publish it anyway.

    The event was based on their essentials course and took use through the different AWS core services (compute, storage, database and network).

    I do know it has nothing to see with open-source. But it is a part of that ultimate cloud based setup I believe in which exists in one central place from where you can manage all your virtual machines independent …


  2. Openstack static ip

    last couple of days I have been fighting with the way an static ip is configured on an openstack virtual centos 6 instance. In our specific use case we ditched as many network openstack services as possible as I previously described.

    We want to have the instances running in our current network spaces of the R&D department. In this department until some days ago we didn't had any DHCP server running. But a few weeks back we added an extra remote network space into our platform where we configured a remote compute-node.

    This is where the issues started popping …


  3. Openstack live-migration

    Some of you may already have notices others just stumbled on this post through a search engine, I have set up an openstack private cloud at one of our projects:

    We have noticed that the benefits of having a private cloud is spreading through the different teams within the organization and therefore the interest into this flexibility is growing. Since this wasn't the original use case we are encountering some design issues right now.

    For the original instances the default overcommit ratios are fine. But the request for new machines with other goals are like …


  4. Openstack layer2

    A few months ago I implemented an RDO based openstack kilo release private cloud at one of our customers for their development platform. Through time we tackled a couple of issues so the cloud could be fitted into their work flows.

    We stumbled onto some minor issues and some major ones. Let's begin with the minor ones ;)

    When upgrading the all-in-one controller before we started using the cloud in 'production' a mean bug bit us in the ankle due to a new hiera package. After some digging around a patch came to the rescue together with the exclusion of the …


  5. SMS twitter wall

    A long time ago I was active in the local scouting group. To earn some money to keep our group in a healthy financial position we organized a so called vedettweekend. It's an event where people can have a beer, vedett obviously spin a dance, enjoy a spaghetti and have a good chat with your friends.

    I always played with the idea of creating a social media wall on one of the projectors we rented for the event. But I never found/made time for it, until today.. My youngest brother is who's interests are overlapping with mine brought up …


  6. Vagrant puppet setup

    We at Inuits are using vagrant for a lot of use cases, neither you are a developer or a sysadmin you for sure will walk into it. Me, myself I do use it merely to automate the many different use cases asked by various projects. It took some time to get myself organized with this pretty nifty piece of software.

    In the beginning I used it with the default virtualization provider virtualbox later on I switched to lxc containers instead. By using those containers I already gained on performance. Spinning up and down new containers to test if an application …


  7. Openstack vlan based flat neutron network provider

    at one of my projects I was been asked to set up a private cloud for a validation platform. The whole idea behind this proof of concept is based on the flexibility to spin up and down certain instances providing some specific functionality so tests banks can be ran against them.

    As soon as the tests are finished the machines could be terminated. Those instances should be configured using some configuration management software, like puppet. That way the instances are rebuildable and could be treated as cattle.

    On the other hand, it takes about 20 minutes to build up an …


  8. Btrfs mount issue

    I decided to bootstrap my new machine with btrfs as filesystem instead of ext4 LVM volumes. By following the excellent arch-wiki btrfs page I successfully crafted a base system with sub volumes, limited on size and snapshots enabled.

    Everything went fine, installed all the other stuff I needed, pulled in my data and was ready to go.

    Obviously on that very moment disaster happened.. Due to an unexpected interrupt the journal went corrupt. When trying to boot I got stuck right after decrypted the disk failing to mount my btrfs root volume.

    Uncool, unpleasant, .. I almost got insane..

    So back …


  9. Simple monitoring

    As I already wrote about in the past I have a raspberry pi running at home. I do also have a VPS running somewhere on the interweb for an owncloud instance.

    Being a sysadmin I wanted to know when my home devices become unreachable and when the owncloud instance is down. By mail in the first place if possible by sms message for free in the ideal world.

    And guess what, I managed to reach the ideal world to monitor my instances. Over here I'll describe how I managed to do so.

    msmtp

    First of all you need to install …


  10. vagrant-setup

    In this article I'll try to describe how I use vagrant in my daily tasks as an operations dude as well as I deployed it at one of our customers to help the developers focusing on the coding part rather than the operations part.

    Vagrant

    Since the beginning of my career at inuits I'm using vagrant almost everyday. If I got payed every time I spin up a box I could have bought that tesla already some years ago! But unfortunately I'm not :)

    For almost 99% of the use cases I use this nifty tool it's related to puppet. Writing …


Page 2 / 6