This blog will be the second in a three-part blog series where we explore the benefits of the GitOps practice, how to get the most from GitOps, and how to measure and maintain success. Here is what you can expect from the series: We’ll dive into the practice of GitOps in this blog, defining and understanding what an efficient workflow can produce. Here you’ll put the principles of GitOps into practice, exploring how infrastructure as code (IaC) can help you get more done with fewer resources.

Finding the right automation tool for Windows environments can be frustrating. Legacy systems, a GUI-centric design, and proprietary tooling are a few of the reasons automating Windows infrastructure can be challenging – especially in environments where Windows isn’t the only OS. Many organizations struggle to choose tools that will let them automate Windows infrastructure without contributing to tool sprawl.

Puppet 8 is here, and it’s included in the latest release of Puppet Enterprise. It’s the biggest update to Puppet since Puppet 7’s first release in November 2020, and it carries a host of enhancements and improvements to make managing and scaling your infrastructure easier than ever. Read on for a list of the major changes included in Puppet 8, how they benefit you, and how to get going with Puppet 8 fast.

Considering moving from Open Source Puppet to Puppet Enterprise? Great! In this article, we'll cover typical use cases for the enterprise version of Puppet, why businesses that moved from Puppet's open source version to Puppet Enterprise made the switch, and how customers drive time to value with Puppet Enterprise faster than Open Source Puppet.

If you moved to the cloud hoping for cost savings and scalability only to find that your cloud costs are ballooning, your cloud performance isn’t up to snuff, or you’re always struggling to align compliance regulations with your cloud deployment, it might be time to look into cloud repatriation as an alternative to public cloud infrastructure.

The artificial intelligence (AI) revolution is here. If you’ve been following the meteoric rise of companies like NVIDIA, you understand that the AI revolution isn’t just a passing hype cycle. To train complex models like Large Language Models (LLMs), organizations are turning back the dial to private data centers and high-performance computing (HPC) infrastructure — which requires thousands of servers all working in harmony.

A patch management process lays out the steps associated with updating software and hardware. Every patch management process shares a few core similarities, but with so many tools for managing patching in so many different kinds of setups, no two IT teams’ patch management processes look alike. What does your patch management process look like? Are you always ahead of the game and ready to patch on time, or are you usually behind schedule and not sure where you’re getting stuck?

This blog will be the first in a three-part blog series where we explore the benefits of the GitOps practice, how to get the most from GitOps, and how to measure and maintain success. Here is what you can expect from the series: Let’s start at the very beginning — what is GitOps? If you want to start to build a single source of truth for both your code and your infrastructure, if you want to ensure your deployments are automated and reliable, you’ll want to know GitOps.

Configuring virtual machines (VMs) is an important task for any organization. Users across departments depend on sysadmins, engineers, and the rest of the IT ops and infrastructure teams to get VMs secured and ready to use, whether you’re spinning one up for a quick test, a new database server, or standing up a whole fleet of dev-ready machines. That need for variability AND consistency can also make VM configuration one of the most tedious sysadmin tasks, especially at enterprise scale.

As a part of Perforce, we are committed to maintaining the highest standards of security for our products and our customers. Recently, we had the opportunity to further strengthen our security practices thanks to valuable input from an independent security researcher. This experience has not only reinforced our robust security protocols but also provided insights that we're eager to share with the wider tech community.