Operations | Monitoring | ITSM | DevOps | Cloud

Choosing the right OpenStack distribution is essential to the success of an OpenStack project at every organisation. When selecting one, organisations should always follow certain criteria. Is it possible to operate the considered OpenStack distributions economically? How easy is it to deploy them? Can the organisation upgrade its production OpenStack cloud without affecting the workloads? Everyone planning to deploy OpenStack should ask themselves these questions.

FIPS 140-2 is a set of publicly announced cryptographic standards developed by the National Institute of Standards and Technology. It is an essential part of FEDRamp requirements for many governmental agencies in the US and Canada, as well as their business partners from all around the world. Furthermore, as a well established and verified security standard, an increasing number of large companies and financial institutions are asking for FIPS compliance.

In the last post, we compared kiam and kube2iam head-to-head. While kube2iam was declared the winner of that comparison, I feel that the case for kiam too compelling, and the setup too complicated, to not share my experience setting it up in production.

Engineering and “the business” don’t always speak the same language. That’s why in this blog post and webinar, we want to show you how to bridge the gap using the language “the business” understands: cold hard cash. When talking to the business value, here are four areas that DevOps provide value for your organization with associated calculators so you can get an exact value to share with your organization.

When monitoring highly distributed applications, which might rely on hundreds of services and infrastructure components across multiple cloud-based and on-premise environments, identifying problems and pinpointing the origin of an issue can be challenging. Even if you already have robust monitoring and alerts, your infrastructure and applications will likely change over time, which may make it difficult to reliably detect irregular behavior.

Rancher 2.4 is here – with new under-the-hood changes that pave the way to supporting up to 1 million clusters. That’s probably the most exciting capability in the new version. But you might ask: why would anyone want to run thousands of Kubernetes clusters – let alone tens of thousands, hundreds of thousands or more? At Rancher Labs, we believe the future of Kubernetes is multi-cluster and fully heterogeneous.

In the last month, we’ve seen one of the most dramatic movements in economic activity ever recorded. Many business owners are clutched in the grips of mandatory closures and uncertainty of the future, for their business and for their employees. The tech world has been hit less hard — at least for now. Remote work is second nature to many of us and offering our products in the digital space means we are open for business.

The Vanilla framework has a history of being released very infrequently. Sometimes it has been months between releases, which made the upgrade process often hard and time-consuming. One of the reasons for that was a manual and a quite time-consuming release process. Over several weeks earlier this year, we’ve been working on various improvements that helped us release more frequently and reliably.