Do you consider yourself a Puppet expert? Even #AI can help streamline your daily workflow. #devops
Learn more about Puppet AI by watching the full length video now!
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Ubuntu Summit 26.04 is coming: Save the date and share your story!
Following the incredible success of Ubuntu Summit 25.10, we are thrilled to announce that Ubuntu Summit 26.04 is officially on the horizon. If you are new to the Ubuntu community, every new release of Ubuntu comes with an Ubuntu Summit – an event that takes place twice a year and serves as a showcase of the absolute best in open source innovation from around the world. Our hub in London hosts the talks, which are then streamed live, across the world.
Authentication vs Authorization: What's the Difference and Why It Matters | Harness Blog
Let's get something out of the way: authentication and authorization are not the same thing. We know, we know. People swap the two terms constantly. And honestly, it's easy to see why. They both start with "auth," they both deal with security, and they often show up in the same conversations on access control. But if you build or secure software, blurring the line between authentication and authorization is how you end up with a system where everyone is logged in and everyone is an admin.
When we say "Observability AI Reckoning," what are we actually talking about?
We’ve spent the last decade collecting more telemetry. Now AI is analyzing it. Here’s the catch: AI needs the full dependency chain to reason correctly. If it sees spans but not storage contention… Services but not Kubernetes scheduling… Frontend metrics but not downstream providers… It will confidently optimize the wrong thing. AI doesn’t lower the need for observability. It raises the standard.
Resolve's Zero Ticket Minute - Ep. 17 #agenticai #aiautomation #itautomation
AI must be reliable and resilient at scale. When systems are exposed, impact spreads fast. Zero Ticket = real-time resolution. The future is autonomous.
FinOps Roles And Responsibilities: Building Your Cloud FinOps Team (2026)
Quick answer: FinOps roles and responsibilities typically span four core functions: FinOps analyst (hands-on cost analysis and anomaly detection), FinOps engineer (resource tagging, automation, and rightsizing), FinOps architect (process design and optimization frameworks), and FinOps lead (program ownership, C-suite alignment, and cross-team accountability).
Architecture deep dive: What makes a bug reproducible?
The most difficult bugs to solve aren't those with the most complex code, but those with the most complex state. For a bug to be "reproducible," it must be deterministic, meaning the same set of inputs always yields the same failure. In a modern cloud environment, those "inputs" include more than just your code; they include the specific version of your database, the latency of your service mesh, and the exact configuration of your underlying infrastructure.
Performance Testing vs Load Testing: Simple Difference
Learn the clear difference between performance testing and load testing in this quick video. Performance testing checks how well your software works under different conditions like speed, stability, and scalability. Load testing focuses only on how the system handles expected user traffic. If you want to build reliable applications, knowing these two helps you test smarter. Perfect for developers, testers, and QA teams.
Implementing Robust Virtualized Environments for 24/7 Mission-Critical Systems
Infrastructure resilience is no longer a luxury in a digital environment where "five nines" (99.999% uptime) has moved from a premium goal to a baseline requirement. We have moved past the era of the "server in a closet," vulnerable to a single power supply failure.
Introducing: Final Steps in Bitbucket Pipelines
If you’ve ever run a pipeline, you’ve certainly encountered the following situation: The pipeline fails halfway through, and the cleanup script you needed at the end to tear down test infrastructure or archive the logs never gets to run. Until now, there was no built-in way in Bitbucket Pipelines to guarantee that a step always executes at the end of your pipeline, regardless of what happened before it. Today, we’re fixing that.