Operations | Monitoring | ITSM | DevOps | Cloud

A proper container security strategy involves evaluating all components in the system.

If you google “DevOps tools,” you’ll see a dizzying litany of software applications, all promising to simplify your life as a DevOps engineer. This can be an intimidating experience — not only because there are so many DevOps solutions available that it can be difficult to know which ones are the best for your needs, but also because the idea of having to learn and “carry around” so many tools is itself unnerving.

With AWS Lambda, we can deploy and scale individual functions. However, we as engineers still like to think in terms of services and maintain a mapping between business capabilities and service boundaries. The service level abstraction makes it easier for us to reason about large systems. As such, cohesive functions that work together to serve a business feature are grouped together and deployed as a unit (i.e. a service) through CloudFormation.

Today we are happy to announce StackStorm v2.10.4. This is another bug fix release in the v2.10.x release series. It includes the following bug fixes and improvements...

I started Blue Matador in 2016 to help people like me. Site reliability engineers and devops engineers time is in short supply while the demands keep growing. We support an increasing number of applications, microservices, tools, libraries, languages, runtimes, pipelines, analytics and BI suites, and more. At the same time we’re supporting more applications, the applications themselves are growing more and more complex both from a deployment and a management angle.

In this blog post, I will focus on configuring OpenEBS as a persistent storage option on the open-source self-managed OpenShift Origin and deploy a stateful workload (MongoDB) both from CLI and custom catalog template using OpenEBS storage classes.