Abstract
The analysis and understanding of resources utilization in shared infrastructures, such as cloud environments, is crucial in order to provide better performance, administration and capacity planning. The management of resource usage of the OpenStack-based cloud infrastructures hosted at INFN-Padova, the Cloud Area Padovana and the INFN-PADOVA-STACK instance of the EGI Federated cloud, started with the deployment of Ceilometer, the OpenStack component responsible for collecting and managing accounting information. However, by using Ceilometer alone we found some limiting problems related to the way it handles information: among others, the imbalance between storage and data retention requirements, and the complexity in computing custom metrics. In this contribution we present a tool, called CAOS, which we have been implementing to overcome the aforementioned issues. CAOS collects, manages and presents the data concerning resource usage of our OpenStack-based cloud infrastructures. By gathering data from both the Ceilometer service and Open-Stack API, CAOS enables us to track resource usage at different levels (e.g. per project), in such a way that both current and past consumption ofresources can be easily determined, stored and presented.
Highlights
In this article we are going to describe our accounting and monitor tool CAOS (Control Application for OpenStack) for different OpenStack based cloud infrastructures: the Cloud Area Padovana (CAP) [1], the INFN-PADOVA-STACK instance of the EGI federated cloud [2], the cloud of the University of Padova [3] and a private testbed cloud
The management of resource usage of the OpenStack-based cloud infrastructures hosted at INFN-Padova, the Cloud Area Padovana and the INFNPADOVA-STACK instance of the EGI Federated cloud, started with the deployment of Ceilometer, the OpenStack component responsible for collecting and managing accounting information
Several post-processing steps or work-arounds are required in order to fix some known bugs affecting different versions of OpenStack adopted, starting from Kilo, successively Mitaka and Ocata. Because of these problems we implemented a tool, called CAOS (Control Application for OpenStack), which manages and presents the accounting data provided by OpenStack
Summary
In this article we are going to describe our accounting and monitor tool CAOS (Control Application for OpenStack) for different OpenStack based cloud infrastructures: the Cloud Area Padovana (CAP) [1], the INFN-PADOVA-STACK instance of the EGI federated cloud [2], the cloud of the University of Padova [3] and a private testbed cloud. We are going to describe the architecture of the software, the functionality that CAOS offers and why we decided to create this new component in our infrastructure
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
