[Starlingx-discuss] [Test] STX Sanity Test Cases after Containerization

[Cabrales, Ada]

Awesome, Numan... let me check them.
Let's sync about this tomorrow.

A.

From: Waheed, Numan [mailto:Numan.Waheed at windriver.com]
Sent: Monday, January 21, 2019 2:27 PM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>; Cabrales, Ada <ada.cabrales at intel.com>
Subject: [Test] STX Sanity Test Cases after Containerization

Hi Ada,

As discussed last week, please find below test case titles for STX Sanity after containerization.

Test Steps for these sanities are posted at the following shared folder:

https://drive.google.com/drive/folders/1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY

Name of the files are "platform_sanity.txt" and "stx_openstack_sanity.txt".

Please note that there will be two sanities after containerization. First will be for Platform services i.e. without installing OpenStack and the second will be with OpenStack.

Sanity (Platform Only)
Platform sanity test cases. Following list of test cases can be executed before stx-openstack is deployed.

test_launch_app_via_kubectl(copy_test_apps, delete_test_pod, controller)
test_launch_app_via_sysinv(copy_test_apps, cleanup_app)
test_push_docker_image_to_local_registry(controller)
test_upload_helm_charts(copy_test_apps, controller)
test_kube_system_services(controller)
test_horizon_host_inventory_display(host_inventory_pg)
test_lock_active_controller_reject(no_simplex)
test_lock_unlock_host(host_type, collect_kpi)
test_swact_controller_platform(wait_for_con_drbd_sync_complete)

To be added:
- Test case to validate container messaging (eg: ssh into pod, messaging between pods)

Sanity (With OpenStack)
Sanity with stx-openstack. Following list of test cases are executed after stx-openstack is deployed.

Tests should be executed with various configurations:
- system with remote storage, single node system, multi-node system, etc.
- https
- IPv4, IPv6

test_openstack_services_healthy()
test_reapply_stx_openstack(skip_for_no_openstack)
test_stx_openstack_helm_override_update_and_reset(skip_for_no_openstack, reset_if_modified)
test_horizon_create_delete_instance(instances_pg)
test_heat_template()
test_system_persist_over_host_reboot(host_type)
test_add_host_simplex_negative(simplex_only)
test_evacuate_vms(self, vms_)
test_swact_controllers(wait_for_con_drbd_sync_complete)
test_measurements_for_metric(meter)
test_ceilometer_meters_exist(meters)
test_system_alarms_and_events_on_lock_unlock_compute(no_simplex)
test_lock_unlock_host(host_type, collect_kpi)
test_vm_meta_data_retrieval()
test_reboot_only_host(self, get_zone)
test_migrate_vm(check_system, guest_os, mig_type, cpu_pol)
test_nova_actions(guest_os, cpu_pol, actions)
test_vm_with_a_large_volume_live_migrate(vms_, pre_alarm_)
test_ping_between_two_vms(guest_os, vm1_vifs, vm2_vifs, skip_for_ovs)

To be added:
- Deploy stx-openstack from controller-1 (currently initial deployment of stx-openstack is always done from controller-0)
- Recovery scenarios: validate pods recovered if process killed or pod deleted (eg: nova-compute, libvirtd)

Thanks,

Numan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190121/3776e343/attachment.html>