Linux Conversations | Episode 1: Running Multi-Linux Environments in Production with Donald Vosburg

SUSE Linux

Welcome to Linux Conversations with SUSE Experts, a blog series where we talk with the brilliant minds behind SUSE Linux.In each post, we present a transcript of a conversation that explores real-world insights, innovations, and best practices in the enterprise Linux world, including how it is created and supported.

Today, we sit down with Donald Vosburg, Product Manager for SUSE Multi-Linux Manager, and Rick Spencer, General Manager of SUSE Linux, to discuss the challenges and strategies for running multi-Linux environments in production.

Also, we’re excited to talk about the upcoming SUSE Multi-Linux Manager 5.1 launch, scheduled for mid-year. This release introduces customer-requested features and enhances interoperability with popular tools like Ansible.

Interview Transcript:

– Rick Spencer: My name is Rick Spencer, and I work with the SUSE Linux team. With me today is Donald Vosburg. Donald, can you start by telling us a little about your role and what you’re currently working on?

– Donald Vosburg: Sure! We have a tool that helps organizations manage their Linux portfolio, regardless of the distributions they use or where they run them. Our goal is to provide the necessary tools to manage these environments successfully.

– Rick Spencer: That’s great! I heard you’re working on a new release, version 5.1. Can you tell us a bit about that?

– Donald Vosburg: Yes, we have a new release planned for mid-year. This update, SUSE Multi-Linux Manager 5.1, includes features that customers have requested for a long time, along with improvements in interoperability with other tools like Ansible.

– Rick Spencer: Sounds exciting! But today, I’d like to pick your brain about what you’ve learned from working with enterprises. You’ve been in this space for 20 years, so I’m sure you have some interesting insights.

– Donald Vosburg: Absolutely! I’ll do my best to condense what I’ve learned over the years.

– Rick Spencer: So, how do enterprises end up with multi-Linux environments in their infrastructure?

– Donald Vosburg: In IT, applications often drive the choice of Linux distribution. Many applications are certified for specific distributions and versions. When businesses deploy those applications, they bring in the required Linux distribution, even if it’s different from what they already use. Mergers, acquisitions, and developers introducing their preferred distributions also contribute to this diversity. Cloud native environments sometimes dictate container runtimes and Kubernetes distributions with opinionated Linux requirements. , and can be automated or manually completed with SUSE Multi-Linux Manager.

– Rick Spencer: Interesting. Is it worthwhile for enterprises to consolidate their Linux environments, or should they just accept the reality of running multiple distributions?

– Donald Vosburg: It depends. Managing multiple distributions requires experts who understand the tools and nuances of each one. Some organizations tolerate many distributions without officially supporting them, while others try to standardize on a few. One large aircraft manufacturer we worked with estimated using nearly 70 distributions! We encouraged them to consolidate to a manageable number while still accommodating critical applications.

– Rick Spencer: We’ve seen cases where some Linux instances miss timely patches and updates. How concerning is that, and what should enterprises do about it?

– Donald Vosburg: It’s a significant concern. Security vulnerabilities accumulate over time, creating potential time bombs. Using deprecated components also exposes enterprises to security and functionality risks. The best practice is to test patches in a staging environment before applying them in production. Tools like SUSE Multi-Linux Manager simplify this process, enabling consistent and controlled patch deployment across environments.

– Rick Spencer: Right, and I imagine fear of disruption also plays a role.

– Donald Vosburg: Definitely. Enterprises worry about outages caused by updates, especially with distributions they don’t fully understand. Testing environments help mitigate this risk by validating updates before production deployment.

– Rick Spencer: Speaking of SUSE Multi-Linux Manager, can you explain the role of multi-Linux support in these environments?

– Donald Vosburg: Sure. SUSE Multi-Linux Manager has supported various enterprise Linux distributions since 2011. We now offer support for distributions like Rocky, Alma, and CentOS without requiring workload migration. The binaries remain compatible, and we automate the process of switching update sources to SUSE’s infrastructure. This approach helps enterprises maintain critical workloads without disruptive migrations.

– Rick Spencer: So if a workload is running fine but lacks updates, you can seamlessly switch to SUSE’s update infrastructure?

– Donald Vosburg: Exactly. The application continues running as before, but updates come from a new, reliable source. It’s a straightforward, risk-free way to keep workloads secure and operational.

– Rick Spencer: This sounds like a practical solution for enterprises with hard-to-move workloads. If someone wants to reach out with follow-up questions, how can they contact you?

– Donald Vosburg: I’m happy to help! People can find me on LinkedIn under “dvosberg” or email me at dvosberg@suse.com.

– Rick Spencer: Thanks so much for your time, Donald. I appreciate your insights.

Conclusion:

Managing heterogeneous Linux environments can be challenging, but with the right tools and practices, enterprises can ensure stability, security, and operational efficiency. SUSE Multi-Linux Manager 5.1 provides a centralized platform to simplify this complexity, supporting various Linux distributions without the need for disruptive migrations.

Stay tuned for more interviews in our Linux Conversations series. Follow our blog or subscribe for the latest insights from SUSE Linux experts.

*Disclaimer: This transcript has been lightly edited for clarity and readability.*