Operations | Monitoring | ITSM | DevOps | Cloud

I recently had a conversation with one of our customers at AWS re:Invent that made me rethink the true value of automation. This customer told me, “You’ve automated so much for us that we almost forget about Qovery. Nobody even asks how to do things anymore.” That statement stuck with me.

High-performance computing (HPC) configuration has become paramount for AI workloads. Companies investing in AI workloads often find themselves with predictable problems: Lots of nodes that are hard to integrate and harder to manage together, under-utilized resources, deployment struggles, inconsistent configurations, and drift.

As the demands of modern software development continue to grow, so too does the complexity of DevOps. To keep pace, many organizations are turning to AI-powered assistants that help manage infrastructures, streamline pipelines, and automate repetitive tasks. These assistants are known as copilots, and they promise to enhance productivity while reducing operational overhead. But not all of them are created equal.

Configuration management tools can help you track and manage changes to systems within your infrastructure, making sure that your software and hardware runs reliably and smoothly.

As organizations scale, managing IT systems and resolving incidents efficiently becomes increasingly complex. Manual processes, while functional in smaller setups, often fall short in speed, accuracy, and scalability. Enter Runbook Automation (RBA)—a transformative approach to streamline and standardize incident resolution. This blog explores what Runbook Automation is, its significance in modern IT operations, and best practices to implement it effectively.

CFEngine build modules are great for quickly integrating 3rd party policy into your policy set. Module input (not to be confused with inputs in body common control or body file control which are the list of policy files to load) allows you to define values that apply for a particular module as it’s integrated into your policy set. Let’s take a look at a case of extending a module to support input.

Ever need to make a decision based on the version of something? The version_compare() function might be useful for you.1 Over time, software changes and features are added and removed. Sometimes, we need to make a decision based on versions. For example, the Include directive in ssh_config was introduced in OpenSSH 7.3.2 Let’s take a look at how we could possibly use it. This example illustrates the basic use of version_compare()

As businesses scale, managing infrastructure becomes increasingly complex and distributed, leading to challenges in consistency, performance, and security. Manual configurations and outdated practices can no longer meet the demands of today’s highly competitive businesses. To tackle these issues, adopting a phased approach; Day 0, Day 1, and Day 2; provides a practical roadmap for scaling infrastructure automation effectively.

Software deployment automation can simplify and speed up your delivery cycle. It can reduce risk, allow teams to easily test after changes are made, and help provide consistency for the overall development pipeline. If it sounds complicated, we’re here to break it down each step into a cheat sheet that provides tips and best practices for the software deployment automation process.