xenapi: enable user interaction with stack.sh

In XenServer, devstack runs inside a virtual machine. This makes it hard
for the user to interact with stack.sh should a parameter be missing.
This change will create an upstart job (devstack) that runs
stack.sh with console enabled so user can interact with it by running
vncviewer or using XenCenter.

Logging the output is also disabled, stamp files are used instead to
detect the script run status in case install_os_domU.sh is used.

As run.sh.log is removed, standard devstack logging should be used.

The change also removes the environment settings from run.sh, as they
are not needed, they should be specified in localrc. This way user
cannot get different experiences by using unstack.sh/stack.sh or run.sh

Also a proper unstack.sh is called instead of killing screen in run.sh

Change-Id: I7eb12bd74746cc7a1db3aa9fd68ece645a50001d
Fix noVNC git repo

Recent change switched base git URL to git.openstack.org.
However, noVNC is only hosted on GitHub.
Change git repo URL for noVNC back to the GitHub one.

Change-Id: Iaa9f570639301be1c29cc400c1c73afcbf637b70
Merge "Fix noVNC git repo"
Merge "xenapi: enable user interaction with stack.sh"
xenapi: display IP and DevStack result on console

The devstack setup service can update /etc/issue, displaying the status
of the installation and the VM's management IP. With this change, after
the devstack service finsihed, the login prompt will look like this:

OpenStack VM - Installed by DevStack
  Management IP:   10.219.3.108
  Devstack run:    SUCCEEDED

DevStackOSDomU login:

This helps people to log in to their system.

Change-Id: Idd6bbd5faf9ced5618cd3e95191bfc3b89473fa2
XenAPI:  Increase DomU's memory

Devstack has been increasing in complexity, and if we use too
much of our memory it can lead to fragmentation which in turn
causes a DomU error and a failure of random tests.

Change-Id: Ide9cc84625caed4e35a64a47ee1e92a6cd567651
XenAPI: Update DomU to Ubuntu Saucy

Driven by a race condition in LVM being hit in the tempest
tests.  This is a locking race between a file lock and a
semaphore which is fixed in 2.02.96-5.

Change-Id: I8a8c215c90a0602288292ffd06b7694d2db6219e