Few vmis not created in tor-agents in tor-scale setup

[Vedamurthy Joshi]

R2.20 30 Ubuntu 14.04 Juno multi-node setup

On this tor-scale setup, with 128 tors, each tor-agent has 1012 vmis (506 interfaces. Each interface in separate a vn having 2 vmis )

It is seen that the agent interface list does not show all 1012 interfaces (~10% intfs missing )

For ex : on ToR ovs-vm46 , interface ns21ovstap23, the lif 'ns21ovstap23lif' has 2 vmis

00:01:00:00:b5:a9 (10.120.192.156)
00:01:00:00:b5:a8 (10.120.192.155)

Only VMI for 00:01:00:00:b5:a9 got downloaded, but not 00:01:00:00:b5:a8

Agent ifmap config does have all 1012 interfaces though

For ex :
env.roledefs = {
    'all': [host2, host3, host4, host5, host6, host7, host8, host9],
    'cfgm': [host2, host3, host4],
    'openstack': [host2, host3, host4],
    'webui': [host3],
    'control': [host2, host3, host4],
    'compute': [host5, host6, host7, host8, host9],
    'collector': [host2, host3, host4],
    'database': [host2, host3, host4],
    'toragent': [host5, host6, host7, host9 ],
    'tsn': [host5, host6, host7,host9 ],
    'build': [host_build],
}

env.hostnames = {
    'all': ['nodei34', 'nodei35', 'nodei36', 'nodei37', 'nodei38', 'nodei28', 'nodei27', 'nodei30']
}

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11087
Submitter: Praveen K V (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11087
Committed: http://github.org/Juniper/contrail-controller/commit/4e049ceb274dd3ab84dd016382986dda3dab6f1c
Submitter: Zuul
Branch: R2.20

commit 4e049ceb274dd3ab84dd016382986dda3dab6f1c
Author: Praveen K V <email address hidden>
Date: Sun May 31 14:14:10 2015 +0530

Fix virtual-machine-interface config processing

Config processing for virtual-machine-interface (vmi) in case of
physical-router are created only if path from physical-router to VMI is
present. The path is,
physical-router <-> physical-interface <-> logical-interface <vmi>

The current code does not handle the case where physical-router to
physical-interface link comes after
physical-interface <-> logical-interface <-> vmi path is created

Method InterfaceTable::PhysicalInterfaceIFNodeToReq handles rebakes all
VMI when local physical-interface is created. The rebaking logic is
skipped in case of remote-physical-interace

Fix: Modifying InterfaceTable::PhysicalInterfaceIFNodeToReq to rebake
virtual-machine-interface even in case of remote-physical-interfaces

Fixes bug: #1459674

Change-Id: I5fc61018908e645b4e492a2006fb16672b0e1db9

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11217
Submitter: Praveen K V (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11217
Committed: http://github.org/Juniper/contrail-controller/commit/59e5b0ab4ccafd14bf30f6b5283adc4688cf0520
Submitter: Zuul
Branch: master

commit 59e5b0ab4ccafd14bf30f6b5283adc4688cf0520
Author: Praveen K V <email address hidden>
Date: Sun May 31 14:14:10 2015 +0530

Fix virtual-machine-interface config processing

Config processing for virtual-machine-interface (vmi) in case of
physical-router are created only if path from physical-router to VMI is
present. The path is,
physical-router <-> physical-interface <-> logical-interface <vmi>

The current code does not handle the case where physical-router to
physical-interface link comes after
physical-interface <-> logical-interface <-> vmi path is created

Method InterfaceTable::PhysicalInterfaceIFNodeToReq handles rebakes all
VMI when local physical-interface is created. The rebaking logic is
skipped in case of remote-physical-interace

Fix: Modifying InterfaceTable::PhysicalInterfaceIFNodeToReq to rebake
virtual-machine-interface even in case of remote-physical-interfaces

Fixes bug: #1459674

Change-Id: I5fc61018908e645b4e492a2006fb16672b0e1db9