Initialize compute manager before loading driver.

The compute virt API uses the conductor API instance on the compute
manager.  Make sure the compute manager has been fully initialized
before loading the driver and passing it the virtapi instance.  This
prevents the possibility of the driver calling back into the compute
manager and using something not initialized yet, such as the conductor
API in the case of this bug.

This patch also moves initialization of a member variable up above
super(), where the rest of the initialization is.  There doesn't appear
to be a reason for needing to have it at the end.

Fix bug 1156490.

Change-Id: I19684f24d590201d135336107425c2be2f74c83e
(cherry picked from commit 9075069098e32b47bd5011e2653a23b61c18d4a3)
Sync lockutils from oslo-incubator stable/grizzly.

Changes include:

3cb71ff Locking edge case when lock_path does not exist
21925b6 Fix locking issues in Windows
547ab34 Fix Copyright Headers - Rename LLC to Foundation

Fix bug 1158179.

Change-Id: I8231a6d37b70c36ba2ce245407b02698faa55aaf
Import latest openstack.common.setup

Import latest openstack.common.setup from oslo-incubator.
Fixes bug 1158319 (Include Co-authored-by entries in AUTHORS), but also:
* stop using --stat for ChangeLog
* failing to get version from git
* returncode for Popen is valid only after communicate call

Change-Id: Ib7a391560ec885b5478208cd441ce2c10e9d8cac
Merge "Initialize compute manager before loading driver." into milestone-proposed
Merge "Sync lockutils from oslo-incubator stable/grizzly." into milestone-proposed
Merge "Import latest openstack.common.setup" into milestone-proposed