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 TC4''' 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 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