DevOps: I will never ever set up and maintain my environment by hand again!

Repeat after me:

I will never ever set up and maintain my environment by hand again!

I will never ever set up and maintain my environment by hand again!

I will never ever set up and maintain my environment by hand again!

If you ignore this advice, you might be ending like a lot of projects I’ve seen in the last years: Unmanageable, unstable, unpredictable and basically unreliable.

Use a tool

Ansible_logo.svgIf you ever happen to set up a something in your environment, learn about tools like Ansible and perhaps Terraform first. Provision your machines and VMs with these tools, roll out your environment using these tools and version the scripts in a repository.

Do not, ever, later on, do changes or install updates on your environment by hand! Again, use Ansible or a similar tool, to roll out and install updates and components.

Version things

220px-Git-logo.svgThe key to automatization is using tools like GIT extensively. Every single configuration file, every single automatization script needs to be put under version control. Every iteration, every change, needs to be versioned as well. Get rid of your local script repositories, keep things in a central, safe place. Share the scripts and configurations, and don’t only document them in your ticketing tool!

Do not use SSH

Of course, SSH is used when working with Ansible or other automatization tools. But you, or any of your team members, should not use it. Using SSH to do tasks on a machine is by definition a manual process, something which has to be avoided! So, forget about SSH as a tool for manually managing infrastructures, configurations, and machines. Script your changes, test your changes, roll out your changes or roll them back – all using Ansible (or other similar tools) and version those scripts as well.

Automatization is key, the tool is not

Don’t feel comfortable with Ansible? Not an issue, use Chef or Puppet or any other automatization framework instead! Don’t want to learn about Terraform? Then go the native route using AWS-CLI or Azure-CLI instead. GIT sucks? Use SVN or CVS or Mercurial!

Regardless of the tool: You need to get the right mindset, and you need to get it, before starting any work! It never worked (and never will work) bringing in automatization and tools later on. You simply won’t be able to consolidate all different configurations without any bigger effort. It’s not gonna work!

Be a developer

Yeah, I know. You are not a developer. You are an administrator. You don’t program things. You don’t write nasty code. You are the specialist, the surgeon.

Well, no. You are a fool if you happen to think so.

You need to think like a developer thinks: Laziness over repetition, scripts over manual approaches, versioning over file-share-based storage. A developer – and believe me, I am one these guys – has a very simple approach: Every repetition of any kind of functionality to be implemented, is basically a wast of time.

A developer tries to write specific code only once, he organizes code in libraries for reusability. He refuses to do things a second time if he could reuse existing code or a library.

Adopt this kind of thinking! Express everything in scripts. Version these scripts. Create your own library of scripts and share it with your fellow colleagues!

Stay in control

I get often asked: What and when do I need to automatize? The answer is simple: Everything, anytime. The moment you SSH into a machine and do any kind of change there, you have lost control. Even if you are unsure about a configurational change being the proper solution to an issue, use a script.

Did I say „Even“? Especially then!

Using an automatization framework, you can roll back the change or set up an environment into a well-known state, allowing you to safely perform changes, test the outcomes and understand the consequences. Since you have versioned everything, you can always revert back to the last known version. Since you have everything in a shared, safe place, you can even lose your computer and your notes – and still remain operational.

And, in case it was not clear enough: This holds true for any kind of environment – Bare-Metal, virtualized, cloud, everything in between.

To stay in control, automatize and version. Everything!

And now repeat the headline. Until you live it.

Life at Cloudibility (IX): I will never ever hire that person!

logo_cloudibility_rgb_transparent_square_smallI said this quite often during several projects over the last years – and often directed to persons being „difficult“ with regards to discussing hard, having different opinions, contradicting a Product Owner or an Architect with thoughtful arguments. This is something you will have to accept, even if it is hard to do so. And it is exhausting, it is stressful working with such people on a day-by-day basis.

But, I changed my mind.

Or, to put it differently, I am now in a position where I want to have such characters around me. Here at Cloudibility, we want persons having their own ideas and their own minds, we want them to contradict us and to proove us to be wrong.

We want to have such minds around us. Of course, they will have to stick to our rules of respect and culture, they will need to be compatible with customers and the team. But besides this: Have your own mind, contradict, improve, overtake us!

So, we are looking for the Crazy Ones:

Are you one of them?

Welcome!

Life at Cloudibility (VII): Can’t we negotiate a special price?

I do often get this question when providing our specialist’s profiles to possible customers.

Well. No. We can’t. And we won’t.

Let me explain that bold statement a little bit. There are plenty of reasons for saying so. The most important one: We have some of the best specialists here at Cloudibility.

We love our experts.

We provide our bright minds with an environment which allows them to shine – a good work-life-balance, paid educational hours, etc. We do this, since we would have liked such an environment ourselves when being employed. But it was not possible due to calculation issues. Which forced us to quit our jobs.

Therefore, we want to pay our experts reasonable salaries and want them to gain even more knowledge. We want them to stay motivated and hunt for solutions instead of billed hours. We are investing a lot into our experts, and we are very happy and proud to do so. We know, that you deserve the best expert and the best approach for your project.

But it’s still expensive, though.

Do you know how much it costs, to do without good experts? Or to simply opt for the cheaper alternative since it is … cheaper? Can you really afford the second best or a somehow okayish solution? Just for the sake of saving some bucks forehand?

Our experts are worth their money.

They are experts and bright minds, they are able to solve problems, they are able to think outside the box. They save you time and money and nerves, they bring knowledge and experience into your projects.

So, no. We won’t do special prices.

We already have the best prices in the market since we have the best experts and the brightest minds here at Cloudibility.

Period.

Life at Cloudibility (VI): Plus 3!

logo_cloudibility_rgb_transparent_square_small

At Cloudibility, we are currently growing enormously – by mindset, by knowledge, and by headcount.

Last week, our team was expanded by three bright minds (in no particular order:

Sandra
Sandra was a Developer once (and a very good one!) and decided to opt for DevOps. She has very strong development skills and is able to transfer this into DevOps-territory. She likes working with CI/CD-components, ELK / EFK and Kubernetes. And from time to time she will be giving presentations and trainings and speeches. She joined our team as Senior DevOps Engineer.

Ronny
Ronny has a profound knowledge in DevOps-technologies as well as Kubernetes. He is doing deep dives with technologies such as Linux, Docker, Ansible, Teraform, Vagrant, Virtualization (VMware, etc.) and many more. He has joined our team as Senior DevOps Engineer.

Emilie
Emilie is part of our sales team. She as an impressive track record of sales even in difficult environments, can handle customers and partners and is a very positive person. She has joined our team as Sales Manager.

Guys, it is so great to have you with us!

Life at Cloudibility (I): Additional vacation days for everyone

Cloudibility-Logo-SquareToday, we decided to grant every employee of Cloudibility up to five additional vacation days in two years. Only condition: The management needs to agree on this and in order to agree, the employee needs to agree to produce some output within these additional vacation days which we (Cloudibility) can use in our marketing or publications.

Such an output could be some photos containing the employee wearing some Cloudibility Shirt and – say – the Colosseum in Rome or some employees running atop the Great Chinese Wall or a Publication. We don’t impose any limits here, as long as we can use it in the end.

So, Cloudibility Employees: Surprise us! Get creative! Go, have some fun!

And, besides: If you want to be a part of Cloudibility, just contact me.

Slides: #CloudNative #Applications – The Big Picture

Below are the slides of my presentation at #ContainerDays 2018 in Hamburg. I spoke about the bigger picture regarding CloudNative Applications – i.e. #DevOps, #Crossfunctional #Collaboration, #IaaS, #SaaS, #PaaS and the change of #Mindset required for utilizing all the advantages of #Cloud environments.

And, BTW: It was a cool event!

#Cloudibility #Cloud #PublicCloud #HybridCloud #PrivateCloud #Kubernetes #OpenShift #OpenStack

Download here