Use json instead of regexp to parse subnet data
Use json instead of regexp to parse subnet data

The order of name/value pairs in the json string for allocation pools
and host routes is not guaranteed, and when it comes in a different
order from what the regular expression expects, it doesn't match and
causes the method to throw an unhandled exception when attempting to
extract values from matchdata.

Change-Id: I80dec4019a51943f0e04fcbb3be193b4a8d77745

plumgrid/puppet-neutron,CiscoSystems/puppet-neutron,openstack/puppet-neutron,fuel-infra/puppet-neutron,rdo-puppet-modules/puppet-neutron,openstack/puppet-neutron,IPnett/puppet-neutron,IPnett/puppet-neutron,IPnett/puppet-neutron,plumgrid/puppet-neutron,CiscoSystems/puppet-neutron,CiscoSystems/puppet-neutron,fuel-infra/puppet-neutron,rdo-puppet-modules/puppet-neutron,fuel-infra/puppet-neutron