packaging: Build and run with Fedora 17 jboss-as

This patch includes changes to build and run the engine with the
jboss-as package included in Fedora 17.

A private instance of jboss-as is created so that there is no
interference with other applications running on top of the
application server. This private instance will be executed by the
user and group "ovirt" and uses the following files and
directories:

/usr/share/ovirt-engine

  A new "modules" subdirectory has been added that holds the JBoss
  modules that are missing in the current jboss-as package in
  Fedora 17. Also some modules that require fixes.

  The application server will be started using a module path that
  contains first this "modules" directory and then the "modules"
  directory of JBoss itself.

  All the content here should be owned by root to prevent writes
  by the engine.

/etc/ovirt-engine

  This directory stores most of the configuration files. In the
  future it should store *all* the configurationfiles.

  It is owned by the ovirt user becase the application server
  will store here backup copies of the main configuration file.

/etc/ovirt-engine/engine-service.xml

  This is the main configuration file of the application server,
  copied from standalone-web.xml and modified to fit the needs of
  the engine.

  My expectation is that maintaining this configuration file will
  be easier than maintaing the parts of the engine-setup script
  that modify the configuration. However, at the moment both
  things are needed.

  It is owned by the ovirt user because the application server
  reads and then writes it during each run.

/etc/ovirt-engine/engine-service-logging.properties

  This contains the log4j configuration used by the application
  server using during boot, mostly copied from "logging.properties".

/etc/ovirt-engine/engine-service-users.properties

  This file should contain the user names and passwords of the
  application server management users. It is empty at the moment.

/var/log/ovirt-engine

  This directory holds the log files of the engine: boot.log for
  the boot messages, server.log for the application server messages,
  engine.log for the engine messages and console.log for the
  standard output and errors of the java virtual machine.

  The directory is owned by the ovirt user so that the application
  server can create/rotate log files.

/var/lib/ovirt-engine

  This is the directory where the application server will store
  variable data.

  The "deployments" subdirectory is created during installation
  and it will contain a symlink to the "engine.ear" directory and
  the "engine.ear.dodeploy" marker file.

  The "content", "timer-service-data" and "tx-object-store"
  subdirectories are created by the application server as needed and
  should't be removed.

  This directory is owned by the "ovirt" user, as the application
  server needs to create subdirectories.

/var/cache/ovirt-engine

  This is where the application server stores temporary content
  like "auth", "vfs" and "work". It is safe to remove this when
  the application server is stopped.

  This directory is also owned by the "ovirt" user.

The private instance of the application server works as a systemd
service started and stopped with the "engine-service.py" script.
This script gets some configuration variables (heap space, debug
flags, directory names, etc) from the "engine-service" sysconfig
file.

The makefile, spec and engine-setup script have been adjusted to
build and install with the private instance of jboss-as.

Change-Id: I5cda15e5219d1b6c8e8306fc7b4f196e6afc66b1
Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>