Push it real good: Continuous delivery at the push of a button

Andrew Rubinger, an architect within Red Hat’s developer programs group, showed us how to revolutionize your deployments. Sounds like a long, complicated talk–surely something like this takes forever to set up. Actually, this was the shortest talk I’ve ever experienced at a Red Hat Summit. 

That’s not a bad thing. It speaks volumes to the shift that we’re seeing in IT. The tools are there. They have the power and can do what we want and need. The change is in how people interact with those tools.

Good news: It’s finally getting easy.

Continue reading “Push it real good: Continuous delivery at the push of a button”

Lessons learned on the DevOps front: A Red Hat tale

I love a good story. I love it even more when the story is true. Today’s session with two fellow Red Hatters, Katrinka McCallum, VP of product and technology operations, and Jay Ferrandini, senior director of worldwide DevOps, gave me both. And it makes me even more excited that their session was about Red Hat eating its own dogfood or, if you prefer, drinking its own champagne.

“We might not be delivering what our customers want…”

Red Hat engineering had a problem when it came to dealing with Red Hat operations. This was referred to as the “banana and pickle problem.” Engineering/QE would come to operations asking for something–a solution that they desperately needed. Let’s call the requested solution the banana. They came to the team and asked for a banana. Ops went away into a black box development cycle and delivered…a pickle. Not exactly the same thing. Similar in some ways, but not what was requested.

This is an issue that many teams face. They’re segmented in such a way that there’s no collaboration or communication across the teams, at least not in a meaningful way.

Maybe DevOps can save the day?

Continue reading “Lessons learned on the DevOps front: A Red Hat tale”

The future of Red Hat Enterprise Linux

What customers wanted: 2002

Gunnar Hellekson’s been with Red Hat long enough to remember what customers wanted in the early days, when they were still buying boxed software off the shelf of the local big box electronics store. What did they expect from the upstart software company back then? In Hellekson’s parlance, Red Hat’s business was “lighting up hardware and making software run.” Customers at that time primarily wanted:

  • Quality support
  • A vast* ecosystem
  • Peerless security response team
  • Options for life cycles (2 years, 10 years, etc.)
rhel-dependency-firefox-example
Firefox only has around 500 packages, and their dependency graph looks like this. Can you imagine what 10K might look like?

What’s happened since then?

The creation of separate streams for Red Hat® Enterprise Linux® and Fedora was a beneficial change that gave both room to grow. They continued to add value over time by, as Hellekson noted, “stuffing more things in the bag.” However, after a decade of adding value, Red Hat Enterprise Linux 7 has nearly 6,000 packages—plus all of their associated dependencies and complexity. According to Hellekson, if you were to package up everything in the upstream of RHEL today, there would be around 10,000 packages.

Continue reading “The future of Red Hat Enterprise Linux”

The Red Hat security roadmap

Josh Bressers, security strategist for Red Hat, laid down the law for the current state and future of security at Red Hat in today’s roadmap session. When talking roadmaps, nothing is definite–Josh stressed that on several occasions and offered some guidance on when we might see some of these advancements. Still, nothing is certain until it’s certain.

5270987711_d18c4b98d0_b
Photo by Marc Falardeau

Foundation > Platform > Technologies > Usage

Security is big. Really big. Especially within the past year, we’ve seen lots of security issues and vulnerabilities exposed, freaked out over, and resolved. It’s on everyone’s mind and the answer to all of this isn’t a silver bullet. Security is not a single solution, but everything in your infrastructure working together–along with your users. If you don’t use it securely, it doesn’t matter how secure it is at the bottom.

 

Continue reading “The Red Hat security roadmap”