Cloud verification¶

MCP enables the deployment, QA, support engineers, and cloud operators to perform functional as well as non-functional types of testing of cloud environments through DriveTrain using the Cloud Verification Pipeline (CVP) tooling.

CVP is a set of tools, procedures, and components allowing for automatic MCP deployments verification. CVP can be applied to the newly built deployments to verify the functionality, performance, and fault tolerance of cloud environments as well as to the exisiting deployments to verify their functionality and performance before and after any changes.

The main characteristics of CVP inlude:

• Non-destructive testing
• Resources cleanup after test run
• Fully automated test runs
• Granular configurable testing
• Extensible tests enabling the operator to add custom tests in the PyTest format and extend the Tempest test framework for OpenStack functional tests

CVP requires the Internet connection to the following URLs:

• https://github.com (for repositories)
• https://files.pythonhosted.org and https://pypi.org (for pip packages)
• http://download.cirros-cloud.net (preferable but not required)

If HTTP or HTTPS proxies are in use, they must be present in the Docker daemon configuration.

CVP pipelines work in the offline mode but some adjustments may be needed for MCP pipelines.

This section explains how to perform different types of cloud verification using corresponding Jenkins pipelines.