Operations | Monitoring | ITSM | DevOps | Cloud

Using a Linux Domain controller such as Red Hat Identity Management or FreeIPA? If so then the fields are a bit different than some other LDAP interfaces, which makes it difficult for some to connect to for authentication. Here is a quick how-to on setting up Puppet Enterprise with authentication from FreeIPA. I am assuming that you already have Puppet Enterprise installed with eyaml configured. If not, then you may want to visit these prerequisites.

One of the best things about cloud computing is how it converts technical efficiencies into cost-savings. Some of those efficiencies are just part of the tool kit, like pay-per-use Lambda jobs. Good DevOps brings a lot of savings to the cloud, as well. It can smooth out high-friction state management challenges. Sprucing up how you provision cloud services, for example, speeds up deployments. That’s where treating infrastructure the same as workflows from the rest of your codebase comes in.

Eric Sorenson and Melissa Sussmann discuss Puppet’s event-driven automation platform, Relay, and how it helps clean up the “DevOps Dumping Ground” left behind from a tangled web of gitops and cloud events. Ditch your digital duct tape with a repeatable and reusable platform. Home-grown glue logic is expensive and high risk compared to the alternative.

As the automation surface area grows to accommodate hundreds of interconnected APIs on the cloud, developers are using their own, home-grown “digital duct tape” to manage a growing “DevOps dumping ground”. For a lot of organizations, home-grown glue logic is inconsistent, not repeatable, and expensive to maintain hundreds of event-based workflows and thousands of combinations. We believe that the answer lies in automation workflows.

As the industry leader in the DevOps space, we’re excited to share recent updates to the Puppet Enterprise platform that give infrastructure operations teams the flexibility to manage and automate more infrastructure and complex workflows in a simple yet powerful way.

Patching systems is not a new problem; this is something that organizations are very familiar with. Organizations have tried solving this issue in various ways by cobbling together multiple tools, processes, different teams, and more. Organizations are constantly trying to stay secure and keep their systems up to date, but patch management isn’t a simple process. In fact, applying the patch itself is just one part of the overall workflow, which involves multiple teams and various steps.

In classic Puppet deployment architecture, compile masters are widely used when the number of managed nodes goes up. Multiple compile masters sit behind a load balancer to take care of the additional workloads. It is not rare to see Puppet adopters launching the compile masters in the public cloud, such as Amazon Web Service (AWS) and Google Cloud Platform.

Many attempts to simplify programming lead to visual interfaces that provide approachable settings for common tasks. These simplifications may appeal to non-developers, but they send experienced coders running for the command line. Yet, no code tools are rapidly expanding. Zapier, Integromat, and Workato are becoming more popular options and some believe developers won’t be needed for most integrations in the future.