Home > Communication Service Provider Solutions > Telecom Multicloud Foundation > Canonical > Guides > Reference Architecture—Canonical Charmed OpenStack (Ussuri) on Dell EMC Hardware > OpenStack validation
When the OpenStack cluster is deployed, ensure that it is fully operational and expected functionality is available.
Canonical recommends that you run a set of automated tests leveraging existing Open Source components for providing the best user experience:
Developed by the OpenStack community, Tempest includes a variety of tests for all possible features provided by OpenStack components. Functional, Unit, and Scenario tests allow performing a comprehensive analysis of the running cluster.
Canonical’s recommendation is to run the test suite based on the RefStack Guideline that covers the functionality of the Charmed OpenStack.
Community-driven project Rally is ideal for performance analysis and functional testing of the OpenStack environment. It acts as the real user only leveraging public endpoints of the cluster, making sure that the cluster users are fully satisfied with OpenStack functionality.
With Ceph being the default storage backend for multiple components of Charmed OpenStack such as Block, Image, Object and Compute services, it is important to get maximum performance from the Ceph cluster. Ceph community provides a native tool for testing of Ceph RADOS (object layer) called Rados Bench. Canonical recommends using this tool for baseline testing of the cluster performance.
In addition to that, it is valuable to separately test the block level of the Ceph cluster with the Open Source tool FIO (flexible I/O tester). Leveraging RBD (RADOS Block Device) driver, FIO tests input/output performance of the image within Ceph in the same fashion as the performance of the generic block device.