Search results

* ARM release criteria / test matrix adjustments * Visible Cloud release criteria / test matrix adjustments

| name = Fedora Test Days | caption = Fedora Cloud Image Testing

| name = Cloud SIG EC2 Image Fedora Test Day | website = [https://fedoraproject.org/wiki/Cloud_SIG Cloud SIG]

...uses existing infrastructure to create scalable and secure AWS-compatible cloud resources for compute, network and storage. * Cloud Controller (The central web service stack, web UI, account management, etc.

...ded to record cloud [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release. == How to test ==

...cerns, send mail to [https://admin.fedoraproject.org/mailman/listinfo/test test@lists.fedoraproject.org]. * [[User:Adamwill|Adamwill]] ([[User talk:Adamwill|talk]]) - We forgot to test Secure Boot until very late.

...records base system [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 PPC''' release. ...Do we support for ppc64/ppc64le architectures all Products listed below in test matrix:

* Primary use cases: (Development, general productivity, etc) * Is your server for production/test/learning/? ?

| name = Cloud SIG BoxGrinder Build Fedora Test Day ...-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

| name = Fedora Test Days | caption = Fedora Cloud Image Testing

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

| name = Fedora Test Days | fedora_mailing_list = cloud

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha TC6''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta TC3''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha RC1''' release. == How to test ==

This is a collaborative list of current and future work for the Fedora Cloud SIG. It's meant to describe what's needed or wanted, and what is being done * [https://fedorahosted.org/cloud/report/1 All active tickets]

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta RC2''' release. == How to test ==

about their virtual instances, as well as cloud admin tasks like managing users and tenants/accounts. == How To Test ==

...records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''Fedora 20 Final RC1.1''' release. == How to test ==

...records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha RC3''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta RC3''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta RC4''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta TC4''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha TC1''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta TC6''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta TC5''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha RC2''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha TC3''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta TC1''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha TC5''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Final TC3''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Final TC1''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Final TC2''' release. == How to test ==

...records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha TC4''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha RC4''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for Rawhide nightly builds in the month of April 2014. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta TC2''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Alpha TC2''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Beta RC5''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Final RC1''' release. == How to test ==

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Final TC4''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''20 Final TC5''' release. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for Rawhide nightly builds in the month of July 2014. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for Rawhide nightly builds in the month of June 2014. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for Fedora 21 nightly builds in the month of August 2014. == How to test ==

This page records [[QA:Base_validation_testing|base validation testing]] test results for Rawhide nightly builds in the month of May 2014. == How to test ==

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release. == How to test ==

= Build Fedora Cloud Images with Hybrid BIOS+UEFI Boot Support = With recent changes in public cloud widely accepting the

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

Taskotron roadmap: https://phab.qadevel.cloud.fedoraproject.org/w/taskotron/roadmap/ * Will need to file another RFE to test AMIs in Taskotron

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...o plans to bring it back. Currently Fedora Infrastructure relies on gifted cloud units from Amazon for this.}} Fedora Infrastructure is running a private cloud infrastructure for various infrastructure and community projects. This infr

| name = Fedora Test Days | fedora_mailing_list = cloud

| name = Fedora Test Days | fedora_mailing_list = cloud

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

Fedora Cloud Work Group- 14 August 2014 - Rochester, NY - FLOCK ...being produced that could do gating and non-gating tests on these images. Test coverage is a challenge right now - we have some tests but it needs to be g

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

| name = Fedora Test Days | caption = OpenStack Test Day

= Modular Kernel Packaging for Cloud = * Name: Cloud SIG / [[User:red|Sandro Mathys]], Kernel Team / [[User:jwboyer|Josh Boyer]]

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

In some cases Fedora Package maintainers may not have access to all supported architectur ...chines/instances that they maintain to allow Fedora package maintainers to test, build, compile or debug their packages.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) == Major use-cases: ==

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

...also be filed as system-wide changes. Each of these will have at least one Cloud SIG member ...and marketing are others. For each of these, we will find someone from the Cloud SIG to take responsibility, including contributing effort where applicable.

These steps could be useful to speed up a droplet deployment in order to test a Fedora image. ...port.digitalocean.com/s/#none|ka21N000000CpMeQAK in order to access Fedora cloud images.<br/>

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

= Make btrfs the default file system for Fedora Cloud = ...age its features and capabilities to improve the quality of experience for Cloud users.

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/20/ChangeSet|accepted Changes of {{FedoraVersion|long|20}}]]

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...on older Ruby and Rails can run happily. Ruby SCL was picked, because many Cloud projects is still dependent on older version of Rails. It would be wise to

=Bringing the Cloud to the Fedora Desktop= ...tionality required by a user to run and manage virtual machines on various cloud service providers such as Amazon EC2, Rackspace, Red Hat RHEV etc.<br/>

This change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation. This change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...run on Fedora. We see it often with Ruby (on Rails) projects like Puppet, Cloud projects (Katello, Foreman, OpenShift, OpenStack). All those cool apps can

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/21/ChangeSet|accepted Changes of {{FedoraVersion|long|21}}]]

...of this Change is to promote support of the rpm-ostree tool for those use cases. ...s first prototyped in Fedora Core 6 timeframe. Today, particularly in the cloud, many deployments perform OS upgrades by terminating an instance, and booti

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...rpms are at http://koji.fedoraproject.org/scratch/jakub/task_8710312/ and test mass rebuild is in progress.

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...t day for Fedora 16, moving forward with a Fedora Cloud spin, work on test cases for brtfs, and much more. Security Advisories brings us current with the s === Test Days ===

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) Marek Polacek has performed a test mass rebuild on x86_64 with gcc-4.9.0-0.*.fc21, most packages have built su

...ll update the Test Day SOP as agreed (encourage use of webapp for tracking test day results)'' - this was [https://fedoraproject.org/w/index.php?title=QA%2 * adamw noted that it was Graphics Test Week and asked people to help out with testing

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...choice about what infrastructure they would like to put in place for their cloud. == How To Test ==

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

...tt>/usr/lib/os-release</tt>) only for the main Fedora Editions (and Fedora Cloud Base, because of its history as an edition previously). This means we can't == How To Test ==

* [https://lists.fedoraproject.org/pipermail/test/2011-October/103729.html Proposed meeting agenda] ...was planned for 2011-10-20, tflink trying to co-ordinate organization with Cloud SIG

...fy enough, the Alpha release of Fedora 18 is even meatier. Anyone can help test this release, guided by the [[QA|Fedora QA team]], which helps us identify === Cloud and Virtualization ===

= Build Fedora Cloud Edition Images Using Kiwi in Koji = ...agefactory ImageFactory] tooling that is currently being used to build the cloud base images.

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

...nstall your own instance of openQA so you can try it out and contribute to test development. ...-level testing. Its key feature is that it interacts with the system under test much like a human would, by sending input using a virtual keyboard and mous

* Test Days ...ecided that it doesn't make sense to do this with the current app. current cloud setup is OK for now

| name = Fedora Test Days | caption = OpenStack Test Day

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) We are working on scratch gcc rpms and will perform a test mass rebuild.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...es selecting some of the rules (or groups of rules) targetting various use cases.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) We are working on scratch gcc rpms and will perform a test mass rebuild.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) We are working on scratch gcc rpms and will perform a test mass rebuild.

= Test Day = We held a [[Test_Day:2012-03-08_OpenStack_Test_Day|test day for OpenStack Essex in Fedora 17 on March 8]].

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/22/ChangeSet|accepted Changes of {{FedoraVersion|long|22}}]]

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...is page provides guidance on arranging and announcing a release validation test event. For any concerns, please contact the [[QA]] group. ...n/caution|This process is now automated|The creation of release validation test events is now automated. Wiki pages are created and an announcement email s

...yslog, Syslog-NG, and even traditional sysklogd will continue to cover use cases outside of the default. ...e). This is significant on systems with limited resources, like the Fedora Cloud image.

** old cloud modules, move to new 2.0 cloud management * Add a unit test suite to the-new-hotness.

...ng|Not current|The Default Offering was effectively replaced with separate Cloud/Server/Workstation editions as part the [[Fedora.next]].}} ...ees with the goal of attracting people to switch to a new OS -- offering a test drive is natural and helpful to the user.

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

...7]]'' - this was done, we have a fix waiting for review and updates.img to test against TC4 * ''tflink to poke roshi about handling test day tickets'' - poke happened, roshi will start more handling later this we

=== '''Cloud''' === The Fedora Cloud SIG works to make Fedora successful on all major cloud platforms, public and private.

...installable media versions of a [[Feature_Freeze_Policy|feature complete]] test release # Test [[Releases/20/ChangeSet|accepted Changes of {{FedoraVersion|long|20}}]]

...cerns, send mail to [https://admin.fedoraproject.org/mailman/listinfo/test test@lists.fedoraproject.org]. ...ittle to no communication regarding status. With only two weeks Alpha ISO test time, losing 50% of time almost certainly results in a slip. See {{ticket|

...orm with "featured server roles" built on top of it. We commit to produce, test, and distribute these server roles. * The platform to deploy an Infrastructure-as-a-Service (IaaS) private cloud.

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

| name = Fedora CoreOS Test Week | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/23/ChangeSet|accepted Changes of {{FedoraVersion|long|23}}]]

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/24/ChangeSet|accepted Changes of {{FedoraVersion|long|24}}]]

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/25/ChangeSet|accepted Changes of {{FedoraVersion|long|25}}]]

...BCs, IoT, and other use cases similar to the Fedora Workstation / Server / Cloud that other Fedora architectures support. ...ience on the 64 bit ARM architecture variants is very similar and, in most cases, identical to what you would find on any other Fedora architecture. We use

| name = Fedora Test Days ...ing-48px.png|link=https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]

...atus. This would include the Server installer, the DVD installer ISOs, the Cloud (qcow2 images) and Docker base images to the same status as other primary S ...ell supported and now more widely used AArch64 architecture for the Server/Cloud/Docker Base image deliverables to a primary status with wider focus.

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/26/ChangeSet|accepted Changes of {{FedoraVersion|long|26}}]]

* [http://lists.fedoraproject.org/pipermail/test/2011-April/099004.html Proposed meeting agenda] === Thursday, April 21 - GNOME3 Test Day #3 ===

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. * '''Test Subject''': The items that are to be tested.

...lications. For the past two Fedora releases, we've included an Atomic Host cloud image as a non-blocking deliverable. However, upstream Atomic is moving ver <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)

| name = Fedora Test Days | website = [http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar]

# All release media must include a standalone memory test utility. A boot menu option to launch this utility must be present and must ...U with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the re

...lications. For the past two Fedora releases, we've included an Atomic Host cloud image as a non-blocking deliverable. However, upstream Atomic is moving ver ...as possible, allowing for local users or products to override this base in cases they need to do so.

...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. * '''Test Subject''': The items that are to be tested.

...U with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the re |15 || In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notification

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...ficially deprecated upstream soon, and probably should not be used in most cases anyway. It contains legacy kerberized utilities, like rsh. There are no pac

# Publicly release installable media versions of a test release # Test accepted Changes for future releases

* [https://lists.fedoraproject.org/pipermail/test/2011-October/103496.html Proposed meeting agenda] * [[Test_Day:2011-10-13_Fedora_Packager_for_Eclipse|Eclipse test day]] looked ready to go

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...ocation of images'' - tflink followed up to some degree, but the status of cloud images and testing did not seem satisfactory, further action required ....org/testcase_stats/ testcase_stats page] tracks how often each validation test case has been run (and with what result), and when it was last run: re-gene

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...ult for Plasma. We will also attempt to automatically fall back to Xorg in cases where wayland is unavailable (like nvidia). There will still be option to u

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...orm with "featured server roles" built on top of it. We commit to produce, test, and distribute these server roles. * The platform to deploy an Infrastructure-as-a-Service (IaaS) private cloud.

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

* Test Days * ''nirik to work on revising the 'desktop updates' test case to be more generic'' - not done yet

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...org/wiki/Test_management_tools test management system] ('TCMS' stands for 'Test Case Management System', but that precise initialism is in fact quite rarel The use of the Fedora wiki to track test results dates back to at least the page [[Releases/5/FC5FinalTreeTesting]]

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

...''test suite'' (including framework) and the CI system that is running the test suite. This is the standard interface. * '''Test Subject''': The items that are to be tested.

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

* [http://lists.fedoraproject.org/pipermail/test/2011-July/101355.html Proposed meeting agenda] # rbergeron will reach out to cloud-sig for a last call on test case ideas

* [http://lists.fedoraproject.org/pipermail/test/2011-June/101057.html Proposed meeting agenda] * At tflink's suggestion, jlaska migrated our remaining production F13 test clients to F14

* ''adamw to draft a new test case and matrix row for validating cloud image checksums'' - adamw didn't get around to this yet, put back on the li ...of freeze tomorrow'' - this was [https://lists.fedoraproject.org/pipermail/test-announce/2013-November/000821.html done]

* to make minimal cloud image Python 2 free ...embedded Python support, like gdb, or Rhythmbox with its plugins. In these cases, it makes no sense to do a python3- subpackage, since the whole package wou

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

...U with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the re # In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notification

* ''tflink to make sure some cloud testing is getting done'' - this was done, tim did some testing on RC4 AMIs ...g got fixed: we still needed to figure out where to file such bugs, as the cloud image kickstarts are not part of a Fedora package (yet?)

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

| name = Fedora Test Days | caption = Virtualization Test Day

# Publicly release installable media versions of a test release # Test accepted Changes for future releases

...U with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the re | 15 || In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notification

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

...luding traditional desktop users, systems administration, development, the cloud, and many more. But a few new features are guaranteed to be seen by nearly Here are just a few of the cloud and virtualization features you'll see in Fedora 18:

...It is also important to allow packagers to locally and manually invoke a ''test suite''. ...he tests package will directly <code>Requires:</code> the package of the ''test subject''.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) I ''think'' this should be beneficial in all cases. I doubt that anyone runs with broken locale settings on purpose.

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

...as possible, allowing for local users or products to override this base in cases they need to do so. <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

...g for nightlies (qa / releng) to match more closely the RC (qa / releng / test-days) == Fedora Cloud ==

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...lly, have a mass rebuild in the 24 release cycle to catch any odd breakage cases, if no mass rebuild, identify packages with BR on texlive* and manually reb

...As one example, JRuby outperforms C Ruby in nearly all benchmarks, in some cases as much as 4x faster [http://www.slideshare.net/CharlesNutter/euruko-2012-j ..., the JVM has proven itself to be the runtime to go to for large scale and cloud-based applications. The Just-in-Time (JIT) compiler, garbage collection fac

...sts.fedoraproject.org/pipermail/test/2013-November/118791.html not for the cloud images] * adamw said he would draft new test cases and submit them to the list

We want to gate packages on test results before they can land in rawhide. This will reduce the amount of bro ===[[Changes/CloudProviderImageUpdates | Cloud Provider Image Updates]]===

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) Please provide your uses and use cases of Fedora base container image(fedora on most of container registries) in [

* [http://lists.fedoraproject.org/pipermail/test/2011-June/100743.html Proposed meeting agenda] * vhumpa started a discussion on test + desktop lists last week - http://lists.fedoraproject.org/pipermail/deskto

Supporting unified kernels for all use cases quickly is not realistic though. Too many features are depending on the cu * Phase 2+: Expand UKI support, tackling the use cases which depend on a host-specific initrd or command line (see below) one by o

...U with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the re # In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notification

...U with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the re # In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notification

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...pm packages. I think using a %pre macro is good enough for the majority of cases. In the case when the user or group is needed by multiple independent packa

...Fedora.Next release, what their target audiences are, and their target use cases. ...it's just bug reporting. You can also help translate software and content, test and give feedback on software updates, write and edit documentation, design

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...n Host and Platform; remaining modules will have to be updated or, in some cases, completely rewritten.

...ritten CLIs (e.g. virsh, smartctl), setup tools (e.g. ipa-server-install), test scripts could be replaced by System Configuration Shell modules ...lasses to minimize repetitive coding of shell wrappers, define simple uses cases and implement initial objects in the configuration hierarchy. The [http://w

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...direct calls of dhclient binary etc links: TBD ). The goal is to find this cases and fix them.

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [http://lists.fedoraproject.org/pipermail/test/2011-July/101230.html Proposed meeting agenda] == Cloud SIG testing ==

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) Node.js 8.x breaks compatibility in a limited number of cases, which may affect third-party software. (See the Detailed Description abov

...luding traditional desktop users, systems administration, development, the cloud, and many more. But a few new features are guaranteed to be seen by nearly ...razing</strike> gazing into the clouds? Here's just a taste of some of the cloud and virt features you'll see in Fedora 18:

== Fedora Cloud Working Group == ...ights from others. I happen to think that Fedora can be a fantastic OS for cloud usage, particularly for those consumers who value MTTR over MTTF. Our quick

<!-- Make sure the pages is named as "Test Day:YYYY-MM-DD topic" --> | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) Node.js 6.x breaks compatibility in a limited number of cases, which may affect third-party software. (See the Detailed Description abov

The role of things like Kickstart, cloud-init, and Ignition and other system config management shrinks significantly Many organizations require agents (cloud agents, security scanners, antivirus) which are not ready to be containeriz

...ptical support 2016-12-06], [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/HLXHEB364LOLFHB2RDX6K4DFA4VJIWMF/ implementa Test cases:

...ptical support 2016-12-06], [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/HLXHEB364LOLFHB2RDX6K4DFA4VJIWMF/ implementa Test cases:

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) * Responsible WG: Cloud SIG

* Test Day status and help wanted ...will be making sure cloud kickstarts get added to spin-kickstarts package, cloud kickstart bugs should be reported against spin-kickstarts package going for

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...-11-openjdk. In all cases, it will be later updated to JDK12. Also in all cases separate package will be created for any LTS JDK - next is java-11-openjdk,

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

...'t in the main koji instance to easily consume for the Server edition or a Cloud component such as Docker. As the Fedora ARM lead there's no way I'd current In the vast majority of cases this will be no more work and they'll never have an issue with these other

...ur processes to take advantage of modern, hybrid cloud footprints. In some cases we are necessarily premise-bound — for instance, Power and s390x. However * Update the compose process such that we can scale to use hybrid cloud footprints

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) --> ...without Modularity can use one of these other spins, including the Fedora Cloud Base image, or else use the "everything netinst".

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...am-utils amd map parsing functionality to cover a large portion of the use cases provided by the am-utils package. Once this is done it will be up to users

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...-11-openjdk. In all cases, it will be lateru pdated to JDK12. Also in all cases separate package will be created for any LTS JDK - next is java-11-openjdk,

The Fedora Continuous Integration SIG develops test automation system for Fedora. As well as tools and workflows for generic Co === Cloud ===

...it ships several tested stacks (profiles) that solve primary supported use cases and are well tested and supported. At the same time, some obsolete features <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...stressful to memory-management subsystem and prone to bailing out in such cases. The swap-on-zram will be favored for evictions in the attempt to free memo

...on platform in the cloud where application developers and teams can build, test, deploy, and run their applications. It manages the infrastructure, middlew ...ft Origin to easily enable developers to code and deploy applications in a cloud environment.''

<!-- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...ific configuration ([[#Interception code]]) should handle all possible use-cases (libldap, openldap-clients and openldap-servers packages). Briefly, the cod

= Cloud APIs REST Style Guide = # Document consensus amongst the various API projects related to Red Hat's cloud stack.

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) well suited for cases where multiple semi-isolated environments might

...ach one a free, Linux-based operating system tailored to meet specific use cases: Fedora 25 Atomic Host, Fedora 25 Server, and Fedora 25 Workstation. Each e * Multiple Python versions — 2.6, 2.7, 3.3, 3.4 and 3.5 — to help run test suites across several Python configurations, as well as PyPy, PyPy3, and Jy

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...ill be built in early January, but Jeff Law has been testing x86_64 Fedora test mass rebuilds with GCC 10 snapshots for a while.

...he latest Test Day on virtualization and the next Test Days on Gnome 3 and cloud integration, as well as details on Fedora 15 beta prep and Sugar build test appliances for use in a Cloud environment.

* cloud-init dustymabe gholms larsks mhayden otubo * python-pytest-cases zbyszek

** Gerrit and Github are supported as well and we could for specific cases provide CI for projects hosted there. ...rpm-test job from the tests template. This job was a duplicate of rpm-sti-test.

...ains all the exciting features of Fedora 19 in a form that anyone can help test. This testing, guided by the [[QA|Fedora QA team]], helps us target and ide ...naconda installer as well. syslinux is especially ideal for images used in cloud environments and virt appliances where the advanced features of GRUB are no

==== Bringing the Cloud to the Fedora Desktop==== ...ualizations, and more closely integrate local data and code w/ that on the cloud.