Description of problem:

ipa-server-install uses different names for the same service for configuration
start/finish messages in progress output and logs. This is confusing and makes
it harder to look for corresponding start or finish messages.

Example output quote:

    Configuring directory server for the CA: Estimated time 30 seconds
      [1/3]: creating directory server user
      [2/3]: creating directory server instance
      [3/3]: restarting directory server
    done configuring pkids.

Example log quote:

    2012-09-07T09:04:58Z DEBUG Configuring directory server for the CA:
Estimated time 30 seconds
    ...
    2012-09-07T09:07:11Z DEBUG done configuring pkids.

Compare the first and the last lines of both.

How reproducible:
always.

Steps to Reproduce:
run ipa-server-install.

Actual results:

    Configuring directory server for the CA: Estimated time 30 seconds
      [1/3]: creating directory server user
      [2/3]: creating directory server instance
      [3/3]: restarting directory server
    done configuring pkids.


Expected results:

    Configuring pkids: Estimated time 30 seconds
      [1/3]: creating directory server user
      [2/3]: creating directory server instance
      [3/3]: restarting directory server
    done configuring pkids.

Or:

    Configuring directory server for the CA: Estimated time 30 seconds
      [1/3]: creating directory server user
      [2/3]: creating directory server instance
      [3/3]: restarting directory server
    done configuring directory server for the CA.

Or maybe:

    Configuring pkids (directory server for the CA): Estimated time 30 seconds
      [1/3]: creating directory server user
      [2/3]: creating directory server instance
      [3/3]: restarting directory server
    done configuring pkids (directory server for the CA).

Additional info:

One way to fix this would be to add a "service_description" field to the
"Service" class, remove "message" argument of the "start_creation" member
function and format start messages there instead, in addition to finish
messages, using service_name and/or service_description fields.