The latest News and Information on DevOps, CI/CD, Automation and related technologies.
First, I’d like to say that pager duty isn’t something we should treat like chronic pain or diabetes, where you just constantly manage symptoms and tend to flare-ups day and night. Being paged out of hours is as serious as a fucking heart attack. It should be RARE and taken SERIOUSLY. Resources should be mustered, product cycles should be reassigned, until the problem is fixed.
I’m sure most of us have heard this saying before, and if you are in the DevOps space, I’m sure this is a scenario that you deal with daily. Most of us started even before we even had all these nice terms, such as DevOps, SREs, DevSecOps, and so many others, when we were all Sys Admins.
October went fast, full of news and packed with interesting robotics applications. This month certainly doesn’t need an intro, so we will let the news take all your attention.
Object storage has by far the most simplistic interface out there, with no need for complicated SCSI drivers, HBA drivers, multipathing tools, or volume managers embedded into your Operating System. All you need to do is point your application at an HTTP endpoint, and use a simple set of verbs to describe what you want to do with a piece of data. Do you want to PUT it somewhere for safekeeping? Do you want to GET it so that you can do some work with that piece of data?
Ask any DevOps engineer, and they will tell you about all the alerts they enable so they can stay informed about their code. These alerts are the first line of defense in the fight for Perfect Uptime SLA. With every good solution out there, you can find plenty of methods for alerting and monitoring events in the code. Each method has its own reasons and logic for how it works and why it’s the best option. But what can you do when you need to connect two opposing methodologies? You innovate!
