Use new render_instance_selector helper
Do not expose service user and passwords in UI

End users don't need to change this (and we already generate a random
password); it can still be changed in the json if really needed.
Do not create proposal if no instance found for barclamp dependencies

We need a rabbitmq instance and a keystone instance to properly
auto-fill the defaults.

Note that the code is already doing this check for database.
Merge pull request #46 from vuntz/render_instance_selector

https://github.com/crowbar/barclamp-quantum/pull/46

Merged by devtool for cloudsleuth
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.
Remove attributes that exist only because of copy&paste from keystone

The admin/regular/service user/password as well as the admin token
clearly come straight from the keystone barclamp but have no use here. I
guess this barclamp was initially created as a copy of the keystone
barclamp.
Do not hardcode admin tenant
Fix creation of /etc/sudoers.d/quantum-rootwrap

It's not needed on SUSE (our package have this already) and the user
should not be hardcoded.
Fix typo
Install quantum packages before doing anything else

We need the basic quantum packages to have quantum-rootwrap and the
quantum services installed, before we do the rest. Otherwise, the first
chef-client run will fail because other recipe will try to access these
resources that don't exist yet.

Example of failure:

[Sun, 16 Jun 2013 13:13:57 +0000] INFO: Processing service[openstack-quantum]
action restart (quantum::server line 186)

================================================================================
Error executing action `restart` on resource 'service[openstack-quantum]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /sbin/service openstack-quantum restart ----
STDOUT:
STDERR: service: no such service openstack-quantum
---- End output of /sbin/service openstack-quantum restart ----
Ran /sbin/service openstack-quantum restart returned 1
Respect debug attribute in all config files
Do not make quantum.conf world-readable

It contains passwords.
Do not hardcode API port when registering endpoint

We have an attribute to set it.
Have a default path for quantum-rootwrap

Finding the path to quantum-rootwrap in a ruby_block makes
node[:quantum][:rootwrap] exist too late to be used when populating
quantum.conf in the first chef-client run. This results in some failures
to use sudo, which are not critical but annoying.

Instead of proceeding this way we just default the path to
quantum-rootwrap to /usr/bin/quantum-rootwrap (correct path for
upstream, Ubuntu and SUSE), and keep the ruby_block to fix the path if
it's not the same. Things will still fail in the first chef-client run
if it's not the right path, but chef convergence will make it work for
later runs. And it now works directly in the first run in most cases.
Merge pull request #48 from vuntz/no-sqlite

Remove possibility to use sqlite
Merge pull request #49 from vuntz/no-keystone-copy

Remove attributes that exist only because of copy&paste from keystone
Merge pull request #50 from vuntz/admin-tenant

Do not hardcode admin tenant
Merge pull request #52 from vuntz/typo

Fix typo
Merge pull request #51 from vuntz/rootwrap-sudoers

Fix creation of /etc/sudoers.d/quantum-rootwrap
Merge pull request #53 from vuntz/install-package-first

Install quantum packages before doing anything else