QA:Testcase freeipav2 installation

{{QA/Test_Case  The freeipa package did not make the F-15 split. To get the latest F-15 packages you'll need to configure the freeipa-devel.repo. Retrieve this file from http://freeipa.org/downloads/freeipa-devel.repo and place it in /etc/yum.repos.d. The dogtag packages are not unfortunately not working in F-15. This does not preclude freeipa testing but it does mean that you won't be able to test with a full CA. The  option will need to be added to every   invocation Ensure the {{package|freeipa-server}} package is installed: (optional) To install with DNS, ensure the {{package|bind}} and {{package|bind-dyndb-ldap}} packages are installed. Make sure  is sane. This means that your host will be listed on a separate line with its IP address with the FQDN listed first, this is necessary to avoid chicken/egg issues when the DNS is installed as name resolution for the public host name is needed to start the DNS itself (to init krb credentials). In particular the hostname SHOULD not appear in either the IPv4 or IPv6 localhost lines. If you have an existing AD server in your network choose a unique name for the IPA server realm name. Clients that use DNS autodiscovery to find the KDC to use may get confused and try to authenticate to the AD KDC. 
 * description=Installation testing.
 * setup=
 * 1) yum install --enablerepo=freeipa-devel freeipa-server
 * actions=

Without DNS
For a fully-interactive install run:


 * 1) ipa-server-install --selfsign

You can optionally provide all options on the command-line:


 * 1) ipa-server-install -a secret123 -p 123Secret --domain=freeipa.org --realm=FREEIPA.ORG -U --selfsign

With DNS

 * 1) ipa-server-install --setup-dns --selfsign

Or with all options on the command-line:


 * 1) ipa-server-install -a secret123 -p 123Secret --domain=freeipa.org --realm=FREEIPA.ORG --setup-dns -U --selfsign

Verify the basics
Ideally each of these installation steps will conclude with no errors and a running set of IPA services.

To briefly test the installation:


 * 1) kinit admin (the password is the admin password, or the password from -a)

Show our own user entry:


 * 1) ipa user-show admin

And make sure nss can see us too:


 * 1) id admin
 * 2) getent passwd admin

Verify Services
We install a number of SSL certificates that should be automatically managed by certmonger:


 * 1) ipa-getcert list

There should be 3 certificates, all in MONITORING. The certificates should be in the following NSS databases:

* /etc/pki/nssdb * /etc/httpd/alias * /etc/dirsrv/slapd-FREEIPA-ORG


 * 1) kinit admin
 * 2) ipa service-find

There should be 2 services: ldap and HTTP for your FreeIPA server

Verify DNS
Verify these only if you installed with a DNS server.


 * 1) dig server.freeipa.org. (yes, add a trailing dot)

Look for a line like this in the output:

server.freeipa.org. 86400  IN      A       192.168.0.1

server.freeipa.org has address 192.168.0.1
 * 1) host server.freeipa.org

--- Found 'server.freeipa.org.' ---
 * 1) ipa dns-resolve server.freeipa.org

Host name: server.freeipa.org Principal name: host/server.freeipa.org@FREEIPA.ORG Keytab: True Managed by: server.freepia.org
 * 1) ipa host-show server.freeipa.org

Uninstallation
FreeIPA provides a way to unininstall the configured services and it does its best to return the system to its previous state. To run the uninstaller execute:


 * 1) ipa-server-install --uninstall -U

Verify uninstallation
Un-installation is intended for developers. It is a best-as-we-can restoration of files primarily to prepare the server to be re-installed.

To verify that the server is in a state where it can be re-installed re-run ipa-server-install:


 * 1) ipa-server-install

If something failed in the un-installation you would get an error message that the server is already installed/configured.

All the test steps should end with the specified results. }}
 * results=