38 KiB

Raw Blame History

The Datera plugin provides a GUI configuration option for Fuel 7.0 and 8.0 to enable configuration of the cinder.conf for use with Datera's Elastic Data Fabric cluster with nodes that receive the Cinder role. The plugin also provides an updated version of the Datera Cinder driver to support the v2 API interface, as the v1 API is deprecated.

Developer’s specification

The plugin is designed to integrate the use of Datera EDF by Mirantis Openstack 7.0 and Mirantis Openstack 8.0 by leveraging Fuel 7.0 and Fuel 8.0.

For more details view the specs/fuel-plugin-datera-cinder.rst

Limitations

Mirantis Fuel 7.0 does not support cinder with multiple backends.

Prerequisites

A configured and running Datera EDF cluster or training VM, attached to the appropriate networks.

Test strategy

The Datera Fuel plugin should add the correct components to cinder.conf resulting in a functional cinder.conf. This means that all the required options should be exposed in the respective Fuel UI level for Datera and be transferred into the cinder.conf. The Datera Cinder driver that supports the v2 API should also be deployed.

All tests will be done for both Fuel 7.0 and 8.0.

Acceptance criteria

The final result should be a functioning Mirantis Fuel 7.0 and Mirantis Fuel 8.0 Openstack deployment with Datera EDF enabled and the ability to consume storage from Datera EDF.

Test environment, infrastructure and tools

The test environments were run on KVM where 7 VMs were used with 5 network interfaces per VM attached to 5 separate virtual networks.

The Storage network is placed on one of the NICs in a separate VLAN, 102 with it's own subnet, 192.168.42.0/24.

Test Environment Fuel 7.0

VM	Description	vCPU	RAM	HD	OS
1	Fuel 7.0 Master	2	4 GB	100 GB	CentOS 6.5
3	Openstack Controllers	2	4 GB	80 GB	Ubuntu
1-2	Openstack Compute	2	4 GB	80 GB	Ubuntu
1	Openstack Ceilometer	2	4 GB	80 GB	Ubuntu
1	Datera EDF Sim.	2	3 GB	64 GB + 100 GB	DaterOS 1.0.1

Test Environment Fuel 8.0

VM	Description	vCPU	RAM	HD	OS
1	Fuel 8.0 Master	2	4 GB	100 GB	CentOS 7.1
3	Openstack Controller	2	4 GB	80 GB	Ubuntu
1-2	Openstack Compute	2	4 GB	80 GB	Ubuntu
1	Openstack Ceilometer	2	4 GB	80 GB	Ubuntu
1	Datera EDF Sim.	2	3 GB	64 GB + 100 GB	DaterOS 1.0.1

Product compatibility matrix

Fuel Plugin Datera Cinder version	Fuel Version	Openstack Version
1.0.0	7.0	Kilo
1.0.0	8.0	Liberty

System testing

1. Install plugin and deploy environment

Test Case ID	install_plugin_deploy_env
Steps	Upload the plugin to the master node. Install the plugin. Create an environment with the plugin enabled. Add 3 nodes with the Controller and Cinder role, 2 node with Compute role and 1 node with another role. Deploy the cluster. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes.
Expected Result	Plugin is installed successfully, cluster is created, network verification and OSTF are passed, and all plugin services are enabled and work as expected.

2. Modifying env with an enabled plugin (removing/adding controller nodes)

Test Case ID	modify_env_with_plugin_remove_add_controller
Steps	Upload the plugin to the master node. Install the plugin. Ensure that the plugin is installed successfully using the CLI. Create an environment with the plugin enabled. Add 3 nodes with the Controller and Cinder role, 2 node with Compute role and 1 node with another role. Deploy the cluster. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes. Remove 1 node with the Controller and Cinder roles. /Remove a node, where the plugin’s services available, to ensure that according to ha mode all the plugins resources will be replaced and available on another live node and continue to work as expected / Deploy changes to Fuel. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes. Add 1 new node with the Controller and Cinder roles (*remark). Deploy changes to Fuel. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes.
Expected Result	Plugin is installed successfully, cluster is created, network verification and OSTF are passed, all plugin services are enabled after migration in ha mode and worked as expected after modification of the environment.
Remark	Make sure when doing this manually the network settings are in line with the rest of the cluster, as Fuel does not take of this for you!.

3. Modifying env with an enabled plugin (removing/adding compute node)

Test Case ID	modify_env_with_plugin_remove_add_compute
Steps	Upload the plugin to the master node. Install the plugin. Ensure that the plugin is installed successfully using the CLI. Create an environment with the plugin enabled. Add 3 nodes with the Controller and Cinder role and 2 nodes with Compute role. Deploy the cluster. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes. Remove 1 Compute node. Deploy the cluster. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes. Add 1 Compute node. Deploy the cluster. Run OSTF and network verification. Verify Datera API for creation and deletion of Volumes.
Expected Result	Plugin is installed successfully, cluster is created, network verification and OSTF are passed, all plugin services are enabled after migration in ha mode and worked as expected after modification of the environment.

4. Uninstall of the plugin with a deployed environment

Test Case ID	uninstall_plugin_with_deployed_env
Steps	Upload the plugin to the master node. Install the plugin. Ensure that the plugin is installed successfully using the CLI. Create an environment with the plugin enabled. Add 3 nodes with the Controller and Cinder role and 2 nodes with Compute role. Deploy the cluster. Run OSTF and network verification. Try to delete the plugin and ensure that the following alert is show on the CLI "400 Client Error: Bad Request (Can't delete plugin which is enabled for some environment.)" Remove environment Remove plugin Check that it was successfully removed
Expected Result	Plugin was installed successfully. Alert is present when attempting to delete the plugin which is attached to an enabled environment. When the environment was removed the plugin was removed successfully too.

5. Uninstall of the plugin

Test Case ID	uninstall_plugin
Steps	Upload the plugin to the master node. Install the plugin. Ensure that the plugin is installed successfully using the CLI. Remove the plugin Check that it was successfully removed
Expected Result	Plugin was installed and then removed successfully.

38 KiB Raw Blame History Unescape Escape

Test Plan for Datara-cinder-1.0.0 Fuel Plugin

Revision history

Datera-Cinder Plugin