I mean, really? If you haven’t heard: The craziest thing went down today at Red Hat Summit. It’s probably a first ever for a tech conference and that’s not even the amazing part. We married some amazing people. To each other. They hitched without a hitch. It was beautiful, romantic, geeky, exciting, punny, and absolutely heart-warming.
I wouldn’t trade the experience of seeing these two wonderful people commit to each other for anything. See what I did there? Commit. Get it? Anyway…
Paul Cormier, Red Hat EVP and president of Products and Technologies, presided over the wedding while Jim Whitehurst, our fearless leader, acted as ring bearer.
Are you a traditional Red Hat customer using Red Hat Enterprise Linux? You may be big on standing still. This doesn’t mean you personally. But you want your platform to be stable. You’re fielding critical applications on it, and you need it to be rock steady and predictable.
Wait, did you say you’re not traditional in that sense? Perhaps you’re looking for new features to support emerging applications, then. You want agility, flexibility, and modularity in your platform, whether it exists on premise or in the cloud.
Those are 2 really different ways of looking at the operating system.
Understanding the problem
Denise Dumas, Red Hat’s VP of Platform Engineering, understands these competing needs. So does Red Hat’s Director of Product Management Ronald Pacheco. They teamed up at the Red Hat Summit to explain how Red Hat Enterprise Linux can support both these types of customers.
As Dumas explained, “RHEL is one-stop shopping” for security, scalability, and stability. That doesn’t change for customers, whether they value a traditional or a non-traditional platform. But with modern, competing needs for infrastructure, she said, the requirements aren’t as simple. “RHEL customers expect stability but also demand innovation.”
Some folks want it to stand still. Others want to use new and innovative code. That’s quite a quandary for an operating system.
Some call it digital transformation. Others say it’s the evolution from traditional to modern, or from mode 1 to mode 2. Paul Cormier, Red Hat president of Products and Technologies, sees it as an evolutionary approach to architecture, processes, and platforms. In his keynote at the 2016 Red Hat Summit, he explores how these shifting landscapes affect both infrastructure and applications, as well as developers and operations.
To start, Cormier looks at infrastructure and app development through the lens of architecture, processes, and platforms.
Infrastructure architecture is moving from proprietary to open source development, and from single footprints to a combination of physical, virtual, private, and public resources. These changes necessitate accessible software-based storage and networking, as well as common management and consistent applications. Without all the pieces working in harmony, infrastructure can become inefficient and complex–and that isn’t sustainable.
With all the changes to infrastructure, processes must change to match. More automation, better tools, and common management can help, but streamlined processes must infiltrate the entire organization to make increasingly complex infrastructure sustainable.
Similarly, the host platform must be utterly stable across the entire stack. Platform consistency is where Red Hat Enterprise Linux has made its mark–our customers can use the same foundation across physical, virtual, private, and public environments.
The best demos are live demos. They’re intense, fast-paced, and full of excitement–for the audience, of course. The presenters never want excitement. They want everything to work as expected. And the keynote demo this morning delivered all of that and more.
“Think of this as our flying trapeze act.”
Burr Sutter, Red Hat’s director of developer experience, gave a demo that spoke to the core of Red Hat Summit: The developers. The operations teams. Those that do. This demo built on the concepts that Paul Cormier addressed earlier in the morning. Developers feel many pains in their day-to-day lives and need resources to make apps work, then into production. Even getting their environment set up properly can be a chore. File tickets. Wait. Hope. Get resources. Code. Rise and repeat.
On the other side, operations teams are constantly getting barraged with requests from developers. Ticket after ticket comes in requesting resources. But developers don’t understand all that ops have to deal with. Dependencies, requests, patches, updates, more tickets, more requests, more updates. It’s impossible to keep up with.
DevOps to the rescue
The power of DevOps is that these teams can be linked together in culture, processes, and tools. What if you had a way to automate all of this? A single place for everyone to work together and cast aside the madness. A way to get to production faster, using containers, and continuously integrating and delivering. And what if you could see it live at the Red Hat Summit? Yeah, that’d be cool…
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.
At 6:00 this morning, hundreds of Summit attendees lined up at the starting line outside the Moscone Center. After a full day of sessions yesterday (and, for some, a late night out on the town afterward), these runners braved the early morning call to come out for the annual Red Hat Summit 5k.