Quality of service…

Most of the time when we try to look at some new software we catch some bugs, have compatibilty problems and so on.

Let me give an example:
We work with a Ubuntu Desktop on an virtual environment and wanted to upgrade it to the newest 17.04 release because our main working tool (terminator) crashed every once in a while letting you sit there without your already opened ssh sessions to many servers or with open vi’s with configuration files / script code / …
Upgrading wasn’t that problem – we used the software updater and everything was fine. Until our monitoring software (zabbix) wrote us an e-mail about a problem with our configuration management agent (puppet) – and BAM, there was the first problem…
So i wanted to install a new puppet agent via the puppet debian repositories -> actually no debian package for ubuntu 17.04…
Next problem -> the upgrade also removed the old puppet package which included facter -> so our monitoring reported a backup problem, because our backup script uses facter variables… the backup works but the monitoring part isn’t…

That’s only one single example but especially when it comes to docker, which is really a great enhancement for IT in general, there are bugs and error’s (not only docker itself) everywhere.

So, getting a system up and running with quality is really hard work with lot’s of testing, searching, reading & implementing.

For me, my part is to raise quality by trying to get any system to a certain standard which includes backup / monitoring / configuration management & scripts for automation. I think these are four of the many important things when developing new systems.

Okay, Houston, we’ve had a problem here.

sdr

This quote perfectly reflects the essence of what makes our job as DevOps thrilling. Sometimes its like on Apollo 13. You are writing an e-mail and just one second later the master caution is triggered and you have no idea what happend. And for me that is the moment where our job gets out of the often boring daily business and the engineer within us awakens. We literally take our slide rulers and we do what we can do best as Einstein said: “Scientists investigate that which already is; Engineers create that which has never been.”

Therefore on this blog I will write about all that technology and engineer stuff that surrounds me like a satellite and about things that I am interested in. And sometimes that will be sarcastic. Have fun and follow up!

Hello IBM i (AS400) community

I will write what drives me (crazy) as IBM i SysAdmin. Transforming a grown AS400 system to a well managed, fully integrated and virtualized Power System running i5/OS remains exciting.

If you understand the following IBM i abbreviations and tradmarkes – stay tuned! ACS, PowerVM, HMC, SVC, V5000, Navigator for i, Admin Server,  PASE, PowerHA, BRMS, RDi, VIOS, LPAR, …

Hello IT World!

This is our “next generation” blog – hopefully it survives a little longer than the last ones.  😀

Mario & i (Bernhard) will try (once again) to let the world know a little about what is going on in our IT world. We’ll try to write something about Docker / LoadBalancing / OpenSource and so on…

It would be nice if you follow us – stay tuned!