Changed identity to proper identity-api

Previous commit had wrong endpoint key. Should have
been identity-api, not identity.

Change-Id: Ia280b7e0da81cdb57d4ffc00ef639b31de0c5dd8
Fix broken libvirt recipe test

As it stands right now, libvirt calls out to system to execute
grub2-set-default and this was stubbed out only in the Suse chefspec
libvirt test. Move this stub to spec_helper and modify our tailor
configuration to allow for this change.

Change-Id: I276d799cb3db5f725ffa396b5bed8724b6e42696
Update vncproxy service resource to use service name

Instead of calling the nova-vncproxy service by the generic
"nova-vncproxy" name, name this resource by its actual service name.
This change aids recieps that are dependent upon knowing which
service to notify when necessary. While it is possible to simply
notify "nova-vncproxy," there are times when that is a less favorable
solution.

Change-Id: Iefbec31b050dd93eba118012b07745dcc215f8c5
Replace config_by_role with search_for

config_by_role is almost entirely unused, and returns inconsisent
results depending on which node it is called from. Similarly, with the
new structure of these cookbooks, the "section" attribute of
config_by_role is pretty useless. So get rid of config_by_role and
replace it with search_for in this case.

Also ajust test to account for change in return type.

This change is related to https://review.openstack.org/38738

Change-Id: I12e99e665a037791ef1f8c351f261cd34ae38d72
Merge "Replace config_by_role with search_for"
Merge "Update vncproxy service resource to use service name"
update to use openstack-common 0.4.0

Change-Id: I4db7a869a7c3c4e84e5ea766b57963d12bdd14c3
Add force_config_drive option to nova.conf.

Allow the force_config_drive option to be set to allow
config_drive to be used as an additional meta-data source
by supported images.

Defaults to false to match the existing nova default.

Change-Id: I2d3e26da484cd0895ceab77aa200e5cf5943a065
Corrects the auth_token middleware configuration

Partially addresses LP 1207504

We need to ensure that auth_uri is set properly, that
auth_version defaults to v2.0, even when the v3 Keystone
API is available, and that the non-auth_uri config options
refer to the admin endpoint, not the service endpoint.

Change-Id: Ifbfbbf86bb6956b9b7c366dec5a8a12b383a476b
Add quantum/neutron support to openstack-compute

This commit introduces a new node attribute which will
turn off nova-networking and enable quantum/neutron
style networking and install the appropriate dependant
packages.

Change-Id: Ia9dadf736e6e916f4b25c202cb88cb8a030d54c0
Merge "Add quantum/neutron support to openstack-compute"
Check if local node has identity role before searching

this was causing the first chef run on an allinone server to fail.
will return the local node hash if the role exists locally, otherwise will search

Change-Id: I7db000223c68a7aaa3732125b31ac2282bb21cca
Removed ceilometer references

Ceilometer has its own cookbook `openstack-metering`.  Removing
ceilo from this cookbook to ensure we focus our efforts on the
new cookbook.  I have yet to perform integration testing on
the metering cookbook, but I imagine things should be in working
order as we all begin to use it.

Change-Id: I0bc5dd3591d9686b5cf7dd7046f0b1d7436ca2fd
Bug fix add_floaters subcommand processing errors

* AttributeError for args.interface Certain argument
parameters are not set depending on whether you are entering
via the neutron or nova subcommands. If we simply set
self._args, we can access the expected arguments within
the appropriate subcommand and not try to blindly
set several of them on FloatingAddress class init.

* Subcommands do not show up as arguments, so we need to
set the subcommand name to a subparser_name argument
we can check to see which subcommand was called

* If the quantum api is down for any reason, the add
add floaters script will fail raising a chef error.  We
need only raise an error if there was an error adding
the IPs, not querying the quantum api.

Change-Id: Iac2cdae03bc3e2af39781994707b5139c401427f
Override quantum network endpoint port

This is a workaround for nova bug LP#1206330.  We want to
allow the endpoint port to be customized, but if it is 443
we will override it since we are already overriding the scheme.

Change-Id: I4585c32a2e8599eefb1ac8770c71d1fb8e0012cd
Merge "Removed ceilometer references"
Updated identity tests to use `#find_resource`.

We use this method in the other cookbooks.  Wanted to bring compute
in-line with the others.

Change-Id: I424de99777e1438363e5a4288a30224a05920164
There was an = missing so force_config_drive was always
showing blank

Change-Id: Ibe3b3cd13d10efd340292c6ecc10b9ed77d2fc85
Merge "Updated identity tests to use `#find_resource`."