Operations | Monitoring | ITSM | DevOps | Cloud

Why make a migration from Ansible to Puppet — or in some cases, start with Puppet over Ansible right out of the gate? In this blog, we’ll explore some common reasons that organizations say they chose Puppet over Ansible, citing specific use case examples around the functionality of each platform.

If you’re doing cloud operations right, your cloud needs are going to change over time. Cloud scaling can help you add cloud resources when you need them and retire or recycle them when you don’t. Cloud scaling is great for meeting traffic demands, accommodating demanding workloads, and controlling the chaos of cloud ops. But for all the flexibility that cloud scaling offers, it can also introduce liabilities in your cloud infrastructure.

Tech debt affects just about every software organization. For better or worse, speed is one of the core tenets of the software development industry – the rush to build more, add new features, and find solutions fast can drive short-term growth for small organizations and add value for large companies. But haste, as it usually does, makes waste: The mass of suboptimal code, redundant services, and bottlenecked processes that we call tech debt.

Following good practices in the Day 0, Day 1, and Day 2 software development lifecycle can help you create a consistent environment that is easier to maintain. In this blog, we will deepen your understanding of how to make Day 2 operations succeed, and how high performing teams put Puppet to work on Day 2 to make a stronger, less manual, software development lifecycle.

In early 2023 Betadots together with Vox Pupuli adopted the Puppet containers and so this article has been updated to contain the new locations. Details of their adoption can be found here. If you’ve ever wanted to get started with Puppet or Docker — or both — you’ve probably faced a bit of a conundrum. Should I use Puppet to deploy Docker on my nodes, and then use Puppet to define container images?

Threat vulnerability management, and managing your attack surface, are critical in the battle against cyberattacks. At some point before an successful attack, the internal process to manage threats and prevent access to sensitive data failed. How could they have done things differently? Were they just managing too much, too often, without the resources they needed?

The definition of a platform engineer can be slippery. Ask several IT professionals “What does a platform engineer do?” and you might get several different answers. One platform engineer might be at the intersection of DevOps, AppSec, architecture, and SRE, while another might broadly support infrastructure for all developers in their organization. (Sometimes, in less successful teams, they’re essentially a DevOps engineer with a fancy title.)

Migrating to the cloud, in whole or in part, can be tempting for organizations of all sizes. The cloud offers agility, potential cost savings, and scalability — all without a commitment to physical devices. But what about the risk? Migrating to the cloud can be a complicated undertaking with the potential for missteps and hidden expenses. You’ll need to take a careful look at why you want to migrate to the cloud, as well as do the work researching cloud vendors and migration approaches.

Welcome to Day 1 of the software development life cycle — what now? We’ve already covered Day 0 server provisioning, and you should be ready to start writing code that will support your DevOps initiatives and make your life easier …or are you? Put some of our wisdom and experience at work for Day 1 of the software life cycle, and make sure you’re fully prepared to handle common pitfalls and problems that can become ongoing issues for Day 2.