Add two options to barclamp UI and handle them in chef too

We add support for the cpu_allocation_ratio/ram_allocation_ratio options for
nova-scheduler (ram_allocation_ratio was already a chef attribute, but with a
value not changeable in the barclamp).

Signed-off-by: Vincent Untz <vuntz@suse.com>
(cherry picked from commit 03623e9fbbd656509480c1a36e322c5d8ffce595)

Signed-off-by: Michal Jura <mjura@suse.com>

Conflicts:
	chef/cookbooks/nova/attributes/default.rb
	crowbar.yml
	crowbar_framework/app/views/barclamp/nova/_edit_attributes.html.haml
Remove auto_assign_floating_ip option again

This does not make sense when using quantum
default cpu_allocation_ratio to 16

this provides continuity with previous versions of SUSE Cloud 1.0
(cherry picked from commit 5eece7aa1bc5a0b57fcce166bc22820f660e0727)

Signed-off-by: Michal Jura <mjura@suse.com>

Conflicts:
	crowbar_framework/app/views/barclamp/nova/_edit_attributes.html.haml
Do not mark new options as required

This creates an issue for existing proposals, since the JSON data will
only have the new options if they get changed; most users trying to save
will face an error because of the schema.

Having them not required is okay since the cookbooks is using a sane
default for the values.
(cherry picked from commit e035f0bc1b5c74fc71ee88fd5635c935d5551c88)

Signed-off-by: Michal Jura <mjura@suse.com>
Remove nova user attribute for the proposals

There is no good reason to change the defaults from the default attributes.
use public method file_edited?

file_edited is not exposed in chef, so we have patched our rubygem-chef
package to expose this for now
Repairing nova.conf.erb template with nova.virt.driver
nova-compute doesn't need database