When it comes to building and configuring IT infrastructure, especially across dozens or even thousands of servers, developers need tools that automate and streamline this process. Enter Puppet, one of the leading DevOps tools for automating delivery and operation of software no matter where it runs. In our course, Getting Started with Puppet, we’ll show you how to bring these benefits to your networks with hands-on exercises every step of the way.

What is Puppet and what can it do for you?

Imagine that you have an IT environment with multiple application servers, but you need to be able to develop and deploy quickly. Perhaps you have slightly different configurations on servers that are supposed to be identical or you frequently add servers to your environment. In these scenarios, a manual approach just won’t cut it.

With Puppet’s automation, new applications and changes can be released simultaneously and with no downtime. You don’t need to figure out why something works on one server but not on another; Puppet will configure them in the same way. You also have less downtime because there is less that can go wrong when everything is configured the way it’s supposed to be. Provisioning servers is a breeze when Puppet already knows how to configure them.

This makes Puppet, available in open source and enterprise versions, a top DevOps tool, according to RightScale’s State of the Cloud Report 2017. Research firm IDC recognized it as one of four innovators as profiled in its DevOps Infrastructure Automation report.

“Puppet has a declarative programming language and an open source-based platform to help enterprise IT and DevOps teams with common machine-readable language across mainframes.”

5 ways Puppet will make a developer’s life easier

It brings consistency to your servers.

With Puppet, you no longer have to figure out why something works on one server but not on another one that is supposed to be identical.

It’s reliable.

When everything is configured the way it’s supposed to be, less can go wrong. And that means less downtime.

Faster time to deployment.

Once you automate the deployment process, you can roll out new versions of your software with the push of a button. If there is a problem with the new version, you can easily revert back to the previous version.

It’s easy to add more servers.

Since an automated infrastructure is scalable, you can easily add more servers.

More time to focus on what you love to do.

Because Puppet is automated, you’re freed up from the drudgery of repetitive tasks, and you’ll have more time to focus on productive work.

What you will learn in Getting Started with Puppet

Our course is designed to give you hands-on experience. We will start by installing Puppet on a virtual machine on your own desktop, and you will use it as a test environment to learn how to write code to automate server configuration. Don’t worry—we’ll guide you through every step.

You will also learn how to:

  • Use pre-built modules
  • Create personalized modules
  • Use manifests, classes, resources, facts, nodes, and templates
  • Build a complex module using conditional statements, operators, and facts about your infrastructure

If you’re interested to learn more on Puppet, I recommend the Cloud Academy’s Getting Started with Puppet Course. Watch this short video for an overview of the Course.



Posted by Editor