Containers are still a buzz word today and one I think we will see die out in the not too distant future and here are my reasons for thinking that.
Testing does not need to be a tedious burden that delays releases. Building an automated framework to facilitate testing early and often in the SDLC as part of a CI/CD pipeline is working smart.
There is much debate about when, what and how much security should figure in the Agile DevOps world.
Can the pursuit of perfection sit side by side with DevOps? By its very nature DevOps is all about making something work first and then making it work better later.
There is a lot that is cloudy about Cloud. There are misunderstandings, misinterpretations and of course lots of misleading hype both for and against Cloud.
This is intended to be a high level introduction to setting up Red Hat OpenShift Container Platform (OSCP).
This blog is intended to be a high level introduction to setting up Red Hat OpenShift Container Platform (OSCP) v3.4.
Business priorities change, customer priorities change, team priorities change and if you cannot find a way of dealing with this you will find yourself firefighting, trying to please everyone the whole time and failing to progress.
In Part 1 we looked at the opposing forces to successful and timely project delivery. In this part 2 we look at the effective force fields you can create to pave the way for a better project delivery environment.
Creating an environment conducive to project work is not easy. There are many opposing forces that can combine to fragment your efforts and impact on any meaningful output.
DevOps is not an exacting science with known results and timescales but more of a try something, see what happens and if it works then make it better science.
In part 1 of Managing BAU and Project Work we considered the reality of how disruptive BAU can be to project work, low and high value output DevOps cultures and how to segregate your DevOps team into functional roles.