Use inet_ntop
[lib/nfv] selftest.sh: Added timeout to `wait_vm_up'.
[core.app/core.lib] Moved `equal' from `core.app' to `core.lib'.
[unified conf] Replace all uses of `dofile' and `loadstring' with the
central `core.lib.load_conf' and `core.lib.load_string'.

Provide central `lib.load_conf' and `lib.store_conf' to read and write
config files and use `store_conf' to generate zone configurations in
`designs/neutron/neutron2snabb'.

Replace leftover string app args with table literals.
Merge pull request #309 from eugeneia/lib/nfv/selftest-timeout

[lib/nfv] selftest.sh: Added timeout to `wait_vm_up'.
Merge pull request #303 from dpino/fix-ntop

Use inet_ntop
Merge pull request #310 from eugeneia/unify-config

Unify NFV and app configuration
fix NFV tests to include rate_limiter
new rate_limited test
[neutron] Move tunnel and QoS into binding:profile

Move parameters from binding:vif_details into binding:profile. This
makes life easier for the Neutron administrator because
binding:profile can be updated at any time using 'neutron
port-update'. (vif_details is read-only to the administrator.) This
means that features like tunneling can be enabled/disabled dynamically
at any time.

The tunnel parameters are moved as-is.

Bandwidth rate limits are now specified with a specific
'rx_police_gbps' parameter. If this is specified then a strict rate
limit will be enforced at the given rate. This feature is orthogonal
to the vif_details.zone_gbps parameter, which does not represent a
strict limit (and is mostly used to share load across physical ports).
Merge Javier's rate_limiter fixes with the binding.profile branch.

Resolved conflict that binding.profile branch moved the rate limiter
configuration into a separate 'rx_police_gbps' paramter.
Removed `designs/nfv/nfv' in favor of `designs/neutron/snabbnfv-bench'.