BZ #1056055 --  [RFE] create cinder-volumes VG backed by a loopback file

https://bugzilla.redhat.com/show_bug.cgi?id=1056055

The default behavior most customers expect for small to medium installations
is to run cinder-volume on the controller node. Packstack does this but
Foreman only allows a dedicated storage backend backed by iSCSI or RHS.
This patch deploys cinder-volume on the Nova or Neutron controller node if
cinder_backend_{iscsi,gluster} are both set to false. It will detect a VG
named cinder-volumes (whether backed by an iSCSI target or loopback device)
and share it via tgtd. The user must create the VG, which is also the case
with the cinder_backend_iscsi parameter for the LVM backend storage group. In
a sense this patch replicates functionality customers expect from packstack.
I tested it against the RHEL OSP 01.31.2014-1 puddle for both iSCSI and LVM
bakced Cinder from the controller node.
BZ #1056383 - Foreman Controller's swift proxy no longer runs ...

https://bugzilla.redhat.com/show_bug.cgi?id=1056383

Build the ringbuilder files on the proxy if no devices exist on its
ring files yet.
BZ #1063514 - cinder_gluster_servers default value in...

https://bugzilla.redhat.com/show_bug.cgi?id=1063514

In either controller host group, the params UI should display the
value for cinder_gluster_servers as an array of IPs, not
${$quickstack::params:cinder_gluster_servers}.
BZ #1049633 - Foreman should support VXLAN

https://bugzilla.redhat.com/show_bug.cgi?id=1049633

A couple of the variables inside the compute and networker classes were missing
the 'ovs_' part of the param name.
Merge pull request #124 from cwolferh/cinder_gluster_servers_fix_param_in_ui

BZ #1063514 -  cinder_gluster_servers default value in controller host groups is confusing
Merge pull request #117 from jliberma/bz1056055

BZ #1056055 --  [RFE] create cinder-volumes VG backed by a loopback file
Merge pull request #125 from jguiditta/vxlan_param_fix

BZ #1049633 - Foreman should support VXLAN
Merge pull request #114 from cwolferh/bz1056383_swift_ringbuilder_on_proxy

 BZ #1056383 - Foreman Controller's swift proxy no longer runs ...