In many organizations development teams are split up from systems administrators. Both teams focus mainly on their roles and responsibilities, but this can lead to problems. Tensions between the groups can hinder your organization’s efforts in getting the best product to the consumers in the shortest amount of time. Below are quotes which are commonly come up between developers and systems administrators.
“Why doesn’t the development team have to be on call? It’s their code that breaks the system.”
“Why does the sysadmin get to dictate what tools/languages I can use to solve the problem?”
“Add more hardware to the server”
“Stop using so many resources on the system!”
You begin to easily see how this relationship is strained and broken, but does it have to be? Let’s talk about some more of the common stereotypes and discuss the ways to move past them. Continue reading →
Have you wanted to use software collections but found packaging has kept you at bay? Tried rebuilding a package only to find it give you weird errors you’ve not seen before? In this blog post we’ll learn how to configure and use mock to build RPM packages for the Python 2.7 Software Collection. Along the way we’ll learn why we can’t use standard mock configurations, and what makes Software Collections (SCL) mock configurations different.
Our infrastructure and how we continuously integrate and deliver (CI/CD) our code changes with each piece of work we finish. We fully expect that it will change even more as we bring up A|B functionality & enhance our testing process. However, we thought it would be fun to give a closer look into the team’s pipeline from checking out code to integration testing.
As we have discussed in the past, Team Inception has been working on a release engine to automate RPM code deployments within Red Hat IT. On July 8 we passed a significant milestone by successfully using Release Engine in our QA environment. This was an incredible achievement which included a number of feature requests, defect fixes, and collaboration between multiple teams to produce an open source application that will address growing needs internally in Red Hat IT. We decided that since we are attempting to make waves internally we should also use a product that is currently making waves throughout the industry: so we chose Docker.
Introduction: Gene Kim, award-winning CTO and co-author of “The Phoenix Project,” recently sat down with Red Hat IT’s Inception team to discuss their DevOps mission. Here are the highlights from the conversation.
On the Inception team’s DevOps and CI/CD implementation strategy: