Me and DevOps
I've just doing some of the EdX course that I signed up for in December on Introduction to DevOps: Transforming and Improving Operations by John Willis. If you are interested in DevOps then this is a great way to get started, but be warned this is just like a University/College course, lots and lots of reading, you need to put the effort in. It's very close to the DevOps Handbook which I thoroughly recommend.
Anyway, the point of this article is, in Chapter 4 section 3.5 Creating Consistency in the Pipeline, John says...
So, a strategy, you know, might be that you create a base image for your organization or for some hardened version,
maybe a Debian version, you give that out to all the kind of infrastructure people, the people that do Red Hat, they can build Tomcat on that ... the people that do Python, they build Python ... and they're all starting with the same base image.
So, there's kind of four models that I would kind of describe, as you know, the areas that you, or strategies that you might want to use for creating a consistent operating system environment, or consistent operating system environment patterns, right?
Guess what I do @ Fujitsu...? That base hardened image for everyone. Just one of the little Ops things we do. We allow anyone and everyone in Fujitsu (globally) to grab a copy and use it. It will be on Fujitsu K5 very soon, so then everyone can use it.
Automation is one of my passions, it's become trendy over the last few years (thanks probably to DevOps). I am a lazy engineer and I really don't like to manually repeat things, so automation is second nature and where I look to usually first. Of course, that base build I do is automated and all the code available to all employees on our internal source code repo with the tickets for bugs/requests/features/etc on our project kanban.
On a personal note, I have some Ansible code for Automation in K5 on my github if any one is wants to take a look. It will build a 3-tier network in around 3-5mins and pop a Guacamole jump server on there as well. If anyone in Fujitsu or related customers are interested in any sort of automation with Ansible, in the cloud or elsewhere, please get in touch with me or your sales manager.
It's nice to know we are on the right track in the world of DevOps. :)
Retired
8 年If this is an example of John Willis's writing style, I'm not surprised you say you have to put the effort in. It might be OK when spoken, but this excerpt comes over as the verbatim transcript of a talk he might have given. It is a shame when the message gets lost because of a lack of clarity in its communication. But perhaps it's worse when an engaging piece, however it's presented, glosses over vital facts or even misrepresents them.