[NETVIRT-434] remove configuration knobs from custom.properties Created: 17/Jan/17  Updated: 06/Apr/18  Resolved: 06/Apr/18

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Robert Varga Assignee: Sam Hague
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Blocks
blocks ODLPARENT-34 Remove project-specific settings from... Resolved
External issue ID: 7571

 Description   

odlparent's custom.properties carries a bunch of configuration:

  1. OVSDB configuration
  2. ovsdb plugin supports both active and passive connections. It listens on port 6640 by default for Active connections.
    ovsdb.listenPort=6640
  1. ovsdb creates Openflow nodes/bridges. This configuration configures the bridge's Openflow version.
  2. default Openflow version = 1.0, we also support 1.3.
  3. ovsdb.of.version=1.3
  1. ovsdb can be configured with ml2 to perform l3 forwarding. The config below enables that functionality, which is
  2. disabled by default.
  3. ovsdb.l3.fwd.enabled=yes
  1. ovsdb can be configured with ml2 to perform arp responder, enabled by default.
    ovsdb.l3.arp.responder.disabled=no
  1. ovsdb can be configured with ml2 to perform l3 forwarding. When used in that scenario, the mac address of the default
  2. gateway -on the external subnet- is expected to be resolved from its inet address. The config below overrides that
  3. specific arp/neighDiscovery lookup.
  4. ovsdb.l3gateway.mac=00:00:5E:00:02:01

We have multiple better configuration primitives other than properties and this is a logical inter-project dependency loop. Remove it.

 Comments   
Comment by Anil Vishnoi [ 22/Feb/17 ]

OVSDB project was using only following config option, but it's not using it anymore, so it can be removed.

ovsdb.listenPort=6640

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.

Comment by Sam Hague [ 13/Apr/17 ]

Adding Venkat as only the legacy netvirt would be using those properties - if still using them.

Comment by Venkatrangan Govindarajan [ 20/Apr/17 ]

Hi,

Legacy Netvirt implemetation is still using these configuration paramater. Since it is not removed in Carbon, We need the below parameters

  1. ovsdb can be configured with ml2 to perform l3 forwarding. The config below enables that functionality, which is
  2. disabled by default.
  3. ovsdb.l3.fwd.enabled=yes
  1. ovsdb can be configured with ml2 to perform arp responder, enabled by default.
    ovsdb.l3.arp.responder.disabled=no
  1. ovsdb can be configured with ml2 to perform l3 forwarding. When used in that scenario, the mac address of the default
  2. gateway -on the external subnet- is expected to be resolved from its inet address. The config below overrides that
  3. specific arp/neighDiscovery lookup.
  4. ovsdb.l3gateway.mac=00:00:5E:00:02:01

We can remove the same in master (Nitrogen).

Comment by Sam Hague [ 09/Mar/18 ]

Legacy NetVirt is deprecated.

Comment by Robert Varga [ 09/Mar/18 ]

shague so if it is deprecated, this issue should remain open until it is actually removed and the properties need to go with it, right?

Comment by Sam Hague [ 09/Mar/18 ]

rovarga this was a bulk move of anything with a legacy component. I moved the component to the new NetVirt and reopened.

Comment by Sam Hague [ 05/Apr/18 ]

https://git.opendaylight.org/gerrit/70383

Generated at Wed Feb 07 20:21:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.