Operations | Monitoring | ITSM | DevOps | Cloud

Microsoft Azure is the public cloud computing platform by Microsoft which offers software as a service (SaaS), platform as a service (PaaS) and infrastructure as a service (IaaS). It comprises more than 600 cloud services and supports varied operating systems, databases, and developer tools. And, even better, Splunk On-Call integrates with Microsoft Azure to help on-call teams improve incident response for Azure-based environments.

DevOps-oriented engineers live at the intersection of IT operations and software development – understanding much of what it takes to maintain IT infrastructure while also being able to write code and deploy new services. DevOps-minded teams not only create services – but they also maintain them. A DevOps structure forces teams to take accountability for their applications and infrastructure instead of allowing developers to throw code over the proverbial wall to IT operations.

Continuous integration (CI) makes the cycle from design to code to building artifacts seamless and consistent. Continuous delivery (CD) makes delivery of that artifact to an environment the same every time. But, what about the actual environment the artifact is running in? Is it the same every time? That’s a hard thing to guarantee — unless you take advantage of an Infrastructure-as-Code (IaC) approach. This post explains how to use Infrastructure-as-Code to improve CI/CD.

Because DevOps practices can bring great speed and reliability to the software delivery lifecycle, release management can seem daunting. But, the improved visibility and collaboration brought about by DevOps can also help with the release management process. While the general concept of release management doesn’t really change between ITIL (IT Infrastructure Library) and DevOps, there are a few ways that the process differs.

Over the past few years, cloud computing has enabled agile, dynamic management of software and hardware components, on-demand. Nowadays, we can define our desired infrastructure in as little as a few lines of code, and we can provision real servers on cloud providers like AWS or Azure. Terraform is an open-source infrastructure-as-code (IaC) tool that has become the de facto solution for provisioning one aspect of those components.

OpenStack vs AWS is a discussion that almost every organisation must conduct when adopting a cloud strategy. This is because OpenStack and AWS are undoubtedly some of the most popular cloud technologies in both public and private cloud space. While AWS is the most popular commercial cloud platform, OpenStack remains its most popular open source equivalent. Both have their own pros and cons. But which one is better for you?

I’m excited to share Puppet’s increased commitment to government agencies through a new relationship with Carahsoft. Through this relationship, Puppet, the industry leader in infrastructure automation, will increase its availability of Puppet Enterprise on preferred government purchasing vehicles, like the General Services Administration (GSA) Schedule 70, NASA SEWP, and a number of other federal, state, and local contracts.

As Kubernetes Pods don't store data persistently, it offers different storage components to prevent this data loss. In this blog, learn how Volume works in Kubernetes, how to create it, and how to attach it to the Pod. Before exploring Kubernetes volumes, let’s first understand Docker. Docker containers are meant to be transient, which means they will only last for a short period. They are called upon when required to process data and are destroyed once finished.

I am super excited to announce that we have released our "clone environment" feature. It is a massive update!! With one click, you can duplicate an existing environment. The cloning environment has been a significant feature expected by our customers and users for a long time. Thanks to our beta testers and our team for making it live for everyone. Here is a short video showing the clone environment in action ‍