The latest News and Information on DevOps, CI/CD, Automation and related technologies.
To manage your Windows desktops and servers based on the version / edition of Windows installed across your organisation, we’ve introduced Windows build-specific facts to Puppet. If you have a mix of Windows servers (Core and ServerStandard) and Windows desktops with varying versions and editions Windows, using Windows build-specific facts allows you to: Let’s see what all this looks like in some Puppet code.
Service Request Automation – Fulfil Cloud Requests The Easy Way The typical Service Desk model consists of 1st line support contemplating how a call should be answered, and then passing it to 2nd and 3rd line to fulfil the requirement. In the new world of Cloud and AI Ops, there is a more streamlined; efficient and autonomous process.
Helm is a popular open-source tool used to manage and configure your Kubernetes cluster. Basically, it is a package manager (think Homebrew or NPM) built for Kubernetes. It helps automate processes like installing, configuring, upgrading, and removing items. This post will give you a brief introduction to Helm and how it might help you manage your Kubernetes cluster.
Continuous integration is the first half of the acronym CI/CD, with Continuous Delivery completing the second half. In this three-part article, we look at the two halves of CI/CD to define and understand them, and then, in part three, we talk about how Uptrends fits into your CI/CD processes. Let’s get started at the beginning with continuous integration.
.NET is an open source software framework for building cross-platform applications on Linux, Windows, and macOS. Ubuntu on WSL allows you to build and test applications for Ubuntu and Windows simultaneously. What happens when we mix these together? This blog will demonstrate how to install a .NET development stack on WSL, build a simple OS-aware application, and then test it on both Linux and Windows.
It’s 3 AM and you are roused out of sleep by the dull buzzing of your phone in the other room. Some sort of emergency, you conclude as you fumble with the lockscreen. There it is: an alert that the API governing user registration is acting up. When we think about the lag between time of incident and time to respond, it’s not just about how long the system went down. How long it physically takes us to respond to the problem also contributes to lost downtime.
