Skip to content

Conversation

@heypnus
Copy link
Contributor

@heypnus heypnus commented Aug 4, 2021

In IPI + NSX-T impactor, the node LSP's addresses are in
discovered_bindings instead of realized_bindings.

This patch also will remove some stale functions. In previous NSX-T,
the addresses locate in both realized_bindings and discovered_bindings,
so we don't need to worry about the upgrade case.

@heypnus heypnus force-pushed the node_controller/discovered_bindings branch from 9679075 to 839e760 Compare August 4, 2021 05:39
@heypnus heypnus force-pushed the node_controller/discovered_bindings branch from 839e760 to c0bf2b4 Compare September 23, 2021 08:08
@heypnus heypnus changed the title [WIP] Expand the port address matching range to DiscoveredBindings Expand the port address matching range to DiscoveredBindings Sep 23, 2021
@heypnus heypnus changed the title Expand the port address matching range to DiscoveredBindings Search node address in port's DiscoveredBindings instead RealizedBindings Sep 23, 2021
@heypnus heypnus force-pushed the node_controller/discovered_bindings branch 2 times, most recently from d9dcb42 to 38e8541 Compare September 23, 2021 08:49
…ings

In IPI + NSX-T impactor ufo, the node LSP's addresses are in
discovered_bindings instead of realized_bindings. In previous NSX-T,
the addresses locate in both realized_bindings and discovered_bindings,
so we don't need to worry about the upgrade case.

This patch also will remove some stale functions.
@heypnus heypnus force-pushed the node_controller/discovered_bindings branch from 38e8541 to 5e85f71 Compare September 23, 2021 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants