Made Vagrant environment working with recent changes

The changes in vrouter code in compute node - to make vhost0 dhcp etc was
causing issues on Vagrant setup.

This patch has below fixes for that.

* Set only one private interface to match with other environments
* Set the private interface to get IP from dhcp to match with other environments
 and also to vrouter to get ip from dhcp in the same network as other nodes.
* Added hiera data for consule agent bind_addr on role "cp" so that it bind to
 ip set on vhost0
Allow passing in more options to apply_resources through environment
Merge pull request #167 from hkumarmk/vagrant_fixes

Made Vagrant environment working with recent changes
Use up-to-date trusty image

This is needed to get a newer kernel so that Contrail won't crash it
once a VM gets a floating ip associated with it.
Added new role gcp to support contrail vgw

Contrail simple gateway (vgw) is used to provide external network connectivity
without any physical router, in test and development environments.

so gcp1 will be act as an edge router for virtual cloud/vagrant environment.

Since vgw cannot advertise its routes to any other system, one have to add route
manually to reach floating IPs.

In order to access default floating IP pool (100.1.0.0/24) from the machine in
side cloud network (say haproxy1), one have to add below route in it.

route add -net 100.1.0.0/24  gw 10.0.0.10 dev eth0

where 10.0.0.10 is gcp1 IP address, eth0 is the machine's interface by which it
connect to the gw, 100.1.0.0/24 is the floating IP network.

I am working on developing rjil::tempest, in which the code to add appropriate
route on tempest machine will be added as it is required for tempest to pass
floating IP tests.

Changes:

* Added service blocker on neutron for Contrail_vgw - I suspect there is a race
 condition between vgw and floating IP pool creation.

Note:

SPEC tests to be added on which I am working on.
This PR depends on PR #23 on jiocloud_contrail