https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-434 netvirt <p>odlparent's custom.properties carries a bunch of configuration:</p> <ol> <li>OVSDB configuration</li> <li>ovsdb plugin supports both active and passive connections. It listens on port 6640 by default for Active connections.<br/> ovsdb.listenPort=6640</li> </ol> <ol> <li>ovsdb creates Openflow nodes/bridges. This configuration configures the bridge's Openflow version.</li> <li>default Openflow version = 1.0, we also support 1.3.</li> <li>ovsdb.of.version=1.3</li> </ol> <ol> <li>ovsdb can be configured with ml2 to perform l3 forwarding. The config below enables that functionality, which is</li> <li>disabled by default.</li> <li>ovsdb.l3.fwd.enabled=yes</li> </ol> <ol> <li>ovsdb can be configured with ml2 to perform arp responder, enabled by default.<br/> ovsdb.l3.arp.responder.disabled=no</li> </ol> <ol> <li>ovsdb can be configured with ml2 to perform l3 forwarding. When used in that scenario, the mac address of the default</li> <li>gateway -<del>on the external subnet</del>- is expected to be resolved from its inet address. The config below overrides that</li> <li>specific arp/neighDiscovery lookup.</li> <li>ovsdb.l3gateway.mac=00:00:5E:00:02:01</li> </ol> <p>We have multiple better configuration primitives other than properties and this is a logical inter-project dependency loop. Remove it.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-434

remove configuration knobs from custom.properties

Bug Medium Resolved Done Sam Hague Robert Varga Tue, 17 Jan 2017 18:07:50 +0000 Fri, 6 Apr 2018 11:23:30 +0000 Fri, 6 Apr 2018 11:23:30 +0000 Carbon General 0 3 <p>OVSDB project was using only following config option, but it's not using it anymore, so it can be removed.</p> <p>ovsdb.listenPort=6640</p> <p>Remaining config options are related to netvirt project, and i believe those are still used by the old implementation of netvirt project. Moving this bug to netvirt project to take action on it.</p> <p>Adding Venkat as only the legacy netvirt would be using those properties - if still using them.</p> <p>Hi,</p> <p> Legacy Netvirt implemetation is still using these configuration paramater. Since it is not removed in Carbon, We need the below parameters</p> <ol> <li>ovsdb can be configured with ml2 to perform l3 forwarding. The config below enables that functionality, which is</li> <li>disabled by default.</li> <li>ovsdb.l3.fwd.enabled=yes</li> </ol> <ol> <li>ovsdb can be configured with ml2 to perform arp responder, enabled by default.<br/> ovsdb.l3.arp.responder.disabled=no</li> </ol> <ol> <li>ovsdb can be configured with ml2 to perform l3 forwarding. When used in that scenario, the mac address of the default</li> <li>gateway -<del>on the external subnet</del>- is expected to be resolved from its inet address. The config below overrides that</li> <li>specific arp/neighDiscovery lookup.</li> <li>ovsdb.l3gateway.mac=00:00:5E:00:02:01</li> </ol> <p>We can remove the same in master (Nitrogen).</p> <p>Legacy NetVirt is deprecated.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=shague" class="user-hover" rel="shague">shague</a> so if it is deprecated, this issue should remain open until it is actually removed and the properties need to go with it, right?</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga" class="user-hover" rel="rovarga">rovarga</a> this was a bulk move of anything with a legacy component. I moved the component to the new NetVirt and reopened.</p> <p><a href="https://git.opendaylight.org/gerrit/70383" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/70383</a></p> Blocks ODLPARENT-34 Development External issue ID 7571 External issue URL Issue Type Rank 0|i01rrz: