make keystone auth strategy configurable

Change-Id: Ib40bfa093d14581cdb3087e9a1154b6e1d14036e
libvirt unix_socket_group attribute

- libvirtd.conf template now suports unix_socket_group defined in
  a attribiutes.
- openstack-nova user shuld be member of libvirt group to be able to read
  from libvirt unix_socket. Implemented group resource in libvirt recipie.

Change-Id: I88370f2d7fd5147f3bb46a1411295868a8ea12ce
manage libvirt group using the chef group resource

also rename the libvirt group attribute name

Change-Id: Ie4304e6c26dafa3a1101c1ff8f90d0236f80914a
Renamed keystone_registration recipe

Renamed keystone_registration to identity_registration, and added
identity_registration tests.  Added registration tests to simply
test the args being passed to the `openstack_identity_register` LWRP.
The identity LWRP should be tested at a deeper level than the consumers.

Testing args passed to a DSL (&block) is a bit tricky. The tests
are not ideal, but give us the necessary coverage to catch common
errors.

Change-Id: I18db535ca1bab357ba083d57a76d86c5ccfddf15
Fixes: Bug 1182576
update metadata requirements after semantic versioning switch

Change-Id: I89af6df6ebfed490237b2be8437f246c8fa65c3b
filter_factory moved to keystone_client in grizzly

Change-Id: I0c9ea590b6f0de90904c70689273655f4f26287a
use the ceilometer cache_dir, not the nova one

Change-Id: I5f715088f07330cd72ce4daabd286db1b7035c3e
Merge "Renamed keystone_registration recipe"
Merge "update metadata requirements after semantic versioning switch"
Merge "use the ceilometer cache_dir, not the nova one"
Merge "filter_factory moved to keystone_client in grizzly"
Add metering-api endpoint registration

Add calls to identity_registration to support the Ceilometer metering
service. Ideally this does not live here long-term, in favor of the
metering cookbook, but until that cookbook is ready, this is being
placed here as a stop-gap measure.

Tests added for these new endpoints. Tests pass.

Change-Id: I13cfdc0fb2f280837fb4bc06dd0e6d46f059081a
Using ~> versioning

Since we should be performing semver across our cookbooks, we should
lock to the patch version.  It means "equal to or greater than in the
last digit", so e.g. "~> 2.3" means "equal to 2.3 or greater than 2.3,
but less than 3.0", while "~> 2.3.0" would mean "equal to 2.3.0 or greater
than 2.3.0, but less than 2.4.0".
  http://stackoverflow.com/questions/5170547/what-does-tilde-greater-than-mean-in-ruby-gem-dependencies

Change-Id: I53b334865909868dcc9b5d003795adead1ecf86c
Merge "make keystone auth strategy configurable"
Fix for nova-compute service not beeing started.

nova-compute service should be started after nova::compute recipie will
finish its work.

Change-Id: I4c9b7de2391f76e9c7cb74df17446b97565a8ed6
spec test for starting nova-api-os-compute immediately

Change-Id: Iea86f62cf5654d644a3025300fa571512ad460c5
Merge "Using ~> versioning"
Merge "Add metering-api endpoint registration"
Merge "Fix for nova-compute service not beeing started."
Merge "spec test for starting nova-api-os-compute immediately"