From Fedora Project Wiki

(update name of services_start test case)
(move several other base tests over here from the base matrix, having them split doesn't make sense)
 
Line 10: Line 10:
 
| Basic
 
| Basic
 
| [[QA:Testcase_base_startup]]
 
| [[QA:Testcase_base_startup]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic
 +
| [[QA:Testcase_base_reboot_unmount]]
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
Line 17: Line 24:
 
| Basic
 
| Basic
 
| [[QA:Testcase_base_system_logging]]
 
| [[QA:Testcase_base_system_logging]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic
 +
| [[QA:Testcase_base_update_cli]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic / Beta
 +
| [[QA:Testcase_package_install_remove]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic / Final
 +
| [[QA:Testcase_base_artwork_release_identification]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Final
 +
| [[QA:Testcase_base_edition_self_identification]]
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
Line 53: Line 88:
 
| Basic
 
| Basic
 
| [[QA:Testcase_base_startup]]
 
| [[QA:Testcase_base_startup]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic
 +
| [[QA:Testcase_base_reboot_unmount]]
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
Line 59: Line 100:
 
| Basic
 
| Basic
 
| [[QA:Testcase_base_system_logging]]
 
| [[QA:Testcase_base_system_logging]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic
 +
| [[QA:Testcase_base_update_cli]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic / Beta
 +
| [[QA:Testcase_package_install_remove]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Basic / Final
 +
| [[QA:Testcase_base_artwork_release_identification]]
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
|-
 +
| Final
 +
| [[QA:Testcase_base_edition_self_identification]]
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}
 
| {{result|none}}

Latest revision as of 18:29, 17 June 2020

Template documentation [edit]
This documentation is transcluded from Template:Cloud test matrix/doc. It will not be transcluded on pages that use this template.
Warning.png
Wikitcms core page
This page is a core component of the Wikitcms system for storing release validation testing results in the Fedora wiki. This system relies on specific expectations regarding page naming, contents, and categorization. Please take special care when editing this page, especially if you change any element of wiki syntax, especially templating elements. If you are at all unsure about the consequences of your planned change, please contact the QA group before applying it.

This template contains the Cloud 'test matrix' of test cases that are usually executed as part of release validation testing. It is pulled into release validation results pages using several nested templates, and can be used in other pages as appropriate. If all you need to do is add, remove or edit a Cloud validation test case, though, don't worry about that stuff, and put it in here.


Cloud Provider Setup

Expand one of the sections below for instructions on getting set up to run these testcases on a specific provider. More information can be found in the Fedora Cloud guide.

Amazon EC2

  1. Get an AWS account (the approval process can take hours)
  2. Make sure that your security group allows for SSH (default tcp port 22)
  3. Log in to the AWS Management Console
  4. Obtain the AMI id of the image you want to test. For officially released images, check http://cloud.fedoraproject.org/. If you're doing validation testing, there should be some tables of AMI IDs above; if not, try looking through the messages published by the AMI publisher
  5. Search for and select the desired AMI on the IMAGES/AMIs section of the EC2 console
  6. Launch an instance with the AMI under test

Amazon provided this information on various instance types that may be useful to test, in August 2019. Note that you can use 750 hours per month on a t2.micro instance (which is Xen-based) for free for the first year; other instance types, and t2.micro after the first year, cost money. To avoid costs, you can contact the the Infrastructure team and request access to Fedora's AWS account for testing purposes, per this SOP.

x86 platforms

  • Xen domU with only PV interfaces (e.g., M3 instances)
  • Xen domU with Intel 82599 virtual functions for Enhanced Networking (e.g., C3 instances running in a VPC)
  • Xen domU with Enhanced Networking Adapter (e.g., R4 instances)
  • Xen domU with NVMe local instance storage (e.g., virtualized I3 instances)
  • Xen domU with more than 32 vCPUs (e.g., c4.8xlarge)
  • Xen domU with four NUMA nodes (e.g., x1.32xlarge)
  • Xen domU with maximum RAM available in EC2 (x1e.32xlarge)
  • KVM guest with consistent performance (e.g., c5.large)
  • KVM guest with burstable performance (e.g., t3.large)
  • KVM guest with local NVMe storage (e.g., c5d.large)
  • KVM guest with 100 Gbps networking and Elastic Fabric Adapter (c5n.18xlarge)
  • KVM guest on AMD processors (e.g., m5a.large)
  • KVM guest on AMD processors with maximum NUMA nodes (e.g., m5a.24xlarge)
  • Bare metal Broadwell (i3.metal)
  • Bare metal Skylake (m5.metal)
  • Bare metal Cascade Lake (c5.metal)

Arm platforms

  • KVM guest on Arm with 1 CPU cluster (a1.xlarge)
  • KVM guest on Arm with 2 CPU clusters (a1.2xlarge)
  • KVM guest on Arm with 4 CPU clusters (a1.4xlarge)

Openstack

  1. Use your own OpenStack deployment
  2. Provide or create an SSH keypair
  3. Make sure that your security group allows for SSH (default tcp port 22)
  4. Log in to the Horizon dashboard
  5. Find the image URL at http://cloud.fedoraproject.org/ or as provided in release candidate documents.
  6. Add the image to OpenStack, either using the OpenStack web dashboard (see step 4 here) or with glance image-create --name "Fedora version" --disk-format qcow2 --container-format bare --is-public true --copy-from url
  7. Launch the instance (in the dashboard, under the "Images" heading, click the "Launch" button for the appropriate image

Local testing

  1. You can deploy the cloud image locally either using the well-known virt-install tool or a Fedora-specific testcloud tool. See Local cloud testing with virt-install or Testcloud quickstart guide, respectively.
  2. Once logged in the virtual cloud instance, you can perform the tests below.

x86_64

Milestone Test Case Local EC2 (KVM) EC2 (Xen) Openstack
Basic QA:Testcase_base_startup
none
none
none
none
Basic QA:Testcase_base_reboot_unmount
none
none
none
none
Basic QA:Testcase_base_system_logging
none
none
none
none
Basic QA:Testcase_base_update_cli
none
none
none
none
Basic / Beta QA:Testcase_package_install_remove
none
none
none
none
Basic / Final QA:Testcase_base_artwork_release_identification
none
none
none
none
Final QA:Testcase_base_edition_self_identification
none
none
none
none
Final QA:Testcase_base_services_start
none
none
none
none
Final QA:Testcase_base_selinux
none
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none
none


aarch64

Milestone Test Case Local EC2 (KVM) Openstack
Basic QA:Testcase_base_startup
none
none
none
Basic QA:Testcase_base_reboot_unmount
none
none
none
Basic QA:Testcase_base_system_logging
none
none
none
Basic QA:Testcase_base_update_cli
none
none
none
Basic / Beta QA:Testcase_package_install_remove
none
none
none
Basic / Final QA:Testcase_base_artwork_release_identification
none
none
none
Final QA:Testcase_base_edition_self_identification
none
none
none
Final QA:Testcase_base_services_start
none
none
none
Final QA:Testcase_base_selinux
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none