Repo as a Service with Rocky Linux
- Zane Hamilton, Director of Sales Engineering, CIQ
- Robert Adolph, Chief Product Officer & Co-Founder, CIQ
- Neil Hanlon, Solutions Architect, CIQ
Note: This transcript was created using speech recognition software. While it has been reviewed by human transcribers, it may contain errors.
Full Webinar Transcript:
Let’s go ahead and start with repo as a service and talk about what it is and what we’re trying to do with it.
I’ll let Neil get into the specifics, but at the higher level, what we are really trying to do is find strategies and solutions that can help customers at scale maintain their environments and do their environments better. Over time, we’re going to have multiple different strategies to help enhance that capability. And that’s the overall goal of what we’re doing with repo. As far as the nuts and bolts, I’ll let Neil jump in and talk through that. But at the end of the day, our goal is to help people long-term utilize Rocky at its fullest.
The idea of repo as a service here is it comes from a lot of experience, investigation, and analysis of a lot of things that are out there and available in the Enterprise Linux space for managing repositories. A common theme among that management is the need to have customized repositories, possibly with different packages that come from various sources. Also, just packages that are updated and you want to have a copy of them locally to ensure that they’re valid and the right packages, and your systems aren’t going out to the internet to a place that could possibly be a less secure site, like any mirror or anything else. This ensures that the content you’re getting is going to be not only secure but up to date, and are the current images or current packages from Rocky Linux. It will enable customization around that to fit your business needs that you want to pin packages at specific levels in various environments and scale that out from an enterprise solutions level to manage your fleet of systems.