It can be challenging for even the most experienced IT organizations to embrace the latest DevOps automation tools and then ensure they are implemented in the most optimal way across a hybrid IT estate. Infrastructure teams are faced with increasing deployment complexities, budget and staffing constraints, competing priorities, and the challenge of supporting expanding development teams, impacting their organizational goals and KPIs.
Continuous Delivery for Puppet Enterprise (PE) is a tool for streamlining and simplifying the CI/CD process of your Puppet code. Continuous Delivery for PE offers a prescriptive workflow to test and deploy Puppet code across environments. ServiceNow includes a powerful Flow Designer. Why not combine Continuous Delivery for PE pipelines with the ServiceNow Flow Designer to improve and automate your change management process even further?
For the second year in a row, we have published a pandemic-era DevOps Salary Report. It’s no surprise that the pandemic catapulted every type of company into a digital transformation frenzy. We have done our best to distinguish between temporary shifts and long-term trends dictated by a newly hyper-digital world. In 2021, we are grappling not only with the reality of the pandemic, but with the Great Resignation – at least in the U.S.
Want to land one of the 20,000 jobs calling for Puppet experience? Or perhaps you already know Puppet but want to advance your skills in order to scale your infrastructure even more quickly and securely? Starting this May, we’re making it easier than ever for you to learn Puppet with an all-new instructor-led curriculum and the opportunity to take all of our Fundamental Core instructor-led training for free.
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.
Would your organization benefit from having powerful, yet easy-to-use filters to inspect your nodes? With our latest Continuous Delivery for Puppet Enterprise release, we’ve updated the filters in the user interface to support more advanced queries. SysAdmins, developers, DataOps, and IT managers will all benefit from having access to these powerful filters.
This article is about how to install Puppet Enterprise using your own self-signed Intermediate CA (Certificate Authority). In some environments, regulations require you to intercept and inspect all SSL traffic to detect malicious activities that could otherwise masquerade as legitimate encrypted traffic. This requires the ability to decrypt and re-encrypt the stream in real time, which can only be done with the proper certificates installed.
