Basic adjustment for SUSE (package-names and init scripts)

Conflicts:
	chef/cookbooks/glance/recipes/common.rb
Use prefixed system user on SUSE
set secure permissions (bnc#771101)

Conflicts:
	chef/cookbooks/glance/recipes/api.rb
Merge pull request #6 from crowbar/release/pebbles/master

Release/pebbles/master
Fixed uid+gid for glance-manage version_control and db_sync.

We are using openstack-glance instead of glance.

I found this accidentally while stracing the disappearance of
/var/run/chef/client.pid (bnc#773182). Not sure of the impact but
the fixed version should be better[TM].

Conflicts:
	chef/cookbooks/glance/recipes/common.rb
disallow access to configs with PWs (bnc#774966)

Conflicts:
	chef/cookbooks/glance/recipes/registry.rb
	chef/cookbooks/glance/recipes/scrubber.rb
Remove code that finds ip addresses that we actually don't need

The scrubber configuration doesn't care about keystone. And the registry
recipe is not using IP addresses.
Add back bind port attributes to json/schema

This broke Dell's smoketesting.
Use new render_instance_selector helper
Merge pull request #86 from vuntz/render_instance_selector

Use new render_instance_selector helper
Merge pull request #82 from vuntz/suse-forward-port

Forward-port patches from SUSE
Merge pull request #85 from vuntz/add-back-port

Add back bind port attributes to json/schema
Remove possibility to use sqlite

It's known to be broken, and there was agreement to only use the
database barclamp.

This means we can remove the whole database_engine dance, which
simplifies things.
Use new protocol attribute from keystone barclamp
Merge pull request #89 from vuntz/no-sqlite

Remove possibility to use sqlite
Merge pull request #91 from vuntz/keystone-protocol-attribute

Add non-configurable attribute for http/https use in keystone [2/7]
The auth_token middleware has beed moved to keystoneclient

Using keystone.middleware.auth_token, which nowadays is just a compatibilty
wrapper for keystoneclient.middleware.auth_token, breaks in setups where
keystone is installed on a different node. Using keystoneclient instead should
work in all cases as it will be pulled in via package dependencies.
Fix endpoints when the service only listens on one IP address

If we let the service bind to all IPs, then the service is obviously
usable from the public and admin networks. Otherwise, the endpoint URLs
should use the unique IP that will be listened on.
Don't hardcode the username in cron files (bnc#826117).

In our tests it surfaced in /etc/cron.d/glance-scrubber.
In SUSE packages the user is openstack-glance.
Move registration of glance service user to common recipe

There's no need to have that code done twice for both api and registry,
which was also causing a CHEF-3694 bug (since the resources had the same
name).

WARN: Cloning resource attributes for keystone_register[register glance user] from prior resource (CHEF-3694)
WARN: Previous keystone_register[register glance user]: /var/chef/cache/cookbooks/glance/recipes/api.rb:108:in `from_file'
WARN: Current  keystone_register[register glance user]: /var/chef/cache/cookbooks/glance/recipes/registry.rb:85:in `from_file'
WARN: Cloning resource attributes for keystone_register[give glance user access] from prior resource (CHEF-3694)
WARN: Previous keystone_register[give glance user access]: /var/chef/cache/cookbooks/glance/recipes/api.rb:118:in `from_file'
WARN: Current  keystone_register[give glance user access]: /var/chef/cache/cookbooks/glance/recipes/registry.rb:95:in `from_file