The next step in Puppet content telemetry
We previously published a blog about the rollout of telemetry for Puppet content back in December 2021. (Read that here.) We’d like to follow up with some important news and an exciting announcement.
We previously published a blog about the rollout of telemetry for Puppet content back in December 2021. (Read that here.) We’d like to follow up with some important news and an exciting announcement.
There were many reasons people came to use CentOS as an alternative Linux platform to Red Hat Enterprise Linux (RHEL). CentOS was originally built as a downstream release of RHEL, which was free to use without support. CentOS became the de facto standard for many organizations that did not want to use RHEL for production workload, since it’s basically the same thing, just rebranded.
Today, we’re starting Relay by Puppet, a new initiative to build the future of cloud-based DevOps automation. This post captures our musings about the evolving world of cloud-native infrastructure and how Relay addresses this evolution.
Over the past few months, we set out to drastically reduce the amount of time Code Manager takes to deploy code and sand down some rough edges to make it more stable and robust. In order to understand what we were able to achieve, we need a quick primer on how code is deployed to a Puppet Server in the first place. There are three parts to a Code Manager code deployment: We’ve improved each of these three parts of the Code Manager code deployment.