OpenStack observability with Sovereign Cloud Stack

Guard Duty

From Health Monitor to CloudMon

OpenStack Health Monitor is an important component for the SCS project. The program relies on the OpenStack API to cover various scenarios and assess the functionality of an OpenStack cloud from a customer perspective.

The OpenStack Health Monitor periodically installs virtual machines, creates load balancers, and checks the availability of these components. It also logs runtimes so that changes such as delayed provisioning of virtual machines can be tracked. This feature is especially helpful when changes are made to the system environment, such as after an upgrade to OpenStack components, to help identify problems – ideally before end users notice them.

The OpenStack Health Monitor first saw the light of day more than four years ago in the Open Telekom Cloud (OTC). The project was initiated then by Kurt Garloff, who is the current CTO of the SCS project. Colleagues at OTC have since further developed the OpenStack Health Monitor for their environment and presented the resulting APIMon project at the OpenInfra Summit 2020 [9].

Following OpenInfra Summit 2022, APIMon developers met with members of the SCS community to consider how to collaborate on the next iteration. The intent was to develop and maintain an independent successor project, CloudMon, to serve as a reference for behavior-driven monitoring.


One of the next priorities for the Monitoring SIG will be to expand log management. Kolla Ansible currently provides a fluentd daemon along with ElasticSearch for log shipping. Especially in terms of compliance requirements in the CSP environment (think audit logging), an installed SCS environment would ideally already include appropriate underpinnings. It would provide SCS operators best practices for aggregating relevant log messages, such as those relating to attempted logins processed by Keycloak.

The reference implementation of the Sovereign Cloud Stack can be easily put through its paces in the OSISM testbed [10], and it also provides a good introduction to the project. All meetings related to SCS can be viewed on the project website under Contribute to SCS [11]. SCS is currently looking for developers to join the community.

The Author

Felix Kronlage-Dammers has been building open source IT infrastructure since the late 1990s. Between then and now, he was part of various open source development communities, from DarwinPorts to OpenDarwin to OpenBSD and, nowadays, the Sovereign Cloud Stack. His interests range from monitoring and observability over infrastructure as code to building and scaling communities and companies. He has been part of the extended board of the Open Source Business Alliance (OSBA) for six years and describes himself as a Unix/open source nerd. If not working, he is usually found on a road bike.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy ADMIN Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Bare metal deployment with OpenStack
    Automating processes in the age of the cloud is not just a preference, but a necessity, especially as it applies to the installation and initial setup of compute nodes. OpenStack helps with built-in resources.
  • The state of OpenStack in 2022
    The unprecedented hype surrounding OpenStack 10 years ago changed to disillusionment, which has nevertheless had a positive effect: OpenStack is still evolving and is now mainly deployed where it actually makes sense to do so.
  • Combining containers and OpenStack
    The OpenStack cosmos cannot ignore the trend toward containers. If you want to combine both technologies, projects like Magnum, Kolla, and Zun come into play. Which one?
  • Questions about the present and future of OpenStack
    OpenStack has been on the market for 12 years and is generally considered one of the great open source projects. Thierry Carrez and Jeremy Stanley both work on the software and provide information about problems, innovations, and future plans.
  • Alternative virtualization solutions when OpenStack is too much
    OpenStack is considered the industry standard for building private clouds, but the solution is still far too complex and too difficult to maintain and operate for many applications. What causes OpenStack projects to fail, and what alternatives do administrators have?
comments powered by Disqus
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs

Support Our Work

ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.

Learn More”>


		<div class=