-
Notifications
You must be signed in to change notification settings - Fork 260
Add Host NC communication support in Windows with HnsV2 #424
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
Add Host NC communication support in Windows with HnsV2 #424
Conversation
…w-vm-container-experiment
…w-vm-container-experiment
Codecov Report
@@ Coverage Diff @@
## master #424 +/- ##
=======================================
Coverage 52.66% 52.66%
=======================================
Files 28 28
Lines 4022 4022
=======================================
Hits 2118 2118
Misses 1631 1631
Partials 273 273Continue to review full report at Codecov.
|
tamilmani1989
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added minor comments. lgtm
| // Following code calculates the subnet prefix from localIPConfiguration IP | ||
| // e.g. IP: 169.254.128.7 Prefix length: 17 then resulting subnet prefix: 169.254.128.0/17 | ||
| // subnetPrefix: ffff8000 | ||
| // subnetPrefix.IP: 169.254.128.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add a todo with workitem
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the workitem here:
https://msazure.visualstudio.com/One/_workitems/edit/5582928/
This PR adds support for host NC bidirectional communication with windows HnsV2. This is supported in multitenant scenario only. AllowHostToNCCommunication and AllowNCToHostCommunication flags are used to enable Host to NC and NC to host communication respectively.
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: