Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows] CNI Server installs OpenFlow entries after PortStatus messa… #95

Closed
wants to merge 1 commit into from

Conversation

wenyingd
Copy link
Owner

…ge is received

@wenyingd wenyingd force-pushed the async_ofport_1 branch 6 times, most recently from 757a336 to 47421ff Compare October 24, 2024 11:15
@wenyingd wenyingd force-pushed the async_ofport_1 branch 11 times, most recently from 323802c to 2bc767d Compare October 30, 2024 09:39
@wenyingd wenyingd force-pushed the async_ofport_1 branch 11 times, most recently from 84227c7 to aa69c18 Compare November 4, 2024 07:46
@wenyingd wenyingd force-pushed the async_ofport_1 branch 8 times, most recently from fa183af to 8244728 Compare November 5, 2024 10:34
…ge is received

This change has introduced a worker in `podConfigurator` to listen for the
OpenFlow PortStatus message when a new OpenFlow port is allocated in OVS. After
receiving the message, antrea-agent Windows will install Pod related OpenFlow
entries. If the OpenFlow port is not allocated within 30s after the CmdAdd
request is responded, an event with type "NetworkNotReady" is added on the Pod;
Whenever the Pod networking forwarding rules are installed, an event with type
"NetworkIsReady" is added.

Signed-off-by: Wenying Dong <wenyingd@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant