Add validation for nova network ranges.

This adds validation for Public Floating Range and
Private Fixed Range.

In addition to the 'required' validation, this adds the following:
1) check for proper IP addr format
2) make sure the param specifies a *range* rather than a single address
3) check for range overlap by comparing the beginning and end of
   each range with the other range param.
Merge pull request #207 from sseago/nova-network-range-validation

Add validation for nova network ranges.
Refresh show page when deployment is in progress
Merge pull request #208 from mtaylor/refresh_deployment_page

Refresh show page when deployment is in progress
Added HA info to title on deployment detail page
Merge pull request #209 from jtomasek/ha_info_in_title

Added HA info to title on deployment detail page
Fixed HA/nonHA info in title
Merge pull request #210 from jtomasek/2ha_info_in_title

Fixed HA/nonHA info in title
version bump: 0.1.12
Merge pull request #211 from sseago/0.1.12-bump

version bump: 0.1.12
bz 1118502: set param type explicitly for erb params

for data seeding, we use the default value class to determine
the proper foreman/puppet param type. This doesn't work for the
dynamic params, since the object type is always a string -- i.e.
an erb snippet,but it doesn't always *evaluate* to a string,
as it could be an array or a hash.
Merge pull request #213 from sseago/BZ1118502

bz 1118502: set param type explicitly for erb params
Update import/export to include new wizard params
Merge pull request #198 from sseago/import-export

Update import/export to include new wizard params
For lvm cinder, use Ptable that includes cinder-volumes

If cinder backend is LVM, set the controller hostgroup's Ptable
to Ptable.find_by_name('LVM with cinder-volumes').

This ptable should possibly be referenced by a Setting object at some point
rather than relying on name matching.

At this point if the PTable isn't found, we just silently ignore it,
since this isn't yet in the installer and I don't want staypuft blowing up
over it. Once this is in the installer, we can consider the proper way
of handling this if the Ptable doesn't exist.

On initial testing this seems to work when switching back and forth
between LVM and NFS cinder storage in non-HA, and also on switching
between HA and non-HA where the cinder change comes along for the
ride.