My setup is up with sriov/pcie/ctrl-data single interface and eam.

You can use if you want to check things

10.204.216.61 - controller
All the files are here /root/contrail-ansible-deployer

Amudha, the pcie interface came up with name eth0 this time. 
[Amudha] - Did you mean eth20?
+++sandipd: It was eth0.When I brought up 2 pcie interfaces, they were ens160f0,ens160f1

ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.204.216.183  netmask 255.255.255.0  broadcast 10.204.216.255
        inet6 fe80::250:56ff:feaa:aa05  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:aa:aa:05  txqueuelen 1000  (Ethernet)
        RX packets 1690602  bytes 579191961 (552.3 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 171108  bytes 232670877 (221.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens192: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        inet6 fe80::250:56ff:febb:bb04  prefixlen 64  scopeid 0x20<link>
        ether 00:50:56:bb:bb:04  txqueuelen 1000  (Ethernet)
        RX packets 207  bytes 66846 (65.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 648 (648.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::225:90ff:fec7:7ff4  prefixlen 64  scopeid 0x20<link>
        ether 00:25:90:c7:7f:f4  txqueuelen 1000  (Ethernet)
        RX packets 127288  bytes 8523996 (8.1 MiB)
        RX errors 0  dropped 17  overruns 0  frame 0
        TX packets 140608  bytes 8934212 (8.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xfd400000-fd4fffff 

We need to fix the interface name something consistent for all kind of configuration of the ctrl-data interface.
[Amudha] - ctrl-data interface is a vmxnet3 interface and comes up as ens*. In case of PCI and SR-IOV interfaces,
they are ixgbe interfaces and will come up as eth* interfaces.

I have a script to give ip to the ctrl-data interface.If the the name  is not same for all the compute-vms,script will fail.
[Amudha] Can your script check for ens and eth* as well? And may be use the driver type for additional check if needed?..

Also will write a script to create bond .I would assume the interfaces names to be eth20 and eth21 for bond.
[Amudha] Should work with the current vmdk.

The vmwarephysicalinterface should also ideally be same for any kind of configuration for ctrl-data.That was the case for fab.It used to be always ‘eth1’
[Amudha] I am not sure about this.. Would think it to be eth2 in case of ctrl-data interface defined.

+++sandipd:It was always ‘eth1’.Please check the fab code and document attached

We have to get rid of the situation where vmwarephysicalinterface=ens192 for some case and vmwarephysicalinterface=ens224 for some other.
[Amudha] Each scenario creates different interfaces, and this is hidden from user. Would not prefer changing this in 5.0.1 beta. 
We can have a discussion once all are available, and see if it really needs changes.

+++sandipd:'Each scenario creates different interfaces’.This is the confusion and difficult to remember.We would definitely will have hard time debugging things going down the line.
                       We wont remember what is the interface in what scenario.Yes, I leave it to Sachin to decide on it.

Regards
Sandip