This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2211302 - [RFE] Add a scenario test instances with cinder volumes launches on all compute nodes.
Summary: [RFE] Add a scenario test instances with cinder volumes launches on all compu...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 16.2 (Train)
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Jakub Skunda
QA Contact: Martin Kopec
URL:
Whiteboard:
: 2211301 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-31 04:47 UTC by Keigo Noha
Modified: 2024-01-24 10:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-01-23 08:51:41 UTC
Target Upstream Version:
Embargoed:
mkopec: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 898732 0 None NEW Add scenario test: test instances with cinder volumes 2023-11-23 15:50:28 UTC
Red Hat Issue Tracker   OSP-25498 0 None None None 2024-01-24 10:15:10 UTC
Red Hat Issue Tracker OSP-31249 0 None None None 2024-01-23 08:54:39 UTC

Description Keigo Noha 2023-05-31 04:47:22 UTC
Description of problem:
Add a scenario test instances with cinder volumes launches on all compute nodes.

This details of this scenario test is below.

1. Required additional configuration
- volume_type_for_boot(string and one volume type can be assigned e.g. volume_type_for_boot = vol_type0)
- volume_types_for_data_volume(string and multiple volume type can be assigned with comma-separated, e.g. volume_types_for_data_volume = vol_type1, vol_type2,... )

2. Test steps
-1. Create an image by cirros or specified one in tempest.conf
-2. Create a keypair
-3. Create boot volumes with the image and volume type specified at volume_type_for_boot
-4. Boot instances with the volume in step3 on all compute nodes.
-5. Create volumes based on volume_types_for_data_volume, If 6 volume type is assigned, each volume type has a volume, the total number of volumes is 6 per instance. If the number of compute nodes is 100, each volume type has 100 volumes for instances.
-6. Attach volumes each volume type in step5 to an instance. As a result, each instance has 6 data volumes except boot volume and each data volume has different volume type.
-7. Assign Floating IP to all instances.
-8. Configure security group for ssh access to all instances.
-9. Confirm ssh access to all instances.
-10. Run write test to all volumes through ssh connection per instance.
-11. Clean up the resources, an instance, volumes, keypair, image.

Comment 2 Martin Kopec 2023-08-30 09:48:46 UTC
*** Bug 2211301 has been marked as a duplicate of this bug. ***

Comment 3 Martin Kopec 2023-08-30 12:33:11 UTC
Discussed on the last PTG, it's viable. The difference in this scenario test and our existing tests is to boot instances on all the compute nodes. In existing scenario tests (example ./scenario/test_volume_boot_pattern.py) we test it on one of the compute nodes only:
https://opendev.org/openstack/tempest/src/branch/master/tempest/scenario/test_volume_boot_pattern.py

Full agenda from the PTG:
https://etherpad.opendev.org/p/vancouver-june2023-qa


Note You need to log in before you can comment on or make changes to this bug.