|Fedora Test Days|
|Date||February 15, 2011|
|Time||all day, UTC|
|Mail • Subscribe • Archives|
What to test?
Today's installment of Fedora Test Day will focus on FreeIPA v2. FreeIPA is an integrated security information management solution combining Linux, 389 Directory Server, MIT Kerberos, NTP, DNS and Dogtag Certificate server. It consists of a web interface and command-line administration tools.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Dmitri Pal (
dpal), Jakub Hrozek (
jhrozek), Martin Kosek (
mkosek), Jan Zeleny (
- Quality Assurance - Gowrishankar Rajaiyan (
shanks), Kashyap Chamarthy (
Prerequisite for Test Day
- An updated Fedora 15 Alpha TC2
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
Update your machine
See the instructions on the Branched page on the various ways in which you can install or update to the Branched Release.
The Dogtag Certificate System is not currently working in F-15/rawhide (BZ 676330)
FreeIPA can still be tested it will just lack full CA features such as certificate revocation. A file-based CA will be configured instead by using the
--selfsign option to the
ipa-server-install command (as outlined in the Installation Test Plan).
The FreeIPA Release Candidate 2.0.0rc1 did not make the F-15 split. The packages are available in the freeipa-devel.repo repository. Copy this file to /etc/yum.repos.d before beginning testing to enable our development repo. The package is also build in rawhide (F-16).
Follow each of these test cases:
For the following tests you will need 2 machines (one for the server and one for client):
For the following test you will need at least 2 machines (the more, the better):
If you have problems with any of the tests, report a bug to Trac or to Bugzilla (usually for the freeIPA product). 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. 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, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.