Recently I was been asked to increase the MTU on the deployed openstack cluster at one of our customers. Since the beginning of my touch on openstack networking has been the hardest part to get my head around. In the first place because openstack does some nifty things on the networking path. But also cause for the use case at the customer a lot of customization has been done to get it implemented in their infrastructure.

Hence the shiver when the MTU question was been made..

Nevertheless together with a colleague who likes a challenge and has a profound knowledge …

Some weeks ago an article on hacker news got my interest. From time to time I really get an healthy dose of jealousy when people found an idea which could make them buy a tesla. My terms of someone who make a lot of money ;)

This one is so brilliant in it's simplicity that I really was flabbergasted and made me wonder why I never came up with the idea. It generates nice reports of the usage of your site which is hosted by aws. Based on the logs of the S3 bucket or the cloudfront domain you setted up …

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 …

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 …

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:

• vlan flat-neutron provider network
• layer2

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 …

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 …

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 …