https://fedoraproject.org/w/api.php?action=feedcontributions&user=Kashyapc&feedformat=atomFedora Project Wiki - User contributions [en]2024-03-28T18:41:05ZUser contributionsMediaWiki 1.39.4https://fedoraproject.org/w/index.php?title=How_to_enable_nested_virtualization_in_KVM&diff=502682How to enable nested virtualization in KVM2017-10-03T08:09:22Z<p>Kashyapc: </p>
<hr />
<div>Nested virtualization allows you to run a virtual machine (VM) inside another VM while still using hardware acceleration from the host.<br />
<br />
== Nested virt support ==<br />
<br />
Check if your system supports it:<br />
<ol><br />
<li> For Intel processors, look into <code>/sys/module/kvm_intel/parameters/nested</code>, for AMD processors into <code>/sys/module/kvm_amd/parameters/nested</code>. You should receive <code>1</code> or <code>Y</code>, if nested virt is supported, <code>0</code> or <code>N</code> otherwise. AMD processors should have it enabled by default, (certain) Intel processors might not. Example:<br />
<pre>$ cat /sys/module/kvm_intel/parameters/nested<br />
Y</pre><br />
<li> If your host system does not have nested virt enabled (most probably just Intel case), try to enable it by booting with <code>kvm-intel.nested=1</code> argument on the kernel command line and check it again.<br />
</ol><br />
<br />
If your system still doesn't advertise support for nested virt, your hardware might be too old, or your distribution version outdated. Try booting latest Fedora.<br />
<br />
== Configuration in virt-manager ==<br />
<br />
Configure your VM to use nested virt:<br />
<ol><br />
<li> Make sure your VM is shut down<br />
<li> Open virt-manager, go to the VM details page for that VM.<br />
<li> Click on the Processor page.<br />
<li> In the Configuration section, there are two options - either type <code>host-passthrough</code> into to Model field or enable <i>Copy host CPU configuration</i> checkbox (that fills <code>host-model</code> value into the Model field). Click Apply.<br />
<ul><li>The difference between those two values is complicated, some details are in [https://bugzilla.redhat.com/show_bug.cgi?id=1055002 bug 1055002]. For nested virt, you'll probably want to use <i>host-passthrough</i> until issues with <i>host-model</i> are worked out. Be aware though, that <i>host-passthrough</i> is not recommended for general usage, just for nested virt purposes.</li></ul><br />
</ol><br />
<br />
== Test nested virt ==<br />
<ol><br />
<li> Start the VM<br />
<li> Inside the VM, run <code>sudo dnf group install virtualization</code><br />
<li> Verify that the guest has virt correctly setup with: <code>sudo virt-host-validate</code> . The check for hardware virtualization should pass:<br />
<pre><br />
$ sudo virt-host-validate <br />
QEMU: Checking for hardware virtualization : PASS<br />
QEMU: Checking for device /dev/kvm : PASS<br />
QEMU: Checking for device /dev/vhost-net : PASS<br />
QEMU: Checking for device /dev/net/tun : PASS<br />
LXC: Checking for Linux >= 2.6.26 : PASS<br />
</pre><br />
</ol><br />
<br />
<br />
== See Also ==<br />
* [[QA:Testcase KVM nested virt]]<br />
* https://bugzilla.redhat.com/show_bug.cgi?id=1055002<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* https://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
<br />
[[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc/Python_Eggs&diff=399954User:Kashyapc/Python Eggs2015-01-06T20:56:17Z<p>Kashyapc: More edits to clarify terminology</p>
<hr />
<div>= Python egg metadata =<br />
<br />
Python packages provide extra metadata about the package in the form of egg metadata. This document explains how to package egg metadata.<br />
<br />
== Why egg metadata ==<br />
egg metadata have several uses including:<br />
<ol><br />
<li>Allowing end users to install egg packages not made from rpms or install egg packages into their home directories. This is an important feature for people working within a shared hosting environment.<br />
<li>Giving python packages an easy way to support plugins.<br />
<li>Giving us a way to support multiple versions of a python module for compat libraries.<br />
</ol><br />
<br />
The egg metatada can be used at runtime so it cannot be replaced with the rpm database which is only useful at install time or by tools specifically for Fedora.<br />
<br />
{{Anchor|Whenegg metadata}}<br />
== When to Provide egg metadata ==<br />
Since egg metadata establish a base of functionality that upstream authors can expect, we need to be sure to include the egg metadata if a package builds them. Starting with Fedora 9 any package that uses setuptools or distutils will build egg-info. In Fedora 8 or less, only setuptools packages build egg-info. If you need to provide egg-info for a distutils package on Fedora 8 or less, [[#Providing_Eggs_for_non-setuptools_packages| Providing egg metadata using Setuptools]] describes a method of substituting setuptools for distutils in the build process so egg-info is created.<br />
<br />
<br />
{{admon/note|| In the past, when there was a requirement for an egg which was not provided by upstream we would patch the requiring package to not require that package. This behaviour is deprecated and as packages are updated maintainers should follow the below guidelines to install egg metadata for the required packages. Please see [[#Providing_Eggs_for_non-setuptools_packages| Creating egg metadata for Non-setuptools Packages]] <br />
}}<br />
<br />
== Upstream egg packages ==<br />
Do not distribute egg packages from upstream. In Fedora, all packages must be rebuilt from source. An egg package (which is different from egg ''metadata'') contains compiled bytecode and may, if it contains a C extension, contain compiled binary extensions as well. These are opaque structures with no guarantee that they were even built from the source distributed with the egg. If you must use an egg from upstream because they do not provide tarballs, you need to include it as a source in your spec, unzip it in %setup, and rebuild from the source files contained within it.<br />
<br />
== Providing egg metadata using Setuptools ==<br />
When upstream uses setuptools to provide egg metadata it is very simple to include them in your package. Your spec file will look something like this:<br />
<br />
<pre><br />
# Must have setuptools to build the package<br />
BuildRequires: python-setuptools<br />
<br />
[...]<br />
<br />
# --root $RPM_BUILD_ROOT makes the package install with a single, expanded<br />
# directory in %{python2_sitelib} and a separate egginfo directory.<br />
%install<br />
%{__python2} setup.py install --skip-build --root $RPM_BUILD_ROOT <br />
<br />
[...]<br />
<br />
%files<br />
[...]<br />
# This captures both the module directory and the egg-info directory<br />
# Something like:<br />
# /usr/lib/python2.7/site-packages/sqlalchemy<br />
# /usr/lib/python2.7/site-packages/SQLAlchemy-0.3.10-py2.7.egg-info<br />
%{python2_sitelib}/*<br />
</pre><br />
<br />
{{admon/note||Older versions of setuptools used the --single-version-externally-managed commandline argument to create egg info and an expanded directory directly in site-packages. This is no longer necessary as --root creates things the way we want for packaging.<br />
}}<br />
<br />
{{Anchor|NonSetuptoolsegg metadata}}<br />
<br />
== Providing egg metadata for non-setuptools packages ==<br />
<br />
{{admon/note||These instructions are only for distutils in RHEL5. Fedora 9 and above will automatically generate egg-info files.}}<br />
<br />
When we need to provide egg metadata in a non-setuptools package because another package requires that functionality we can modify our spec files to generate the egg-info:<br />
<br />
<pre><br />
BuildRequires: python-setuptools<br />
<br />
[...] <br />
<br />
%build<br />
CFLAGS="$RPM_OPT_FLAGS" %{__python2} -c 'import setuptools; execfile("setup.py")' build<br />
<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
%{__python2} -c 'import setuptools; execfile("setup.py")' install --skip-build --root $RPM_BUILD_ROOT<br />
<br />
%files<br />
%{python2_sitelib}/*egg-info<br />
%{python2_sitelib}/[MODULENAME] <br />
</pre><br />
<br />
By importing setuptools before executing setup.py we override the distutils functions that process the file with their setuptools equivalents. Those functions create the egg-info files.<br />
<br />
== Multiple Versions ==<br />
<br />
Sometimes we want to keep an old version of a module around for compatibility. When upstream has renamed the module for us, this is a straightforward creation of a new module. For instance, python-psycopg and python-psycopg2.<br />
<br />
When upstream doesn't include the version in the name, we have to find another way to parallel install two versions of the package. egg metadata give us this ability. The latest version of a package must be installed as the python-MODULENAME and is built using the normal guidelines. The compatibility versions of the module should be named python-$MODULENAME$DISTINGUISHINGVER and be enabled by making these spec file changes:<br />
<br />
<pre><br />
# Require setuptools as the consumer will need pkg_resources to use this module<br />
Requires: python-setuptools<br />
<br />
%build<br />
# Build an egg file that we can then install from<br />
CFLAGS="$RPM_OPT_FLAGS" %{__python2} setup.py bdist_egg<br />
<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
# Install the egg so that only code that wants this particular version can get it.<br />
mkdir -p $RPM_BUILD_ROOT%{python2_sitelib}<br />
easy_install -m --prefix $RPM_BUILD_ROOT%{_usr} -Z dist/*.egg<br />
</pre><br />
<br />
This creates the python egg under the %{python2_sitelib}/*.egg directory. This module is not directly usable via the import statement. Instead, the consuming package must setup the PYTHONPATH to reference the compat version before it imports the module. This can be done in a variety of ways.<br />
* Manually modifying sys.path is quick if the user just wants to try out some code with the old version:<br />
<pre><br />
>>> import sys<br />
>>> sys.path.insert(0, '/usr/lib/python2.7/site-packages/CherryPy-2.2.1-py2.7.egg/')<br />
>>> import cherrypy<br />
</pre><br />
* Using setuptools and easy_install to create "script wrappers" to invoke the programs. Setuptools has you define an entrypoint in the program's module (basically, a main() function) and then writes a script to access that via an option in setup.py.<br />
<br />
It is highly recommended that any such compatibility packages install a README.fedora file explaining how to use this module. The file should contain the above examples of how to call the module from code and explain that this is a compat package and that a newer version exists.<br />
<br />
There are several other methods of invoking scripts so that they might take the right version but they suffer from various problems. They are listed here because a program you're packaging may use them and you need to know about them if they break. If you mention them in README.fedora, please also add why they are dangerous to use.<br />
<br />
* <code>pkg_resources.requires('MODULE[VERSIONINFO] ')</code>: Does not work with a default version (able to be imported via import MODULE). The setuptools author refuses to remove this limitation and refuses to document that it is a limitation. Therefore you may run across scripts that use this method and need to patch them to use one of the above, supported methods instead.<br />
* <code>__requires__='MODULE[VERSIONINFO] '</code>: This works but the setuptools author feels that it is only a workaround and will not support it. It works presently but could stop in a future version of setuptools. Some upstreams use this method and may need to be fixed if the setuptools author ever changes the interface.<br />
<br />
== Egg "Features" to avoid ==<br />
egg metadata provide some features that are to be avoided as part of the packaging process for Fedora. Some of these may provide benefit to our users but should not be used when creating system packages.<br />
<br />
* Do not let easy_install download and install packages from the net to add to the build root. This will fail on the build system as well as being bad packaging. Packages which are downloaded are probably missing from your BuildRequires.<br />
<br />
== Links ==<br />
<br />
* http://peak.telecommunity.com/DevCenter/Pythonegg metadata<br />
* http://peak.telecommunity.com/DevCenter/setuptools<br />
* http://lists.debian.org/debian-python/2007/09/msg00004.html -- Discussion of egg metadata in Debian<br />
* http://mail.python.org/pipermail/distutils-sig/2007-September/008181.html -- Discussion of these guidelines on the distutils list<br />
<br />
[[Category:Packaging guidelines]]<br />
[[Category:Python]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc/Python_Eggs&diff=399951User:Kashyapc/Python Eggs2015-01-06T20:29:21Z<p>Kashyapc: Replaced the term 'eggs' with 'egg metadata' for better clarity. (Retained the term 'Eggs' in two occurrences of a URL)</p>
<hr />
<div>= Python egg metadata =<br />
<br />
Python packages provide extra metadata about the package in the form of egg metadata. This document explains how to package egg metadata.<br />
<br />
== Why egg metadata ==<br />
egg metadata have several uses including:<br />
<ol><br />
<li>Allowing end users to install egg metadata not made from rpms or install egg metadata into their home directories. This is an important feature for people working within a shared hosting environment.<br />
<li>Giving python packages an easy way to support plugins.<br />
<li>Giving us a way to support multiple versions of a python module for compat libraries.<br />
</ol><br />
<br />
The egg metatada can be used at runtime so it cannot be replaced with the rpm database which is only useful at install time or by tools specifically for Fedora.<br />
<br />
{{Anchor|Whenegg metadata}}<br />
== When to Provide egg metadata ==<br />
Since egg metadata establish a base of functionality that upstream authors can expect, we need to be sure to include the egg files if a package builds them. Starting with Fedora 9 any package that uses setuptools or distutils will build egg-info. In Fedora 8 or less, only setuptools packages build egg-info. If you need to provide egg-info for a distutils package on Fedora 8 or less, [[#Providing_Eggs_for_non-setuptools_packages| Providing egg metadata using Setuptools]] describes a method of substituting setuptools for distutils in the build process so egg-info is created.<br />
<br />
<br />
{{admon/note|| In the past, when there was a requirement for an egg which was not provided by upstream we would patch the requiring package to not require that package. This behaviour is deprecated and as packages are updated maintainers should follow the below guidelines to install egg metadata for the required packages. Please see [[#Providing_Eggs_for_non-setuptools_packages| Creating egg metadata for Non-setuptools Packages]] <br />
}}<br />
<br />
== Upstream egg metadata ==<br />
Do not distribute egg metadata from upstream. In Fedora, all packages must be rebuilt from source. An egg package (which is different from egg ''metadata'') contains compiled bytecode and may, if it contains a C extension, contain compiled binary extensions as well. These are opaque structures with no guarantee that they were even built from the source distributed with the egg. If you must use an egg from upstream because they do not provide tarballs, you need to include it as a source in your spec, unzip it in %setup, and rebuild from the source files contained within it.<br />
<br />
== Providing egg metadata using Setuptools ==<br />
When upstream uses setuptools to provide egg metadata it is very simple to include them in your package. Your spec file will look something like this:<br />
<br />
<pre><br />
# Must have setuptools to build the package<br />
BuildRequires: python-setuptools<br />
<br />
[...]<br />
<br />
# --root $RPM_BUILD_ROOT makes the package install with a single, expanded<br />
# directory in %{python2_sitelib} and a separate egginfo directory.<br />
%install<br />
%{__python2} setup.py install --skip-build --root $RPM_BUILD_ROOT <br />
<br />
[...]<br />
<br />
%files<br />
[...]<br />
# This captures both the module directory and the egg-info directory<br />
# Something like:<br />
# /usr/lib/python2.7/site-packages/sqlalchemy<br />
# /usr/lib/python2.7/site-packages/SQLAlchemy-0.3.10-py2.7.egg-info<br />
%{python2_sitelib}/*<br />
</pre><br />
<br />
{{admon/note||Older versions of setuptools used the --single-version-externally-managed commandline argument to create egg info and an expanded directory directly in site-packages. This is no longer necessary as --root creates things the way we want for packaging.<br />
}}<br />
<br />
{{Anchor|NonSetuptoolsegg metadata}}<br />
<br />
== Providing egg metadata for non-setuptools packages ==<br />
<br />
{{admon/note||These instructions are only for distutils in RHEL5. Fedora 9 and above will automatically generate egg-info files.}}<br />
<br />
When we need to provide egg metadata in a non-setuptools package because another package requires that functionality we can modify our spec files to generate the egg-info:<br />
<br />
<pre><br />
BuildRequires: python-setuptools<br />
<br />
[...] <br />
<br />
%build<br />
CFLAGS="$RPM_OPT_FLAGS" %{__python2} -c 'import setuptools; execfile("setup.py")' build<br />
<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
%{__python2} -c 'import setuptools; execfile("setup.py")' install --skip-build --root $RPM_BUILD_ROOT<br />
<br />
%files<br />
%{python2_sitelib}/*egg-info<br />
%{python2_sitelib}/[MODULENAME] <br />
</pre><br />
<br />
By importing setuptools before executing setup.py we override the distutils functions that process the file with their setuptools equivalents. Those functions create the egg-info files.<br />
<br />
== Multiple Versions ==<br />
<br />
Sometimes we want to keep an old version of a module around for compatibility. When upstream has renamed the module for us, this is a straightforward creation of a new module. For instance, python-psycopg and python-psycopg2.<br />
<br />
When upstream doesn't include the version in the name, we have to find another way to parallel install two versions of the package. egg metadata give us this ability. The latest version of a package must be installed as the python-MODULENAME and is built using the normal guidelines. The compatibility versions of the module should be named python-$MODULENAME$DISTINGUISHINGVER and be enabled by making these spec file changes:<br />
<br />
<pre><br />
# Require setuptools as the consumer will need pkg_resources to use this module<br />
Requires: python-setuptools<br />
<br />
%build<br />
# Build an egg file that we can then install from<br />
CFLAGS="$RPM_OPT_FLAGS" %{__python2} setup.py bdist_egg<br />
<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
# Install the egg so that only code that wants this particular version can get it.<br />
mkdir -p $RPM_BUILD_ROOT%{python2_sitelib}<br />
easy_install -m --prefix $RPM_BUILD_ROOT%{_usr} -Z dist/*.egg<br />
</pre><br />
<br />
This creates the python egg under the %{python2_sitelib}/*.egg directory. This module is not directly usable via the import statement. Instead, the consuming package must setup the PYTHONPATH to reference the compat version before it imports the module. This can be done in a variety of ways.<br />
* Manually modifying sys.path is quick if the user just wants to try out some code with the old version:<br />
<pre><br />
>>> import sys<br />
>>> sys.path.insert(0, '/usr/lib/python2.7/site-packages/CherryPy-2.2.1-py2.7.egg/')<br />
>>> import cherrypy<br />
</pre><br />
* Using setuptools and easy_install to create "script wrappers" to invoke the programs. Setuptools has you define an entrypoint in the program's module (basically, a main() function) and then writes a script to access that via an option in setup.py.<br />
<br />
It is highly recommended that any such compatibility packages install a README.fedora file explaining how to use this module. The file should contain the above examples of how to call the module from code and explain that this is a compat package and that a newer version exists.<br />
<br />
There are several other methods of invoking scripts so that they might take the right version but they suffer from various problems. They are listed here because a program you're packaging may use them and you need to know about them if they break. If you mention them in README.fedora, please also add why they are dangerous to use.<br />
<br />
* <code>pkg_resources.requires('MODULE[VERSIONINFO] ')</code>: Does not work with a default version (able to be imported via import MODULE). The setuptools author refuses to remove this limitation and refuses to document that it is a limitation. Therefore you may run across scripts that use this method and need to patch them to use one of the above, supported methods instead.<br />
* <code>__requires__='MODULE[VERSIONINFO] '</code>: This works but the setuptools author feels that it is only a workaround and will not support it. It works presently but could stop in a future version of setuptools. Some upstreams use this method and may need to be fixed if the setuptools author ever changes the interface.<br />
<br />
== Egg "Features" to avoid ==<br />
egg metadata provide some features that are to be avoided as part of the packaging process for Fedora. Some of these may provide benefit to our users but should not be used when creating system packages.<br />
<br />
* Do not let easy_install download and install packages from the net to add to the build root. This will fail on the build system as well as being bad packaging. Packages which are downloaded are probably missing from your BuildRequires.<br />
<br />
== Links ==<br />
<br />
* http://peak.telecommunity.com/DevCenter/Pythonegg metadata<br />
* http://peak.telecommunity.com/DevCenter/setuptools<br />
* http://lists.debian.org/debian-python/2007/09/msg00004.html -- Discussion of egg metadata in Debian<br />
* http://mail.python.org/pipermail/distutils-sig/2007-September/008181.html -- Discussion of these guidelines on the distutils list<br />
<br />
[[Category:Packaging guidelines]]<br />
[[Category:Python]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=395914User:Kashyapc2014-11-26T12:00:52Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* I work at Red Hat on Virtualization and Cloud (OpenStack) related open source projects<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* Random notes on KVM based Virtualization<br />
** http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.fedorapeople.org/virt/openstack<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
<br />
<br />
=== Packaging ===<br />
<br />
== Reviews ==<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022950 Completed Reviews]<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ON_QA&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022952 Inprogress Reviews]<br />
<br />
<br />
<br />
== Maintenance ==<br />
* [https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc Package maintenance]<br />
<br />
<br />
{{ #fedorabadges: kashyapc }}</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=395913User:Kashyapc2014-11-26T11:59:11Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* I work at Red Hat on Virtualization and Cloud (OpenStack) related open source projects<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* Random notes on KVM based Virtualization<br />
** http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.fedorapeople.org/virt/openstack<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
<br />
<br />
=== Packaging ===<br />
<br />
== Reviews ==<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022950 Completed Reviews]<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ON_QA&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022952 Inprogress Reviews]<br />
<br />
<br />
{{ #fedorabadges: kashyapc }}<br />
<br />
<br />
== Maintenance ==<br />
* [https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc Package maintenance]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2014-09-25_Virtualization&diff=388737Test Day:2014-09-25 Virtualization2014-09-25T06:48:28Z<p>Kashyapc: /* Who's available */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_20_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = Thursday 2014-09-25<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day]<br />
([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = virt}} <!-- {{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}} -->{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule [[https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day on Fedocal]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 21. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 21.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyapc)<br />
<br />
== Known issues ==<br />
<!-- Before you begin testing, there are a few known bugs that should be taken into account: --><br />
* Fedora 21 Workstation media is not detected as Fedora 21 by boxes/virt-manager: [https://bugzilla.redhat.com/show_bug.cgi?id=1145264 bug 1145264]<br />
* SPICE auto guest resize isn't working: [https://bugzilla.redhat.com/show_bug.cgi?id=1146175 bug 1146175]<br />
* Latest virt-customize/virt-builder seem to have issues setting passwords [https://bugzilla.redhat.com/show_bug.cgi?id=1146275 bug 1146275]<br />
* virt-manager can lose track of guest state, think VM is running when it's actually stopped [https://bugzilla.redhat.com/show_bug.cgi?id=1146277 bug 1146277]<br />
* F21 workstation livecd in a VM has no network connectivity, conflicts with host 'default' network [https://bugzilla.redhat.com/show_bug.cgi?id=1146232 1146232]<br />
* spice-vdagent: drag + drop doesn't open nautilus right away: [https://bugzilla.redhat.com/show_bug.cgi?id=1146289 bug 1146289]<br />
* virt-manager: UI error when trying to hotplug USB/PCI: [https://bugzilla.redhat.com/show_bug.cgi?id=1146297 bug 1146297]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]).<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with: <code>yum groupinstall virtualization</code><br />
<br />
As for getting the latest virt packages, you have a few options:<br />
<br />
=== Fedora 21 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 21 machine. You have a few options for getting the Fedora 21 bits:<br />
<br />
==== Install with CD/DVD ====<br />
<br />
You can download the Fedora 21 Alpha in various formats [https://fedoraproject.org/get-prerelease here].<br />
<br />
==== Upgrade from Fedora 20 ====<br />
<br />
* The supported way is using 'fedup': [[FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F]] You may also find the instructions in the [[QA:Testcase_upgrade_fedup_cli_previous_desktop|fedup test case]] useful for using fedup to upgrade to a pre-release.<br />
* [[Upgrading_Fedora_using_yum|Upgrade using 'yum']]: This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 21 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 21? Nested virt might be an option! This allows you to create KVM guests ''inside'' a Fedora 21 VM.<br />
<br />
Use the [[#Fedora_21_virt_packages_on_Fedora_20|virt-preview instructions]] below, install a guest using one of the [[#VM_Install|install test cases]], and follow the [[QA:Testcase_KVM_nested_virt|nested virt test case]] to finish the setup and verify things are working correctly.<br />
<br />
=== Fedora 21 virt packages on Fedora 20 ===<br />
<br />
If you aren't ready to make the jump to Fedora 21, this is the next best thing! Run latest virt packages on Fedora 20 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''Ensure you are using the latest virt packages!''' ===<br />
<br />
Several updated packages were pushed to Fedora 21 only recently. The recommended versions are:<br />
<br />
* qemu-system-x86-2.1.1-2.fc21 (same version for all qemu* packages)<br />
* libvirt-daemon-1.2.8-6.fc21<br />
* virt-manager-common-1.1.0-3.git310f6527.fc21<br />
<br />
If a 'yum update' isn't pulling these packages in, try 'sudo yum clean all', then 'sudo yum update'.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install|Guest install via CDROM/ISO]]<br />
* [[QA:Testcase Virtualization URL Guest Install|Guest install via URL]]<br />
* [[QA:Testcase_Virtualization_Import_Guest_Install|Import existing VM image (your own disk image, or Fedora cloud image, or virt-builder image)]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase_Virt_Snapshot_UI|VM snapshot management]]<br />
* [[QA:Testcase_Virtualization_Spice_Features|Spice features: copy/paste, drag/drop, USB redirection, auto guest resize]]<br />
* [[QA:Testcase_Virt_Change_CDROM_Media|Change CDROM media for running VM]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|Host USB device hotplug]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
* [[QA:Testcase_KVM_nested_virt|Enabling nested virtualization for a VM]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virt_ARM_on_x86|Run Fedora ARM image as a VM on x86]]<br />
<br />
=== '''New features''' ===<br />
<br />
* [[QA:Testcase_Virtualization_Q35_Chipset|Q35 Chipset]]<br />
* [[QA:Testcase_Virt_AArch64_on_x86|Import AArch64 image as a VM on x86]]<br />
* [[QA:Testcase_Virtualization_UEFI|Install VM using OVMF/UEFI]]<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 21 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 20 features:<br />
* [[QA:Testcase_Virt_ACLs|Virt ACLs]]<br />
* [[QA:Testcase_Virt_CPU_Hotplug|VM CPU hotplug]]<br />
* [[QA:Testcase_Virt_Multiqueue_Net|Enable multiqueue virtio networking]]<br />
<br />
Fedora 19 features:<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device passthrough]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase_Virtualization_PXE_Guest_Install|Guest install via PXE (only if you have a pre-existing PXE setup)]]<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
* [[QA:Testcase_Virt_Serial_Console|VM serial console login]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
=== OpenVZ ===<br />
<br />
* [[QA:Testcase_vzctl_base]]<br />
* [[QA:Testcase_vzctl_network]]<br />
<br />
== Debugging ==<br />
<br />
* https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems<br />
<br />
== Test Results ==<br />
<!-- metadata: https://fedoraproject.org/wiki/User:Crobinso/Sandbox:F21VirtTestAppMetadata<br />
To update the results tool, put the metadata in the following form and submit: http://testdays.qa.fedoraproject.org/testdays/admin/update_testday --><br />
<br />
'''We are tracking test results in a web application [http://testdays.qa.fedoraproject.org/testdays/show_event?event_id=19 over here]'''<br />
<br />
Results from this web application will be automatically transferred to the Wiki a week after the test day, and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.<br />
<br />
[[Category:Test Days]] [[Category:Fedora 21 Test Days]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=FAD_Pune_Aug_2014&diff=384960FAD Pune Aug 20142014-08-23T04:29:26Z<p>Kashyapc: /* Attendees */</p>
<hr />
<div>{{header|events}}<br />
<br />
==When and Where==<br />
Aug 23, 2014, 9:00 AM at the [http://www.openstreetmap.org/#map=19/18.51695/73.92676 Red Hat Pune office].<br />
<br />
You'll need to get in touch with [[User:Siddhesh|Siddhesh]] in advance so that passes can be arranged for your entry into the office. Please note that we could accommodate maximum 25 participants for the day. These would be the first 25 registered on this page. While tea/coffee would be available at the venue, participants need to arrange for their lunch.<br />
<br />
==Attendees==<br />
* [[User:Siddhesh|Siddhesh Poyarekar]]<br />
* [[User:amsharma|Amita Sharma]]<br />
* Miraj Ranpura<br />
* [[User:Kumarpraveen|Praveen Kumar]]<br />
* [[User:Amitshah|Amit Shah]]<br />
* [[User:ciypro|Chandan Kumar]]<br />
* [[User:anishpatil|Anish]]<br />
* [[User:mrniranjan|Niranjan MR]]<br />
* [[User:Uday288|Udayendu Kar]]<br />
* [[User:sinnykumari|Sinny Kumari]]<br />
* [[User:huzaifas|Huzaifa Sidhpurwala]]<br />
* [[User:pjp|P J P]]<br />
* [[User:kaushikub|Kaushik Banerjee]]<br />
* [[User:natesh|Natesh Sharma]]<br />
* [[User:madhuri|Madhuri Gaykar]]<br />
* [[User:Anisha|Anisha Narang]]<br />
* [[User:ratul|Ratul Dutta]]<br />
* [[User:Sgaikwad|Suresh Gaikwad]]<br />
* [[User:Siddharths|Siddharth Sharma]]<br />
* [[User:Aziza|Aziza Karol]]<br />
* [[User:Samxan|Samikshan Bairagya]]<br />
* [[user:Coolsvap| Swapnil Kulkarni]]<br />
* [[user:mohitsuman| Mohit Suman]]<br />
* [[user:hmadhava| Himanshu Madhavani]]<br />
* [[user:amar2424| Amar Huchchanavar]]<br />
* [[User:kashyapc| Kashyap Chamarthy]]<br />
{{admon/note | Note | Feel free to add your name here}}<br />
<br />
==Activities==<br />
<br />
* Testing Fedora 21 (Details TBD)<br />
<br />
{|<br />
! Name !! Component(s) !! comments <br />
|-<br />
| [[User:huzaifas | Huzaifa Sidhpurwala]] || Security Regression testing || Test fedora 21 against some security flaw reproducers <br />
|-<br />
| [[User:Amitshah | Amit Shah]] || Desktop, Virt testing || Test F21 as host and guest; desktop (gnome); suspend-resume<br />
|-<br />
| [[User:kashyapc | Kashyap Chamarthy]] || Virt, OpenStack testing || Test latest Virtualization from virt-preview; snapshots, disk image management<br />
|-<br />
| [[User:Siddhesh | Siddhesh]] || glibc || Run and review glibc tests<br />
|-<br />
| [[User:amsharma | Amita Sharma]] || 389 || Test 389 installation and basic features for F21 alpha<br />
|-<br />
| [[User:kaushikub | Kaushik Banerjee]] || SSSD || Integration of Linux Desktop with Samba PDC<br />
|-<br />
| [[User:siddharths | Siddharth Sharma]] || Security / Mitigation features || Test F21 packages for security / mitigation features<br />
|-<br />
| [[User:pjp | P J P]] || [https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver Default DNSSEC resolver] || Test F21 DNSSEC feature<br />
|}<br />
<br />
==Status==<br />
<br />
==Blogs and Reports==<br />
<br />
==Photos==<br />
<br />
[[Category:Events 2014]] [[Category:FAD]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=FAD_Pune_Aug_2014&diff=384956FAD Pune Aug 20142014-08-23T03:35:29Z<p>Kashyapc: /* Activities */</p>
<hr />
<div>{{header|events}}<br />
<br />
==When and Where==<br />
Aug 23, 2014, 9:00 AM at the [http://www.openstreetmap.org/#map=19/18.51695/73.92676 Red Hat Pune office].<br />
<br />
You'll need to get in touch with [[User:Siddhesh|Siddhesh]] in advance so that passes can be arranged for your entry into the office. Please note that we could accommodate maximum 25 participants for the day. These would be the first 25 registered on this page. While tea/coffee would be available at the venue, participants need to arrange for their lunch.<br />
<br />
==Attendees==<br />
* [[User:Siddhesh|Siddhesh Poyarekar]]<br />
* [[User:amsharma|Amita Sharma]]<br />
* Miraj Ranpura<br />
* [[User:Kumarpraveen|Praveen Kumar]]<br />
* [[User:Amitshah|Amit Shah]]<br />
* [[User:ciypro|Chandan Kumar]]<br />
* [[User:anishpatil|Anish]]<br />
* [[User:mrniranjan|Niranjan MR]]<br />
* [[User:Uday288|Udayendu Kar]]<br />
* [[User:sinnykumari|Sinny Kumari]]<br />
* [[User:huzaifas|Huzaifa Sidhpurwala]]<br />
* [[User:pjp|P J P]]<br />
* [[User:kaushikub|Kaushik Banerjee]]<br />
* [[User:natesh|Natesh Sharma]]<br />
* [[User:madhuri|Madhuri Gaykar]]<br />
* [[User:Anisha|Anisha Narang]]<br />
* [[User:ratul|Ratul Dutta]]<br />
* [[User:Sgaikwad|Suresh Gaikwad]]<br />
* [[User:Siddharths|Siddharth Sharma]]<br />
* [[User:Aziza|Aziza Karol]]<br />
* [[User:Samxan|Samikshan Bairagya]]<br />
* [[user:Coolsvap| Swapnil Kulkarni]]<br />
* [[user:mohitsuman| Mohit Suman]]<br />
* [[user:hmadhava| Himanshu Madhavani]]<br />
* [[user:amar2424| Amar Huchchanavar]]<br />
{{admon/note | Note | Feel free to add your name here}}<br />
<br />
==Activities==<br />
<br />
* Testing Fedora 21 (Details TBD)<br />
<br />
{|<br />
! Name !! Component(s) !! comments <br />
|-<br />
| [[User:huzaifas | Huzaifa Sidhpurwala]] || Security Regression testing || Test fedora 21 against some security flaw reproducers <br />
|-<br />
| [[User:Amitshah | Amit Shah]] || Desktop, Virt testing || Test F21 as host and guest; desktop (gnome); suspend-resume<br />
|-<br />
| [[User:kashyapc | Kashyap Chamarthy]] || Virt, OpenStack testing || Test latest Virtualization from virt-preview; snapshots, disk image management<br />
|-<br />
| [[User:Siddhesh | Siddhesh]] || glibc || Run and review glibc tests<br />
|-<br />
| [[User:amsharma | Amita Sharma]] || 389 || Test 389 installation and basic features for F21 alpha<br />
|-<br />
| [[User:kaushikub | Kaushik Banerjee]] || SSSD || Integration of Linux Desktop with Samba PDC<br />
|-<br />
| [[User:siddharths | Siddharth Sharma]] || Security / Mitigation features || Test F21 packages for security / mitigation features<br />
|-<br />
| [[User:pjp | P J P]] || [https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver Default DNSSEC resolver] || Test F21 DNSSEC feature<br />
|}<br />
<br />
==Status==<br />
<br />
==Blogs and Reports==<br />
<br />
==Photos==<br />
<br />
[[Category:Events 2014]] [[Category:FAD]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=FAD_Pune_Aug_2014&diff=384955FAD Pune Aug 20142014-08-23T03:35:06Z<p>Kashyapc: /* Activities */</p>
<hr />
<div>{{header|events}}<br />
<br />
==When and Where==<br />
Aug 23, 2014, 9:00 AM at the [http://www.openstreetmap.org/#map=19/18.51695/73.92676 Red Hat Pune office].<br />
<br />
You'll need to get in touch with [[User:Siddhesh|Siddhesh]] in advance so that passes can be arranged for your entry into the office. Please note that we could accommodate maximum 25 participants for the day. These would be the first 25 registered on this page. While tea/coffee would be available at the venue, participants need to arrange for their lunch.<br />
<br />
==Attendees==<br />
* [[User:Siddhesh|Siddhesh Poyarekar]]<br />
* [[User:amsharma|Amita Sharma]]<br />
* Miraj Ranpura<br />
* [[User:Kumarpraveen|Praveen Kumar]]<br />
* [[User:Amitshah|Amit Shah]]<br />
* [[User:ciypro|Chandan Kumar]]<br />
* [[User:anishpatil|Anish]]<br />
* [[User:mrniranjan|Niranjan MR]]<br />
* [[User:Uday288|Udayendu Kar]]<br />
* [[User:sinnykumari|Sinny Kumari]]<br />
* [[User:huzaifas|Huzaifa Sidhpurwala]]<br />
* [[User:pjp|P J P]]<br />
* [[User:kaushikub|Kaushik Banerjee]]<br />
* [[User:natesh|Natesh Sharma]]<br />
* [[User:madhuri|Madhuri Gaykar]]<br />
* [[User:Anisha|Anisha Narang]]<br />
* [[User:ratul|Ratul Dutta]]<br />
* [[User:Sgaikwad|Suresh Gaikwad]]<br />
* [[User:Siddharths|Siddharth Sharma]]<br />
* [[User:Aziza|Aziza Karol]]<br />
* [[User:Samxan|Samikshan Bairagya]]<br />
* [[user:Coolsvap| Swapnil Kulkarni]]<br />
* [[user:mohitsuman| Mohit Suman]]<br />
* [[user:hmadhava| Himanshu Madhavani]]<br />
* [[user:amar2424| Amar Huchchanavar]]<br />
{{admon/note | Note | Feel free to add your name here}}<br />
<br />
==Activities==<br />
<br />
* Testing Fedora 21 (Details TBD)<br />
<br />
{|<br />
! Name !! Component(s) !! comments <br />
|-<br />
| [[User:huzaifas | Huzaifa Sidhpurwala]] || Security Regression testing || Test fedora 21 against some security flaw reproducers <br />
|-<br />
| [[User:Amitshah | Amit Shah]] || Desktop, Virt testing || Test F21 as host and guest; desktop (gnome); suspend-resume<br />
|-<br />
| [[User:kashyapc | Kashyap Chamarthy]] || Virt, OpenStack testing || Test latest Virtualization from virt-review; snapshots, disk image management<br />
|-<br />
| [[User:Siddhesh | Siddhesh]] || glibc || Run and review glibc tests<br />
|-<br />
| [[User:amsharma | Amita Sharma]] || 389 || Test 389 installation and basic features for F21 alpha<br />
|-<br />
| [[User:kaushikub | Kaushik Banerjee]] || SSSD || Integration of Linux Desktop with Samba PDC<br />
|-<br />
| [[User:siddharths | Siddharth Sharma]] || Security / Mitigation features || Test F21 packages for security / mitigation features<br />
|-<br />
| [[User:pjp | P J P]] || [https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver Default DNSSEC resolver] || Test F21 DNSSEC feature<br />
|}<br />
<br />
==Status==<br />
<br />
==Blogs and Reports==<br />
<br />
==Photos==<br />
<br />
[[Category:Events 2014]] [[Category:FAD]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Fedora_Release_Life_Cycle&diff=381758Fedora Release Life Cycle2014-07-09T19:48:05Z<p>Kashyapc: </p>
<hr />
<div>{{autolang|base=yes}}<br />
<br />
The Fedora Project releases a new version of Fedora approximately every 6 months and provides updated packages (maintenance) to these releases for approximately 13 months. This allows users to "skip a release" while still being able to always have a system that is still receiving updates. <br />
<br />
== Development Schedule ==<br />
<br />
We say developed and released ''approximately every 6 months'' because like many things, they don't always go exactly as planned.<br />
<br />
The schedule for the release currently under development, {{FedoraVersion|full|next}}, is on its [[Releases/{{FedoraVersion||next}}/Schedule| release schedule]] page. Alpha, Beta, and General Availability (final) releases happen at 10:00am Eastern US Time, which is either 1500UTC or 1400UTC depending on whether or not daylight savings is in effect.<br />
<br />
=== Schedule Methodology ===<br />
<br />
Fedora release schedules are proposed by the Release Engineering team and ratified by [[FESCo | Fedora Engineering Steering Committee (FESCo)]]. FESCo is responsible for overseeing the technical direction of the Fedora distribution. A core schedule is created using the key tasks listed below. Detailed team schedules are built around these dates.<br />
<br />
{|border="1" <br />
!Task/Milestone !! Start Day !! Length<br />
|-<br />
| Planning and Development || Day After GA of Previous Release || Depends on GA date and working backwards from all the tasks below<br />
|-<br />
| Feature Acceptance Deadline || Tuesday--Two weeks before Feature Freeze || n/a<br />
|-<br />
| [[ReleaseEngineering/FeatureFreezePolicy|Feature Freeze]] || Tuesday--1 week before Alpha Change Deadline || Until GA<br />
|-<br />
| Branch Freeze Event || Tuesday--One week before Alpha Change Deadline || [[Branch Freeze Policy]] in effect until GA.<br />
|-<br />
| [[Change_deadlines | Alpha Change Deadline]] || Tuesday--Two weeks before the [[Alpha Release]] || <br />
|-<br />
| String Freeze || Same time as Alpha Change Deadline || [[Software String Freeze Policy]] in effect until GA.<br />
|-<br />
| Alpha Compose || Thursday--Two days after the Alpha Change Deadline || 1 day<br />
|-<br />
| Alpha Go/No-Go Meeting || Wednesday @ 17:00 E{D,S}T--six days after Alpha Compose || n/a<br />
|-<br />
| Alpha Release || Tuesday--Two weeks after Branch Freeze and 12 days after Alpha Compose || Public testing of Alpha lasts 3 weeks<br />
|-<br />
| [[Change_deadlines | Beta Change Deadline]] || Tuesday--Two weeks before the [[Beta Release]] || <br />
|-<br />
| Feature Complete || Tuesday--Same as the Beta Change Deadeline || n/a<br />
|-<br />
| Beta Compose || Thursday--Two days after the Beta Change Deadline || 1 day<br />
|-<br />
| Beta Go/No-Go Meeting || Wednesday @ 17:00 E{D,S}T--six days after Beta Compose || n/a<br />
|-<br />
| Beta Release || Tuesday--Two weeks after the Beta Change Deadline and 12 days after Beta Compose || Public testing of Beta lasts 2 weeks + 6 days (ends on a Monday)<br />
|-<br />
| [[Change_deadlines | Final Change Deadline]] || Monday--End of Beta Release Testing || In effect until GA<br />
|-<br />
| Compose Final RC || Thursday--three days after Final Change Deadline || 1 day<br />
|-<br />
| Test Final RC || Thursday to Tuesday || 6 days<br />
|-<br />
| Final Go/No-Go Meeting || Tuesday @ 17:00 E{D,S}T after Test Final RC || n/a<br />
|-<br />
| GA Release || Tuesday--Seven days after Test Final RC ends || n/a<br />
|-<br />
| Maintenance || Tuesday--GA release day || ~13 Months<br />
|-<br />
| End of Life || One month after GA of current release + 2 releases || n/a<br />
|-<br />
|}<br />
<br />
=== Steps to Construct a New Schedule ===<br />
This is admittedly an unusual methodology, but it is fairly easy to generate using the the TaskJuggler schedules John Poelstra creates.<br />
<br />
# Pick GA date (the Tuesday before May 1st or October 31st)<br />
# Work backwards using consistent spacing for freezes, composes, and releases for Alpha, Beta, and Final, as described above<br />
# Set the feature submission and completion dates working backwards from the Branch Freeze date<br />
# The time between the feature submission deadline and the GA of the previous release is the time dedicated to ''development''<br />
#* Development time varies from from release to release based on how when the previous release finished<br />
#* The freeze and testing time (from Branch Freeze until GA) is held constant from release to release<br />
<br />
=== Development Schedule Rationale ===<br />
<br />
Fedora generally develops new releases over a six month period to provide a regular and predictable release schedule. The bi-annual targeted release dates are ''May Day'' (May 1st) and ''Halloween'' (October 31) making them easy to remember and avoiding significant holiday breaks. Changes to this standard must be approved by the community-elected [[FESCo | Fedora Engineering Steering Committee (FESCo)]].<br />
<br />
A six month release schedule also follows the precedence of Red Hat Linux (precursor to Fedora). Former Red Hat software engineer Havoc Pennington offers a historical perspective [http://article.gmane.org/gmane.linux.redhat.fedora.advisory-board/1475/ here]. GNOME started following a time based release based on the ideas and success of Red Hat Linux and other distributions following Fedora having adopted a similar release cycle. Several other major components, including the Linux kernel, Openoffice.org, Xorg, have started following a time based release schedule. While the exact release schedules vary between these components and other upstream projects, the interactions between these components and Fedora makes a six month time based release schedule a good balance.<br />
<br />
=== Schedule Contingency Planning ===<br />
<br />
If the Alpha, Beta, or Final Go/No Go meetings result in a "No Go" determination, that milestone and subsequent milestones will be pushed back by one week.<br />
<br />
One week is added to the schedule to maintain the practice of releasing on Tuesdays. Tuesdays are the designated release day because they are good days for news coverage and the established day we synchronize our content with the mirrors that carry our releases. Go/No Go meetings receive input from representatives of FESCo, Release Engineering, and Quality Assurance.<br />
<br />
== Maintenance Schedule ==<br />
We say maintained for ''approximately 13 months'' because the supported period for releases is dependent on the date the release under development goes final. As a result, ''Release X'' is supported until one month after the release of ''Release X+2''.<br />
<br />
This translates into:<br />
<br />
* {{FedoraVersion|long|previous}} will be maintained until 1 month after the release of {{FedoraVersion|long|next}}.<br />
* {{FedoraVersion|long|current}} will be maintained until 1 month after the release of {{FedoraVersion|long|next2}}.<br />
<br />
=== Maintenance Schedule Rationale ===<br />
<br />
Fedora is [[Objectives | focused]] on free and open source software [[Red Hat contributions | innovations]] and moves quickly. If you want a distribution that moves slower but has a longer lifecycle, Red Hat Enterprise Linux, which is derivative of Fedora or free rebuilds of that such as CentOS might be more suitable for you. Refer to the [[RHEL]] page for more details.<br />
<br />
Historically, the Fedora Project has found supporting two releases plus Rawhide and the pre-release Branched code to be a manageable work load.<br />
<br />
== End of Life (EOL) ==<br />
<br />
When a release reaches the point where it is no longer supported nor updates are created for it, then it is considered ''End of Life'' (EOL). Branches for new packages in the SCM are not allowed for distribution X after the Fedora X+2 release and new builds are no longer allowed.<br />
<br />
The tasks performed at EOL are documented in the [[End of life SOP]].<br />
<br />
= Additional Release Schedule Information =<br />
* Overview of [[Releases]], including currently supported releases<br />
* [[End of life | Unsupported Releases]]<br />
* [[Releases/HistoricalSchedules | Historical Release Information]]<br />
<br />
[[Category:Distribution]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=File:Kashyap-chamarthy.JPG&diff=373619File:Kashyap-chamarthy.JPG2014-03-20T10:30:57Z<p>Kashyapc: Kashyapc uploaded a new version of &quot;File:Kashyap-chamarthy.JPG&quot;</p>
<hr />
<div></div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=373612User:Kashyapc2014-03-20T10:21:32Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* I work at Red Hat on Virtualization and Cloud (OpenStack) related open source projects<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* Random notes on KVM based Virtualization<br />
** http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.fedorapeople.org/virt/openstack<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
<br />
<br />
=== Packaging ===<br />
<br />
== Reviews ==<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022950 Completed Reviews]<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ON_QA&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022952 Inprogress Reviews]<br />
<br />
<br />
== Maintenance ==<br />
* [https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc Package maintenance]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=File:Prof.jpg&diff=373611File:Prof.jpg2014-03-20T10:18:16Z<p>Kashyapc: </p>
<hr />
<div></div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=373608User:Kashyapc2014-03-20T10:14:13Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* I work at Red Hat on Virtualization and Cloud (OpenStack) related open source projects<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* Random notes on KVM based Virtualization<br />
** http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
* Presentations at conferences and simple virt related scripts <br />
** https://github.com/kashyapc<br />
<br />
=== Packaging ===<br />
<br />
== Reviews ==<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022950 Completed Reviews]<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ON_QA&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022952 Inprogress Reviews]<br />
<br />
<br />
== Maintenance ==<br />
* [https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc Package maintenance]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=364820User:Kashyapc2013-12-16T20:19:41Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* Working on Virtualization and Cloud related aspects at Red Hat<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* Random notes on KVM based Virtualization<br />
** http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
* Presentations at conferences and simple virt related scripts <br />
** https://github.com/kashyapc<br />
<br />
=== Packaging ===<br />
<br />
== Reviews ==<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022950 Completed Reviews]<br />
<br />
[https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=MODIFIED&bug_status=ON_QA&component=Package%20Review&email1=kchamart%40redhat.com&emailassigned_to1=1&emailtype1=exact&list_id=2022952 Inprogress Reviews]<br />
<br />
<br />
== Maintenance ==<br />
* [https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc Package maintenance]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-10-08_Virtualization&diff=355610Test Day:2013-10-08 Virtualization2013-10-05T08:54:35Z<p>Kashyapc: /* Who's available */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_20_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-10-08<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day]<br />
<!-- ([http://webchat.freenode.net/?channels=fedora-test-day webirc] [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/fedora-test-day.2013-05-28-11.10.log.txt IRC logs]) --><br />
| fedora_mailing_list = virt}} <!-- {{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}} --> {{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 20. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 20.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:ericb|Eric Blake]] (eblake on IRC)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap on IRC)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* libvirt managed save occasionally fails with 'unexpected migration status in setup': https://bugzilla.redhat.com/show_bug.cgi?id=1015636<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]).<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with: <code>yum groupinstall virtualization</code><br />
<br />
As for getting the latest virt packages, you have a few options:<br />
<!--<br />
=== Virt Test Day Live CD ===<br />
<br />
There's a Fedora 20 live CD image that already has all the required virtualization packages installed (though you should still <code>yum update</code> after booting). You will probably want a good amount of RAM if using this option (greater than 4G) since you'll be using RAM for both a VM and running the live OS.<br />
<br />
* Get the image: <code>wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso</code><br />
* For Live CD or USB setup instructions, see: [[FedoraLiveCD#Download_and_Create_Live_image_or_Live_USB]]<br />
* If you have a really beefy machine, you can probably run the Live CD in a VM using nested virtualization! (see instructions below)<br />
--><br />
=== Fedora 20 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 20 machine. You have a few options for getting the Fedora 20 bits:<br />
<br />
==== Install with CD/DVD ====<br />
<br />
You can download the Fedora 20 Alpha in various formats [https://fedoraproject.org/get-prerelease here].<br />
<br />
==== Upgrade from Fedora 19 ====<br />
<br />
* The supported way is using 'fedup': [[FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F]] You may also find the instructions in the [[QA:Testcase_upgrade_fedup_cli_previous_desktop|fedup test case]] useful for using fedup to upgrade to a pre-release.<br />
* [[Upgrading_Fedora_using_yum|Upgrade using 'yum']]: This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 20 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 19? Nested virt might be an option! This allows you to create KVM guests ''inside'' a Fedora 20 VM.<br />
<br />
Use the [[#Fedora_20_virt_packages_on_Fedora_19|virt-preview instructions]] below, install a guest using one of the [[#VM_Install|install test cases]], and follow the [[QA:Testcase_KVM_nested_virt|nested virt test case]] to finish the setup and verify things are working correctly.<br />
<br />
=== Fedora 20 virt packages on Fedora 19 ===<br />
<br />
If you aren't ready to make the jump to Fedora 20, this is the next best thing! Run latest virt packages on Fedora 19 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase_Virt_Serial_Console|VM serial console login]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|Host USB device hotplug]]<br />
* [[QA:Testcase_KVM_nested_virt|Enabling nested virtualization for a VM]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
* [[QA:Testcase_Virt_Change_CDROM_Media|Change CDROM media for running VM]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 20:<br />
<br />
* [[QA:Testcase_Virt_ACLs|Virt ACLs]]<br />
* [[QA:Testcase_Virt_x86_on_ARM|Import ARM guest on your x86 machine and manage with virt-manager/libvirt]]<br />
* [[QA:Testcase_Virt_Snapshot_UI|Snapshot UI in virt-manager]]<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 20 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 19 features:<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Debugging ==<br />
<br />
* https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems<br />
<br />
== Test Results ==<br />
<br />
<!-- metadata: https://fedoraproject.org/wiki/User:Jskladan/Sandbox:F20VirtualizationTestDay<br />
To update the results tool, put the metadata in the following form and submit: http://testdays.qa.fedoraproject.org/testdays/admin/update_testday --><br />
<br />
'''We are tracking test results in a web application [http://autoqa-stg.fedoraproject.org/testdays/show_event?event_id=7 over here]'''<br />
<br />
Results from this web application will be automatically transferred to the Wiki a week after the test day, and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.<br />
<br />
Should you encounter any problem while using the web application, please contact jskladan on #fedora-qa channel at freenode, or send an email to jskladan@fedoraproject.org<br />
<br />
[[Category:Test Days]] [[Category:Fedora 20 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=QA/Meetings/20130812&diff=349533QA/Meetings/201308122013-08-16T02:45:21Z<p>Kashyapc: </p>
<hr />
<div>= Attendees =<br />
adamw (live)<br />
tflink (live)<br />
viking-ice (live)<br />
jskladan (live)<br />
handsome_pirate (live)<br />
pbrobinson (live)<br />
kashyapc (live)<br />
mattdm (live)<br />
<br />
= Agenda =<br />
* ARM release criteria / test matrix adjustments<br />
* Visible Cloud release criteria / test matrix adjustments<br />
* Open floor<br />
<br />
== ARM release criteria / test matrix adjustments ==<br />
* https://fedorahosted.org/fedora-qa/ticket/393<br />
* https://fedorahosted.org/fedora-qa/ticket/394<br />
* Which images will we build for which milestones?<br />
* Which of the images will be release-blocking?<br />
* What requirements do we want to apply to them?<br />
* Do we need to add or revise any test cases to cover this?<br />
* How should we express the requirements in the criteria and validation test pages?<br />
<br />
== Visible Cloud release criteria / test matrix adjustments ==<br />
* https://fedoraproject.org/wiki/Changes/VisibleCloud<br />
* Change requests 'first class' (which pretty much implies 'release blocking') status for 'the cloud image' on EC2 and OpenStack for F20<br />
* What precisely are the configurations we are requested to test?<br />
* Do we have the necessary accounts, systems, knowledge to do this testing?<br />
* What precise functionality do we require from the tested configurations?<br />
* What changes are needed to the release criteria and test matrices to reflect this?<br />
<br />
== Open floor ==<br />
<br />
== Action items ==<br />
<br />
== IRC Log ==</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_Volunteers&diff=348873Flock Volunteers2013-08-11T18:18:52Z<p>Kashyapc: /* Sunday August 11 */</p>
<hr />
<div>{{admon/note | Room information | "Auditorium" is the 4th floor ballroom of the Stern Center}}<br />
<br />
= Volunteers =<br />
Each 45 minute session needs to have a volunteer running the camera, watching a timer, and monitoring IRC for Q&A (if it happens).<br />
<br />
There are 10 tracks. The workshop/hackfest sessions will not need volunteers, as most of them will not be practical to record or stream.<br />
<br />
By signing up for a session, you're committing to:<br />
* Attending that session<br />
* Getting there a few minutes early to start the video stream<br />
* Watching a timer and signalling the speaker (with signs) when he/she has 10, 5, and 0 minutes remaining.<br />
<br />
If possible you should also try to: <br />
* Make sure someone starts meeting recording in the irc channel for your room (#fedora-flock-ectrNNN) using https://fedoraproject.org/wiki/Zodbot#Meeting_Functions (ie, #startmeeting sessionname)<br />
* Ask them to also gateway questions and comments from IRC to the room/speaker as needed. <br />
* Make sure they also #endmeeting when the session is complete. <br />
NOTE: this person doesn't need to be you, just try and make sure there is someone. <br />
<br />
You should not volunteer for a session where you are the speaker, or where you are giving a talk at the same time, or where you want to be in a separate session.<br />
<br />
Just put your name beside the sessions that you want to volunteer for. Take as many as you want, but please, only one volunteer per session. <br />
<br />
Remember, by doing this, you make it possible for the rest of the Fedora community to participate (and view for years to come). Thanks!<br />
<br />
Transcription means typing the speaker's words and the questions and answers to the designated IRC room LIVE. If nobody volunteered for the transcription, just ask if anybody in the room would do it or do it yourself.<br />
<br />
= Volunteer Slots =<br />
<br />
== Friday August 9 ==<br />
<br />
{|class="wikitable sortable"<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
! Transcriber<br />
|-<br />
|Auditorium || Friday || 9 AM || [[Flock/Volunteers/FPL Keynote | FPL Keynote]] || Tom Callaway || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|Auditorium || Friday || 10 AM || [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-09/fedora-flock-auditorium.2013-08-09-13.34.log.html Fedmsg] || [[User:Hguemar|Haikel Guemar]] ||<br />
|-<br />
|Auditorium || Friday || 11 AM || [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-09/fedora-flock-auditorium.2013-08-09-14.35.log.html Why Fedora Sucks!] || [[User:Qubodup|Iwan Gabovitch]] || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Friday || 12 PM || [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-09/fedora-flock-auditorium.2013-08-09-15.33.log.html ARM Architecture 101] || [[User:jsmith|Jared Smith]] || [[User:jsmith|Jared Smith]]<br />
|-<br />
|ECTR 101 || Friday || 10 AM || [[Flock/Volunteers/Creating an RPM from scratch | Creating an RPM from scratch]] || [[User:Jzb|Joe Brockmeier]] || Someone did! Who were you :)<br />
|-<br />
|ECTR 101 || Friday || 11 AM || Darkserver: Current and Future Roadmap [http://www.youtube.com/watch?v=R3oYVmQIi7Q YouTube Video Recording] || <del>[[User:Jreznik|Jaroslav Reznik]]</del> (flight cancelled) ||<br />
|-<br />
|ECTR 101 || Friday || 12 PM || Agility and FOSS [https://www.youtube.com/watch?v=vv_Fy8oFJv8 YouTube Video Recording] || [[User:pingou|Pierre-Yves Chibon]] ||<br />
|-<br />
|ECTR 101 || Friday || 4 PM || Document Your Code [[Flock/Volunteers/DocumentYourCode | Notes]] || ||<br />
|-<br />
|ECTR 103 || Friday || 10 AM || Ask Fedora Update [https://www.youtube.com/watch?v=Cl8RDGfifY8 YouTube Video Recording] || [[User:ib54003|Benedikt Schäfer]] ||<br />
|- <br />
|ECTR 103 || Friday || 11 AM || Hyperkitty: The new mailing list UI [http://meetbot.fedoraproject.org/fedora-flock-ectr103/2013-08-09/fedora-flock-ectr103.2013-08-09-14.30.log.html Transcript] [https://www.youtube.com/watch?v=Ut_m5W0Of8M YouTube Video Recording] || [[User:Ianweller|Ian Weller]] || also Ian<br />
|-<br />
|ECTR 103 || Friday || 12 PM || Bugzilla [https://www.youtube.com/watch?v=sgU4mnjkwDM YouTube Recording] || [[User:ib54003|Benedikt Schäfer]] ||<br />
|-<br />
|ECTR 107 || Friday || 10 AM || Evolution of a Linux Distribution and its Ecosystem [[Flock/Volunteers/Evolution of a Linux Distribution and its Ecosystem | Transcript]] [https://www.youtube.com/watch?v=HRp9czS-eAo YouTube Video Recording] ||[[User:Qubodup|Iwan Gabovitch]] || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|ECTR 107 || Friday || 11 AM || Installer Redesign and Rewrite Retrospective || [[User:Jzb|Joe Brockmeier]] ||<br />
|-<br />
|ECTR 107 || Friday || 12 PM || Fedora Ambassadors - State of the Union [https://www.youtube.com/watch?v=r6ecwkMmvA8 YouTube Video Recording] ||<del>[[User:Johannbg|Jóhann B. Guðmundsson]]</del> (flight cancelled) ||<br />
|- <br />
|ECTR 109 || Friday || 10 AM || Fedora ARM - State of the Union [[Flock/Volunteers/FedoraArmStateOfUnion | Transcript]] [https://www.youtube.com/watch?v=Gvio-5W0eFs YouTube Video Recording] || <del>[[User:Jreznik|Jaroslav Reznik]]</del> (flight cancelled) ||<br />
|- ]] ||<br />
|-<br />
|ECTR 109 || Friday || 11 AM || Porting Fedora to 64-bit ARM [http://meetbot.fedoraproject.org/fedora-flock-ectr109/2013-08-09/fedora-flock-ectr109.2013-08-09-14.42.log.txt Transcript] [https://www.youtube.com/watch?v=4ZM2CNUJexU YouTube Video Recording]|| John Dulaney || Jared Smith<br />
|-<br />
|ECTR 109 || Friday || 12 PM || Future of the Data Center [https://www.youtube.com/watch?v=9wMzWUTHYo0 YouTube Video Recording] || ||<br />
|-<br />
|ECTR 112 || Friday || 10 AM || State of Security in Fedora [https://www.youtube.com/watch?v=Xvcz7z1UH8w YouTube Video Recording] || || <br />
|-<br />
|ECTR 112 || Friday || 11 AM || FreeIPA Two Factor Authentication [https://www.youtube.com/watch?v=njf6kgi96z0 YouTube Video Recording]|| || <br />
|-<br />
|ECTR 112 || Friday || 12 PM || P***** - Product Naming in Global Communities [[http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-09/fedora-flock-ectr112.2013-08-09-15.32.log.txt Transcript]] [https://www.youtube.com/watch?v=AYoLc01RRFk YouTube Video Recording] || [[User:Qubodup|Iwan Gabovitch]] || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|ECTR 114 || Friday || 2 PM || Building Desktop Apps with NodeWebKit [[Flock/Volunteers/NodeWebKit | Notes]] || ||<br />
|-<br />
|ECTR 115 || Friday || 10 AM || A Tour of Linux portability [[https://www.youtube.com/watch?v=BW9XldiGpb8 YouTube Video Recording]] || ||<br />
|-<br />
|ECTR 115 || Friday || 11 AM || State of the Fedora Kernel [https://www.youtube.com/watch?v=fMh2nxTSbzY YouTube Video Recording] || [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|- <br />
|ECTR 115 || Friday || 12 PM || KERNEL BUG TRIAGE LIVE! [https://www.youtube.com/watch?v=E4l32TgB_Cg YouTube Video Recording] || [[User:Ianweller|Ian Weller]] || also Ian<br />
|- <br />
|ECTR 115 || Friday || 4 PM || Get Go-ing! [http://www.youtube.com/watch?v=iXMQTJFaCmw YouTube Video Recording] || || <br />
|-<br />
|ECTR 120 || Friday || 10 AM || Is "cloud" something beyond a buzzword and should Fedora care? [http://www.youtube.com/watch?v=ZWgzA1pRyxc YouTube Vide Link] || [[User:Pfrields|Paul Frields]] ||<br />
|-<br />
|ECTR 120 || Friday || 11 AM || Putting the PaaS in Fedora [http://www.youtube.com/watch?v=6ZJ6COXbdMY YouTube Video Recording] || [[User:Tuanta|Truong Anh Tuan]] ||<br />
|-<br />
|ECTR 120 || Friday || 12 PM || Bringing Hadoop to Fedora || [[User:Kpeeples|Kenneth Peeples]] ||<br />
|-<br />
|ECTR 212 || Friday || 10 AM || Education with Fedora || [[User:tatica|tatica leandro]] ||<br />
|-<br />
|ECTR 212 || Friday || 11 AM || Fedora College || [[User:tatica|tatica leandro]] ||<br />
|-<br />
|ECTR 212 || Friday || 12 PM || Fedora Software Center || [[User:Sgallagh|Stephen Gallagher]] ||<br />
|-<br />
|Auditorium || Friday || 2 PM || [[Flock/Volunteers/Fedora Crystal Ball | Fedora Crystal Ball]] || ||<br />
|-<br />
|ECTR 101 || Friday || 2 PM || [[Flock/Volunteers/Making Fedora Python3 Ready | Making Fedora Python3 Ready]] || ||<br />
|}<br />
<br />
== Saturday August 10 ==<br />
<br />
{|class="wikitable sortable"<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
! Transcriber<br />
|-<br />
|Auditorium || Saturday || 9 AM || Lulzbot Keynote [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-10/fedora-flock-auditorium.2013-08-10-12.38.log.html Transcript] || Tom Callaway || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Saturday || 10 AM || Pidora 18 (Raspberry Pi Fedora Remix) || Steve Castelli ||<br />
|-<br />
|Auditorium || Saturday || 11 AM || Fedora Badges [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-10/fedora-flock-auditorium.2013-08-10-14.58.log.html Transcript] || [[User:tatica|Tatica Leandro]] || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Saturday || 12 PM || OpenShift, Fedora, and the future of packaged web apps || [[User:Tuanta|Truong Anh Tuan]] ||<br />
|-<br />
|ECTR 101 || Saturday || 10 AM || Using Fedora for developing things other than Fedora || [[User:Chrisroberts|Chris Roberts]] ||<br />
|-<br />
|ECTR 101 || Saturday || 11 AM || Make Games Using Free as in Freedom Art and Audio [http://meetbot.fedoraproject.org/fedora-flock-ectr101/2013-08-10/fedora-flock-ectr101.2013-08-10-14.43.log.html Transcript] [http://www.youtube.com/watch?v=B7j1GFGffls YouTube Video Recording] || || [http://www.gurdonark.com/ Gurdonark]<br />
|-<br />
|ECTR 101 || Saturday || 12 PM || KVM and Virtio Introduction [http://meetbot.fedoraproject.org/fedora-flock-ectr101/2013-08-10/fedora-flock-ectr101.2013-08-10-15.44.log.html Notes] [http://www.youtube.com/watch?v=yTZ1P30SUn0 YouTube Video Recording] || [[User:Jreznik|Jaroslav Reznik]] ||<br />
|-<br />
|ECTR 103 || Saturday || 10 AM || Fedora At Yahoo! [http://meetbot.fedoraproject.org/fedora-flock-ectr103/2013-08-10/fedora-flock-ectr103.2013-08-10-14.04.log.html Transcript] [http://www.youtube.com/watch?v=GQzm1qoc2XA YouTube Video Recording] || [[User:Eseyman|Emmanuel Seyman]] ||<br />
|-<br />
|ECTR 103 || Saturday || 11 AM || Fedora Passwords (then and now) || [[User:Ianweller|Ian Weller]] ||<br />
|-<br />
|ECTR 103 || Saturday || 12 PM || Submitting Updates via Bodhi [http://www.youtube.com/watch?v=itMS3Edq-KE YouTube Video Recording] || [[User:Churchyard|Miro Hrončok]] ||<br />
|-<br />
|ECTR 103 || Saturday || 2 PM || OAuth Hackfest [[Flock/Volunteers/OAuthHackfest | Gobby Notes]] || ||<br />
|-<br />
|ECTR 107 || Saturday || 10 AM || Web Security Standards || ||<br />
|-<br />
|ECTR 107 || Saturday || 11 AM || An Architecture for a More Agile Fedora [http://meetbot.fedoraproject.org/fedora-flock-ectr107/2013-08-10/fedora-flock-ectr107.2013-08-10-14.44.log.html Transcript] [http://www.youtube.com/watch?v=K4dNP9DiaXc YouTube Recording] || [[User:Bochecha|Mathieu Bridon]] ||<br />
|-<br />
|ECTR 107 || Saturday || 12 AM || Task Automation in Fedora QA [http://meetbot.fedoraproject.org/fedora-flock-ectr107/2013-08-10/fedora-flock-ectr107.2013-08-10-15.42.log.html Notes] [http://www.youtube.com/watch?v=78nJ6UTjevQ YouTube Video Recording] || [[User:Bochecha|Mathieu Bridon]] ||<br />
|-<br />
|ECTR 109 || Saturday || 10 AM || Virtualization on ARM [http://www.youtube.com/watch?v=Bvlvv57ipBw YouTube Video Recording] || [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|-<br />
|ECTR 109 || Saturday || 11 AM || The Hotrodder's Guide to Maximum Performance LAMP [http://www.youtube.com/watch?v=Krt9jjhZkCc YouTube Video Recording] || ||<br />
|-<br />
|ECTR 109 || Saturday || 12 PM || Mozilla Open Badges in Sugar on OLPC || [[User:Calweb|Calvin Webster]] ||<br />
|-<br />
|ECTR 112 || Saturday || 10 AM || SELinux for Mere Mortals [http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-10/fedora-flock-ectr112.2013-08-10-13.58.log.html Transcript] [http://www.youtube.com/watch?v=-koXLPBi-4k YouTube Video Recording] || [[User:Imabug|Eugene Mah]] || [[User:Mavjs | Maverick]]<br />
|-<br />
|ECTR 112 || Saturday || 11 AM || What's New With SELinux? [http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-10/fedora-flock-ectr112.2013-08-10-14.50.log.html Transcript] [http://www.youtube.com/watch?v=e9e3AxwfH4Y YouTube Video Recording] || [[User:Imabug|Eugene Mah]] || <br />
|-<br />
|ECTR 112 || Saturday || 12 PM || Hardening Apache || [[User:Chrisroberts|Chris Roberts]] ||<br />
|-<br />
|ECTR 112 || Saturday || 4 PM || Creating 3D Racing Game Maps with GIMP and Inkscape [http://www.youtube.com/watch?v=fJaJm_8U1U0 YouTube Video Recording] || ] ||<br />
|-<br />
|ECTR 114 || Saturday || 10 AM || Gource: Telling Stories via Source Code [http://meetbot.fedoraproject.org/fedora-flock-ectr114/2013-08-10/gource.2013-08-10-13.48.log.html Transcript] [http://www.youtube.com/watch?v=dHdzTA_EIiA YouTube Video Recording] || || Stephen Gallagher<br />
|-<br />
|ECTR 114 || Saturday || 11 AM || What's New In Software Management [http://www.youtube.com/watch?v=X0FNNHNSjQw YouTube Video Recording] || ||<br />
|-<br />
|ECTR 114 || Saturday || 12 PM || AWS, Private Cloud, and Open Source || [[User:Hguemar|Haikel Guemar]] ||<br />
|-<br />
|ECTR 114 || Saturday || 4 PM || Sugar and OLPC Birds of a Feather [http://www.youtube.com/watch?v=tHnOUqQqW4s YouTube Video Recording] || ||<br />
|-<br />
|ECTR 115 || Saturday || 10 AM || Kernel Regression Testing for Fun and Profit [http://www.youtube.com/watch?v=oDGkXZYwMSY YouTube Video Recording] || ||<br />
|-<br />
|ECTR 115 || Saturday || 11 AM || Btrfs - Cool Butter [http://www.youtube.com/watch?edit=vd&v=XmOPP0niJjY YouTube Video Recording] || [[User:ib54003|Benedikt Schäfer]] ||<br />
|- <br />
|ECTR 115 || Saturday || 12 AM || Kernel Fuzz Testing [http://www.youtube.com/watch?v=yEUF1jL_oiE YouTube Video Recording] || [[User:Johannbg|Jóhann B. Guðmundsson]] || [[User:Mavjs | Maverick]]<br />
|-<br />
|ECTR 120 || Saturday || 10 AM || Federated and Free - Distributed and Decentralized Apps on OpenShift [http://www.youtube.com/watch?v=lWFiTTdHJPw YouTube Video Recording] || [[User:Emichan|Emily Dirsh]] ||<br />
|-<br />
|ECTR 120 || Saturday || 11 AM || Scale or Fail - Give your app the Speed it Needs in the Cloud [http://www.youtube.com/watch?v=DarkoGbVX7s YouTube Video Recording] || [[User:mitchenerg|Garrett Mitchener]] ||<br />
|-<br />
|ECTR 120 || Saturday || 12 PM || pcp+systemtap: Performance Monitoring for Workstations and Networks [http://www.youtube.com/watch?v=EzhfGEevBN4 YouTube Video Recording] || ||<br />
|-<br />
|}<br />
<br />
== Sunday August 11 ==<br />
<br />
{|class="wikitable sortable"<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
! Transcriber<br />
|-<br />
|Auditorium || Sunday || 9 AM || Dave Crossland Keynote || Tom Callaway || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Sunday || 10 AM || Changing the Default Updates Model || [[User:Abompard|Aurélien Bompard]] || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Sunday || 11 AM || Gaming on Fedora || [[User:Qubodup|Iwan Gabovitch]] || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Sunday || 12 PM || Ansible || [[User:Abompard|Aurélien Bompard]] ||<br />
|-<br />
|ECTR 101 || Sunday || 10 AM || User Build Tools || [[User:Ianweller|Ian Weller]] ||<br />
|-<br />
|ECTR 101 || Sunday || 11 AM || About MATE Desktop || [[User:Jreznik|Jaroslav Reznik]] ||<br />
|-<br />
|ECTR 101 || Sunday || 12 PM || Scaling Integration Testing with Beaker || [[User:Jreznik|Jaroslav Reznik]] ||<br />
|-<br />
|ECTR 103 || Sunday || 10 AM || Code Review for Fedora Apps || [[User:Ralph|Ralph Bean]] ||<br />
|-<br />
|ECTR 103 || Sunday || 11 AM || OpenID in the Fedora Services || [[User:Ianweller|Ian Weller]] ||<br />
|-<br />
|ECTR 103 || Sunday || 12 PM || The Life of a Package || Mahrud Sayrafi ||<br />
|-<br />
|ECTR 107 || Sunday || 10 AM || User Testing for the Rest of Us || Liam Bulkley ||<br />
|-<br />
|ECTR 107 || Sunday || 11 AM || Making Distributed VoIP Work (and Work Well) || Steve Castelli ||<br />
|-<br />
|ECTR 107 || Sunday || 12 AM || State of OrangeFS || [[User:mitchenerg|Garrett Mitchener]] ||<br />
|-<br />
|ECTR 109 || Sunday || 10 AM || Fedora Project Ambassadors - Collaborate, Design, Engage || [[User:Tuanta|Truong Anh Tuan]] ||<br />
|-<br />
|ECTR 109 || Sunday || 11 AM || Ambassadors Work in a Region - Annual Planning || [[User:ib54003|Benedikt Schäfer]] ||<br />
|-<br />
|ECTR 109 || Sunday || 12 PM || The Fedora Ambassadors Census ||[[User:Johannbg|Jóhann B. Guðmundsson]] ||<br />
|-<br />
|ECTR 112 || Sunday || 10 AM || Secure Linux Containers || Mahrud Sayrafi ||<br />
|-<br />
|ECTR 112 || Sunday || 11 AM || PKI Made Easy: Managing Certificates With Dogtag [http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-11/fedora-flock-ectr112.2013-08-11-14.31.log.html Transcript]|| [[User:Kashyapc|Kashyap Chamarthy]] || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|-<br />
|ECTR 112 || Sunday || 12 PM || Measuring the Fedora Community with Census || [[User:pingou|Pierre-Yves Chibon]] ||<br />
|-<br />
|ECTR 114 || Sunday || 10 AM || Fedora vs the Semantic Web || ||<br />
|-<br />
|ECTR 114 || Sunday || 11 AM || Fedora Videos || [[User:Ralph|Ralph Bean]] ||<br />
|-<br />
|ECTR 114 || Sunday || 12 PM || Unifying Administration with OpenLMI || [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|-<br />
|ECTR 120 || Sunday || 10 AM || Hyperscale Cloud Management with OpenStack || ||<br />
|-<br />
|ECTR 120 || Sunday || 11 AM || Polyglot Spatial with FOSS in the Cloud || ||<br />
|-<br />
|ECTR 120 || Sunday || 12 PM || See the light: SDN, OpenDaylight, Open vSwitch and Fedora || ||<br />
|-<br />
|}<br />
<br />
<br />
[[Category:Flock]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_Volunteers&diff=348872Flock Volunteers2013-08-11T18:18:00Z<p>Kashyapc: /* Sunday August 11 */</p>
<hr />
<div>{{admon/note | Room information | "Auditorium" is the 4th floor ballroom of the Stern Center}}<br />
<br />
= Volunteers =<br />
Each 45 minute session needs to have a volunteer running the camera, watching a timer, and monitoring IRC for Q&A (if it happens).<br />
<br />
There are 10 tracks. The workshop/hackfest sessions will not need volunteers, as most of them will not be practical to record or stream.<br />
<br />
By signing up for a session, you're committing to:<br />
* Attending that session<br />
* Getting there a few minutes early to start the video stream<br />
* Watching a timer and signalling the speaker (with signs) when he/she has 10, 5, and 0 minutes remaining.<br />
<br />
If possible you should also try to: <br />
* Make sure someone starts meeting recording in the irc channel for your room (#fedora-flock-ectrNNN) using https://fedoraproject.org/wiki/Zodbot#Meeting_Functions (ie, #startmeeting sessionname)<br />
* Ask them to also gateway questions and comments from IRC to the room/speaker as needed. <br />
* Make sure they also #endmeeting when the session is complete. <br />
NOTE: this person doesn't need to be you, just try and make sure there is someone. <br />
<br />
You should not volunteer for a session where you are the speaker, or where you are giving a talk at the same time, or where you want to be in a separate session.<br />
<br />
Just put your name beside the sessions that you want to volunteer for. Take as many as you want, but please, only one volunteer per session. <br />
<br />
Remember, by doing this, you make it possible for the rest of the Fedora community to participate (and view for years to come). Thanks!<br />
<br />
Transcription means typing the speaker's words and the questions and answers to the designated IRC room LIVE. If nobody volunteered for the transcription, just ask if anybody in the room would do it or do it yourself.<br />
<br />
= Volunteer Slots =<br />
<br />
== Friday August 9 ==<br />
<br />
{|class="wikitable sortable"<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
! Transcriber<br />
|-<br />
|Auditorium || Friday || 9 AM || [[Flock/Volunteers/FPL Keynote | FPL Keynote]] || Tom Callaway || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|Auditorium || Friday || 10 AM || [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-09/fedora-flock-auditorium.2013-08-09-13.34.log.html Fedmsg] || [[User:Hguemar|Haikel Guemar]] ||<br />
|-<br />
|Auditorium || Friday || 11 AM || [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-09/fedora-flock-auditorium.2013-08-09-14.35.log.html Why Fedora Sucks!] || [[User:Qubodup|Iwan Gabovitch]] || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Friday || 12 PM || [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-09/fedora-flock-auditorium.2013-08-09-15.33.log.html ARM Architecture 101] || [[User:jsmith|Jared Smith]] || [[User:jsmith|Jared Smith]]<br />
|-<br />
|ECTR 101 || Friday || 10 AM || [[Flock/Volunteers/Creating an RPM from scratch | Creating an RPM from scratch]] || [[User:Jzb|Joe Brockmeier]] || Someone did! Who were you :)<br />
|-<br />
|ECTR 101 || Friday || 11 AM || Darkserver: Current and Future Roadmap [http://www.youtube.com/watch?v=R3oYVmQIi7Q YouTube Video Recording] || <del>[[User:Jreznik|Jaroslav Reznik]]</del> (flight cancelled) ||<br />
|-<br />
|ECTR 101 || Friday || 12 PM || Agility and FOSS [https://www.youtube.com/watch?v=vv_Fy8oFJv8 YouTube Video Recording] || [[User:pingou|Pierre-Yves Chibon]] ||<br />
|-<br />
|ECTR 101 || Friday || 4 PM || Document Your Code [[Flock/Volunteers/DocumentYourCode | Notes]] || ||<br />
|-<br />
|ECTR 103 || Friday || 10 AM || Ask Fedora Update [https://www.youtube.com/watch?v=Cl8RDGfifY8 YouTube Video Recording] || [[User:ib54003|Benedikt Schäfer]] ||<br />
|- <br />
|ECTR 103 || Friday || 11 AM || Hyperkitty: The new mailing list UI [http://meetbot.fedoraproject.org/fedora-flock-ectr103/2013-08-09/fedora-flock-ectr103.2013-08-09-14.30.log.html Transcript] [https://www.youtube.com/watch?v=Ut_m5W0Of8M YouTube Video Recording] || [[User:Ianweller|Ian Weller]] || also Ian<br />
|-<br />
|ECTR 103 || Friday || 12 PM || Bugzilla [https://www.youtube.com/watch?v=sgU4mnjkwDM YouTube Recording] || [[User:ib54003|Benedikt Schäfer]] ||<br />
|-<br />
|ECTR 107 || Friday || 10 AM || Evolution of a Linux Distribution and its Ecosystem [[Flock/Volunteers/Evolution of a Linux Distribution and its Ecosystem | Transcript]] [https://www.youtube.com/watch?v=HRp9czS-eAo YouTube Video Recording] ||[[User:Qubodup|Iwan Gabovitch]] || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|ECTR 107 || Friday || 11 AM || Installer Redesign and Rewrite Retrospective || [[User:Jzb|Joe Brockmeier]] ||<br />
|-<br />
|ECTR 107 || Friday || 12 PM || Fedora Ambassadors - State of the Union [https://www.youtube.com/watch?v=r6ecwkMmvA8 YouTube Video Recording] ||<del>[[User:Johannbg|Jóhann B. Guðmundsson]]</del> (flight cancelled) ||<br />
|- <br />
|ECTR 109 || Friday || 10 AM || Fedora ARM - State of the Union [[Flock/Volunteers/FedoraArmStateOfUnion | Transcript]] [https://www.youtube.com/watch?v=Gvio-5W0eFs YouTube Video Recording] || <del>[[User:Jreznik|Jaroslav Reznik]]</del> (flight cancelled) ||<br />
|- ]] ||<br />
|-<br />
|ECTR 109 || Friday || 11 AM || Porting Fedora to 64-bit ARM [http://meetbot.fedoraproject.org/fedora-flock-ectr109/2013-08-09/fedora-flock-ectr109.2013-08-09-14.42.log.txt Transcript] [https://www.youtube.com/watch?v=4ZM2CNUJexU YouTube Video Recording]|| John Dulaney || Jared Smith<br />
|-<br />
|ECTR 109 || Friday || 12 PM || Future of the Data Center [https://www.youtube.com/watch?v=9wMzWUTHYo0 YouTube Video Recording] || ||<br />
|-<br />
|ECTR 112 || Friday || 10 AM || State of Security in Fedora [https://www.youtube.com/watch?v=Xvcz7z1UH8w YouTube Video Recording] || || <br />
|-<br />
|ECTR 112 || Friday || 11 AM || FreeIPA Two Factor Authentication [https://www.youtube.com/watch?v=njf6kgi96z0 YouTube Video Recording]|| || <br />
|-<br />
|ECTR 112 || Friday || 12 PM || P***** - Product Naming in Global Communities [[http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-09/fedora-flock-ectr112.2013-08-09-15.32.log.txt Transcript]] [https://www.youtube.com/watch?v=AYoLc01RRFk YouTube Video Recording] || [[User:Qubodup|Iwan Gabovitch]] || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|ECTR 114 || Friday || 2 PM || Building Desktop Apps with NodeWebKit [[Flock/Volunteers/NodeWebKit | Notes]] || ||<br />
|-<br />
|ECTR 115 || Friday || 10 AM || A Tour of Linux portability [[https://www.youtube.com/watch?v=BW9XldiGpb8 YouTube Video Recording]] || ||<br />
|-<br />
|ECTR 115 || Friday || 11 AM || State of the Fedora Kernel [https://www.youtube.com/watch?v=fMh2nxTSbzY YouTube Video Recording] || [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|- <br />
|ECTR 115 || Friday || 12 PM || KERNEL BUG TRIAGE LIVE! [https://www.youtube.com/watch?v=E4l32TgB_Cg YouTube Video Recording] || [[User:Ianweller|Ian Weller]] || also Ian<br />
|- <br />
|ECTR 115 || Friday || 4 PM || Get Go-ing! [http://www.youtube.com/watch?v=iXMQTJFaCmw YouTube Video Recording] || || <br />
|-<br />
|ECTR 120 || Friday || 10 AM || Is "cloud" something beyond a buzzword and should Fedora care? [http://www.youtube.com/watch?v=ZWgzA1pRyxc YouTube Vide Link] || [[User:Pfrields|Paul Frields]] ||<br />
|-<br />
|ECTR 120 || Friday || 11 AM || Putting the PaaS in Fedora [http://www.youtube.com/watch?v=6ZJ6COXbdMY YouTube Video Recording] || [[User:Tuanta|Truong Anh Tuan]] ||<br />
|-<br />
|ECTR 120 || Friday || 12 PM || Bringing Hadoop to Fedora || [[User:Kpeeples|Kenneth Peeples]] ||<br />
|-<br />
|ECTR 212 || Friday || 10 AM || Education with Fedora || [[User:tatica|tatica leandro]] ||<br />
|-<br />
|ECTR 212 || Friday || 11 AM || Fedora College || [[User:tatica|tatica leandro]] ||<br />
|-<br />
|ECTR 212 || Friday || 12 PM || Fedora Software Center || [[User:Sgallagh|Stephen Gallagher]] ||<br />
|-<br />
|Auditorium || Friday || 2 PM || [[Flock/Volunteers/Fedora Crystal Ball | Fedora Crystal Ball]] || ||<br />
|-<br />
|ECTR 101 || Friday || 2 PM || [[Flock/Volunteers/Making Fedora Python3 Ready | Making Fedora Python3 Ready]] || ||<br />
|}<br />
<br />
== Saturday August 10 ==<br />
<br />
{|class="wikitable sortable"<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
! Transcriber<br />
|-<br />
|Auditorium || Saturday || 9 AM || Lulzbot Keynote [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-10/fedora-flock-auditorium.2013-08-10-12.38.log.html Transcript] || Tom Callaway || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Saturday || 10 AM || Pidora 18 (Raspberry Pi Fedora Remix) || Steve Castelli ||<br />
|-<br />
|Auditorium || Saturday || 11 AM || Fedora Badges [http://meetbot.fedoraproject.org/fedora-flock-auditorium/2013-08-10/fedora-flock-auditorium.2013-08-10-14.58.log.html Transcript] || [[User:tatica|Tatica Leandro]] || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Saturday || 12 PM || OpenShift, Fedora, and the future of packaged web apps || [[User:Tuanta|Truong Anh Tuan]] ||<br />
|-<br />
|ECTR 101 || Saturday || 10 AM || Using Fedora for developing things other than Fedora || [[User:Chrisroberts|Chris Roberts]] ||<br />
|-<br />
|ECTR 101 || Saturday || 11 AM || Make Games Using Free as in Freedom Art and Audio [http://meetbot.fedoraproject.org/fedora-flock-ectr101/2013-08-10/fedora-flock-ectr101.2013-08-10-14.43.log.html Transcript] [http://www.youtube.com/watch?v=B7j1GFGffls YouTube Video Recording] || || [http://www.gurdonark.com/ Gurdonark]<br />
|-<br />
|ECTR 101 || Saturday || 12 PM || KVM and Virtio Introduction [http://meetbot.fedoraproject.org/fedora-flock-ectr101/2013-08-10/fedora-flock-ectr101.2013-08-10-15.44.log.html Notes] [http://www.youtube.com/watch?v=yTZ1P30SUn0 YouTube Video Recording] || [[User:Jreznik|Jaroslav Reznik]] ||<br />
|-<br />
|ECTR 103 || Saturday || 10 AM || Fedora At Yahoo! [http://meetbot.fedoraproject.org/fedora-flock-ectr103/2013-08-10/fedora-flock-ectr103.2013-08-10-14.04.log.html Transcript] [http://www.youtube.com/watch?v=GQzm1qoc2XA YouTube Video Recording] || [[User:Eseyman|Emmanuel Seyman]] ||<br />
|-<br />
|ECTR 103 || Saturday || 11 AM || Fedora Passwords (then and now) || [[User:Ianweller|Ian Weller]] ||<br />
|-<br />
|ECTR 103 || Saturday || 12 PM || Submitting Updates via Bodhi [http://www.youtube.com/watch?v=itMS3Edq-KE YouTube Video Recording] || [[User:Churchyard|Miro Hrončok]] ||<br />
|-<br />
|ECTR 103 || Saturday || 2 PM || OAuth Hackfest [[Flock/Volunteers/OAuthHackfest | Gobby Notes]] || ||<br />
|-<br />
|ECTR 107 || Saturday || 10 AM || Web Security Standards || ||<br />
|-<br />
|ECTR 107 || Saturday || 11 AM || An Architecture for a More Agile Fedora [http://meetbot.fedoraproject.org/fedora-flock-ectr107/2013-08-10/fedora-flock-ectr107.2013-08-10-14.44.log.html Transcript] [http://www.youtube.com/watch?v=K4dNP9DiaXc YouTube Recording] || [[User:Bochecha|Mathieu Bridon]] ||<br />
|-<br />
|ECTR 107 || Saturday || 12 AM || Task Automation in Fedora QA [http://meetbot.fedoraproject.org/fedora-flock-ectr107/2013-08-10/fedora-flock-ectr107.2013-08-10-15.42.log.html Notes] [http://www.youtube.com/watch?v=78nJ6UTjevQ YouTube Video Recording] || [[User:Bochecha|Mathieu Bridon]] ||<br />
|-<br />
|ECTR 109 || Saturday || 10 AM || Virtualization on ARM [http://www.youtube.com/watch?v=Bvlvv57ipBw YouTube Video Recording] || [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|-<br />
|ECTR 109 || Saturday || 11 AM || The Hotrodder's Guide to Maximum Performance LAMP [http://www.youtube.com/watch?v=Krt9jjhZkCc YouTube Video Recording] || ||<br />
|-<br />
|ECTR 109 || Saturday || 12 PM || Mozilla Open Badges in Sugar on OLPC || [[User:Calweb|Calvin Webster]] ||<br />
|-<br />
|ECTR 112 || Saturday || 10 AM || SELinux for Mere Mortals [http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-10/fedora-flock-ectr112.2013-08-10-13.58.log.html Transcript] [http://www.youtube.com/watch?v=-koXLPBi-4k YouTube Video Recording] || [[User:Imabug|Eugene Mah]] || [[User:Mavjs | Maverick]]<br />
|-<br />
|ECTR 112 || Saturday || 11 AM || What's New With SELinux? [http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-10/fedora-flock-ectr112.2013-08-10-14.50.log.html Transcript] [http://www.youtube.com/watch?v=e9e3AxwfH4Y YouTube Video Recording] || [[User:Imabug|Eugene Mah]] || <br />
|-<br />
|ECTR 112 || Saturday || 12 PM || Hardening Apache || [[User:Chrisroberts|Chris Roberts]] ||<br />
|-<br />
|ECTR 112 || Saturday || 4 PM || Creating 3D Racing Game Maps with GIMP and Inkscape [http://www.youtube.com/watch?v=fJaJm_8U1U0 YouTube Video Recording] || ] ||<br />
|-<br />
|ECTR 114 || Saturday || 10 AM || Gource: Telling Stories via Source Code [http://meetbot.fedoraproject.org/fedora-flock-ectr114/2013-08-10/gource.2013-08-10-13.48.log.html Transcript] [http://www.youtube.com/watch?v=dHdzTA_EIiA YouTube Video Recording] || || Stephen Gallagher<br />
|-<br />
|ECTR 114 || Saturday || 11 AM || What's New In Software Management [http://www.youtube.com/watch?v=X0FNNHNSjQw YouTube Video Recording] || ||<br />
|-<br />
|ECTR 114 || Saturday || 12 PM || AWS, Private Cloud, and Open Source || [[User:Hguemar|Haikel Guemar]] ||<br />
|-<br />
|ECTR 114 || Saturday || 4 PM || Sugar and OLPC Birds of a Feather [http://www.youtube.com/watch?v=tHnOUqQqW4s YouTube Video Recording] || ||<br />
|-<br />
|ECTR 115 || Saturday || 10 AM || Kernel Regression Testing for Fun and Profit [http://www.youtube.com/watch?v=oDGkXZYwMSY YouTube Video Recording] || ||<br />
|-<br />
|ECTR 115 || Saturday || 11 AM || Btrfs - Cool Butter [http://www.youtube.com/watch?edit=vd&v=XmOPP0niJjY YouTube Video Recording] || [[User:ib54003|Benedikt Schäfer]] ||<br />
|- <br />
|ECTR 115 || Saturday || 12 AM || Kernel Fuzz Testing [http://www.youtube.com/watch?v=yEUF1jL_oiE YouTube Video Recording] || [[User:Johannbg|Jóhann B. Guðmundsson]] || [[User:Mavjs | Maverick]]<br />
|-<br />
|ECTR 120 || Saturday || 10 AM || Federated and Free - Distributed and Decentralized Apps on OpenShift [http://www.youtube.com/watch?v=lWFiTTdHJPw YouTube Video Recording] || [[User:Emichan|Emily Dirsh]] ||<br />
|-<br />
|ECTR 120 || Saturday || 11 AM || Scale or Fail - Give your app the Speed it Needs in the Cloud [http://www.youtube.com/watch?v=DarkoGbVX7s YouTube Video Recording] || [[User:mitchenerg|Garrett Mitchener]] ||<br />
|-<br />
|ECTR 120 || Saturday || 12 PM || pcp+systemtap: Performance Monitoring for Workstations and Networks [http://www.youtube.com/watch?v=EzhfGEevBN4 YouTube Video Recording] || ||<br />
|-<br />
|}<br />
<br />
== Sunday August 11 ==<br />
<br />
{|class="wikitable sortable"<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
! Transcriber<br />
|-<br />
|Auditorium || Sunday || 9 AM || Dave Crossland Keynote || Tom Callaway || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Sunday || 10 AM || Changing the Default Updates Model || [[User:Abompard|Aurélien Bompard]] || [[User:duffy| Máirín Duffy]]<br />
|-<br />
|-<br />
|Auditorium || Sunday || 11 AM || Gaming on Fedora || [[User:Qubodup|Iwan Gabovitch]] || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Sunday || 12 PM || Ansible || [[User:Abompard|Aurélien Bompard]] ||<br />
|-<br />
|ECTR 101 || Sunday || 10 AM || User Build Tools || [[User:Ianweller|Ian Weller]] ||<br />
|-<br />
|ECTR 101 || Sunday || 11 AM || About MATE Desktop || [[User:Jreznik|Jaroslav Reznik]] ||<br />
|-<br />
|ECTR 101 || Sunday || 12 PM || Scaling Integration Testing with Beaker || [[User:Jreznik|Jaroslav Reznik]] ||<br />
|-<br />
|ECTR 103 || Sunday || 10 AM || Code Review for Fedora Apps || [[User:Ralph|Ralph Bean]] ||<br />
|-<br />
|ECTR 103 || Sunday || 11 AM || OpenID in the Fedora Services || [[User:Ianweller|Ian Weller]] ||<br />
|-<br />
|ECTR 103 || Sunday || 12 PM || The Life of a Package || Mahrud Sayrafi ||<br />
|-<br />
|ECTR 107 || Sunday || 10 AM || User Testing for the Rest of Us || Liam Bulkley ||<br />
|-<br />
|ECTR 107 || Sunday || 11 AM || Making Distributed VoIP Work (and Work Well) || Steve Castelli ||<br />
|-<br />
|ECTR 107 || Sunday || 12 AM || State of OrangeFS || [[User:mitchenerg|Garrett Mitchener]] ||<br />
|-<br />
|ECTR 109 || Sunday || 10 AM || Fedora Project Ambassadors - Collaborate, Design, Engage || [[User:Tuanta|Truong Anh Tuan]] ||<br />
|-<br />
|ECTR 109 || Sunday || 11 AM || Ambassadors Work in a Region - Annual Planning || [[User:ib54003|Benedikt Schäfer]] ||<br />
|-<br />
|ECTR 109 || Sunday || 12 PM || The Fedora Ambassadors Census ||[[User:Johannbg|Jóhann B. Guðmundsson]] ||<br />
|-<br />
|ECTR 112 || Sunday || 10 AM || Secure Linux Containers || Mahrud Sayrafi ||<br />
|-<br />
|ECTR 112 || Sunday || 11 AM || PKI Made Easy: Managing Certificates With Dogtag [http://meetbot.fedoraproject.org/fedora-flock-ectr112/2013-08-11/fedora-flock-ectr112.2013-08-11-14.31.log.html Transcript]|| [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|-<br />
|ECTR 112 || Sunday || 12 PM || Measuring the Fedora Community with Census || [[User:pingou|Pierre-Yves Chibon]] ||<br />
|-<br />
|ECTR 114 || Sunday || 10 AM || Fedora vs the Semantic Web || ||<br />
|-<br />
|ECTR 114 || Sunday || 11 AM || Fedora Videos || [[User:Ralph|Ralph Bean]] ||<br />
|-<br />
|ECTR 114 || Sunday || 12 PM || Unifying Administration with OpenLMI || [[User:Kashyapc|Kashyap Chamarthy]] ||<br />
|-<br />
|ECTR 120 || Sunday || 10 AM || Hyperscale Cloud Management with OpenStack || ||<br />
|-<br />
|ECTR 120 || Sunday || 11 AM || Polyglot Spatial with FOSS in the Cloud || ||<br />
|-<br />
|ECTR 120 || Sunday || 12 PM || See the light: SDN, OpenDaylight, Open vSwitch and Fedora || ||<br />
|-<br />
|}<br />
<br />
<br />
[[Category:Flock]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_Volunteers&diff=347817Flock Volunteers2013-08-03T07:20:46Z<p>Kashyapc: /* Saturday August 10 */</p>
<hr />
<div>= Volunteers =<br />
Each 45 minute session needs to have a volunteer running the camera, watching a timer, and monitoring IRC for Q&A (if it happens).<br />
<br />
There are 10 tracks. The workshop/hackfest sessions will not need volunteers, as most of them will not be practical to record or stream.<br />
<br />
By signing up for a session, you're committing to:<br />
* Attending that session<br />
* Getting there a few minutes early to start the video stream<br />
* Watching a timer and signalling the speaker (with signs) when he/she has 10, 5, and 0 minutes remaining.<br />
<br />
You should not volunteer for a session where you are the speaker, or where you are giving a talk at the same time, or where you want to be in a separate session.<br />
<br />
Just put your name beside the sessions that you want to volunteer for. Take as many as you want, but please, only one volunteer per session. <br />
<br />
Remember, by doing this, you make it possible for the rest of the Fedora community to participate (and view for years to come). Thanks!<br />
<br />
= Volunteer Slots =<br />
<br />
== Friday August 9 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Friday || 9 AM || FPL Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Friday || 10 AM || Fedmsg || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|-<br />
|Auditorium || Friday || 11 AM || Why Fedora Sucks! || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Friday || 12 PM || ARM Architecture 101 ||<br />
|-<br />
|ECTR 101 || Friday || 10 AM || Creating an RPM from scratch || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 101 || Friday || 11 AM || Darkserver: Current and Future Roadmap ||<br />
|-<br />
|ECTR 101 || Friday || 12 PM || Agility and FOSS || <br />
|-<br />
|ECTR 103 || Friday || 10 AM || Ask Fedora Update ||<br />
|-<br />
|ECTR 103 || Friday || 11 AM || HyperKitty: The new mailing list UI ||<br />
|-<br />
|ECTR 103 || Friday || 12 PM || Bugzilla ||<br />
|-<br />
|ECTR 107 || Friday || 10 AM || Evolution of a Linux Distribution and its Ecosystem ||<br />
|-<br />
|ECTR 107 || Friday || 11 AM || Installer Redesign and Rewrite Retrospective ||<br />
|-<br />
|ECTR 107 || Friday || 12 PM || Fedora Ambassadors - State of the Union ||<br />
|- <br />
|ECTR 109 || Friday || 10 AM || Fedora ARM - State of the Union ||<br />
|-<br />
|ECTR 109 || Friday || 11 AM || Porting Fedora to 64-bit ARM || John Dulaney<br />
|-<br />
|ECTR 109 || Friday || 12 PM || Future of the Data Center ||<br />
|-<br />
|ECTR 112 || Friday || 10 AM || State of Security in Fedora ||<br />
|-<br />
|ECTR 112 || Friday || 11 AM || FreeIPA Two Factor Authentication ||<br />
|-<br />
|ECTR 112 || Friday || 12 PM || P***** - Product Naming in Global Communities ||<br />
|-<br />
|ECTR 115 || Friday || 10 AM || A Tour of Linux portability ||<br />
|-<br />
|ECTR 115 || Friday || 11 AM || State of the Fedora Kernel || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|- <br />
|ECTR 115 || Friday || 12 AM || KERNEL BUG TRIAGE LIVE! ||<br />
|-<br />
|ECTR 120 || Friday || 10 AM || Is "cloud" something beyond a buzzword and should Fedora care? ||<br />
|-<br />
|ECTR 120 || Friday || 11 AM || Putting the PaaS in Fedora ||<br />
|-<br />
|ECTR 120 || Friday || 12 PM || Bringing Hadoop to Fedora || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 212 || Friday || 10 AM || Education with Fedora ||<br />
|-<br />
|ECTR 212 || Friday || 11 AM || Fedora College ||<br />
|-<br />
|ECTR 212 || Friday || 12 PM || Fedora Software Center ||<br />
|-<br />
|}<br />
<br />
== Saturday August 10 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Saturday || 9 AM || Lulzbot Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Saturday || 10 AM || Pidora 18 (Raspberry Pi Fedora Remix) ||<br />
|-<br />
|Auditorium || Saturday || 11 AM || Fedora Badges ||<br />
|-<br />
|Auditorium || Saturday || 12 PM || OpenShift, Fedora, and the future of packaged web apps ||<br />
|-<br />
|ECTR 101 || Saturday || 10 AM || Using Fedora for developing things other than Fedora || [[User:Chrisroberts|Chris Roberts]]<br />
|-<br />
|ECTR 101 || Saturday || 11 AM || Make Games Using Free as in Freedom Art and Audio ||<br />
|-<br />
|ECTR 101 || Saturday || 12 PM || KVM and Virtio Introduction || <br />
|-<br />
|ECTR 103 || Saturday || 10 AM || Fedora At Yahoo! ||<br />
|-<br />
|ECTR 103 || Saturday || 11 AM || Fedora Passwords (then and now) ||<br />
|-<br />
|ECTR 103 || Saturday || 12 PM || Submitting Updates via Bodhi ||<br />
|-<br />
|ECTR 107 || Saturday || 11 AM || An Architecture for a More Agile Fedora || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 107 || Saturday || 12 AM || Task Automation in Fedora QA || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 109 || Saturday || 10 AM || Virtualization on ARM || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|-<br />
|ECTR 109 || Saturday || 11 AM || The Hotrodder's Guide to Maximum Performance LAMP ||<br />
|-<br />
|ECTR 109 || Saturday || 12 PM || Mozilla Open Badges in Sugar on OLPC ||<br />
|-<br />
|ECTR 112 || Saturday || 10 AM || SELinux for Mere Mortals ||<br />
|-<br />
|ECTR 112 || Saturday || 11 AM || What's New With SELinux? ||<br />
|-<br />
|ECTR 112 || Saturday || 12 PM || Hardening Apache ||<br />
|-<br />
|ECTR 114 || Saturday || 10 AM || Gource: Telling Stories via Source Code ||<br />
|-<br />
|ECTR 114 || Saturday || 11 AM || What's New In Software Management ||<br />
|-<br />
|ECTR 114 || Saturday || 12 PM || AWS, Private Cloud, and Open Source || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|ECTR 115 || Saturday || 10 AM || Kernel Regression Testing for Fun and Profit ||<br />
|-<br />
|ECTR 115 || Saturday || 11 AM || Btrfs - Cool Butter ||<br />
|- <br />
|ECTR 115 || Saturday || 12 AM || Kernel Fuzz Testing ||<br />
|-<br />
|ECTR 120 || Saturday || 10 AM || Federated and Free - Distributed and Decentralized Apps on OpenShift || [[User:Emichan|Emily Dirsh]]<br />
|-<br />
|ECTR 120 || Saturday || 11 AM || Scale or Fail - Give your app the Speed it Needs in the Cloud ||<br />
|-<br />
|ECTR 120 || Saturday || 12 PM || pcp+systemtap: Performance Monitoring for Workstations and Networks ||<br />
|-<br />
|}<br />
<br />
== Sunday August 11 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Sunday || 9 AM || Dave Crossland Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Sunday || 10 AM || Changing the Default Updates Model ||<br />
|-<br />
|Auditorium || Sunday || 11 AM || Gaming on Fedora || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Sunday || 12 PM || Ansible ||<br />
|-<br />
|ECTR 101 || Sunday || 10 AM || User Build Tools ||<br />
|-<br />
|ECTR 101 || Sunday || 11 AM || About MATE Desktop ||<br />
|-<br />
|ECTR 101 || Sunday || 12 PM || Scaling Integration Testing with Beaker || <br />
|-<br />
|ECTR 103 || Sunday || 10 AM || Code Review for Fedora Apps ||<br />
|-<br />
|ECTR 103 || Sunday || 11 AM || OpenID in the Fedora Services ||<br />
|-<br />
|ECTR 103 || Sunday || 12 PM || The Life of a Package || Mahrud Sayrafi<br />
|-<br />
|ECTR 107 || Sunday || 10 AM || User Testing for the Rest of Us ||<br />
|-<br />
|ECTR 107 || Sunday || 11 AM || Making Distributed VoIP Work (and Work Well) ||<br />
|-<br />
|ECTR 107 || Sunday || 12 AM || State of OrangeFS ||<br />
|-<br />
|ECTR 109 || Sunday || 10 AM || Fedora Project Ambassadors - Collaborate, Design, Engage ||<br />
|-<br />
|ECTR 109 || Sunday || 11 AM || Ambassadors Work in a Region - Annual Planning ||<br />
|-<br />
|ECTR 109 || Sunday || 12 PM || The Fedora Ambassadors Census ||<br />
|-<br />
|ECTR 112 || Sunday || 10 AM || Secure Linux Containers || Mahrud Sayrafi<br />
|-<br />
|ECTR 112 || Sunday || 11 AM || PKI Made Easy: Managing Certificates With Dogtag ||<br />
|-<br />
|ECTR 112 || Sunday || 12 PM || Measuring the Fedora Community with Census ||<br />
|-<br />
|ECTR 114 || Sunday || 10 AM || Fedora vs the Semantic Web ||<br />
|-<br />
|ECTR 114 || Sunday || 11 AM || Fedora Videos ||<br />
|-<br />
|ECTR 114 || Sunday || 12 PM || Unifying Administration with OpenLMI || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|-<br />
|ECTR 120 || Sunday || 10 AM || Hyperscale Cloud Management with OpenStack ||<br />
|-<br />
|ECTR 120 || Sunday || 11 AM || Polyglot Spatial with FOSS in the Cloud ||<br />
|-<br />
|ECTR 120 || Sunday || 12 PM || See the light: SDN, OpenDaylight, Open vSwitch and Fedora ||<br />
|-<br />
|}</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_Volunteers&diff=347816Flock Volunteers2013-08-03T07:19:56Z<p>Kashyapc: /* Saturday August 10 */</p>
<hr />
<div>= Volunteers =<br />
Each 45 minute session needs to have a volunteer running the camera, watching a timer, and monitoring IRC for Q&A (if it happens).<br />
<br />
There are 10 tracks. The workshop/hackfest sessions will not need volunteers, as most of them will not be practical to record or stream.<br />
<br />
By signing up for a session, you're committing to:<br />
* Attending that session<br />
* Getting there a few minutes early to start the video stream<br />
* Watching a timer and signalling the speaker (with signs) when he/she has 10, 5, and 0 minutes remaining.<br />
<br />
You should not volunteer for a session where you are the speaker, or where you are giving a talk at the same time, or where you want to be in a separate session.<br />
<br />
Just put your name beside the sessions that you want to volunteer for. Take as many as you want, but please, only one volunteer per session. <br />
<br />
Remember, by doing this, you make it possible for the rest of the Fedora community to participate (and view for years to come). Thanks!<br />
<br />
= Volunteer Slots =<br />
<br />
== Friday August 9 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Friday || 9 AM || FPL Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Friday || 10 AM || Fedmsg || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|-<br />
|Auditorium || Friday || 11 AM || Why Fedora Sucks! || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Friday || 12 PM || ARM Architecture 101 ||<br />
|-<br />
|ECTR 101 || Friday || 10 AM || Creating an RPM from scratch || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 101 || Friday || 11 AM || Darkserver: Current and Future Roadmap ||<br />
|-<br />
|ECTR 101 || Friday || 12 PM || Agility and FOSS || <br />
|-<br />
|ECTR 103 || Friday || 10 AM || Ask Fedora Update ||<br />
|-<br />
|ECTR 103 || Friday || 11 AM || HyperKitty: The new mailing list UI ||<br />
|-<br />
|ECTR 103 || Friday || 12 PM || Bugzilla ||<br />
|-<br />
|ECTR 107 || Friday || 10 AM || Evolution of a Linux Distribution and its Ecosystem ||<br />
|-<br />
|ECTR 107 || Friday || 11 AM || Installer Redesign and Rewrite Retrospective ||<br />
|-<br />
|ECTR 107 || Friday || 12 PM || Fedora Ambassadors - State of the Union ||<br />
|- <br />
|ECTR 109 || Friday || 10 AM || Fedora ARM - State of the Union ||<br />
|-<br />
|ECTR 109 || Friday || 11 AM || Porting Fedora to 64-bit ARM || John Dulaney<br />
|-<br />
|ECTR 109 || Friday || 12 PM || Future of the Data Center ||<br />
|-<br />
|ECTR 112 || Friday || 10 AM || State of Security in Fedora ||<br />
|-<br />
|ECTR 112 || Friday || 11 AM || FreeIPA Two Factor Authentication ||<br />
|-<br />
|ECTR 112 || Friday || 12 PM || P***** - Product Naming in Global Communities ||<br />
|-<br />
|ECTR 115 || Friday || 10 AM || A Tour of Linux portability ||<br />
|-<br />
|ECTR 115 || Friday || 11 AM || State of the Fedora Kernel || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|- <br />
|ECTR 115 || Friday || 12 AM || KERNEL BUG TRIAGE LIVE! ||<br />
|-<br />
|ECTR 120 || Friday || 10 AM || Is "cloud" something beyond a buzzword and should Fedora care? ||<br />
|-<br />
|ECTR 120 || Friday || 11 AM || Putting the PaaS in Fedora ||<br />
|-<br />
|ECTR 120 || Friday || 12 PM || Bringing Hadoop to Fedora || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 212 || Friday || 10 AM || Education with Fedora ||<br />
|-<br />
|ECTR 212 || Friday || 11 AM || Fedora College ||<br />
|-<br />
|ECTR 212 || Friday || 12 PM || Fedora Software Center ||<br />
|-<br />
|}<br />
<br />
== Saturday August 10 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Saturday || 9 AM || Lulzbot Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Saturday || 10 AM || Pidora 18 (Raspberry Pi Fedora Remix) ||<br />
|-<br />
|Auditorium || Saturday || 11 AM || Fedora Badges ||<br />
|-<br />
|Auditorium || Saturday || 12 PM || OpenShift, Fedora, and the future of packaged web apps ||<br />
|-<br />
|ECTR 101 || Saturday || 10 AM || Using Fedora for developing things other than Fedora || [[User:Chrisroberts|Chris Roberts]]<br />
|-<br />
|ECTR 101 || Saturday || 11 AM || Make Games Using Free as in Freedom Art and Audio ||<br />
|-<br />
|ECTR 101 || Saturday || 12 PM || KVM and Virtio Introduction || <br />
|-<br />
|ECTR 103 || Saturday || 10 AM || Fedora At Yahoo! ||<br />
|-<br />
|ECTR 103 || Saturday || 11 AM || Fedora Passwords (then and now) ||<br />
|-<br />
|ECTR 103 || Saturday || 12 PM || Submitting Updates via Bodhi ||<br />
|-<br />
|ECTR 107 || Saturday || 11 AM || An Architecture for a More Agile Fedora || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 107 || Saturday || 12 AM || Task Automation in Fedora QA || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 109 || Saturday || 10 AM || Virtualization on ARM || [[User:Kashyapc||Kashyap Chamarthy]]<br />
|-<br />
|ECTR 109 || Saturday || 11 AM || The Hotrodder's Guide to Maximum Performance LAMP ||<br />
|-<br />
|ECTR 109 || Saturday || 12 PM || Mozilla Open Badges in Sugar on OLPC ||<br />
|-<br />
|ECTR 112 || Saturday || 10 AM || SELinux for Mere Mortals ||<br />
|-<br />
|ECTR 112 || Saturday || 11 AM || What's New With SELinux? ||<br />
|-<br />
|ECTR 112 || Saturday || 12 PM || Hardening Apache ||<br />
|-<br />
|ECTR 114 || Saturday || 10 AM || Gource: Telling Stories via Source Code ||<br />
|-<br />
|ECTR 114 || Saturday || 11 AM || What's New In Software Management ||<br />
|-<br />
|ECTR 114 || Saturday || 12 PM || AWS, Private Cloud, and Open Source || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|ECTR 115 || Saturday || 10 AM || Kernel Regression Testing for Fun and Profit ||<br />
|-<br />
|ECTR 115 || Saturday || 11 AM || Btrfs - Cool Butter ||<br />
|- <br />
|ECTR 115 || Saturday || 12 AM || Kernel Fuzz Testing ||<br />
|-<br />
|ECTR 120 || Saturday || 10 AM || Federated and Free - Distributed and Decentralized Apps on OpenShift || [[User:Emichan|Emily Dirsh]]<br />
|-<br />
|ECTR 120 || Saturday || 11 AM || Scale or Fail - Give your app the Speed it Needs in the Cloud ||<br />
|-<br />
|ECTR 120 || Saturday || 12 PM || pcp+systemtap: Performance Monitoring for Workstations and Networks ||<br />
|-<br />
|}<br />
<br />
== Sunday August 11 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Sunday || 9 AM || Dave Crossland Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Sunday || 10 AM || Changing the Default Updates Model ||<br />
|-<br />
|Auditorium || Sunday || 11 AM || Gaming on Fedora || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Sunday || 12 PM || Ansible ||<br />
|-<br />
|ECTR 101 || Sunday || 10 AM || User Build Tools ||<br />
|-<br />
|ECTR 101 || Sunday || 11 AM || About MATE Desktop ||<br />
|-<br />
|ECTR 101 || Sunday || 12 PM || Scaling Integration Testing with Beaker || <br />
|-<br />
|ECTR 103 || Sunday || 10 AM || Code Review for Fedora Apps ||<br />
|-<br />
|ECTR 103 || Sunday || 11 AM || OpenID in the Fedora Services ||<br />
|-<br />
|ECTR 103 || Sunday || 12 PM || The Life of a Package || Mahrud Sayrafi<br />
|-<br />
|ECTR 107 || Sunday || 10 AM || User Testing for the Rest of Us ||<br />
|-<br />
|ECTR 107 || Sunday || 11 AM || Making Distributed VoIP Work (and Work Well) ||<br />
|-<br />
|ECTR 107 || Sunday || 12 AM || State of OrangeFS ||<br />
|-<br />
|ECTR 109 || Sunday || 10 AM || Fedora Project Ambassadors - Collaborate, Design, Engage ||<br />
|-<br />
|ECTR 109 || Sunday || 11 AM || Ambassadors Work in a Region - Annual Planning ||<br />
|-<br />
|ECTR 109 || Sunday || 12 PM || The Fedora Ambassadors Census ||<br />
|-<br />
|ECTR 112 || Sunday || 10 AM || Secure Linux Containers || Mahrud Sayrafi<br />
|-<br />
|ECTR 112 || Sunday || 11 AM || PKI Made Easy: Managing Certificates With Dogtag ||<br />
|-<br />
|ECTR 112 || Sunday || 12 PM || Measuring the Fedora Community with Census ||<br />
|-<br />
|ECTR 114 || Sunday || 10 AM || Fedora vs the Semantic Web ||<br />
|-<br />
|ECTR 114 || Sunday || 11 AM || Fedora Videos ||<br />
|-<br />
|ECTR 114 || Sunday || 12 PM || Unifying Administration with OpenLMI || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|-<br />
|ECTR 120 || Sunday || 10 AM || Hyperscale Cloud Management with OpenStack ||<br />
|-<br />
|ECTR 120 || Sunday || 11 AM || Polyglot Spatial with FOSS in the Cloud ||<br />
|-<br />
|ECTR 120 || Sunday || 12 PM || See the light: SDN, OpenDaylight, Open vSwitch and Fedora ||<br />
|-<br />
|}</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_Volunteers&diff=347815Flock Volunteers2013-08-03T07:13:35Z<p>Kashyapc: /* Sunday August 11 */</p>
<hr />
<div>= Volunteers =<br />
Each 45 minute session needs to have a volunteer running the camera, watching a timer, and monitoring IRC for Q&A (if it happens).<br />
<br />
There are 10 tracks. The workshop/hackfest sessions will not need volunteers, as most of them will not be practical to record or stream.<br />
<br />
By signing up for a session, you're committing to:<br />
* Attending that session<br />
* Getting there a few minutes early to start the video stream<br />
* Watching a timer and signalling the speaker (with signs) when he/she has 10, 5, and 0 minutes remaining.<br />
<br />
You should not volunteer for a session where you are the speaker, or where you are giving a talk at the same time, or where you want to be in a separate session.<br />
<br />
Just put your name beside the sessions that you want to volunteer for. Take as many as you want, but please, only one volunteer per session. <br />
<br />
Remember, by doing this, you make it possible for the rest of the Fedora community to participate (and view for years to come). Thanks!<br />
<br />
= Volunteer Slots =<br />
<br />
== Friday August 9 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Friday || 9 AM || FPL Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Friday || 10 AM || Fedmsg || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|-<br />
|Auditorium || Friday || 11 AM || Why Fedora Sucks! || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Friday || 12 PM || ARM Architecture 101 ||<br />
|-<br />
|ECTR 101 || Friday || 10 AM || Creating an RPM from scratch || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 101 || Friday || 11 AM || Darkserver: Current and Future Roadmap ||<br />
|-<br />
|ECTR 101 || Friday || 12 PM || Agility and FOSS || <br />
|-<br />
|ECTR 103 || Friday || 10 AM || Ask Fedora Update ||<br />
|-<br />
|ECTR 103 || Friday || 11 AM || HyperKitty: The new mailing list UI ||<br />
|-<br />
|ECTR 103 || Friday || 12 PM || Bugzilla ||<br />
|-<br />
|ECTR 107 || Friday || 10 AM || Evolution of a Linux Distribution and its Ecosystem ||<br />
|-<br />
|ECTR 107 || Friday || 11 AM || Installer Redesign and Rewrite Retrospective ||<br />
|-<br />
|ECTR 107 || Friday || 12 PM || Fedora Ambassadors - State of the Union ||<br />
|- <br />
|ECTR 109 || Friday || 10 AM || Fedora ARM - State of the Union ||<br />
|-<br />
|ECTR 109 || Friday || 11 AM || Porting Fedora to 64-bit ARM || John Dulaney<br />
|-<br />
|ECTR 109 || Friday || 12 PM || Future of the Data Center ||<br />
|-<br />
|ECTR 112 || Friday || 10 AM || State of Security in Fedora ||<br />
|-<br />
|ECTR 112 || Friday || 11 AM || FreeIPA Two Factor Authentication ||<br />
|-<br />
|ECTR 112 || Friday || 12 PM || P***** - Product Naming in Global Communities ||<br />
|-<br />
|ECTR 115 || Friday || 10 AM || A Tour of Linux portability ||<br />
|-<br />
|ECTR 115 || Friday || 11 AM || State of the Fedora Kernel || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|- <br />
|ECTR 115 || Friday || 12 AM || KERNEL BUG TRIAGE LIVE! ||<br />
|-<br />
|ECTR 120 || Friday || 10 AM || Is "cloud" something beyond a buzzword and should Fedora care? ||<br />
|-<br />
|ECTR 120 || Friday || 11 AM || Putting the PaaS in Fedora ||<br />
|-<br />
|ECTR 120 || Friday || 12 PM || Bringing Hadoop to Fedora || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 212 || Friday || 10 AM || Education with Fedora ||<br />
|-<br />
|ECTR 212 || Friday || 11 AM || Fedora College ||<br />
|-<br />
|ECTR 212 || Friday || 12 PM || Fedora Software Center ||<br />
|-<br />
|}<br />
<br />
== Saturday August 10 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Saturday || 9 AM || Lulzbot Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Saturday || 10 AM || Pidora 18 (Raspberry Pi Fedora Remix) ||<br />
|-<br />
|Auditorium || Saturday || 11 AM || Fedora Badges ||<br />
|-<br />
|Auditorium || Saturday || 12 PM || OpenShift, Fedora, and the future of packaged web apps ||<br />
|-<br />
|ECTR 101 || Saturday || 10 AM || Using Fedora for developing things other than Fedora || [[User:Chrisroberts|Chris Roberts]]<br />
|-<br />
|ECTR 101 || Saturday || 11 AM || Make Games Using Free as in Freedom Art and Audio ||<br />
|-<br />
|ECTR 101 || Saturday || 12 PM || KVM and Virtio Introduction || <br />
|-<br />
|ECTR 103 || Saturday || 10 AM || Fedora At Yahoo! ||<br />
|-<br />
|ECTR 103 || Saturday || 11 AM || Fedora Passwords (then and now) ||<br />
|-<br />
|ECTR 103 || Saturday || 12 PM || Submitting Updates via Bodhi ||<br />
|-<br />
|ECTR 107 || Saturday || 11 AM || An Architecture for a More Agile Fedora || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 107 || Saturday || 12 AM || Task Automation in Fedora QA || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 109 || Saturday || 10 AM || Virtualization on ARM ||<br />
|-<br />
|ECTR 109 || Saturday || 11 AM || The Hotrodder's Guide to Maximum Performance LAMP ||<br />
|-<br />
|ECTR 109 || Saturday || 12 PM || Mozilla Open Badges in Sugar on OLPC ||<br />
|-<br />
|ECTR 112 || Saturday || 10 AM || SELinux for Mere Mortals ||<br />
|-<br />
|ECTR 112 || Saturday || 11 AM || What's New With SELinux? ||<br />
|-<br />
|ECTR 112 || Saturday || 12 PM || Hardening Apache ||<br />
|-<br />
|ECTR 114 || Saturday || 10 AM || Gource: Telling Stories via Source Code ||<br />
|-<br />
|ECTR 114 || Saturday || 11 AM || What's New In Software Management ||<br />
|-<br />
|ECTR 114 || Saturday || 12 PM || AWS, Private Cloud, and Open Source || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|ECTR 115 || Saturday || 10 AM || Kernel Regression Testing for Fun and Profit ||<br />
|-<br />
|ECTR 115 || Saturday || 11 AM || Btrfs - Cool Butter ||<br />
|- <br />
|ECTR 115 || Saturday || 12 AM || Kernel Fuzz Testing ||<br />
|-<br />
|ECTR 120 || Saturday || 10 AM || Federated and Free - Distributed and Decentralized Apps on OpenShift || [[User:Emichan|Emily Dirsh]]<br />
|-<br />
|ECTR 120 || Saturday || 11 AM || Scale or Fail - Give your app the Speed it Needs in the Cloud ||<br />
|-<br />
|ECTR 120 || Saturday || 12 PM || pcp+systemtap: Performance Monitoring for Workstations and Networks ||<br />
|-<br />
|}<br />
<br />
== Sunday August 11 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Sunday || 9 AM || Dave Crossland Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Sunday || 10 AM || Changing the Default Updates Model ||<br />
|-<br />
|Auditorium || Sunday || 11 AM || Gaming on Fedora || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Sunday || 12 PM || Ansible ||<br />
|-<br />
|ECTR 101 || Sunday || 10 AM || User Build Tools ||<br />
|-<br />
|ECTR 101 || Sunday || 11 AM || About MATE Desktop ||<br />
|-<br />
|ECTR 101 || Sunday || 12 PM || Scaling Integration Testing with Beaker || <br />
|-<br />
|ECTR 103 || Sunday || 10 AM || Code Review for Fedora Apps ||<br />
|-<br />
|ECTR 103 || Sunday || 11 AM || OpenID in the Fedora Services ||<br />
|-<br />
|ECTR 103 || Sunday || 12 PM || The Life of a Package || Mahrud Sayrafi<br />
|-<br />
|ECTR 107 || Sunday || 10 AM || User Testing for the Rest of Us ||<br />
|-<br />
|ECTR 107 || Sunday || 11 AM || Making Distributed VoIP Work (and Work Well) ||<br />
|-<br />
|ECTR 107 || Sunday || 12 AM || State of OrangeFS ||<br />
|-<br />
|ECTR 109 || Sunday || 10 AM || Fedora Project Ambassadors - Collaborate, Design, Engage ||<br />
|-<br />
|ECTR 109 || Sunday || 11 AM || Ambassadors Work in a Region - Annual Planning ||<br />
|-<br />
|ECTR 109 || Sunday || 12 PM || The Fedora Ambassadors Census ||<br />
|-<br />
|ECTR 112 || Sunday || 10 AM || Secure Linux Containers || Mahrud Sayrafi<br />
|-<br />
|ECTR 112 || Sunday || 11 AM || PKI Made Easy: Managing Certificates With Dogtag ||<br />
|-<br />
|ECTR 112 || Sunday || 12 PM || Measuring the Fedora Community with Census ||<br />
|-<br />
|ECTR 114 || Sunday || 10 AM || Fedora vs the Semantic Web ||<br />
|-<br />
|ECTR 114 || Sunday || 11 AM || Fedora Videos ||<br />
|-<br />
|ECTR 114 || Sunday || 12 PM || Unifying Administration with OpenLMI || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|-<br />
|ECTR 120 || Sunday || 10 AM || Hyperscale Cloud Management with OpenStack ||<br />
|-<br />
|ECTR 120 || Sunday || 11 AM || Polyglot Spatial with FOSS in the Cloud ||<br />
|-<br />
|ECTR 120 || Sunday || 12 PM || See the light: SDN, OpenDaylight, Open vSwitch and Fedora ||<br />
|-<br />
|}</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_Volunteers&diff=347814Flock Volunteers2013-08-03T07:10:33Z<p>Kashyapc: /* Friday August 9 */</p>
<hr />
<div>= Volunteers =<br />
Each 45 minute session needs to have a volunteer running the camera, watching a timer, and monitoring IRC for Q&A (if it happens).<br />
<br />
There are 10 tracks. The workshop/hackfest sessions will not need volunteers, as most of them will not be practical to record or stream.<br />
<br />
By signing up for a session, you're committing to:<br />
* Attending that session<br />
* Getting there a few minutes early to start the video stream<br />
* Watching a timer and signalling the speaker (with signs) when he/she has 10, 5, and 0 minutes remaining.<br />
<br />
You should not volunteer for a session where you are the speaker, or where you are giving a talk at the same time, or where you want to be in a separate session.<br />
<br />
Just put your name beside the sessions that you want to volunteer for. Take as many as you want, but please, only one volunteer per session. <br />
<br />
Remember, by doing this, you make it possible for the rest of the Fedora community to participate (and view for years to come). Thanks!<br />
<br />
= Volunteer Slots =<br />
<br />
== Friday August 9 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Friday || 9 AM || FPL Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Friday || 10 AM || Fedmsg || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|-<br />
|Auditorium || Friday || 11 AM || Why Fedora Sucks! || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Friday || 12 PM || ARM Architecture 101 ||<br />
|-<br />
|ECTR 101 || Friday || 10 AM || Creating an RPM from scratch || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 101 || Friday || 11 AM || Darkserver: Current and Future Roadmap ||<br />
|-<br />
|ECTR 101 || Friday || 12 PM || Agility and FOSS || <br />
|-<br />
|ECTR 103 || Friday || 10 AM || Ask Fedora Update ||<br />
|-<br />
|ECTR 103 || Friday || 11 AM || HyperKitty: The new mailing list UI ||<br />
|-<br />
|ECTR 103 || Friday || 12 PM || Bugzilla ||<br />
|-<br />
|ECTR 107 || Friday || 10 AM || Evolution of a Linux Distribution and its Ecosystem ||<br />
|-<br />
|ECTR 107 || Friday || 11 AM || Installer Redesign and Rewrite Retrospective ||<br />
|-<br />
|ECTR 107 || Friday || 12 PM || Fedora Ambassadors - State of the Union ||<br />
|- <br />
|ECTR 109 || Friday || 10 AM || Fedora ARM - State of the Union ||<br />
|-<br />
|ECTR 109 || Friday || 11 AM || Porting Fedora to 64-bit ARM || John Dulaney<br />
|-<br />
|ECTR 109 || Friday || 12 PM || Future of the Data Center ||<br />
|-<br />
|ECTR 112 || Friday || 10 AM || State of Security in Fedora ||<br />
|-<br />
|ECTR 112 || Friday || 11 AM || FreeIPA Two Factor Authentication ||<br />
|-<br />
|ECTR 112 || Friday || 12 PM || P***** - Product Naming in Global Communities ||<br />
|-<br />
|ECTR 115 || Friday || 10 AM || A Tour of Linux portability ||<br />
|-<br />
|ECTR 115 || Friday || 11 AM || State of the Fedora Kernel || [[User:Kashyapc|Kashyap Chamarthy]]<br />
|- <br />
|ECTR 115 || Friday || 12 AM || KERNEL BUG TRIAGE LIVE! ||<br />
|-<br />
|ECTR 120 || Friday || 10 AM || Is "cloud" something beyond a buzzword and should Fedora care? ||<br />
|-<br />
|ECTR 120 || Friday || 11 AM || Putting the PaaS in Fedora ||<br />
|-<br />
|ECTR 120 || Friday || 12 PM || Bringing Hadoop to Fedora || [[User:Kpeeples|Kenneth Peeples]]<br />
|-<br />
|ECTR 212 || Friday || 10 AM || Education with Fedora ||<br />
|-<br />
|ECTR 212 || Friday || 11 AM || Fedora College ||<br />
|-<br />
|ECTR 212 || Friday || 12 PM || Fedora Software Center ||<br />
|-<br />
|}<br />
<br />
== Saturday August 10 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Saturday || 9 AM || Lulzbot Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Saturday || 10 AM || Pidora 18 (Raspberry Pi Fedora Remix) ||<br />
|-<br />
|Auditorium || Saturday || 11 AM || Fedora Badges ||<br />
|-<br />
|Auditorium || Saturday || 12 PM || OpenShift, Fedora, and the future of packaged web apps ||<br />
|-<br />
|ECTR 101 || Saturday || 10 AM || Using Fedora for developing things other than Fedora || [[User:Chrisroberts|Chris Roberts]]<br />
|-<br />
|ECTR 101 || Saturday || 11 AM || Make Games Using Free as in Freedom Art and Audio ||<br />
|-<br />
|ECTR 101 || Saturday || 12 PM || KVM and Virtio Introduction || <br />
|-<br />
|ECTR 103 || Saturday || 10 AM || Fedora At Yahoo! ||<br />
|-<br />
|ECTR 103 || Saturday || 11 AM || Fedora Passwords (then and now) ||<br />
|-<br />
|ECTR 103 || Saturday || 12 PM || Submitting Updates via Bodhi ||<br />
|-<br />
|ECTR 107 || Saturday || 11 AM || An Architecture for a More Agile Fedora || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 107 || Saturday || 12 AM || Task Automation in Fedora QA || [[User:Bochecha|Mathieu Bridon]]<br />
|-<br />
|ECTR 109 || Saturday || 10 AM || Virtualization on ARM ||<br />
|-<br />
|ECTR 109 || Saturday || 11 AM || The Hotrodder's Guide to Maximum Performance LAMP ||<br />
|-<br />
|ECTR 109 || Saturday || 12 PM || Mozilla Open Badges in Sugar on OLPC ||<br />
|-<br />
|ECTR 112 || Saturday || 10 AM || SELinux for Mere Mortals ||<br />
|-<br />
|ECTR 112 || Saturday || 11 AM || What's New With SELinux? ||<br />
|-<br />
|ECTR 112 || Saturday || 12 PM || Hardening Apache ||<br />
|-<br />
|ECTR 114 || Saturday || 10 AM || Gource: Telling Stories via Source Code ||<br />
|-<br />
|ECTR 114 || Saturday || 11 AM || What's New In Software Management ||<br />
|-<br />
|ECTR 114 || Saturday || 12 PM || AWS, Private Cloud, and Open Source || [[User:Hguemar|Haikel Guemar]]<br />
|-<br />
|ECTR 115 || Saturday || 10 AM || Kernel Regression Testing for Fun and Profit ||<br />
|-<br />
|ECTR 115 || Saturday || 11 AM || Btrfs - Cool Butter ||<br />
|- <br />
|ECTR 115 || Saturday || 12 AM || Kernel Fuzz Testing ||<br />
|-<br />
|ECTR 120 || Saturday || 10 AM || Federated and Free - Distributed and Decentralized Apps on OpenShift || [[User:Emichan|Emily Dirsh]]<br />
|-<br />
|ECTR 120 || Saturday || 11 AM || Scale or Fail - Give your app the Speed it Needs in the Cloud ||<br />
|-<br />
|ECTR 120 || Saturday || 12 PM || pcp+systemtap: Performance Monitoring for Workstations and Networks ||<br />
|-<br />
|}<br />
<br />
== Sunday August 11 ==<br />
<br />
{|<br />
! Room<br />
! Day<br />
! Time<br />
! Topic<br />
! Volunteer<br />
|-<br />
|Auditorium || Sunday || 9 AM || Dave Crossland Keynote || Tom Callaway<br />
|-<br />
|Auditorium || Sunday || 10 AM || Changing the Default Updates Model ||<br />
|-<br />
|Auditorium || Sunday || 11 AM || Gaming on Fedora || [[User:Qubodup|Iwan Gabovitch]]<br />
|-<br />
|Auditorium || Sunday || 12 PM || Ansible ||<br />
|-<br />
|ECTR 101 || Sunday || 10 AM || User Build Tools ||<br />
|-<br />
|ECTR 101 || Sunday || 11 AM || About MATE Desktop ||<br />
|-<br />
|ECTR 101 || Sunday || 12 PM || Scaling Integration Testing with Beaker || <br />
|-<br />
|ECTR 103 || Sunday || 10 AM || Code Review for Fedora Apps ||<br />
|-<br />
|ECTR 103 || Sunday || 11 AM || OpenID in the Fedora Services ||<br />
|-<br />
|ECTR 103 || Sunday || 12 PM || The Life of a Package || Mahrud Sayrafi<br />
|-<br />
|ECTR 107 || Sunday || 10 AM || User Testing for the Rest of Us ||<br />
|-<br />
|ECTR 107 || Sunday || 11 AM || Making Distributed VoIP Work (and Work Well) ||<br />
|-<br />
|ECTR 107 || Sunday || 12 AM || State of OrangeFS ||<br />
|-<br />
|ECTR 109 || Sunday || 10 AM || Fedora Project Ambassadors - Collaborate, Design, Engage ||<br />
|-<br />
|ECTR 109 || Sunday || 11 AM || Ambassadors Work in a Region - Annual Planning ||<br />
|-<br />
|ECTR 109 || Sunday || 12 PM || The Fedora Ambassadors Census ||<br />
|-<br />
|ECTR 112 || Sunday || 10 AM || Secure Linux Containers || Mahrud Sayrafi<br />
|-<br />
|ECTR 112 || Sunday || 11 AM || PKI Made Easy: Managing Certificates With Dogtag ||<br />
|-<br />
|ECTR 112 || Sunday || 12 PM || Measuring the Fedora Community with Census ||<br />
|-<br />
|ECTR 114 || Sunday || 10 AM || Fedora vs the Semantic Web ||<br />
|-<br />
|ECTR 114 || Sunday || 11 AM || Fedora Videos ||<br />
|-<br />
|ECTR 114 || Sunday || 12 PM || Unifying Administration with OpenLMI ||<br />
|-<br />
|ECTR 120 || Sunday || 10 AM || Hyperscale Cloud Management with OpenStack ||<br />
|-<br />
|ECTR 120 || Sunday || 11 AM || Polyglot Spatial with FOSS in the Cloud ||<br />
|-<br />
|ECTR 120 || Sunday || 12 PM || See the light: SDN, OpenDaylight, Open vSwitch and Fedora ||<br />
|-<br />
|}</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Flock_2017_Rideshare&diff=347161Flock 2017 Rideshare2013-07-30T05:09:00Z<p>Kashyapc: </p>
<hr />
<div>This page is intended to help Flock attendees find rides to and from Flock and the airport. Please add your name and flight information if you need a ride or have a vehicle and would like to offer one.<br />
<br />
There are also shared vans that can be organized at approximately $15 USD per person or taxis at a flat rate of around $25 USD for up to three riders if people want to organize that.<br />
<br />
== Arrival ==<br />
{|class="wikitable sortable"<br />
! Name !! Date !! Time !! Flight number !! Passengers/Co-riders !! Notes<br />
|-<br />
| Stephen Gallagher || 2013-08-08 || 1:18pm || JetBlue 1667 || Nathaniel McCallum || Looking for a ride or a taxi-share<br />
|-<br />
| Nathaniel McCallum || 2013-08-08 || 1:15pm || Delta 1730 || Stephen Gallagher || Looking for a ride or a taxi-share<br />
|-<br />
| Rahul Sundaram || 2013-08-08 || 1:55pm || US Airways Flight # 2832 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| David Sugar || 2013-08-08 || 2:45pm || Delta Flight # 6006 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Truong Anh Tuan || 2013-08-08 || 4:03pm || JetBlue Airways 1373 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Ricky Elrod || 2013-08-08 || 3:28pm || US Airways Flight # 4583 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Peter Robinson || 2013-08-08 || 21:35 || America Airlines # BA2450 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Benedikt Schäfer || 2013-08-07 || 3:29pm || US Airways Flight # 4583 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Chris Roberts || 2013-08-08 || 4:01 PM || Delta Airlines Flight #6092 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| [[User:Cwickert|Christoph Wickert]] || 2013-08-07 || 08:26pm || Delta 1607 || N/A || Looking for a ride or a taxi-share (considering renting a car)<br />
|-<br />
| [[User:Jstanley|Jon Stanley]] || 2013-08-07 || 08:26PM || Delta 1607 || N/A || Looking for a rids<br />
|-<br />
| [[User:Churchyard|Miro Hrončok]] || 2013-08-08 || 07:31pm || United #5812 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Mathieu Bridon || 2013-08-08 || 07:31pm || UA5812 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]] || 2013-08-07 || 05:27 PM || (UA) LH5152 || N/A || Looking for a ride or a taxi-share<br />
|}<br />
<br />
== Departure ==<br />
{|class="wikitable sortable"<br />
! Name !! Date !! Time !! Flight number !! Passengers/Co-riders !! Notes<br />
|-<br />
| David Sugar || 2013-08-13 || 12:03pm || Delta # 5109 || || Looking for a ride or a taxi-share<br />
|-<br />
| Stephen Gallagher || 2013-08-13 || 1:54pm || JetBlue 1668 || || Looking for a ride or a taxi-share<br />
|-<br />
| Nathaniel McCallum || 2013-08-12 || 8:45am || Delta 2252 || || Looking for a ride or a taxi-share<br />
|-<br />
| Rahul Sundaram|| 2013-08-13 || 12:58pm|| US Airways Flight # 4634|| N/A|| Looking for a ride or a taxi-share<br />
|-<br />
| Truong Anh Tuan || 2013-08-13 || 6:30am || American Airlines 3395 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Ricky Elrod || 2013-08-13 || 7:30pm || US Airways Flight # 2705 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Peter Robinson || 2013-08-14 || 09:35 || America Airlines # BA2456 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Benedikt Schäfer || 2013-08-14 || 2:29pm || US Airways Flight # 2873 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| Chris Roberts || 2013-08-12 || 5:12 PM || Delta Airlines Flight #1791|| N/A || Looking for a ride or a taxi-share<br />
|-<br />
| [[User:Cwickert|Christoph Wickert]] || 2013-08-14 || 12:45pm || Delta 5847 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| [[User:Churchyard|Miro Hrončok]] || 2013-08-13 || 06:12pm || United #5832 || N/A || Looking for a ride or a taxi-share<br />
|-<br />
| [[User:Jstanley|Jon Stanley]] || 2013-08-12 || 06:30pm || Delta #730 || N/A || Looking for a ride or taxi-share<br />
|-<br />
| Mathieu Bridon || 2013-08-13 || 10:01AM || UA4111 || N/A || Looking for a ride or taxi-share<br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]] || 2013-08-13 || 12:46 PM || (UA) LH5175 || N/A || Looking for a ride or a taxi-share<br />
|}</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339508Test Day:2013-05-28 Virtualization2013-05-28T06:29:31Z<p>Kashyapc: /* Test Results */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
* [[User:rjones|Richard W.M. Jones]] (rwmjones)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
* Fedora 19 isn't listed as an OS option in virt-manager [https://bugzilla.redhat.com/show_bug.cgi?id=950230 bug 950230]<br />
* VM's can hang when trying to destroy: [https://bugzilla.redhat.com/show_bug.cgi?id=961665 bug 961665]<br />
* QXL + VNC has graphical corruption: [https://bugzilla.redhat.com/show_bug.cgi?id=948717 bug 948717]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with: <code>yum groupinstall virtualization</code><br />
<br />
As for getting the latest virt packages, you have a few options:<br />
<br />
=== Virt Test Day Live CD ===<br />
<br />
There's a Fedora 19 live CD image that already has all the required virtualization packages installed (though you should still <code>yum update</code> after booting). You will probably want a good amount of RAM if using this option (greater than 4G) since you'll be using RAM for both a VM and running the live OS.<br />
<br />
* Get the image: <code>wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso</code><br />
* For Live CD or USB setup instructions, see: [[FedoraLiveCD#Download_and_Create_Live_image_or_Live_USB]]<br />
* If you have a really beefy machine, you can probably run the Live CD in a VM using nested virtualization! (see instructions below)<br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:<br />
<br />
==== Install with CD/DVD ====<br />
<br />
You can download the Fedora 19 Beta in various formats [https://fedoraproject.org/get-prerelease here]. Note: the Beta will be officially released on 2013-05-28, the day of the Test Day; if you wish to download it ahead of time, the images can be found [https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/ here].<br />
<br />
==== Upgrade from Fedora 18 ====<br />
<br />
* The supported way is using 'fedup': [[FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F]] You may also find the instructions in the [[QA:Testcase_upgrade_fedup_cli_previous_desktop|fedup test case]] useful for using fedup to upgrade to a pre-release.<br />
* [[Upgrading_Fedora_using_yum|Upgrade using 'yum']]: This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option! This allows you to create KVM guests ''inside'' a Fedora 19 VM.<br />
<br />
Use the [[#Fedora_19_virt_packages_on_Fedora_18|virt-preview instructions]] below, install a guest using one of the [[#VM_Install|install test cases]], and follow the [[[[QA:Testcase_KVM_nested_virt|nested virt test case]] to finish the setup and verify things are working correctly.<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase_Virt_Serial_Console|VM serial console login]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|Host USB device hotplug]]<br />
* [[QA:Testcase_KVM_nested_virt|Enabling nested virtualization for a VM]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
'''We are tracking test results in a web application [http://autoqa-stg.fedoraproject.org/testdays/show_event?event_id=5 over here]<br />
<br />
Results from this web application will be automatically transferred to the Wiki on 2013-06-11 and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]<br />
<br />
<br />
== Debugging ==<br />
<br />
* https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339403Test Day:2013-05-28 Virtualization2013-05-27T16:19:26Z<p>Kashyapc: /* Extra tests */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== Fedora 19 Live Image tailored for the test day == <br />
<br />
Here's a Fedora Live image already containing all the packages related to virtualization. You can download the below image, burn it on a USB, install the ISO on a physical machine, and proceed to "Areas to test" section, below.<br />
<pre> wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso </pre><br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
If you already have an F19 machine - as an alternative to above, you could install a minimal set of packages to provide KVM-based virutalation, do:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Nested Virtualization ===<br />
<br />
If you're using an Intel processor:<br />
* For Fedora-19 -- https://github.com/kashyapc/nvmx-haswell/blob/master/SETUP-nVMX.rst<br />
* http://kashyapc.wordpress.com/2013/02/12/nested-virtualization-with-kvm-and-intel-on-fedora-18/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
<br />
If you're using an AMD processor:<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|pass}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339402Test Day:2013-05-28 Virtualization2013-05-27T16:08:03Z<p>Kashyapc: /* Fedora 19 Live Image tailored for the test day */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== Fedora 19 Live Image tailored for the test day == <br />
<br />
Here's a Fedora Live image already containing all the packages related to virtualization. You can download the below image, burn it on a USB, install the ISO on a physical machine, and proceed to "Areas to test" section, below.<br />
<pre> wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso </pre><br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
If you already have an F19 machine - as an alternative to above, you could install a minimal set of packages to provide KVM-based virutalation, do:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|pass}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339401Test Day:2013-05-28 Virtualization2013-05-27T16:07:36Z<p>Kashyapc: </p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== Fedora 19 Live Image tailored for the test day == <br />
<br />
Here's a Fedora Live image already containing all the packages related to virtualization. You can download the below image, burn it on a USB, install the ISO on a physical machine, and proceed with "Areas to test" section.<br />
<pre> wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso </pre><br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
If you already have an F19 machine - as an alternative to above, you could install a minimal set of packages to provide KVM-based virutalation, do:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|pass}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339400Test Day:2013-05-28 Virtualization2013-05-27T16:00:04Z<p>Kashyapc: /* What's needed to test */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
If you already have an F19 machine - as an alternative to above, you could install a minimal set of packages to provide KVM-based virutalation, do:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-RC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|pass}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339335Test Day:2013-05-28 Virtualization2013-05-27T04:09:06Z<p>Kashyapc: /* What's needed to test */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
Alternative to above you could also install a minimal set of packages to provide KVM-based virutalation, do:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 18 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-TC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|pass}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339334Test Day:2013-05-28 Virtualization2013-05-27T04:06:01Z<p>Kashyapc: /* Test Results */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
Alternative to abov,e you could also install a minimal KVM base set of packages by doing:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 18 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-TC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|pass}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=339333Test Day:2013-05-28 Virtualization2013-05-27T04:04:51Z<p>Kashyapc: /* What's needed to test */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* saving (migrate to file) a guest using spice is crashy [https://bugzilla.redhat.com/show_bug.cgi?id=962954 bug 962954]<br />
* /dev/vfio/vfio has wrong default permissions. [https://bugzilla.redhat.com/show_bug.cgi?id=967230 bug 967230]<br />
* Storage migration can fail at the end of the process [https://bugzilla.redhat.com/show_bug.cgi?id=967242 bug 967242]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
Alternative to abov,e you could also install a minimal KVM base set of packages by doing:<br />
<pre><br />
$ yum install libvirt-daemon-kvm libvirt-daemon-config-network libvirt-daemon-config-nwfilter -y<br />
$ yum install python-virtinst -y<br />
$ yum install libguestfs libguestfs-tools libguestfs-tools-c -y<br />
$ yum install virt-viewer -y<br />
</pre><br />
<br />
== Install a minimal, unattended F18 guest ==<br />
Here's a minimal script that'll create an unattended install, with a minimal set of packages (@core only). Guest configuration - 10G qcow2 disk, 2 vCPU, 2G vMEM, x86_64:<br />
<pre><br />
$ wget https://raw.github.com/kashyapc/virt-scripts/master/create-guest-qcow2.bash<br />
<br />
<br />
$ ./create-guest-qcow2.bash f18-testday f18 x86_64<br />
</pre><br />
<br />
Once the install is finished (takes 5 minutes or so), you can can login via <code>virsh</code> serial console (configured by default). Root password credentials: testpwd (the eagle-eyed will notice this in the kickstart section of the script). To exit out of serial console, do: ESC + ]<br />
<br />
<br />
As for getting the latest virt packages, you have a few options: <br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 18 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: https://dl.fedoraproject.org/pub/alt/stage/19-Beta-TC4/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
At present, some of the packages in virt-preview are actually newer than what's in Fedora 19 (qemu 1.4 vs. qemu 1.5), but testing is still useful.<br />
<br />
== '''Areas to test''' ==<br />
<br />
All these tests have an entry in the '''[[#Test Results |Test Results]]''' table, please record them there.<br />
<br />
=== '''VM Install''' ===<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
=== '''Standard features'''===<br />
<br />
These are recurring tests of standard virt features, they ensure nothing obvious is broken.<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, clone, delete, ...)]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug]]<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]<br />
<br />
=== '''New features''' ===<br />
<br />
New or improved features in Fedora 19:<br />
<br />
* [[QA:Testcase_Virtualization_VirtioRNG| Virtio RNG (Random Number Generator)]]<br />
* [[QA:Testcase_Live_Migration_using_libvirt/virsh#Migration_without_shared_storage| Live migration without shared storage (steps included for doing this with a single physical host)]]<br />
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment#Device_assignment_with_VFIO| Host PCI device assignment using VFIO]]<br />
<br />
<br />
== Extra tests ==<br />
<br />
These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs: <code># yum install '*guestf*'</code><br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions! <br />
<br />
Fedora 18 features:<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Misc tests:<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
All tests:<br />
* [[:Category:Virtualization_Test_Cases|Complete list of previous tests]]<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-05-28_Virtualization&diff=337744Test Day:2013-05-28 Virtualization2013-05-17T20:55:21Z<p>Kashyapc: /* Who's available */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2013-05-28<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
<!-- [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-30/XXXX IRC logs]) --><br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 19. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 19.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use this format:<br />
* [[User:<yourfedoracct>|<your name>]] (<your irc nick>)<br />
<br />
* [[User:berrange|Daniel Berrange]] (danpb)<br />
* [[User:rjones|Richard W.M. Jones]] (rwmjones)<br />
* [[User:stefanha|Stefan Hajnoczi]] (stefanha)<br />
* [[User:mrezanin|Miroslav Rezanina]] (mrezanin)<br />
* [[User:ericb|Eric Blake]] (eblake)<br />
* [[User:laine|Laine Stump]] (laine)<br />
--><br />
* [[User:crobinso|Cole Robinson]] (crobinso)<br />
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap)<br />
<br />
<!--<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* some graphical corruption if using cirrus virtual card for guests: [https://bugzilla.redhat.com/show_bug.cgi?id=871247 bug 871247]<br />
--><br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
As for getting the latest virt packages, you have a few options:<br />
<br />
=== Fedora 19 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 18 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 18<br />
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Fedora 19 virt packages on Fedora 18 ===<br />
<br />
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
=== Run Fedora 19 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 19 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 19 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
Some notes on nested virt with AMD and Intel:<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
== Areas to test ==<br />
<br />
=== '''VM Install''' ===<br />
<br />
Record your results for these test cases in the '''[[#Test Results |Test Results]]''' section.<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]<br />
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]<br />
<br />
Next give this a run through, which should ensure things aren't broken in some obvious manner:<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle (start, stop, save, delete, ...)]]<br />
<br />
=== '''New tests and features''' ===<br />
<br />
Record your results for these test cases in the '''[[#Test Results|Test Results]]''' section.<br />
<br />
FIXME<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 19 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs:<br />
<br />
# yum install '*guestf*'<br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
In Fedora 19, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure]. Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions!<br />
<br />
Fedora 17 features:<br />
<br />
* [[QA:Testcase Virtualization Live Backup|Live VM disk backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate|VM suspend/hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing|VM sandboxing w/ syscall filters]]<br />
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]<br />
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]<br />
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]<br />
<br />
Migration:<br />
<br />
* [[QA:Testcase Live Migration using libvirt/virsh|Live migration with virsh]]<br />
* [[QA:Testcase Offline (paused) Migration using libvirt/virsh|Offline migration with virsh]]<br />
<br />
Hotplug:<br />
<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach|NIC hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Attach/Detach a SCSI device to guest|SCSI hotplug with virsh]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest|USB hotplug with virsh]]<br />
<br />
virtio-scsi:<br />
<br />
* [[QA:Testcase Virtualization Virtio SCSI Install|Virtio SCSI install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug|Virtio SCSI hotplug]]<br />
<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! References<br />
|-<br />
<br />
<!--<br />
Some notes about template format. Example results<br />
<br />
{{result|pass}}<br />
{{result|fail}} <ref>Some notes about the failure. Link to a bug like {{bz|123456}} </ref><br />
{{result|inprogress}} <ref>This shows a rotating progress icon</ref><br />
{{result|warn}} <ref>Maybe you hit a separate issue but the test didn't fail</ref><br />
{{result|none}} <ref>Haven't done this test yet</ref><br />
--><br />
<br />
<!--<br />
Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
<br />
| [[User:crobinso|Cole Robinson]]<br />
| {{result|inprogress}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
[[Category:Test Days]] [[Category:Fedora 19 Test Days]] [[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Cloud_images&diff=335332Cloud images2013-05-03T20:10:56Z<p>Kashyapc: </p>
<hr />
<div>{{admon/tip| 1=URLS to download Fefora Cloud Images| 2=Here is a more update wiki page with [http://fedoraproject.org/en/get-fedora-options#cloud URLs to download Fedora images].}}<br />
<br />
{{autolang|base=yes}}<br />
In addition to DVDs and Live CDs, the Fedora Project makes its distribution available on cloud computing architectures. These Fedora images provide an excellent (and extensible) foundation for your server or appliance.<br />
<br />
== Amazon Elastic Compute Cloud (EC2) ==<br />
<br />
Fedora's EC2 images follow the standard EC2 login conventions, meaning that root login is disabled, but sudo access is granted.<br />
<br />
'''The default username for the images is ec2-user.'''<br />
<br />
Full documentation for interacting with EC2 is available from [http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/ Amazon Web Services].<br />
<br />
Direct questions or comments to the [[Cloud SIG]] [https://admin.fedoraproject.org/mailman/listinfo/cloud email list].<br />
<br />
=== Currently supported EC2 images ===<br />
<br />
==== Fedora 18 ====<br />
All Fedora 18 AMIs are EBS-Backed<br />
{|<br />
! AMI ID !! Region !! Architecture<br />
|-<br />
| ami-30aeec62 || ap-southeast-1 || x86_64<br />
|-<br />
| ami-caa9eb98 || ap-southeast-1 || i386<br />
|-<br />
| ami-9ae472a0 || ap-southeast-2 || x86_64<br />
|-<br />
| ami-dce771e6 || ap-southeast-2 || i386<br />
|-<br />
| ami-5f01bb5e || ap-northeast-1 || x86_64<br />
|-<br />
| ami-7100ba70 || ap-northeast-1 || i386<br />
|-<br />
| ami-6145cc08 || us-east-1 || x86_64<br />
|-<br />
| ami-0d44cd64 || us-east-1 || i386<br />
|-<br />
| ami-0899b94d || us-west-1 || x86_64<br />
|-<br />
| ami-de99b99b || us-west-1 || i386<br />
|-<br />
| ami-0266ed32 || us-west-2 || x86_64<br />
|-<br />
| ami-6467ec54 || us-west-2 || i386<br />
|-<br />
| ami-bafcf3ce || eu-west-1 || x86_64<br />
|-<br />
| ami-cafef1be || eu-west-1 || i386<br />
|-<br />
| ami-81558d9c || sa-east-1 || x86_64<br />
|-<br />
| ami-e5548cf8 || sa-east-1 || i386<br />
|}<br />
==== Fedora 17 ====<br />
{|<br />
! Region !! Architecture !! Root store !! AMI ID<br />
|-<br />
| us-west-2 || x86_64 || EBS-backed || ami-8e69e5be<br />
|-<br />
| us-west-2 || i386 || EBS-backed || ami-e269e5d2<br />
|-<br />
| us-west-1 || x86_64 || EBS-backed || ami-877e24c2<br />
|-<br />
| us-west-1 || i386 || EBS-backed || ami-417f2504<br />
|-<br />
| us-east-1 || x86_64 || EBS-backed || ami-2ea50247<br />
|-<br />
| us-east-1 || i386 || EBS-backed || ami-08d97e61<br />
|-<br />
| sa-east-1 || x86_64 || EBS-backed || ami-eee23cf3<br />
|-<br />
| sa-east-1 || i386 || EBS-backed || ami-1ae33d07<br />
|-<br />
| ap-northeast-1 || x86_64 || EBS-backed || ami-26e65527<br />
|-<br />
| ap-northeast-1 || i386 || EBS-backed || ami-5ae6555b<br />
|-<br />
| ap-southeast-1 || x86_64 || EBS-backed || ami-2e86c07c<br />
|-<br />
| ap-southeast-1 || i386 || EBS-backed || ami-cc86c09e<br />
|-<br />
| ap-southeast-2 || x86_64 || EBS-backed || ami-e3a433d9<br />
|-<br />
| ap-southeast-2 || i386 || EBS-backed || ami-87a433bd<br />
|-<br />
| eu-west-1 || x86_64 || EBS-backed || ami-9980baed<br />
|-<br />
| eu-west-1 || i386 || EBS-backed || ami-e981bb9d<br />
|}<br />
<br />
==== Fedora 16 ====<br />
<br />
{|<br />
! Region !! Architecture !! Root store !! AMI ID<br />
|-<br />
| us-east-1 || i386 || EBS-backed || ami-5f16d836<br />
|-<br />
| us-east-1 || x86_64 || EBS-backed || ami-0316d86a<br />
|-<br />
| us-west-1 || i386 || EBS-backed || ami-25e0bc60<br />
|-<br />
| us-west-1 || x86_64 || EBS-backed || ami-69e0bc2c<br />
|-<br />
| us-west-2 || i386 || EBS-backed || ami-e2f37ed2<br />
|-<br />
| us-west-2 || x86_64 || EBS-backed || ami-88f37eb8<br />
|-<br />
| eu-west-1 || i386 || EBS-backed || ami-7bf4c90f<br />
|-<br />
| eu-west-1 || x86_64 || EBS-backed || ami-2df4c959<br />
|-<br />
| ap-southeast-1 || i386 || EBS-backed || ami-9694eec4<br />
|-<br />
| ap-southeast-1 || x86_64 || EBS-backed || ami-5095ef02<br />
|-<br />
| ap-northeast-1 || i386 || EBS-backed || ami-f22094f3<br />
|-<br />
| ap-northeast-1 || x86_64 || EBS-backed || ami-16219517<br />
|-<br />
| sa-east-1 || i386 || EBS-backed || ami-5a34eb47<br />
|-<br />
| sa-east-1 || x86_64 || EBS-backed || ami-4c34eb51<br />
|}<br />
<br />
=== Custom image creation ===<br />
<br />
Visit [[Cloud_SIG/EC2_Creation]] for instructions on how to build custom versions of these images.<br />
<br />
[[Category:Cloud SIG]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-04-02_OpenStack&diff=328966Test Day:2013-04-02 OpenStack2013-04-02T17:31:55Z<p>Kashyapc: /* Test Results */</p>
<hr />
<div>{{Infobox_group<br />
| name = OpenStack Test Day<br />
| date = 2013-04-02<br />
| time = all day<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day, webirc])<br />
}}<br />
<br />
<br />
{{admon/note | Can't make the dates? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<br />
Development<br />
* [[User:Pbrady|Pbrady]] (pixelbeat)<br />
* [[User:Mrunge|Mrunge]] (mrunge)<br />
* [[User:Eglynn|Eglynn]] (eglynn)<br />
* [[User:Apevec|Apevec]] (apevec)<br />
* [[User:Gkotton|GKotton]] (garyk)<br />
* [[User:Eharney|eharney]] (eharney)<br />
* [[User:Vaneldik|Vaneldik]] (vaneldik)<br />
* [[User:spstarr|spstarr]] (spstarr)<br />
Testing<br />
* [[User:kashyapc|kashyapc]] (kashyap)<br />
* [[User:spstarr|spstarr]] (spstarr)<br />
* [[User:mkollaro|mkollaro]] (mkollaro)<br />
<br />
<br />
== Prerequisite for Test Day == <br />
<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V).<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
{{admon/note|Hardware Requirements|You can do basic testing of OpenStack in a virtual machine, which is auto detected by the install script below}}<br />
<br />
This is a Fedora 19 test day, but we have OpenStack Grizzly packages available for both Fedora 19 and Fedora 18.<br />
It would be advisable to download and install your Fedora 18 or Fedora 19 test systems before the test day if possible.<br />
<br />
=== Fedora 19 ===<br />
* [https://dl.fedoraproject.org/pub/alt/stage/ Fedora 19 Alpha live image] can be used to install a virtual machine.<br />
* Currently bare metal installs are not supported [https://bugzilla.redhat.com/show_bug.cgi?id=928228 #928228]<br />
* VMs should have at least 2G RAM and 16G disk made available [https://bugzilla.redhat.com/show_bug.cgi?id=928886 #928886]<br />
<br />
Please record common Fedora 19 issues here:<br />
* System doesn't boot after install until /run is manually created [https://bugzilla.redhat.com/show_bug.cgi?id=922988#c27 #922988]<br />
* Screen blanking/locking can't be undone. So disable immediately on first boot [https://bugzilla.redhat.com/show_bug.cgi?id=923364 #923364]<br />
<br />
* If you have an F18, machine, since F19 is branched, you can update to f19 using the below way:<br />
<br />
yum update yum; yum clean all ; yum --releasever=19 distro-sync --nogpgcheck -y;<br />
<br />
=== Fedora 18 ===<br />
[http://alt.fedoraproject.org/pub/alt/live-respins/ Recent Fedora 18 live image respins] can be used to install a bare metal or virtual machine.<br />
<br />
== How to test? ==<br />
<br />
Follow the steps below to prepare the machine, then follow each of the test cases in order.<br />
<br />
=== Configure sudo ===<br />
<br />
Add <span style="color:red;">your account</span> to sudoers, which can be done from a root prompt like:<br />
<br />
(umask 337; echo "<span style="color:red;">non_root_user</span> ALL = (ALL) NOPASSWD: ALL" > /etc/sudoers.d/testday)<br />
<br />
=== Update your machine ===<br />
<br />
Make sure you have all the current updates for it installed:<br />
<br />
sudo yum --enablerepo=updates-testing clean all<br />
sudo yum update -y<br />
<br />
=== SELinux ===<br />
<br />
SELinux should work with OpenStack services.<br />
If there are issues you can disable like:<br />
<br />
sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config<br />
sudo setenforce permissive<br />
<br />
Please do note any AVC _denials_ you see in /var/log/audit/audit.log and file them in bugzilla, and update this list:<br />
<br />
* {{bz|123456}} general - ....<br />
<br />
== Install and setup all Openstack services on a single node ==<br />
<br />
'''Test day only''' Please use the official Fedora repositories otherwise<br />
sudo curl http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/fedora-openstack-grizzly.repo -o /etc/yum.repos.d/fedora-openstack-grizzly.repo<br />
<br />
So now the yum repositories are in place, so we'll install packstack.<br />
This can install all OpenStack services on a single node, including:<br />
nova, glance, quantum, cinder, swift, keystone, dashboard, ceilometer.<br />
Note it configures and enables all but the quantum and ceilometer services at this time:<br />
'''Packstack is not working on F19 https://bugzilla.redhat.com/show_bug.cgi?id=927298'''<br />
sudo yum install -y openstack-packstack<br />
sudo packstack --gen-answer-file=ans.txt<br />
# edit ans.txt as required<br />
sudo packstack --answer-file=ans.txt<br />
<br />
'''packstack known issues : '''<br />
# packstack fails to start keystone, if you hit a keystone error during the packstack run, change the permission of the keystone log file and rerun packstack ([https://bugzilla.redhat.com/show_bug.cgi?id=946915 rhbz#946915])<br />
sudo chown keystone:keystone /var/log/keystone/keystone.log<br />
# if sometimes outputs an erorr when trying to start tdtd if this happens start it manually and rerun packstack<br />
sudo systemctl start tgtd<br />
<br />
Alternatively one can use the openstack-demo-install script to do the install:<br />
<br />
sudo yum install -y openstack-utils<br />
sudo [https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-demo-install openstack-demo-install]<br />
<br />
Note this is a major test in itself, so please record any issues encountered.<br />
<br />
Now copy the keystonerc file created by the install script above to your home directory,<br />
so that it can be easily sourced to provide the credentials used by the various OpenStack command line utilities.<br />
<br />
sudo cp /root/keystonerc ~<br />
# or if using packstack<br />
sudo cp /root/keystonerc_admin ~<br />
<br />
=== Known issues ===<br />
<br />
== Setup OpenStack volumes ==<br />
<br />
The OpenStack volume service provides persistent block level storage to instances.<br />
<br />
This is a commonly used service automatically setup by packstack.<br />
If you ran openstack-demo-install instead please enable by following:<br />
<br />
[[QA:Testcase_Create_Cinder_Volumes | Setup Cinder Volumes]]<br />
<br />
== Install and setup Quantum on a single node ==<br />
<br />
As an option, you can replace the network manager<br />
internal to the OpenStack Nova project with Quantum.<br />
<br />
[[Quantum | Enable Quantum networking]]<br />
<br />
'''Note''' if packstack was used then you need to terminate nova networking. This is done as follows:<br />
service openstack-nova-network stop<br />
chkconfig openstack-nova-network off<br />
<br />
== Test Cases ==<br />
<br />
Basic setup:<br />
<br />
# [[QA:Testcase_add_SSH_keypair_to_OpenStack|Add SSH keypair]]<br />
# [[QA:Testcase_register_images_with_OpenStack|Register guest images]]<br />
# [[QA:Testcase_create_OpenStack_nova_network|Create nova network]]<br />
<br />
Core functionality:<br />
<br />
# [[QA:Testcase_launch_an_instance_on_OpenStack|Launch an instance]]<br />
# [[QA:Testcase_attach_a_cinder_volume_to_an_instance|Attach a volume]]<br />
# [[QA:Testcase_OpenStack_floating_IPs|Floating IPs]]<br />
# [[QA:Testcase_separate_OpenStack_compute_node|Separate compute node]]<br />
<br />
Nova boot-from-volume:<br />
<br />
# [[QA:Testcase_Nova_Create_Builder_Instance | Create a builder instance]]<br />
# [[QA:Testcase_Nova_Create_Bootable_Volume | Create and boot from a bootable volume]]<br />
# [[QA:Testcase_Nova_Snapshot_Volume_Backed_Instance | Create an image from a running volume-backed instance]]<br />
<br />
Quantum functionality:<br />
<br />
# [[QA:Testcase_Quantum_V2#How_to_test | Configure and use a network topology in Quantum]]<br />
<br />
Swift functionality:<br />
<br />
# [[QA:Testcase_Swift_Upload_Download_Files | Upload and download files]]<br />
# [[QA:Testcase_Swift_Upload_Large_File | Upload Segmented File]]<br />
# [[QA:Testcase_Swift_Auditor_Replicator | Test Auditor/Replicator]]<br />
# [[QA:Testcase_Swift_Add_Device | Add Storage Device to ring]]<br />
<br />
Dashboard functionality:<br />
<br />
# [[QA:Testcase_OpenStack_dashboard_setup|Basic dashboard setup and login]]<br />
# [[QA:Testcase_OpenStack_dashboard_launch_instance|Launch/terminate an instance with the dashboard]]<br />
# [[QA:Testcase_OpenStack_dashboard_add_users|Managing projects and users with the dashboard]]<br />
# [[QA:Testcase_OpenStack_dashboard_vnc|VNC access to instances through the dashboard]]<br />
<br />
Heat basic functionality (recommended for all developers):<br />
<br />
# [[QA:Testcase_OpenStack_heat_setup|Basic heat setup and configuration]]<br />
# [[QA:Testcase_OpenStack_heat_launch|Launch a basic wordpress stack]]<br />
# [[QA:Testcase_OpenStack_heat_stop|Stop Heat services and uninstall Heat]]<br />
<br />
Heat advanced functionality (recommended for all developers):<br />
<br />
# [[QA:Testcase_OpenStack_heat_rununit|Run nose unit tests]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_With_LB|Run Load Balancing testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_With_RDS|Run Relational Database service testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance_With_EIP|Run EIP testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance_With_EBS|Run EBS testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance_With_EBS_EIP|Run EBS and EIP testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance|Run Single Instance Wordpress testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_Composed_Instances|Run Compsed Instances testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_2_Instances_With_EBS|Run 2 instance EBS testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_2_Instances_With_EBS_EIP|Run 2 instances with EBS and EIP]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_2_Instances|Run 2 instance Wordpress testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_HAProxy_Single_Instance|Run HAProxy Single Instance testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_CFN_API_Actions|Run CFN API actions testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_AutoScalingMultiAZSample|Run AutoScaling testcase]]<br />
<br />
Ceilometer functionality (recommended for all developers):<br />
<br />
# [[QA:Testcase_OpenStack_ceilometer_install|Install ceilometer]]<br />
# [[QA:Testcase_OpenStack_ceilometer_metering_glance|Enable metering of glance]]<br />
# [[QA:Testcase_OpenStack_ceilometer_metering_nova|Enable metering of nova]]<br />
# [[QA:Testcase_OpenStack_ceilometer_mongodb_store|Explore the metering store]]<br />
<br />
Extra credit:<br />
<br />
# [[QA:Testcase_run_Tempest_tests|Tempest tests]]<br />
# [[QA:Testcase_build_an_OpenStack_guest_image_with_Oz|Build an image with Oz]]<br />
# [[QA:Testcase_run_the_OpenStack_smoke_tests|Smoke tests]]<br />
<br />
== Test Results ==<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for one of the [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-nova openstack-nova], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-glance openstack-glance], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-keystone openstack-keystone], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-cinder openstack-cinder],[https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-quantum openstack-quantum], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-swift openstack-swift] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-heat openstack-heat] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-ceilometer openstack-ceilometer] components. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.<br />
<br />
Basic setup:<br />
<br />
{|<br />
! User<br />
! openstack-demo-install<br />
! [[QA:Testcase_Create_Cinder_Volumes|Create Cinder Volumes]]<br />
! [[QA:Testcase_add_SSH_keypair_to_OpenStack|Add SSH keypair]]<br />
! [[QA:Testcase_register_images_with_OpenStack|Register images]]<br />
! [[QA:Testcase_create_OpenStack_nova_network|Create nova network]]<br />
! References<br />
<br />
|-<br />
| [[User:SampleUser|Sample User]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass}}<br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| <references/><br />
|-<br />
<br />
|-<br />
| [[User:rvaknin|Rami Vaknin]]<br />
| {{result|none}} Packstack installation fails due to "/etc/init.d/xinetd reload" command that it runs<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|fail}} <ref>{{bz|947427}}</ref><br />
| <references/><br />
|-<br />
<br />
|-<br />
| [[User:rvaknin|Rami Vaknin]]<br />
| {{result|none}} Packstack installation fails due to syntax error in /etc/httpd/conf.d/ssl.conf (Fedora bug)<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|fail}} <ref>{{bz|947421}}</ref><br />
| <references/><br />
|-<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|none}} no obvious way to delete incorrect security rules (added to the default nova security group) <br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|fail}} <ref>{{bz|947075}}</ref> Also reproducible on Fedora-19. Upstream bz - https://bugs.launchpad.net/nova/+bug/1163469<br />
| <references/><br />
|-<br />
<br />
|-<br />
| [[User:mrceresa|Mario Ceresa]]<br />
| {{result|none}} Packstack on f18 VM<ref> It worked but encountered {{bz|947419}} </ref><br />
| {{result|pass}} <ref>was already configured</ref><br />
| {{result|pass}} <ref>credentials in keystonerc_admin no keystonerc</ref><br />
| {{result|warn}} <br />
* glance copy_from hangs on stdin <ref>{{bz|923844}}</ref><br />
* tty images failed with "Could not resolve host: images.ansolabs.com; Name or service not known"<br />
* Manually downloading a cirros image + glance add name=cirros is_public=true disk_format=qcow2 container_format=bare < cirros-0.3.0-x86_64-disk.img worked.<br />
| {{result|pass}} <br />
| <references/><br />
|-<br />
<br />
|-<br />
| [[User:mkollaro|Martina Kollarova]]<br />
| {{result|none}} Packstack on f18 VM<ref> swift proxy server fails to start {{bz|947469}}</ref><ref> tgtd service fails to start but can be manually started {{bz|947419}} </ref><br />
| {{result|pass}} <ref>done automatically by packstack</ref><br />
| {{result|pass}} <br />
| {{result|fail}} <br />
* glance add using copy_from hangs <ref>{{bz|923844}}</ref><br />
* could not test using tty images, the server is unavailable<br />
| {{result|pass}} <br />
| <references/><br />
|-<br />
<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_launch_an_instance_on_OpenStack|Launch an instance]]<br />
! [[QA:Testcase_attach_a_cinder_volume_to_an_instance|Attach a volume]]<br />
! [[QA:Testcase_OpenStack_floating_IPs|Floating IPs]]<br />
! [[QA:Testcase_separate_OpenStack_compute_node|Separate compute node]]<br />
! References<br />
|-<br />
<br />
|-<br />
| [[User:mrceresa|Mario Ceresa]]<br />
| {{result|pass}} <ref>If you get a wrong ip on the instance, remember to check if packstack silently configured an additional network or if the default nework of libvirtd is active</ref><br />
| {{result|fail}} <ref>{{bz|947463}}</ref><br />
| {{result|none}} <br />
| {{result|pass}} <ref>Should update the test case page: lokkit does not work with firewallD</ref><br />
| <references/><br />
|-<br />
<br />
|-<br />
| [[User:mkollaro|Martina Kollarova]]<br />
| {{result|pass}} <br />
| {{result|fail}} <ref>{{bz|947463}}</ref><br />
| {{result|none}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
<br />
<br />
Core functionality:<br />
<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_Nova_Create_Builder_Instance | Create a builder instance]]<br />
! [[QA:Testcase_Nova_Create_Bootable_Volume | Create and boot from a bootable volume]]<br />
! [[QA:Testcase_Nova_Snapshot_Volume_Backed_Instance | Create an image from a running volume-backed instance]]<br />
! References<br />
|-<br />
<br />
Nova boot-from-volume:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_Quantum_V2#How_to_test | Configure and use a network topology in Quantum]]<br />
! References<br />
|-<br />
<br />
Quantum functionality:<br />
<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_Swift_Upload_Download_Files | Upload and download files]]<br />
! [[QA:Testcase_Swift_Upload_Large_File | Upload Segmented File]]<br />
! [[QA:Testcase_Swift_Auditor_Replicator | Test Auditor/Replicator]]<br />
! [[QA:Testcase_Swift_Add_Device | Add Storage Device to ring]]<br />
! References<br />
|-<br />
Swift functionality:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_OpenStack_dashboard_setup|Basic dashboard setup and login]]<br />
! [[QA:Testcase_OpenStack_dashboard_launch_instance|Launch/terminate an instance with the dashboard]]<br />
! [[QA:Testcase_OpenStack_dashboard_add_users|Managing projects and users with the dashboard]]<br />
! [[QA:Testcase_OpenStack_dashboard_vnc|VNC access to instances through the dashboard]]<br />
! References<br />
|-<br />
Dashboard functionality:<br />
<br />
|-<br />
| [[User:mrceresa|Mario Ceresa]]<br />
| {{result|fail}} <ref>horizon starts but halts when logging in. Setting DEBUG=true in local_settings showed that python-cinderclient hits the same error as in {{bz|947463}}</ref><br />
| {{result|none}} <br />
| {{result|none}} <br />
| {{result|none}} <br />
| <references/><br />
|-<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_OpenStack_heat_setup|Basic heat setup and login]]<br />
! [[QA:Testcase_OpenStack_heat_launch|Launch a basic wordpress stack]]<br />
! [[QA:Testcase_OpenStack_heat_stop|Stop Heat services and uninstall Heat]]<br />
! References<br />
|-<br />
<br />
|-<br />
heat functionality:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_OpenStack_ceilometer_install|Install ceilometer]]<br />
! [[QA:Testcase_OpenStack_ceilometer_metering_glance|Enable metering of glance]]<br />
! [[QA:Testcase_OpenStack_ceilometer_metering_nova|Enable metering of nova]]<br />
! [[QA:Testcase_OpenStack_ceilometer_mongodb_store|Explore the metering store]]<br />
! References<br />
|-<br />
Ceilometer functionality:<br />
<br />
|-<br />
| [[User:Eglynn|Eoghan Glynn]]<br />
| {{result|pass}}<br />
| {{result|pass}} <br />
| {{result|pass}} <br />
| {{result|pass}} <br />
| <references/><br />
|-<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_run_Tempest_tests|Tempest tests]]<br />
! [[QA:Testcase_build_an_OpenStack_guest_image_with_Oz|Build an image with Oz]]<br />
! [[QA:Testcase_run_the_OpenStack_smoke_tests|Smoke tests]]<br />
! References<br />
<br />
|-<br />
Extra credit:<br />
<br />
[[Category:Test Days]]<br />
[[Category:OpenStack]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2013-04-02_OpenStack&diff=328839Test Day:2013-04-02 OpenStack2013-04-02T07:14:18Z<p>Kashyapc: </p>
<hr />
<div>{{Infobox_group<br />
| name = OpenStack Test Day<br />
| date = 2013-04-02<br />
| time = all day<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day, webirc])<br />
}}<br />
<br />
<br />
{{admon/note | Can't make the dates? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<br />
* Development - [[User:Pbrady|Pbrady]] (pixelbeat)<br />
* Development - [[User:Mrunge|Mrunge]] (mrunge)<br />
* Deployment - [[User:Vaneldik|Vaneldik]] (vaneldik), [[User:spstarr|spstarr]] (spstarr)<br />
* Test - [[User:kashyapc|kashyapc]] (kashyap), [[User:spstarr|spstarr]] (spstarr)<br />
<br />
== Prerequisite for Test Day == <br />
<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V).<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
{{admon/note|Hardware Requirements|You can do basic testing of OpenStack in a virtual machine, which is auto detected by the install script below}}<br />
<br />
This is a Fedora 19 test day, but we have OpenStack Grizzly packages available for both Fedora 19 and Fedora 18.<br />
It would be advisable to download and install your Fedora 18 or Fedora 19 test systems before the test day if possible.<br />
<br />
=== Fedora 19 ===<br />
* [https://dl.fedoraproject.org/pub/alt/stage/ Fedora 19 Alpha live image] can be used to install a virtual machine.<br />
* Currently bare metal installs are not supported [https://bugzilla.redhat.com/show_bug.cgi?id=928228 #928228]<br />
* VMs should have at least 2G RAM and 16G disk made available [https://bugzilla.redhat.com/show_bug.cgi?id=928886 #928886]<br />
<br />
Please record common Fedora 19 issues here:<br />
* System doesn't boot after install until /run is manually created [https://bugzilla.redhat.com/show_bug.cgi?id=922988#c27 #922988]<br />
* Screen blanking/locking can't be undone. So disable immediately on first boot [https://bugzilla.redhat.com/show_bug.cgi?id=923364 #923364]<br />
<br />
=== Fedora 18 ===<br />
[http://alt.fedoraproject.org/pub/alt/live-respins/ Recent Fedora 18 live image respins] can be used to install a bare metal or virtual machine.<br />
<br />
== How to test? ==<br />
<br />
Follow the steps below to prepare the machine, then follow each of the test cases in order.<br />
<br />
=== Configure sudo ===<br />
<br />
Add <span style="color:red;">your account</span> to sudoers, which can be done from a root prompt like:<br />
<br />
(umask 337; echo "<span style="color:red;">non_root_user</span> ALL = (ALL) NOPASSWD: ALL" > /etc/sudoers.d/testday)<br />
<br />
=== Update your machine ===<br />
<br />
Make sure you have all the current updates for it installed:<br />
<br />
sudo yum --enablerepo=updates-testing clean all<br />
sudo yum update -y<br />
<br />
=== SELinux ===<br />
<br />
SELinux should work with OpenStack services.<br />
If there are issues you can disable like:<br />
<br />
sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config<br />
sudo setenforce permissive<br />
<br />
Please do note any AVC _denials_ you see in /var/log/audit/audit.log and file them in bugzilla, and update this list:<br />
<br />
* {{bz|123456}} general - ....<br />
<br />
== Install and setup all Openstack services on a single node ==<br />
<br />
'''Test day only''' Please use the official Fedora repositories otherwise<br />
sudo curl http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/fedora-openstack-grizzly.repo -o /etc/yum.repos.d/fedora-openstack-grizzly.repo<br />
<br />
So now the yum repositories are in place, so we'll install packstack.<br />
This can install all OpenStack services on a single node, including:<br />
nova, glance, quantum, cinder, swift, keystone, dashboard, ceilometer.<br />
Note it configures and enables all but the quantum and ceilometer services at this time:<br />
<br />
sudo yum install -y openstack-packstack<br />
sudo packstack --gen-answer-file=ans.txt<br />
# edit ans.txt as required<br />
sudo packstack --answer-file=ans.txt<br />
<br />
'''packstack known issues : '''<br />
# packstack fails to start keystone, if you hit a keystone error during the packstack run, change the permission of the keystone log file and rerun packstack ([https://bugzilla.redhat.com/show_bug.cgi?id=946915 rhbz#946915])<br />
sudo chown keystone:keystone /var/log/keystone/keystone.log<br />
<br />
Alternatively one can use the openstack-demo-install script to do the install:<br />
<br />
sudo yum install -y openstack-utils<br />
sudo [https://github.com/fedora-openstack/openstack-utils/blob/master/utils/openstack-demo-install openstack-demo-install]<br />
<br />
Note this is a major test in itself, so please record any issues encountered.<br />
<br />
Now copy the keystonerc file created by the install script above to your home directory,<br />
so that it can be easily sourced to provide the credentials used by the various OpenStack command line utilities.<br />
<br />
sudo cp /root/keystonerc ~<br />
<br />
=== Known issues ===<br />
<br />
== Setup OpenStack volumes ==<br />
<br />
The OpenStack volume service provides persistent block level storage to instances.<br />
<br />
This is a commonly used service, so please enable using<br />
<br />
[[QA:Testcase_Create_Cinder_Volumes | Setup Cinder Volumes]]<br />
<br />
== Install and setup Quantum on a single node ==<br />
<br />
As an option, you can replace the network manager<br />
internal to the OpenStack Nova project with Quantum.<br />
<br />
[[Quantum | Enable Quantum networking]]<br />
<br />
== Test Cases ==<br />
<br />
Basic setup:<br />
<br />
# [[QA:Testcase_add_SSH_keypair_to_OpenStack|Add SSH keypair]]<br />
# [[QA:Testcase_register_images_with_OpenStack|Register guest images]]<br />
# [[QA:Testcase_create_OpenStack_nova_network|Create nova network]]<br />
<br />
Core functionality:<br />
<br />
# [[QA:Testcase_launch_an_instance_on_OpenStack|Launch an instance]]<br />
# [[QA:Testcase_attach_a_cinder_volume_to_an_instance|Attach a volume]]<br />
# [[QA:Testcase_OpenStack_floating_IPs|Floating IPs]]<br />
# [[QA:Testcase_separate_OpenStack_compute_node|Separate compute node]]<br />
<br />
Nova boot-from-volume:<br />
<br />
# [[QA:Testcase_Nova_Create_Builder_Instance | Create a builder instance]]<br />
# [[QA:Testcase_Nova_Create_Bootable_Volume | Create and boot from a bootable volume]]<br />
# [[QA:Testcase_Nova_Snapshot_Volume_Backed_Instance | Create an image from a running volume-backed instance]]<br />
<br />
Quantum functionality:<br />
<br />
# [[QA:Testcase_Quantum_V2#How_to_test | Configure and use a network topology in Quantum]]<br />
<br />
Swift functionality:<br />
<br />
# [[QA:Testcase_Swift_Upload_Download_Files | Upload and download files]]<br />
# [[QA:Testcase_Swift_Upload_Large_File | Upload Segmented File]]<br />
# [[QA:Testcase_Swift_Auditor_Replicator | Test Auditor/Replicator]]<br />
# [[QA:Testcase_Swift_Add_Device | Add Storage Device to ring]]<br />
<br />
Dashboard functionality:<br />
<br />
# [[QA:Testcase_OpenStack_dashboard_setup|Basic dashboard setup and login]]<br />
# [[QA:Testcase_OpenStack_dashboard_launch_instance|Launch/terminate an instance with the dashboard]]<br />
# [[QA:Testcase_OpenStack_dashboard_add_users|Managing projects and users with the dashboard]]<br />
# [[QA:Testcase_OpenStack_dashboard_vnc|VNC access to instances through the dashboard]]<br />
<br />
Heat basic functionality (recommended for all developers):<br />
<br />
# [[QA:Testcase_OpenStack_heat_setup|Basic heat setup and configuration]]<br />
# [[QA:Testcase_OpenStack_heat_launch|Launch a basic wordpress stack]]<br />
# [[QA:Testcase_OpenStack_heat_stop|Stop Heat services and uninstall Heat]]<br />
<br />
Heat advanced functionality (recommended for all developers):<br />
<br />
# [[QA:Testcase_OpenStack_heat_rununit|Run nose unit tests]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_With_LB|Run Load Balancing testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_With_RDS|Run Relational Database service testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance_With_EIP|Run EIP testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance_With_EBS|Run EBS testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance_With_EBS_EIP|Run EBS and EIP testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_Single_Instance|Run Single Instance Wordpress testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_Composed_Instances|Run Compsed Instances testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_2_Instances_With_EBS|Run 2 instance EBS testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_2_Instances_With_EBS_EIP|Run 2 instances with EBS and EIP]]<br />
# [[QA:Testcase_OpenStack_heat_run_WordPress_2_Instances|Run 2 instance Wordpress testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_HAProxy_Single_Instance|Run HAProxy Single Instance testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_CFN_API_Actions|Run CFN API actions testcase]]<br />
# [[QA:Testcase_OpenStack_heat_run_AutoScalingMultiAZSample|Run AutoScaling testcase]]<br />
<br />
Ceilometer functionality (recommended for all developers):<br />
<br />
# [[QA:Testcase_OpenStack_ceilometer_install|Install ceilometer]]<br />
<br />
Extra credit:<br />
<br />
# [[QA:Testcase_run_Tempest_tests|Tempest tests]]<br />
# [[QA:Testcase_build_an_OpenStack_guest_image_with_Oz|Build an image with Oz]]<br />
# [[QA:Testcase_run_the_OpenStack_smoke_tests|Smoke tests]]<br />
<br />
== Test Results ==<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for one of the [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-nova openstack-nova], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-glance openstack-glance], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-keystone openstack-keystone], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-cinder openstack-cinder],[https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-quantum openstack-quantum], [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-swift openstack-swift] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-heat openstack-heat] or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=openstack-ceilometer openstack-ceilometer] components. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.<br />
<br />
Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.<br />
<br />
Basic setup:<br />
<br />
{|<br />
! User<br />
! openstack-demo-install<br />
! [[QA:Testcase_Create_Cinder_Volumes|Create Cinder Volumes]]<br />
! [[QA:Testcase_add_SSH_keypair_to_OpenStack|Add SSH keypair]]<br />
! [[QA:Testcase_register_images_with_OpenStack|Register images]]<br />
! [[QA:Testcase_create_OpenStack_nova_network|Create nova network]]<br />
! References<br />
<br />
|-<br />
| [[User:SampleUser|Sample User]]<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|pass}}<br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| <references/><br />
|-<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_launch_an_instance_on_OpenStack|Launch an instance]]<br />
! [[QA:Testcase_attach_a_cinder_volume_to_an_instance|Attach a volume]]<br />
! [[QA:Testcase_OpenStack_floating_IPs|Floating IPs]]<br />
! [[QA:Testcase_separate_OpenStack_compute_node|Separate compute node]]<br />
! References<br />
|-<br />
<br />
Core functionality:<br />
<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_Nova_Create_Builder_Instance | Create a builder instance]]<br />
! [[QA:Testcase_Nova_Create_Bootable_Volume | Create and boot from a bootable volume]]<br />
! [[QA:Testcase_Nova_Snapshot_Volume_Backed_Instance | Create an image from a running volume-backed instance]]<br />
! References<br />
|-<br />
<br />
Nova boot-from-volume:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_Quantum_V2#How_to_test | Configure and use a network topology in Quantum]]<br />
! References<br />
|-<br />
<br />
Quantum functionality:<br />
<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_Swift_Upload_Download_Files | Upload and download files]]<br />
! [[QA:Testcase_Swift_Upload_Large_File | Upload Segmented File]]<br />
! [[QA:Testcase_Swift_Auditor_Replicator | Test Auditor/Replicator]]<br />
! [[QA:Testcase_Swift_Add_Device | Add Storage Device to ring]]<br />
! References<br />
|-<br />
Swift functionality:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_OpenStack_dashboard_setup|Basic dashboard setup and login]]<br />
! [[QA:Testcase_OpenStack_dashboard_launch_instance|Launch/terminate an instance with the dashboard]]<br />
! [[QA:Testcase_OpenStack_dashboard_add_users|Managing projects and users with the dashboard]]<br />
! [[QA:Testcase_OpenStack_dashboard_vnc|VNC access to instances through the dashboard]]<br />
! References<br />
|-<br />
Dashboard functionality:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_OpenStack_heat_setup|Basic heat setup and login]]<br />
! [[QA:Testcase_OpenStack_heat_launch|Launch a basic wordpress stack]]<br />
! [[QA:Testcase_OpenStack_heat_stop|Stop Heat services and uninstall Heat]]<br />
! References<br />
|-<br />
<br />
|-<br />
heat functionality:<br />
<br />
{|<br />
! User<br />
! [[QA:Testcase_run_Tempest_tests|Tempest tests]]<br />
! [[QA:Testcase_build_an_OpenStack_guest_image_with_Oz|Build an image with Oz]]<br />
! [[QA:Testcase_run_the_OpenStack_smoke_tests|Smoke tests]]<br />
! References<br />
<br />
|-<br />
Extra credit:<br />
<br />
[[Category:Test Days]]<br />
[[Category:OpenStack]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=328557User:Kashyapc2013-03-29T02:13:44Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* A Red Hat test engineer, working on OpenStack and its underlying KVM based virt stack.<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* KVM based Virtualization testing<br />
** Notes: http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
* Presentations at conferences and simple virt related scripts <br />
** https://github.com/kashyapc<br />
* (Occasional) package maintenance<br />
* https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=328556User:Kashyapc2013-03-29T02:07:54Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* Senior Software Test Engineer at Red Hat, working on OpenStack and other KVM based virt components.<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* KVM based Virtualization testing<br />
** Notes: http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
* Presentations at conferences and simple virt related scripts <br />
** https://github.com/kashyapc<br />
* (Occasional) package maintenance<br />
* https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc</div>Kashyapchttps://fedoraproject.org/w/index.php?title=User:Kashyapc&diff=321990User:Kashyapc2013-02-03T13:49:16Z<p>Kashyapc: </p>
<hr />
<div>= Kashyap Chamarthy =<br />
<br />
<br />
[[Image: kashyap-chamarthy.JPG | right | thumb| Kashyap Chamarthy]]<br />
* Senior Software Test Engineer at Red Hat<br />
* '''Fedora Account''': kashyapc<br />
* '''Email''': [mailto:kashyapc@fedoraproject.org kashyapc@fedoraproject.org]<br />
* '''IRC''': kashyap<br />
* '''Website''': [http://kashyapc.wordpress.com/ blog]<br />
<br />
=== Activities ===<br />
* KVM based Virtualization testing<br />
** Notes: http://kashyapc.fedorapeople.org/virt/<br />
** http://kashyapc.wordpress.com/tag/virtualization<br />
* Presentations at conferences and simple virt related scripts <br />
** https://github.com/kashyapc<br />
* (Occasional) package maintenance<br />
* https://admin.fedoraproject.org/pkgdb/users/packages/kashyapc</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2012-11-01_Virtualization&diff=309439Test Day:2012-11-01 Virtualization2012-11-01T06:40:10Z<p>Kashyapc: /* Test Results */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_16_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2012-11-01<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 18. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 18.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use one of these formats:<br />
* Developer - [[User:<yourfedoracct>|<your name>]] (irc: <your nick>)<br />
* Tester - [[User:<yourfedoracct>|<your name>]] (irc: <your nick>)<br />
--><br />
* Developer - [[User:berrange|Daniel Berrange]] (irc: danpb)<br />
* Developer - [[User:rjones|Richard W.M. Jones]] (irc: rwmjones)<br />
* Developer - [[User:crobinso|Cole Robinson]] (irc: crobinso)<br />
* Developer - [[User:stefanha|Stefan Hajnoczi]] (irc: stefanha)<br />
* Developer - [[User:mrezanin|Miroslav Rezanina]] (irc: mrezanin)<br />
* Developer - [[User:ericb|Eric Blake]] (irc: eblake)<br />
* Developer - [[User:laine|Laine Stump]] (irc: laine)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* Pausing a KVM guest can crash that guest. Might be specific to guests using a QXL video device (the default created by virt-manager): [https://bugzilla.redhat.com/show_bug.cgi?id=870811 bug 870811]<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: [https://bugzilla.redhat.com/show_bug.cgi?id=855162 bug 855162]<br />
* some graphical corruption if using cirrus virtual card for guests: [https://bugzilla.redhat.com/show_bug.cgi?id=871247 bug 871247]<br />
* virt-manager will backtrace trying to show guests in the 'suspended' state [https://bugzilla.redhat.com/show_bug.cgi?id=871237 bug 871237]<br />
* Closing a graphical window triggers a guest resume [https://bugzilla.redhat.com/show_bug.cgi?id=871240 bug 871240]<br />
* ctrl-alt-f2,3,4 don't have effect in guests (unless xserver is restarted): [https://bugzilla.redhat.com/show_bug.cgi?id=871241 bug 871241]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
As for getting the latest virt packages, you have a few options:<br />
<br />
=== Fedora 18 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 18 machine. You have a few options for getting the Fedora 18 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 17<br />
** The supported way is using CD/DVD upgrade. See media links above<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Fedora 18 virt packages on Fedora 17 ===<br />
<br />
If you aren't ready to make the jump to Fedora 18, this is the next best thing! Run latest virt packages on Fedora 17 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
=== Run Fedora 18 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 18 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 18 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
== Some notes on nested virt with AMD and Intel ==<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
== Areas to test ==<br />
<br />
=== '''VM Install''' ===<br />
<br />
Record your results for these test cases in the '''[[#Test Results |Test Results]]''' section.<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization URL Guest Install]]<br />
* [[QA:Testcase Virtualization CDROM Guest Install]]<br />
<br />
Next give this a run through, which should ensure things aren't broken in some obvious manner:<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle]]<br />
<br />
=== '''New tests and features''' ===<br />
<br />
Record your results for these test cases in the '''[[#Test Results|Test Results]]''' section.<br />
<br />
* [[QA:Testcase Virtualization Live Backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing]]<br />
* [[QA:Testcase Virtualization IO Throttling]]<br />
* [[QA:Testcase Virtualization PV EOI]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough]]<br />
* [[QA:Testcase Virtualization USB Redirection]]<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 18 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs:<br />
<br />
# yum install '*guestf*'<br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
In Fedora 18, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure]. Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions!<br />
<br />
Migration:<br />
<br />
* [[QA:Testcase Live Migration using libvirt/virsh]]<br />
* [[QA:Testcase Offline (paused) Migration using libvirt/virsh]]<br />
<br />
Hotplug:<br />
<br />
* [[QA:Testcase Virtualization Attach/Detach a SCSI device to guest]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest]]<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach]]<br />
<br />
virtio-scsi:<br />
<br />
* [[QA:Testcase Virtualization Virtio SCSI Install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug]]<br />
<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! [[QA:Testcase Virtualization Live Backup|Live Backup]]<br />
! [[QA:Testcase Virtualization Guest Suspend Hibernate|Suspend]]<br />
! [[QA:Testcase Virtualization Seccomp Sandboxing|Seccomp]]<br />
! [[QA:Testcase Virtualization IO Throttling|IO Throttling]]<br />
! [[QA:Testcase Virtualization PV EOI|PV EOI]]<br />
! [[QA:Testcase Virtualization USB3 Device Passthrough|USB3]]<br />
! [[QA:Testcase Virtualization USB Redirection|USB Redir]]<br />
! References<br />
|-<br />
<br />
<br />
<!-- Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
| [[User:crobinso|crobinso]]<br />
| {{result|inprogress}}<br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|fail}} <ref>Guest fails to start {{bz|855162}}</ref><br />
| {{result|pass}} <br />
| {{result|pass}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| <references/><br />
|-<br />
<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| <references/><br />
|-<br />
<br />
|}<br />
<br />
[[Category:Fedora 18 Test Days]]<br />
[[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2012-11-01_Virtualization&diff=309438Test Day:2012-11-01 Virtualization2012-11-01T06:39:04Z<p>Kashyapc: /* Run Fedora 18 in a VM with nested virtualization */</p>
<hr />
<div>{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_16_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2012-11-01<br />
| time = all day<br />
| website = [[Virtualization]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = virt}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
<br />
== What to test? ==<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] in Fedora 18. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 18.<br />
<br />
== Who's available ==<br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
<!--<br />
Use one of these formats:<br />
* Developer - [[User:<yourfedoracct>|<your name>]] (irc: <your nick>)<br />
* Tester - [[User:<yourfedoracct>|<your name>]] (irc: <your nick>)<br />
--><br />
* Developer - [[User:berrange|Daniel Berrange]] (irc: danpb)<br />
* Developer - [[User:rjones|Richard W.M. Jones]] (irc: rwmjones)<br />
* Developer - [[User:crobinso|Cole Robinson]] (irc: crobinso)<br />
* Developer - [[User:stefanha|Stefan Hajnoczi]] (irc: stefanha)<br />
* Developer - [[User:mrezanin|Miroslav Rezanina]] (irc: mrezanin)<br />
* Developer - [[User:ericb|Eric Blake]] (irc: eblake)<br />
* Developer - [[User:laine|Laine Stump]] (irc: laine)<br />
<br />
== Known issues ==<br />
<br />
Before you begin testing, there are a few known bugs that should be taken into account:<br />
<br />
* Pausing a KVM guest can crash that guest. Might be specific to guests using a QXL video device (the default created by virt-manager): [https://bugzilla.redhat.com/show_bug.cgi?id=870811 bug 870811]<br />
* running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: [https://bugzilla.redhat.com/show_bug.cgi?id=811967 bug 811967]<br />
* qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: [https://bugzilla.redhat.com/show_bug.cgi?id=855162 bug 855162]<br />
* some graphical corruption if using cirrus virtual card for guests: [https://bugzilla.redhat.com/show_bug.cgi?id=871247 bug 871247]<br />
* virt-manager will backtrace trying to show guests in the 'suspended' state [https://bugzilla.redhat.com/show_bug.cgi?id=871237 bug 871237]<br />
* Closing a graphical window triggers a guest resume [https://bugzilla.redhat.com/show_bug.cgi?id=871240 bug 871240]<br />
* ctrl-alt-f2,3,4 don't have effect in guests (unless xserver is restarted): [https://bugzilla.redhat.com/show_bug.cgi?id=871241 bug 871241]<br />
<br />
== What's needed to test ==<br />
<br />
For starters, your physical machine should have:<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* Get the packages with <br><pre>yum groupinstall virtualization</pre><br />
<br />
As for getting the latest virt packages, you have a few options:<br />
<br />
=== Fedora 18 on a physical machine ===<br />
<br />
The preferred testing platform is a fully updated Fedora 18 machine. You have a few options for getting the Fedora 18 bits:<br />
<br />
* Install with CD/DVD.<br />
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/<br />
** Latest 64 Bit DVD: http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/Fedora/x86_64/iso/<br />
<br />
* Upgrade from Fedora 17<br />
** The supported way is using CD/DVD upgrade. See media links above<br />
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum <br>This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!<br />
<br />
=== Fedora 18 virt packages on Fedora 17 ===<br />
<br />
If you aren't ready to make the jump to Fedora 18, this is the next best thing! Run latest virt packages on Fedora 17 from the virt-preview repo:<br />
<br />
http://fedoraproject.org/wiki/Virtualization_Preview_Repository<br />
<br />
=== Run Fedora 18 in a VM with nested virtualization ===<br />
<br />
Do you have a new machine with a ton of ram and storage space, running Fedora 17? Nested virt might be an option!<br />
This allows you to create KVM guests _inside_ a Fedora 18 VM.<br />
<br />
# Install the latest virt packages from virt-preview using the instructions above.<br />
# Install a Fedora 18 guest using one of the test cases below.<br />
# Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root: <br><pre>virt-host-validate</pre><br />
<br />
== Some notes on nested virt with AMD and Intel ==<br />
<br />
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/<br />
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/<br />
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/<br />
<br />
== Areas to test ==<br />
<br />
=== '''VM Install''' ===<br />
<br />
Record your results for these test cases in the '''[[#Test Results |Test Results]]''' section.<br />
<br />
If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!<br />
<br />
* [[QA:Testcase Virtualization URL Guest Install]]<br />
* [[QA:Testcase Virtualization CDROM Guest Install]]<br />
<br />
Next give this a run through, which should ensure things aren't broken in some obvious manner:<br />
<br />
* [[QA:Testcase Virtualization Virt Manager Lifecycle]]<br />
<br />
=== '''New tests and features''' ===<br />
<br />
Record your results for these test cases in the '''[[#Test Results|Test Results]]''' section.<br />
<br />
* [[QA:Testcase Virtualization Live Backup]]<br />
* [[QA:Testcase Virtualization Guest Suspend Hibernate]]<br />
* [[QA:Testcase Virtualization Seccomp Sandboxing]]<br />
* [[QA:Testcase Virtualization IO Throttling]]<br />
* [[QA:Testcase Virtualization PV EOI]]<br />
* [[QA:Testcase Virtualization USB3 Device Passthrough]]<br />
* [[QA:Testcase Virtualization USB Redirection]]<br />
<br />
=== libguestfs and tools ===<br />
<br />
You will need Fedora 18 (host) and at least one guest (but the more the merrier).<br />
<br />
Install libguestfs:<br />
<br />
# yum install '*guestf*'<br />
<br />
and run through the tests here: http://libguestfs.org/guestfs-testing.1.html<br />
<br />
In Fedora 18, we are using [http://libvirt.org libvirt] to launch the appliance, and [http://selinuxproject.org/page/SVirt sVirt] + SELinux to make everything [http://libguestfs.org/guestfs.3.html#security much more secure]. Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.<br />
<br />
=== Previous test cases ===<br />
<br />
Some test cases used in previous test days. Still useful to test for regressions!<br />
<br />
Migration:<br />
<br />
* [[QA:Testcase Live Migration using libvirt/virsh]]<br />
* [[QA:Testcase Offline (paused) Migration using libvirt/virsh]]<br />
<br />
Hotplug:<br />
<br />
* [[QA:Testcase Virtualization Attach/Detach a SCSI device to guest]]<br />
* [[QA:Testcase Virtualization Hotplug USB device to guest]]<br />
* [[QA:Testcase Virtualization NIC Hotplug virsh attach detach]]<br />
<br />
virtio-scsi:<br />
<br />
* [[QA:Testcase Virtualization Virtio SCSI Install]]<br />
* [[QA:Testcase Virtualization Virtio SCSI Hotplug]]<br />
<br />
<br />
== Test Results ==<br />
<br />
Each tester should add a row for their results.<br />
<br />
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla]. If you have any questions about what component to file against,<br />
just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!<br />
<br />
<!-- Don't touch this part! --><br />
{|<br />
! User<br />
! VM Install<br />
! [[QA:Testcase Virtualization Virt Manager Lifecycle|VM Lifecycle]]<br />
! [[QA:Testcase Virtualization Live Backup|Live Backup]]<br />
! [[QA:Testcase Virtualization Guest Suspend Hibernate|Suspend]]<br />
! [[QA:Testcase Virtualization Seccomp Sandboxing|Seccomp]]<br />
! [[QA:Testcase Virtualization IO Throttling|IO Throttling]]<br />
! [[QA:Testcase Virtualization PV EOI|PV EOI]]<br />
! [[QA:Testcase Virtualization USB3 Device Passthrough|USB3]]<br />
! [[QA:Testcase Virtualization USB Redirection|USB Redir]]<br />
! References<br />
|-<br />
<br />
<br />
<!-- Copy the block below as a template<br />
<br />
| [[User:SampleUser|SampleUser]]<br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| <references/><br />
|-<br />
<br />
--><br />
<br />
| [[User:crobinso|crobinso]]<br />
| {{result|inprogress}}<br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|inprogress}} <br />
| {{result|fail}} <ref>Guest fails to start {{bz|855162}}</ref><br />
| {{result|pass}} <br />
| {{result|pass}}<br />
| {{result|inprogress}}<br />
| {{result|inprogress}}<br />
| <references/><br />
|-<br />
<br />
<br />
|}<br />
<br />
[[Category:Fedora 18 Test Days]]<br />
[[Category:Virtualization]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Features/Virt_Live_Snapshots&diff=308364Features/Virt Live Snapshots2012-10-23T18:33:14Z<p>Kashyapc: /* Testing Live Blockcommit */</p>
<hr />
<div><!-- All fields on this form are required to be accepted by FESCo.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
= Virt Live Snapshots =<br />
<br />
== Summary ==<br />
<br />
Live snapshots allow a user to take a snapshot of a virtual machine while the guest is running, thus preserving the state and data of a VM at a specific point in time. <br />
<br />
== Owner ==<br />
* Name: [[User:crobinso| Cole Robinson]]<br />
* Email: crobinso@redhat.com<br />
* Name: Jeff Cody<br />
* Email: jtc@redhat.com<br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/18 | Fedora 18]]<br />
* Last updated: June 6 2012<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --><br />
<br />
QEMU has had snapshotting capabilities for a long time, but they have always required the guest to be paused/stopped for a short period of time while the storage was snapshoted. Live snapshots allow for qemu and libvirt to snapshot a the guest's storage with no downtime. This even works on guests with 'raw' disk images: libvirt will snapshot using an external qcow2 file, and transparently switch the guest over to running off the new external image.<br />
<br />
== Benefit to Fedora ==<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--><br />
* Snapshots can be performed on guests using any storage configuration (utilizing external qcow2 snapshots)<br />
* No downtime during the snapshotting process.<br />
<br />
== Scope ==<br />
* Live snapshot support in qemu (DONE, 1.1 is in rawhide/f18)<br />
* Live snapshot support in qemu-ga (DONE)<br />
* Live snapshot support in libvirt (DONE, but checkpointing usecase is still lacking)<br />
* Apps (all optional but would be nice if they are done)<br />
** Snapshot support in ovirt? (available, used for live backup)<br />
** Snapshot support in virt-manager? (not done, not a requirement)<br />
** Snapshot support in boxes? (out of scope)<br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this feature? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the feature is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
=== Live backup ===<br />
<br />
You can backup the storage of a VM from the host machine with no VM downtime.<br />
<br />
Snapshot the VM:<br />
<br />
virsh snapshot-create-as myvm snapshot1 "snapshot1 description" --disk-only --atomic<br />
<br />
Backup the original storage using your regular backup method.<br />
<br />
Merge the disk changes that accumulated in the snapshot back with the original disk. --path is the disk device (such as <code>vda</code>) or path to the current disk image, just created by the snapshot command (in this example, <code>/var/lib/libvirt/images/myvm.snapshot1</code>).<br />
<br />
virsh blockpull --domain myvm --path /var/lib/libvirt/images/myvm.snapshot1<br />
<br />
'blockpull' needs to be done for every disk image that was snapshotted. You can optionally supply a --base argument to blockpull, if it is desired to keep a common backing file while still collapsing the rest of a longer backing chain.<br />
<br />
=== VM checkpointing ===<br />
<br />
The below commands are not fully implemented in libvirt yet.<br />
<br />
Any guest KVM guest can be snapshotted using external snapshot files. Simplest way:<br />
<br />
virsh snapshot-create-as myvm snapshot1 "snapshot1 description" --disk-only --atomic<br />
virsh snapshot-create-as myvm snapshot2 "snapshot2 description" --disk-only --atomic<br />
<br />
You make some changes and want to switch back to an older snapshot state, you do:<br />
<br />
virsh snapshot-revert myvm snapshot1<br />
<br />
XXX: however this doesn't work right now: 'revert to external disk snapshot not supported yet'<br />
<br />
If you want to delete a snapshot, use:<br />
<br />
virsh snapshot-delete myvm snapshot2<br />
<br />
XXX: also doesn't work: 'deletion of 1 external disk snapshots not supported yet'<br />
<br />
If the guest has qemu-ga installed and configured, passing --quiesce to snapshot-create-as will make sure the guest's filesystems are frozen for extra safety.<br />
<br />
--atomic should ensure all disks are snapshotted atomically<br />
<br />
=== Testing Live Blockcommit ===<br />
http://kashyapc.fedorapeople.org/virt/blockcommit/recursive-blockcommit-base-raw.txt<br />
<br />
(Side note: The "./qemu-img info --backing-chain " is with a patch available only via upstream qemu. Which will be available in QEMU-1.3)<br />
<br />
== User Experience ==<br />
Virtualization users will have a more production ready mechanism for snapshotting than QEMU previously supported (no loss of uptime). Exposing snapshotting in tools like ovirt and/or virt-manager will essentially be a new and compelling feature for those users.<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
Since this is brand new functionality, if it doesn't make it in time for F18, nothing has changed. We just drop this feature page.<br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
* http://wiki.qemu.org/Features/Snapshots<br />
* http://wiki.qemu.org/Features/SnapshotsMultipleDevices<br />
* http://wiki.libvirt.org/page/Snapshots<br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --><br />
* KVM and libvirt now support storage snapshotting of live guests with no downtime.<br />
<br />
== Comments and Discussion ==<br />
* See [[Talk:Features/Virt_Live_Snapshots]]<br />
<br />
<br />
[[Category:FeatureAcceptedF18]]<br />
<!-- When your feature page is completed and ready for review --><br />
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --><br />
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--><br />
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --></div>Kashyapchttps://fedoraproject.org/w/index.php?title=Features/Virt_Live_Snapshots&diff=308363Features/Virt Live Snapshots2012-10-23T18:32:18Z<p>Kashyapc: </p>
<hr />
<div><!-- All fields on this form are required to be accepted by FESCo.<br />
We also request that you maintain the same order of sections so that all of the feature pages are uniform. --><br />
<br />
= Virt Live Snapshots =<br />
<br />
== Summary ==<br />
<br />
Live snapshots allow a user to take a snapshot of a virtual machine while the guest is running, thus preserving the state and data of a VM at a specific point in time. <br />
<br />
== Owner ==<br />
* Name: [[User:crobinso| Cole Robinson]]<br />
* Email: crobinso@redhat.com<br />
* Name: Jeff Cody<br />
* Email: jtc@redhat.com<br />
<br />
== Current status ==<br />
* Targeted release: [[Releases/18 | Fedora 18]]<br />
* Last updated: June 6 2012<br />
* Percentage of completion: 100%<br />
<br />
== Detailed Description ==<br />
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --><br />
<br />
QEMU has had snapshotting capabilities for a long time, but they have always required the guest to be paused/stopped for a short period of time while the storage was snapshoted. Live snapshots allow for qemu and libvirt to snapshot a the guest's storage with no downtime. This even works on guests with 'raw' disk images: libvirt will snapshot using an external qcow2 file, and transparently switch the guest over to running off the new external image.<br />
<br />
== Benefit to Fedora ==<br />
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--><br />
* Snapshots can be performed on guests using any storage configuration (utilizing external qcow2 snapshots)<br />
* No downtime during the snapshotting process.<br />
<br />
== Scope ==<br />
* Live snapshot support in qemu (DONE, 1.1 is in rawhide/f18)<br />
* Live snapshot support in qemu-ga (DONE)<br />
* Live snapshot support in libvirt (DONE, but checkpointing usecase is still lacking)<br />
* Apps (all optional but would be nice if they are done)<br />
** Snapshot support in ovirt? (available, used for live backup)<br />
** Snapshot support in virt-manager? (not done, not a requirement)<br />
** Snapshot support in boxes? (out of scope)<br />
<br />
== How To Test ==<br />
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. <br />
<br />
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.<br />
<br />
A good "how to test" should answer these four questions:<br />
<br />
0. What special hardware / data / etc. is needed (if any)?<br />
1. How do I prepare my system to test this feature? What packages<br />
need to be installed, config files edited, etc.?<br />
2. What specific actions do I perform to check that the feature is<br />
working like it's supposed to?<br />
3. What are the expected results of those actions?<br />
--><br />
<br />
=== Live backup ===<br />
<br />
You can backup the storage of a VM from the host machine with no VM downtime.<br />
<br />
Snapshot the VM:<br />
<br />
virsh snapshot-create-as myvm snapshot1 "snapshot1 description" --disk-only --atomic<br />
<br />
Backup the original storage using your regular backup method.<br />
<br />
Merge the disk changes that accumulated in the snapshot back with the original disk. --path is the disk device (such as <code>vda</code>) or path to the current disk image, just created by the snapshot command (in this example, <code>/var/lib/libvirt/images/myvm.snapshot1</code>).<br />
<br />
virsh blockpull --domain myvm --path /var/lib/libvirt/images/myvm.snapshot1<br />
<br />
'blockpull' needs to be done for every disk image that was snapshotted. You can optionally supply a --base argument to blockpull, if it is desired to keep a common backing file while still collapsing the rest of a longer backing chain.<br />
<br />
=== VM checkpointing ===<br />
<br />
The below commands are not fully implemented in libvirt yet.<br />
<br />
Any guest KVM guest can be snapshotted using external snapshot files. Simplest way:<br />
<br />
virsh snapshot-create-as myvm snapshot1 "snapshot1 description" --disk-only --atomic<br />
virsh snapshot-create-as myvm snapshot2 "snapshot2 description" --disk-only --atomic<br />
<br />
You make some changes and want to switch back to an older snapshot state, you do:<br />
<br />
virsh snapshot-revert myvm snapshot1<br />
<br />
XXX: however this doesn't work right now: 'revert to external disk snapshot not supported yet'<br />
<br />
If you want to delete a snapshot, use:<br />
<br />
virsh snapshot-delete myvm snapshot2<br />
<br />
XXX: also doesn't work: 'deletion of 1 external disk snapshots not supported yet'<br />
<br />
If the guest has qemu-ga installed and configured, passing --quiesce to snapshot-create-as will make sure the guest's filesystems are frozen for extra safety.<br />
<br />
--atomic should ensure all disks are snapshotted atomically<br />
<br />
== Testing Live Blockcommit ==<br />
http://kashyapc.fedorapeople.org/virt/blockcommit/recursive-blockcommit-base-raw.txt<br />
<br />
(Side note: The "./qemu-img info --backing-chain " is with a patch available only via upstream qemu. Which will be available in QEMU-1.3)<br />
<br />
== User Experience ==<br />
Virtualization users will have a more production ready mechanism for snapshotting than QEMU previously supported (no loss of uptime). Exposing snapshotting in tools like ovirt and/or virt-manager will essentially be a new and compelling feature for those users.<br />
<br />
== Dependencies ==<br />
None<br />
<br />
== Contingency Plan ==<br />
Since this is brand new functionality, if it doesn't make it in time for F18, nothing has changed. We just drop this feature page.<br />
<br />
== Documentation ==<br />
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --><br />
* http://wiki.qemu.org/Features/Snapshots<br />
* http://wiki.qemu.org/Features/SnapshotsMultipleDevices<br />
* http://wiki.libvirt.org/page/Snapshots<br />
<br />
== Release Notes ==<br />
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --><br />
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --><br />
* KVM and libvirt now support storage snapshotting of live guests with no downtime.<br />
<br />
== Comments and Discussion ==<br />
* See [[Talk:Features/Virt_Live_Snapshots]]<br />
<br />
<br />
[[Category:FeatureAcceptedF18]]<br />
<!-- When your feature page is completed and ready for review --><br />
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --><br />
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--><br />
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --></div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS-Results&diff=284209Test Day:2012-04-12 Virtualization Test Day-GuestOS-Results2012-04-12T05:02:01Z<p>Kashyapc: /* Fedora */</p>
<hr />
<div>= Guest OS Support Results =<br />
<br />
This page provides the results of testing guest operating systems on a Fedora 17 KVM host.<br />
<br />
There are 4 test cases to be evaluated against each guest OS:<br />
<br />
* [[Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS#Test_case_1:_ISO_media_detection | Test case 1: ISO media detection]] - whether osinfo-detect can find info for the ISO install media<br />
* [[Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS#Test_case_2:_Installation | Test case 2: Installation]] - verify that the installer runs to completion without unexpected problems<br />
* [[Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS#Test_case_3:_Post-install_first_boot | Test case 3: Post-install first boot]] - verify the resulting installed image can successfully boot up again<br />
* [[Test_Day:2012-04-12_Virtualization_Test_Day-GuestOS#Test_case_4:_Disk_image_inspection | Test case 4: Disk image inspection]] - whether virt-inspect can find info for the resulting installed OS disk image<br />
<br />
== Fedora ==<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media detect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 17<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:kashyapc|Kashyap Chamarthy]]<br />
| 17<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 16<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 16<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 15<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 15<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<!--<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| <br />
| <br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
--><br />
|}<br />
<br />
== RHEL ==<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media detect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| RHEL-6.2<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| RHEL-6.2<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| RHEL-5.8<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| RHEL-5.8<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| RHEL-4.9<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| RHEL-4.9<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<!--<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| <br />
| <br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
--><br />
|}<br />
<br />
<br />
== Ubuntu ==<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media detect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| Oneiric (11.10)<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| Oneiric (11.10)<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| Natty (11.04)<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| Natty (11.04)<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| Maverick (10.10)<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| Maverick (10.10)<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<!--<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| <br />
| <br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
--><br />
|}<br />
<br />
<br />
== FreeBSD ==<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media detect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 9.0<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 9.0<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 8.2<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 8.2<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 8.1<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 8.1<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 8.0<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 8.0<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.4<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.3<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.3<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.2<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.2<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.4<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.1<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.1<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.0<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 7.0<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<!--<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| <br />
| <br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
--><br />
|}<br />
<br />
<br />
== Windows ==<br />
<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media detect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| 2k<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| 2k3<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k3<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k3<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| 2k3r2<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k3r2<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k3r2<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| 2k8<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| {{result|pass}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k8<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k8<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k8r2<br />
| i686<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k8r2<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 2k8r2<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| XP<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| XP<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| XP<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| Vista<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| Vista<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| Vista<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:Berrange|Daniel Berrange]]<br />
| 7<br />
| i686<br />
| i686<br />
| {{result|pass}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 7<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| <!--[[User:FASName|Your Name]]--><br />
| 7<br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
|}<br />
<br />
== Other distro ==<br />
<br />
Create a copy of this section, for any other OS distros you want to submit results for. Yes, even for MS-Dos if you want to. Knowledge is power!<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media detect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| <!--[[User:SampleUser|Sample User]]--><br />
| 9.0<br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
|}<br />
<!--<br />
=== Distro Name ===<br />
<br />
{|<br />
<br />
! User<br />
! OS Release<br />
! Host Arch<br />
! Guest Arch<br />
! 1: ISO media inspect<br />
! 2: Installation<br />
! 3: Post-install first boot<br />
! 4: Disk image inspect<br />
! Notes<br />
|-<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| x86_64<br />
| i686<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| x86_64<br />
| x86_64<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
| [[User:SampleUser|Sample User]]<br />
| <br />
| <br />
| <br />
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref><br />
| {{result|fail}} <ref>{{bz|12345}}</ref><br />
| {{result|none}}<br />
| {{result|none}}<br />
| <references/><br />
|-<br />
<br />
|}<br />
<br />
--></div>Kashyapchttps://fedoraproject.org/w/index.php?title=Test_Day:2012-04-12_Virtualization_Test_Day&diff=281862Test Day:2012-04-12 Virtualization Test Day2012-04-03T09:01:55Z<p>Kashyapc: /* Virtualization Test Day */</p>
<hr />
<div>= Virtualization Test Day =<br />
<br />
{{Infobox_group<br />
| name = Fedora Test Days<br />
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_16_test_days]]<br />
| caption = Virtualization Test Day<br />
| date = 2012-04-12<br />
| time = all day<br />
| website = [[QA/Fedora_17_test_days]]<br />
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])<br />
| fedora_mailing_list = virt<br />
}}<br />
<br />
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}<br />
<br />
=== What to test? ===<br />
<br />
Today's installment of Fedora Test Day will focus on [[Virtualization]] improvements in Fedora 17. There is a '''large''' list of virtualization improvements coming in Fedora. To simplify things, testing will be divided up into a number of sections.<br />
<br />
=== Who's available === <br />
<br />
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...<br />
* Development / general help - [[User:berrange|Daniel Berrange (danpb on FreeNode)]]<br />
* Development / general help - [[User:rjones|Richard W.M. Jones]] (rwmjones on FreeNode)<br />
<br />
== What's needed to test ==<br />
* A fully updated Fedora 17 Beta machine. See instructions below.<br />
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F Is My Guest Using KVM?]]). If unavailable, you can still help with testing QEMU support.<br />
* At least one guest image installed before the test day (suggested reading - [[Virtualization_Quick_Start]])<br />
* Up to 10-20Gb free disk space. Guest images take up a lot of space.<br />
* See the individual test area pages for specific requirements.<br />
** The below are the some of the virt features accepted for F17 :<br />
*** http://fedoraproject.org/wiki/Features/KVM_Live_Block_Migration<br />
*** https://fedoraproject.org/wiki/Features/KVM_Guest_PMU<br />
*** https://fedoraproject.org/wiki/Features/virtio-scsi<br />
*** https://fedoraproject.org/wiki/Features/Open_vSwitch<br />
*** https://fedoraproject.org/wiki/Features/KVMThinProv<br />
*** http://fedoraproject.org/wiki/Features/VirtSandbox</div>Kashyapchttps://fedoraproject.org/w/index.php?title=FOSDEM_2012_Attendees&diff=267829FOSDEM 2012 Attendees2012-01-20T04:25:21Z<p>Kashyapc: /* Attendees and Visitors */</p>
<hr />
<div>== About ==<br />
<br />
In the past years there were always many people been listed as attendees. This is the first years time we split that list because the event owner needs to know who will be at the booth. If you want the work at the booth, please add your name to [[FOSDEM_2012_Booth_Attendance| Booth personal list]]. Don't forget to add your information to the [[FOSDEM_2012_Accommodation|Accommodation]] page.<br />
<br />
== Attendees and Visitors ==<br />
<br />
{|<br />
! # !! Name!! Friday !! Saturday !! Sunday !! Comments !! Languages<br />
|-<br />
|| 1 || [[User:biertie | Bert Desmet]] || {{check}} || {{check}} || {{check}} || Event owner || EN, NL, (FR)<br />
|-<br />
|| 2 || [[User:any0n3 | Michael Spahn]] || {{check}} || {{check}} || {{check}} || Attendee || DE, EN, (FR)<br />
|-<br />
|| 3 || [[User:ilyes | Ilyes Gouta]] || {{check}} || {{check}} || {{check}} || Attendee || TN, EN, FR<br />
|-<br />
|| 4 || [[User:comzeradd | Nikos Roussos]] || {{check}} || {{check}} || {{check}} || Attendee || EN, GR<br />
|-<br />
|| 5 || [[User:spot| Tom Callaway]] || {{check}} || {{check}} || {{check}} || Attendee || EN, C, Python<br />
|-<br />
|| 5 || [[User:pingou| Pierre-Yves Chibon]] || {{check}} || {{check}} || {{check}} || Attendee || EN, FR, Python<br />
|-<br />
|| 6 || [[User:cwickert| Christoph Wickert]] || {{check}} || {{check}} || {{check}} || Attendee || EN, DE<br />
|-<br />
|| 7 || [[User:geroldka| Gerold Kassube]] || {{check}} || {{check}} || {{check}} || Attendee || EN, DE <br />
|-<br />
|| 8 || [[User:shaiton| Kévin Raymond]] || {{check}} || {{check}} || {{check}} || Attendee || EN, FR<br />
|-<br />
|| 9 || [[User:thl| Thorsten Leemhuis]] || {{check}} || {{check}} || {{check}} || Attendee || EN, DE<br />
|-<br />
|| 9 || [[User:schendje| Jef van Schendel]] || {{check}} || {{check}} || {{check}} || Attendee || EN, NL<br />
|-<br />
|| 10 || [[User:jreznik| Jaroslav Reznik]] || {{caution}} || {{check}} || {{check}} || Attendee but can help on booth too || EN, CZ, ES<br />
|-<br />
|| 11 || [[User:gbraad| Gerard Braad]] || {{note}} || {{check}} || {{check}} || Attendee || EN, NL, CN<br />
|-<br />
|| 12 || [[User:akurtakov| Alexander Kurtakov]] || {{check}} || {{check}} || {{check}} || Attendee || EN, BG<br />
|-<br />
|| 13 || [[User:asrob| Peter Borsa]] || {{check}} || {{check}} || {{check}} || Attendee || EN, HU<br />
|-<br />
|| 14 || [[User:zoltanh721| Zoltan Hoppar]] || {{check}} || {{check}} || {{check}} || Attendee || EN, DE, HU<br />
|-<br />
|| 15 || [[User:rgeri77| Gergely Rakosi]] || {{check}} || {{check}} || {{check}} || Attendee || EN, HU<br />
|-<br />
|| 16 || [[User:fcrippa| Francesco Crippa]] || {{caution}} || {{check}} || {{check}} || Attendee || EN, IT<br />
|-<br />
|| 17 || [[User:kashyapc| Kashyap Chamarthy]] || {{check}} || {{check}} || {{check}} || Attendee || EN<br />
|-<br />
! # !! Name!! Friday !! Saturday !! Sunday !! Comments !! Languages<br />
|}<br />
<br />
{{check}} : Present<br />
{{caution}} : Absentee<br />
{{note}} : No idea yet<br />
<br />
<br />
[[Category:Events]] [[Category:FOSDEM]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=Fosdem_2012_Super_Bowl&diff=266542Fosdem 2012 Super Bowl2012-01-12T09:15:47Z<p>Kashyapc: </p>
<hr />
<div>Only 10 people can enjoy the super bowl at the american sports bar in brussels. <br />
So, the first 10 to subscribe get an entrance ticket. <br />
I'm sorry I couldn't get more tickets. <br />
<br />
The event is close to the hotel, in [http://www.fatboys-be.com fatboys].<br />
<br />
== list of attendees ==<br />
<br />
# [[User:biertie | Bert Desmet]]<br />
# [[User:Th0br0 | Andreas Osowski]]<br />
# [[User:spot | Tom Callaway]]<br />
# [[User:kashyapc | Kashyap Chamarthy]]<br />
#<br />
#<br />
#<br />
#<br />
#<br />
#<br />
---- Reserve<br />
#<br />
#<br />
#<br />
<br />
[[Category:Marketing]] [[Category:Events]] [[Category:FOSDEM]] [[Category:Events 2012]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=FOSDEM_2012_Accommodation&diff=264056FOSDEM 2012 Accommodation2011-12-21T09:15:24Z<p>Kashyapc: </p>
<hr />
<div>== About ==<br />
This page is related to FOSDEM 2012 Accomodation.<br />
<br />
{{note}} : For more details about the event in itself, please go to ''' [[FOSDEM 2012 | Fedora Events: FOSDEM 2012 in Brussels, Belgium ]] ''' related wiki page.<br />
<br />
If you have already made arrangements for a hotel at FOSDEM 2012, please list that information here:<br />
<br />
{|<br />
! Name !! Arrival !! Departure !! Roommate? !! Where?<br />
|-<br />
|| [[User:biertie|Bert Desmet]] || 04/02/2011 || 06/02/2011 || Yes please || [http://www.hotelthemoon.com/ Hotel Moon]<br />
|-<br />
|| [[User:zoltanh721|Zoltan Hoppar]] || 03/02/2011 || 07/02/2011 || Yes please || [http://www.hotelthemoon.com/ Hotel Moon]<br />
|-<br />
|| [[User:Pingou|Pierre-Yves Chibon]] || 03/02/2012 || 05/02/2012 || [[User:Shaiton|Kévin Raymond]] || [http://www.marriott.com/hotels/travel/brubr-renaissance-brussels-hotel/ Renaissance Brussels]<br />
|-<br />
|| [[User:Shaiton|Kévin Raymond]] || 03/02/2012 || 05/02/2012 || [[User:Pingou|Pierre-Yves Chibon]] || [http://www.marriott.com/hotels/travel/brubr-renaissance-brussels-hotel/ Renaissance Brussels]<br />
|-<br />
|| [[User:Kashyapc|Kashyap Chamarthy]] || 02/02/2011 || 09/02/2011 ||No, thanks || [http://www.marriott.com/hotels/travel/brubr-renaissance-brussels-hotel/ Renaissance Brussels]<br />
|-<br />
|| [[User:spot|Tom Callaway]] || 03/02/2012 || 07/02/2012 || Not at this time. || [http://www.marriott.com/hotels/travel/brubr-renaissance-brussels-hotel/ Renaissance Brussels]<br />
|-<br />
|| [[User:Cwickert|Christoph Wickert]] || 03/02/2012 || 06/02/2012 || Sure, but I'll be with the Xfce guys || TBD<br />
|-<br />
! Name !! Arrival !! Departure !! Roommate? !! Where?<br />
|}<br />
<br />
[[Category:Events]] [[Category:FOSDEM]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=JBossAS7&diff=263426JBossAS72011-12-14T15:18:16Z<p>Kashyapc: /* Current progress */</p>
<hr />
<div>This wiki page shows the progress of including JBoss AS 7.<br />
<br />
== People involved ==<br />
<br />
Below is the list of currently involved people in the process.<br />
<br />
{|<br />
!Name<br />
!IRC<br />
!Current work<br />
!Additional info<br />
|-<br />
|[[User:Goldmann|Marek Goldmann]]<br />
|mgoldmann<br />
|Doing the dirty work of preparing jars to be packaged. See [[JBossAS7#Current_approach|Current approach]] section for more info.<br />
|UTC+2<br />
|-<br />
|[[User:vakwetu|Ade Lee]]<br />
|alee<br />
|Packaging parts of RESTeasy (and whatever is required to do so).<br />
|UTC-5<br />
|-<br />
|}<br />
<br />
== Current approach ==<br />
<br />
The idea is to '''package minimal set of JAR's'''. This means that only core JARs required to run or build AS7 will be packaged. This will let us package AS7 in reasonable timeframe. All additional JARs can be added later, for example to improve/enable test execution.<br />
<br />
I am ([[User:Goldmann|Marek Goldmann]]) now using following approach to select what needs to be packaged and what not:<br />
<br />
* Create a spec file.<br />
* Try to build the package.<br />
** Failure - see what what was the cause and:<br />
*** Missing dependency? Comment it out and build.<br />
**** Success - cool!<br />
**** Failure - go to beginning and start with that dependency.<br />
*** Issue in code? Create a patch.<br />
** Success - add spec file to [[JBossAS7#Cleanup_queue|queue for cleanup]]!<br />
<br />
=== Cleanup queue ===<br />
<br />
{{admon/note|Cleanup queue location|Cleanup queue is located here: http://goldmann.fedorapeople.org/jboss_as/queue/.}}<br />
<br />
{{admon/tip|Want to help us?|Cleaning up packages in cleanup queue and submitting them to Fedora is the easiest way you can help us! If you pick up a package - let us know on [irc://irc.freenode.net/fedora-java IRC] and add you to the table below.}}<br />
<br />
In cleanup queue you can find packages that are building fine, but the spec files needs cleanup. Cleanup can include (but is not limited to):<br />
<br />
* License, description, url, name, version, changelog are correct.<br />
* Make sure the spec files is following [[JBossAS7#Rules_for_JBoss-related_packages|additional rules]].<br />
<br />
'''After cleanup''' - package can be [[Package_Review_Process|submitted to Fedora]].<br />
<br />
==== Rules for JBoss-related packages ====<br />
<br />
Additionally to Java packaging rules - please meet following instructions for JBoss-related packages, like jboss-dmr, jboss-logging and so on:<br />
<br />
* JARs should be installed in <code>$RPM_BUILD_ROOT%{_javadir}/jboss</code><br />
* POM files should be installed in <code>$RPM_BUILD_ROOT%{_mavenpomdir}/JPP.jboss-%{name}.pom</code><br />
* Use [[User:Akurtakov/JavaPackagingDraftUpdate#add_maven_depmap_macro|<code>%add_maven_depmap</code> macro]]. It should look similar to this:<br />
<br />
<pre>%add_maven_depmap JPP.jboss-%{name}.pom jboss/%{name}.jar</pre><br />
<br />
==== Wishlist ====<br />
<br />
Below you can find examples of packages which you can pick up and start to package<br />
<br />
* [http://www.jboss.org/arquillian Arquillian] 1.0.0.CR4 or newer<br />
* [http://www.hibernate.org/ Hibernate] 4.0.0.Beta5 or newer<br />
* <s>[http://www.jboss.org/ironjacamar/ IronJacamar]</s> 1.0.3.Final or newer<br />
* [http://www.jboss.org/hornetq HornetQ] 2.2.7.Final or newer<br />
* [http://www.jboss.org/mod_cluster mod_cluster] 1.1.3.Final or newer<br />
* [http://seamframework.org/Weld Weld] 1.1.2.Final or newer<br />
* [http://www.jboss.org/infinispan Infinispan] 5.0.0.FINAL or newer<br />
* [http://www.jboss.org/resteasy Resteasy] 2.2.1.GA or newer <br />
** alee - packaging parts of resteasy: specifically resteasy-jaxrs, resteasy-jaxrs-api, resteasy-jaxb-provider, reseasy-jettison-provider<br />
** Currently packaging the following dependencies: scannotation, jaxb-impl<br />
* [http://www.jboss.org/shrinkwrap ShrinkWrap] 1.0.0-beta-5 or newer<br />
* [http://www.jboss.org/picketbox PicketBox] 4.0.1 or newer<br />
<br />
=== We need your help! ===<br />
<br />
Feel free to grab dependency you want to package and add you to the list. You can talk to us on [irc://irc.freenode.net/fedora-java #fedora-java] IRC or using [https://admin.fedoraproject.org/mailman/listinfo/java-devel mailing list].<br />
<br />
{{admon/note|Be fast!|Make sure you add the dependency immediately after you decide to pick it up so other can see what deps are available for packaging.}}<br />
<br />
== Current progress ==<br />
<br />
Table below shows what is officially submitted to Fedora (after creating review request). This is '''not''' the [[JBossAS7#Cleanup_queue|cleanup queue]] content.<br />
<br />
{|<br />
<br />
!#<br />
!Package<br />
!Version<br />
!POM<br />
!Review request<br />
!Packager<br />
!Status<br />
!Comments<br />
|-<br />
|1<br />
|hibernate-commons-annotations<br />
|3.2.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/hibernate/hibernate-commons-annotations/3.2.0.Final/hibernate-commons-annotations-3.2.0.Final.pom POM]<br />
|{{bz|706832}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|2<br />
|hibernate-jpa-2.0-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.0.Final/hibernate-jpa-2.0-api-1.0.0.Final.pom POM]<br />
|{{bz|706846}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|3<br />
|fusesource-pom<br />
|1.5<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/fusesource-pom/1.5/fusesource-pom-1.5.pom POM]<br />
|{{bz|708645}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|4<br />
|hawtjni<br />
|1.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/hawtjni/hawtjni-pom/1.1/hawtjni-pom-1.1.pom Parent POM]<br />
|{{bz|708670}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span> '''<br />
|Depends on <s>{{bz|708669}}</s>. Needs upgrade to 1.2.<br />
|-<br />
|5<br />
|jansi-native<br />
|1.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/jansi/jansi-native/1.1/jansi-native-1.1.pom POM]<br />
|{{bz|708836}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708669}}</s> and <s>{{bz|708670}}</s><br />
|-<br />
|6<br />
|jansi<br />
|1.5<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/jansi/jansi/1.5/jansi-1.5.pom POM]<br />
|{{bz|708842}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708669}}</s> and <s>{{bz|708836}}</s><br />
|-<br />
|7<br />
|gossip<br />
|1.7<br />
|[http://search.maven.org/remotecontent?filepath=org/sonatype/gossip/gossip/1.7/gossip-1.7.pom POM]<br />
|{{bz|709051}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708842}}</s>. Packaged as sonatype-gossip.<br />
|-<br />
|8<br />
|jline2<br />
|2.5<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/sonatype/jline/jline/2.5/jline-2.5.pom POM]<br />
|{{bz|709300}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708842}}</s><br />
|-<br />
|9<br />
|jboss-parent<br />
|6<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-parent/6/jboss-parent-6.pom POM]<br />
|{{bz|711350}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Updated to version 6.<br />
|-<br />
|10<br />
|apiviz<br />
|1.3.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/apiviz/apiviz/1.3.1.GA/apiviz-1.3.1.GA.pom POM]<br />
|{{bz|723523}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Project lead informed about the process.<br />
|-<br />
|11<br />
|byteman<br />
|1.5.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/byteman/byteman/1.5.1/byteman-1.5.1.pom POM]<br />
|{{bz|723875}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Project lead informed about the process.<br />
|-<br />
|12<br />
|cookxml<br />
|3.0.2<br />
|Generated<br />
|{{bz|724914}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|13<br />
|cookcc<br />
|0.3.3<br />
|[https://repository.jboss.org/nexus/service/local/repositories/thirdparty-uploads/content/com/google/code/cookcc/cookcc/0.3.3/cookcc-0.3.3.pom POM]<br />
|{{bz|724924}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|724914}}</s><br />
|-<br />
|14<br />
|jboss-logmanager<br />
|1.2.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/logmanager/jboss-logmanager/1.2.0.GA/jboss-logmanager-1.2.0.GA.pom POM]<br />
|{{bz|726044}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|711350}}</s><br />
|-<br />
|15<br />
|jboss-logging<br />
|3.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/logging/jboss-logging/3.0.0.GA/jboss-logging-3.0.0.GA.pom POM]<br />
|{{bz|726351}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|711350}}</s><br />
|-<br />
|16<br />
|jboss-common-core<br />
|2.2.17<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-common-core/2.2.17.GA/jboss-common-core-2.2.17.GA.pom POM]<br />
|{{bz|727152}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|17<br />
|jboss-dmr<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-dmr/1.0.0.Final/jboss-dmr-1.0.0.Final.pom POM]<br />
|{{bz|727171}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|724924}}</s><br />
|-<br />
|18<br />
|maven-injection-plugin<br />
|1.0.2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/maven/plugins/maven-injection-plugin/1.0.2/maven-injection-plugin-1.0.2.pom POM]<br />
|{{bz|727220}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|19<br />
|jboss-modules<br />
|1.0.2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/maven/plugins/maven-injection-plugin/1.0.2/maven-injection-plugin-1.0.2.pom POM]<br />
|{{bz|727608}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|727220}}</s><br />
|-<br />
|20<br />
|jboss-marshalling<br />
|1.3.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/marshalling/jboss-marshalling/1.3.0.GA/jboss-marshalling-1.3.0.GA.pom POM]<br />
|{{bz|728131}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on {{bz|725991}} <s>{{bz|727608}}</s><br />
|-<br />
|21<br />
|jboss-vfs<br />
|3.0.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-vfs/3.0.1.GA/jboss-vfs-3.0.1.GA.pom POM]<br />
|{{bz|728158}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|22<br />
|jboss-logging-tools<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/logging/jboss-logging-tools-parent/1.0.0.Beta7/jboss-logging-tools-parent-1.0.0.Beta7.pom POM]<br />
|{{bz|728171}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|23<br />
|jboss-threads<br />
|2.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/threads/jboss-threads/2.0.0.GA/jboss-threads-2.0.0.GA.pom POM]<br />
|{{bz|728208}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|24<br />
|jboss-msc<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/msc/jboss-msc/1.0.0.GA/jboss-msc-1.0.0.GA.pom POM]<br />
|{{bz|728202}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|723875}}</s> <s>{{bz|726351}}</s> <s>{{bz|728158}}</s> <s>{{bz|728171}}</s> <s>{{bz|728208}}</s><br />
|-<br />
|25<br />
|xnio<br />
|3.0.0.Beta4<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/xnio/xnio-api/3.0.0.Beta4/xnio-api-3.0.0.Beta4.pom POM]<br />
|{{bz|728460}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|727635}}</s> <s>{{bz|726351}}</s><br />
|-<br />
|26<br />
|jboss-remoting<br />
|3.2.0.Beta2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/remoting3/jboss-remoting/3.2.0.Beta2/jboss-remoting-3.2.0.Beta2.pom POM]<br />
|{{bz|728501}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|728171}}</s> <s>{{bz|728460}}</s><br />
|-<br />
|27<br />
|jboss-sasl<br />
|1.0.0.Beta1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/sasl/jboss-sasl/1.0.0.Beta1/jboss-sasl-1.0.0.Beta1.pom POM]<br />
|{{bz|728504}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|728501}}</s> <s>{{bz|727220}}</s> <s>{{bz|728171}}</s><br />
|-<br />
|28<br />
|jboss-httpserver<br />
|1.0.0.Beta1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/com/sun/httpserver/httpserver/1.0.0.Beta1/httpserver-1.0.0.Beta1.pom POM]<br />
|{{bz|729926}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|29<br />
|jandex<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jandex/1.0.0.Final/jandex-1.0.0.Final.pom POM]<br />
|{{bz|729970}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|30<br />
|jboss-specs-parent<br />
|1.0.0.Beta2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/jboss-specs-parent/1.0.0.Beta2/jboss-specs-parent-1.0.0.Beta2.pom POM]<br />
|{{bz|730226}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|31<br />
|jboss-transaction-1.1-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/transaction/jboss-transaction-api_1.1_spec/1.0.0.Final/jboss-transaction-api_1.1_spec-1.0.0.Final.pom POM]<br />
|{{bz|730227}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Depends on <s>{{bz|730226}}</s> Waiting for Legal...<br />
|-<br />
|32<br />
|jboss-servlet-3.0-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/servlet/jboss-servlet-api_3.0_spec/1.0.0.Final/jboss-servlet-api_3.0_spec-1.0.0.Final.pom POM]<br />
|{{bz|730232}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|730226}}</s><br />
|-<br />
|33<br />
|jboss-jaxrpc-1.1-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/xml/rpc/jboss-jaxrpc-api_1.1_spec/1.0.0.Final/jboss-jaxrpc-api_1.1_spec-1.0.0.Final.pom POM]<br />
|{{bz|730233}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Depends on <s>{{bz|730226}}</s> {{bz|730232}} Waiting for Legal...<br />
|-<br />
|34<br />
|jboss-ejb-3.1-api<br />
|1.0.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/ejb/jboss-ejb-api_3.1_spec/1.0.1.Final/jboss-ejb-api_3.1_spec-1.0.1.Final.pom POM]<br />
|{{bz|730234}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">In review</span> '''<br />
|Depends on <s>{{bz|730226}}</s> {{bz|730227}} {{bz|730233}}<br />
|-<br />
|35<br />
|jboss-interceptors-api_1.1<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/interceptor/jboss-interceptors-api_1.1_spec/1.0.0.Final/jboss-interceptors-api_1.1_spec-1.0.0.Final.pom POM]<br />
|{{bz|730306}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|730226}}</s><br />
|-<br />
|36<br />
|jboss-classfilewriter<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/classfilewriter/jboss-classfilewriter/1.0.0.Final/jboss-classfilewriter-1.0.0.Final.pom POM]<br />
|{{bz|730312}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|37<br />
|jboss-invocation<br />
|1.1.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/invocation/jboss-invocation/1.1.0.Final/jboss-invocation-1.1.0.Final.pom POM]<br />
|{{bz|730314}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|726351}}</s> <s>{{bz|728131}}</s> <s>{{bz|728171}}</s> <s>{{bz|730312}}</s><br />
|-<br />
|38<br />
|jboss-logmanager-log4j<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/logmanager/jboss-logmanager-log4j/1.0.0.GA/jboss-logmanager-log4j-1.0.0.GA.pom POM]<br />
|{{bz|730317}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|39<br />
|jboss-stdio<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/stdio/jboss-stdio/1.0.0.GA/jboss-stdio-1.0.0.GA.pom POM]<br />
|{{bz|730322}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|40<br />
|bean-validation-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.pom POM]<br />
|{{bz|730982}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|41<br />
|jboss-jad-api_1.2_spec<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/enterprise/deploy/jboss-jad-api_1.2_spec/1.0.0.Final/jboss-jad-api_1.2_spec-1.0.0.Final.pom POM]<br />
|{{bz|740799}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|726351}}</s> <s>{{bz|727152}}</s><br />
|-<br />
|42<br />
|Scannotation<br />
|1.0.3-0.2.r12<br />
|[ POM]<br />
|{{bz|767226 }}<br />
|[[User:Kashyapc|kashyap]] , [[User:vakwetu|Ade Lee]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|}<br />
<br />
<br />
=== Status legend ===<br />
<br />
{|<br />
!Status<br />
!Meaning<br />
|-<br />
|'''<span style="color:red">Issue</span>'''<br />
|Package encountered a serious issue while packaging (license, etc) - see Comments field for more info.<br />
|-<br />
|'''<span style="color:orange">Waiting for review</span>'''<br />
|Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review.<br />
|-<br />
|'''<span style="color:orange">In review</span>'''<br />
|Package is submitted for review and being reviewed by someone.<br />
|-<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Package passed review and packages is waiting for creating git repo in Fedora for this package.<br />
|-<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Package is available in Rawhide. Yay!<br />
|-<br />
|}<br />
<br />
[[Category:Java]] [[Category:JBoss]]</div>Kashyapchttps://fedoraproject.org/w/index.php?title=JBossAS7&diff=263327JBossAS72011-12-13T15:19:03Z<p>Kashyapc: /* Current progress */</p>
<hr />
<div>This wiki page shows the progress of including JBoss AS 7.<br />
<br />
== People involved ==<br />
<br />
Below is the list of currently involved people in the process.<br />
<br />
{|<br />
!Name<br />
!IRC<br />
!Current work<br />
!Additional info<br />
|-<br />
|[[User:Goldmann|Marek Goldmann]]<br />
|mgoldmann<br />
|Doing the dirty work of preparing jars to be packaged. See [[JBossAS7#Current_approach|Current approach]] section for more info.<br />
|UTC+2<br />
|-<br />
|[[User:vakwetu|Ade Lee]]<br />
|alee<br />
|Packaging parts of RESTeasy (and whatever is required to do so).<br />
|UTC-5<br />
|-<br />
|}<br />
<br />
== Current approach ==<br />
<br />
The idea is to '''package minimal set of JAR's'''. This means that only core JARs required to run or build AS7 will be packaged. This will let us package AS7 in reasonable timeframe. All additional JARs can be added later, for example to improve/enable test execution.<br />
<br />
I am ([[User:Goldmann|Marek Goldmann]]) now using following approach to select what needs to be packaged and what not:<br />
<br />
* Create a spec file.<br />
* Try to build the package.<br />
** Failure - see what what was the cause and:<br />
*** Missing dependency? Comment it out and build.<br />
**** Success - cool!<br />
**** Failure - go to beginning and start with that dependency.<br />
*** Issue in code? Create a patch.<br />
** Success - add spec file to [[JBossAS7#Cleanup_queue|queue for cleanup]]!<br />
<br />
=== Cleanup queue ===<br />
<br />
{{admon/note|Cleanup queue location|Cleanup queue is located here: http://goldmann.fedorapeople.org/jboss_as/queue/.}}<br />
<br />
{{admon/tip|Want to help us?|Cleaning up packages in cleanup queue and submitting them to Fedora is the easiest way you can help us! If you pick up a package - let us know on [irc://irc.freenode.net/fedora-java IRC] and add you to the table below.}}<br />
<br />
In cleanup queue you can find packages that are building fine, but the spec files needs cleanup. Cleanup can include (but is not limited to):<br />
<br />
* License, description, url, name, version, changelog are correct.<br />
* Make sure the spec files is following [[JBossAS7#Rules_for_JBoss-related_packages|additional rules]].<br />
<br />
'''After cleanup''' - package can be [[Package_Review_Process|submitted to Fedora]].<br />
<br />
==== Rules for JBoss-related packages ====<br />
<br />
Additionally to Java packaging rules - please meet following instructions for JBoss-related packages, like jboss-dmr, jboss-logging and so on:<br />
<br />
* JARs should be installed in <code>$RPM_BUILD_ROOT%{_javadir}/jboss</code><br />
* POM files should be installed in <code>$RPM_BUILD_ROOT%{_mavenpomdir}/JPP.jboss-%{name}.pom</code><br />
* Use [[User:Akurtakov/JavaPackagingDraftUpdate#add_maven_depmap_macro|<code>%add_maven_depmap</code> macro]]. It should look similar to this:<br />
<br />
<pre>%add_maven_depmap JPP.jboss-%{name}.pom jboss/%{name}.jar</pre><br />
<br />
==== Wishlist ====<br />
<br />
Below you can find examples of packages which you can pick up and start to package<br />
<br />
* [http://www.jboss.org/arquillian Arquillian] 1.0.0.CR4 or newer<br />
* [http://www.hibernate.org/ Hibernate] 4.0.0.Beta5 or newer<br />
* <s>[http://www.jboss.org/ironjacamar/ IronJacamar]</s> 1.0.3.Final or newer<br />
* [http://www.jboss.org/hornetq HornetQ] 2.2.7.Final or newer<br />
* [http://www.jboss.org/mod_cluster mod_cluster] 1.1.3.Final or newer<br />
* [http://seamframework.org/Weld Weld] 1.1.2.Final or newer<br />
* [http://www.jboss.org/infinispan Infinispan] 5.0.0.FINAL or newer<br />
* [http://www.jboss.org/resteasy Resteasy] 2.2.1.GA or newer <br />
** alee - packaging parts of resteasy: specifically resteasy-jaxrs, resteasy-jaxrs-api, resteasy-jaxb-provider, reseasy-jettison-provider<br />
** Currently packaging the following dependencies: scannotation, jaxb-impl<br />
* [http://www.jboss.org/shrinkwrap ShrinkWrap] 1.0.0-beta-5 or newer<br />
* [http://www.jboss.org/picketbox PicketBox] 4.0.1 or newer<br />
<br />
=== We need your help! ===<br />
<br />
Feel free to grab dependency you want to package and add you to the list. You can talk to us on [irc://irc.freenode.net/fedora-java #fedora-java] IRC or using [https://admin.fedoraproject.org/mailman/listinfo/java-devel mailing list].<br />
<br />
{{admon/note|Be fast!|Make sure you add the dependency immediately after you decide to pick it up so other can see what deps are available for packaging.}}<br />
<br />
== Current progress ==<br />
<br />
Table below shows what is officially submitted to Fedora (after creating review request). This is '''not''' the [[JBossAS7#Cleanup_queue|cleanup queue]] content.<br />
<br />
{|<br />
<br />
!#<br />
!Package<br />
!Version<br />
!POM<br />
!Review request<br />
!Packager<br />
!Status<br />
!Comments<br />
|-<br />
|1<br />
|hibernate-commons-annotations<br />
|3.2.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/hibernate/hibernate-commons-annotations/3.2.0.Final/hibernate-commons-annotations-3.2.0.Final.pom POM]<br />
|{{bz|706832}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|2<br />
|hibernate-jpa-2.0-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.0.Final/hibernate-jpa-2.0-api-1.0.0.Final.pom POM]<br />
|{{bz|706846}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|3<br />
|fusesource-pom<br />
|1.5<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/fusesource-pom/1.5/fusesource-pom-1.5.pom POM]<br />
|{{bz|708645}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|4<br />
|hawtjni<br />
|1.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/hawtjni/hawtjni-pom/1.1/hawtjni-pom-1.1.pom Parent POM]<br />
|{{bz|708670}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span> '''<br />
|Depends on <s>{{bz|708669}}</s>. Needs upgrade to 1.2.<br />
|-<br />
|5<br />
|jansi-native<br />
|1.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/jansi/jansi-native/1.1/jansi-native-1.1.pom POM]<br />
|{{bz|708836}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708669}}</s> and <s>{{bz|708670}}</s><br />
|-<br />
|6<br />
|jansi<br />
|1.5<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/fusesource/jansi/jansi/1.5/jansi-1.5.pom POM]<br />
|{{bz|708842}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708669}}</s> and <s>{{bz|708836}}</s><br />
|-<br />
|7<br />
|gossip<br />
|1.7<br />
|[http://search.maven.org/remotecontent?filepath=org/sonatype/gossip/gossip/1.7/gossip-1.7.pom POM]<br />
|{{bz|709051}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708842}}</s>. Packaged as sonatype-gossip.<br />
|-<br />
|8<br />
|jline2<br />
|2.5<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/sonatype/jline/jline/2.5/jline-2.5.pom POM]<br />
|{{bz|709300}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|708842}}</s><br />
|-<br />
|9<br />
|jboss-parent<br />
|6<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-parent/6/jboss-parent-6.pom POM]<br />
|{{bz|711350}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Updated to version 6.<br />
|-<br />
|10<br />
|apiviz<br />
|1.3.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/apiviz/apiviz/1.3.1.GA/apiviz-1.3.1.GA.pom POM]<br />
|{{bz|723523}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Project lead informed about the process.<br />
|-<br />
|11<br />
|byteman<br />
|1.5.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/byteman/byteman/1.5.1/byteman-1.5.1.pom POM]<br />
|{{bz|723875}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Project lead informed about the process.<br />
|-<br />
|12<br />
|cookxml<br />
|3.0.2<br />
|Generated<br />
|{{bz|724914}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|13<br />
|cookcc<br />
|0.3.3<br />
|[https://repository.jboss.org/nexus/service/local/repositories/thirdparty-uploads/content/com/google/code/cookcc/cookcc/0.3.3/cookcc-0.3.3.pom POM]<br />
|{{bz|724924}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|724914}}</s><br />
|-<br />
|14<br />
|jboss-logmanager<br />
|1.2.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/logmanager/jboss-logmanager/1.2.0.GA/jboss-logmanager-1.2.0.GA.pom POM]<br />
|{{bz|726044}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|711350}}</s><br />
|-<br />
|15<br />
|jboss-logging<br />
|3.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/logging/jboss-logging/3.0.0.GA/jboss-logging-3.0.0.GA.pom POM]<br />
|{{bz|726351}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|711350}}</s><br />
|-<br />
|16<br />
|jboss-common-core<br />
|2.2.17<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-common-core/2.2.17.GA/jboss-common-core-2.2.17.GA.pom POM]<br />
|{{bz|727152}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|17<br />
|jboss-dmr<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-dmr/1.0.0.Final/jboss-dmr-1.0.0.Final.pom POM]<br />
|{{bz|727171}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|724924}}</s><br />
|-<br />
|18<br />
|maven-injection-plugin<br />
|1.0.2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/maven/plugins/maven-injection-plugin/1.0.2/maven-injection-plugin-1.0.2.pom POM]<br />
|{{bz|727220}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|19<br />
|jboss-modules<br />
|1.0.2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/maven/plugins/maven-injection-plugin/1.0.2/maven-injection-plugin-1.0.2.pom POM]<br />
|{{bz|727608}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|727220}}</s><br />
|-<br />
|20<br />
|jboss-marshalling<br />
|1.3.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/marshalling/jboss-marshalling/1.3.0.GA/jboss-marshalling-1.3.0.GA.pom POM]<br />
|{{bz|728131}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on {{bz|725991}} <s>{{bz|727608}}</s><br />
|-<br />
|21<br />
|jboss-vfs<br />
|3.0.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jboss-vfs/3.0.1.GA/jboss-vfs-3.0.1.GA.pom POM]<br />
|{{bz|728158}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|22<br />
|jboss-logging-tools<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/logging/jboss-logging-tools-parent/1.0.0.Beta7/jboss-logging-tools-parent-1.0.0.Beta7.pom POM]<br />
|{{bz|728171}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|23<br />
|jboss-threads<br />
|2.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/threads/jboss-threads/2.0.0.GA/jboss-threads-2.0.0.GA.pom POM]<br />
|{{bz|728208}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|726351}}</s><br />
|-<br />
|24<br />
|jboss-msc<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/msc/jboss-msc/1.0.0.GA/jboss-msc-1.0.0.GA.pom POM]<br />
|{{bz|728202}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|723875}}</s> <s>{{bz|726351}}</s> <s>{{bz|728158}}</s> <s>{{bz|728171}}</s> <s>{{bz|728208}}</s><br />
|-<br />
|25<br />
|xnio<br />
|3.0.0.Beta4<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/xnio/xnio-api/3.0.0.Beta4/xnio-api-3.0.0.Beta4.pom POM]<br />
|{{bz|728460}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|727635}}</s> <s>{{bz|726351}}</s><br />
|-<br />
|26<br />
|jboss-remoting<br />
|3.2.0.Beta2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/remoting3/jboss-remoting/3.2.0.Beta2/jboss-remoting-3.2.0.Beta2.pom POM]<br />
|{{bz|728501}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Depends on <s>{{bz|728171}}</s> <s>{{bz|728460}}</s><br />
|-<br />
|27<br />
|jboss-sasl<br />
|1.0.0.Beta1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/sasl/jboss-sasl/1.0.0.Beta1/jboss-sasl-1.0.0.Beta1.pom POM]<br />
|{{bz|728504}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|728501}}</s> <s>{{bz|727220}}</s> <s>{{bz|728171}}</s><br />
|-<br />
|28<br />
|jboss-httpserver<br />
|1.0.0.Beta1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/com/sun/httpserver/httpserver/1.0.0.Beta1/httpserver-1.0.0.Beta1.pom POM]<br />
|{{bz|729926}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|29<br />
|jandex<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/jandex/1.0.0.Final/jandex-1.0.0.Final.pom POM]<br />
|{{bz|729970}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|30<br />
|jboss-specs-parent<br />
|1.0.0.Beta2<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/jboss-specs-parent/1.0.0.Beta2/jboss-specs-parent-1.0.0.Beta2.pom POM]<br />
|{{bz|730226}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|31<br />
|jboss-transaction-1.1-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/transaction/jboss-transaction-api_1.1_spec/1.0.0.Final/jboss-transaction-api_1.1_spec-1.0.0.Final.pom POM]<br />
|{{bz|730227}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Depends on <s>{{bz|730226}}</s> Waiting for Legal...<br />
|-<br />
|32<br />
|jboss-servlet-3.0-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/servlet/jboss-servlet-api_3.0_spec/1.0.0.Final/jboss-servlet-api_3.0_spec-1.0.0.Final.pom POM]<br />
|{{bz|730232}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|730226}}</s><br />
|-<br />
|33<br />
|jboss-jaxrpc-1.1-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/xml/rpc/jboss-jaxrpc-api_1.1_spec/1.0.0.Final/jboss-jaxrpc-api_1.1_spec-1.0.0.Final.pom POM]<br />
|{{bz|730233}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Depends on <s>{{bz|730226}}</s> {{bz|730232}} Waiting for Legal...<br />
|-<br />
|34<br />
|jboss-ejb-3.1-api<br />
|1.0.1<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/ejb/jboss-ejb-api_3.1_spec/1.0.1.Final/jboss-ejb-api_3.1_spec-1.0.1.Final.pom POM]<br />
|{{bz|730234}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">In review</span> '''<br />
|Depends on <s>{{bz|730226}}</s> {{bz|730227}} {{bz|730233}}<br />
|-<br />
|35<br />
|jboss-interceptors-api_1.1<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/interceptor/jboss-interceptors-api_1.1_spec/1.0.0.Final/jboss-interceptors-api_1.1_spec-1.0.0.Final.pom POM]<br />
|{{bz|730306}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|730226}}</s><br />
|-<br />
|36<br />
|jboss-classfilewriter<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/classfilewriter/jboss-classfilewriter/1.0.0.Final/jboss-classfilewriter-1.0.0.Final.pom POM]<br />
|{{bz|730312}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|37<br />
|jboss-invocation<br />
|1.1.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/invocation/jboss-invocation/1.1.0.Final/jboss-invocation-1.1.0.Final.pom POM]<br />
|{{bz|730314}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|726351}}</s> <s>{{bz|728131}}</s> <s>{{bz|728171}}</s> <s>{{bz|730312}}</s><br />
|-<br />
|38<br />
|jboss-logmanager-log4j<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/logmanager/jboss-logmanager-log4j/1.0.0.GA/jboss-logmanager-log4j-1.0.0.GA.pom POM]<br />
|{{bz|730317}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|39<br />
|jboss-stdio<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/stdio/jboss-stdio/1.0.0.GA/jboss-stdio-1.0.0.GA.pom POM]<br />
|{{bz|730322}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|40<br />
|bean-validation-api<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.pom POM]<br />
|{{bz|730982}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|<br />
|-<br />
|41<br />
|jboss-jad-api_1.2_spec<br />
|1.0.0<br />
|[https://repository.jboss.org/nexus/service/local/repositories/central/content/org/jboss/spec/javax/enterprise/deploy/jboss-jad-api_1.2_spec/1.0.0.Final/jboss-jad-api_1.2_spec-1.0.0.Final.pom POM]<br />
|{{bz|740799}}<br />
|[[User:Goldmann|goldmann]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|Depends on <s>{{bz|726351}}</s> <s>{{bz|727152}}</s><br />
|-<br />
|42<br />
|Scannotation<br />
|1.0.3-0.1.r12<br />
|[ POM]<br />
|{{bz|767226 }}<br />
|[[User:Kashyapc|kashyap]] , [[User:vakwetu|Ade Lee]]<br />
|'''<span style="color:orange">Waiting for review</span> '''<br />
|<br />
|}<br />
<br />
<br />
=== Status legend ===<br />
<br />
{|<br />
!Status<br />
!Meaning<br />
|-<br />
|'''<span style="color:red">Issue</span>'''<br />
|Package encountered a serious issue while packaging (license, etc) - see Comments field for more info.<br />
|-<br />
|'''<span style="color:orange">Waiting for review</span>'''<br />
|Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review.<br />
|-<br />
|'''<span style="color:orange">In review</span>'''<br />
|Package is submitted for review and being reviewed by someone.<br />
|-<br />
|'''<span style="color:green">After review, waiting for SCM</span>'''<br />
|Package passed review and packages is waiting for creating git repo in Fedora for this package.<br />
|-<br />
|'''<span style="color:green">In Rawhide</span>'''<br />
|Package is available in Rawhide. Yay!<br />
|-<br />
|}<br />
<br />
[[Category:Java]] [[Category:JBoss]]</div>Kashyapc