Operations | Monitoring | ITSM | DevOps | Cloud

Azure Government is a dedicated cloud for public sector organizations that want to leverage Azure’s suite of services in their highly regulated environments. As these organizations migrate their applications to Azure Government, they need to ensure that they can maintain visibility into the status and health of their entire infrastructure.

FP&A is a strategic part of the finance organization and has the potential to drive important business outcomes. When done right, it can have a major positive impact on the future of the business. When done poorly, it can slow a company down. The role of FP&A has evolved. Today it isn’t just about taking inputs and crunching numbers — it’s about being a strategic advisor to the organization.

We are very excited to announce that you can now install Shipa from the SUSE Rancher Marketplace. Installing Shipa On-Prem can now be done with a click-to-install inside of SUSE Rancher. Follow this quick guide to get you up and started with Shipa if you are leveraging SUSE Rancher.

Cloud infrastructures have introduced increasing levels of complexity—you have to manage workloads across on-premises, private, and multiple public cloud environments. This requires you to migrate efficiently, optimize effectively, and stay rightsized on an ongoing basis, all while meeting evolving business requirements. With so many moving parts, it can be a massive challenge with lots of pitfalls that can cost you time and money and even put your business results in jeopardy.

Intel and Canonical collaborate to build and publish OpenVINO™ container images based on the Ubuntu ecosystem. This work aims to provide trusted, secure, and developer-friendly container images for AI/ML applications in many industries.

Improving your influence over the company will help you deliver high quality work as your goals will be closely aligned with those of the company. In this blog piece, Ricardo has explained how to improve your influence as an SRE. Balancing fast-paced business requirements with the demands of keeping production services stable is not an easy task.

When you write enough Puppet code, you will eventually find yourself in need of a Facter fact or Puppet resource type that doesn’t exist in Puppet itself. Then, if you’re like me, you go to the Puppet Forge and see if someone else has written what you need. Oftentimes, you find what you need, add a new module to your Puppetfile or module metadata, and move on with your life.

While service incidents can be wildly dissimilar, they tend to have one thing in common: a need for quick resolution. Response teams need a robust, repeatable process to follow that ensures fast, mistake-free execution, especially for those 4 AM calls. Having a documented checklist saved where the entire team can access and use it at any time could make the difference between quick resolution or compounding the problem.