Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

feat: Move creation of 'ext' HNS network into cse for Windows #2450

Merged
merged 2 commits into from Dec 17, 2019

Conversation

marosset
Copy link
Contributor

@marosset marosset commented Dec 12, 2019

Reason for Change:

Issue Fixed:

Fixes #2432

Requirements:

Notes:

@codecov
Copy link

codecov bot commented Dec 12, 2019

Codecov Report

Merging #2450 into master will increase coverage by 0.27%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2450      +/-   ##
==========================================
+ Coverage    72.3%   72.57%   +0.27%     
==========================================
  Files         130      130              
  Lines       23648    23916     +268     
==========================================
+ Hits        17098    17358     +260     
- Misses       5524     5530       +6     
- Partials     1026     1028       +2

@marosset
Copy link
Contributor Author

/cc @pradipd

@acs-bot acs-bot requested a review from pradipd December 12, 2019 23:56
@@ -275,12 +279,14 @@ try
-IdentitySystem "{{ GetIdentitySystem }}"
}

} elseif ($global:NetworkPlugin -eq "kubenet") {
New-ExternalHnsNetwork
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to clarify - is New-ExternalHnsNetwork not required for kubenet?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It isn't being created for kubenet today

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So i assume it isn't

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The removal is in the code block for if ($NetworkPlugin -eq "azure") { }

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe @pradipd or @dineshgovindasamy can comment on what scenarios we should create the ext HNS network?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be created if you want to prevent that brief network disconnect on reboot

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated to create the network for all network plugings.

}

# If there is more than one adapter, use the first adapter.
$managementIP = (Get-NetIPAddress -ifIndex $na[0].ifIndex -AddressFamily IPv4).IPAddress
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pradipd - should this be smarter? @dineshgovindasamy said there may be cases where a NIC doesn't have an IP and we should choose another?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is re: #2281

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Actually, the (Get-NetAdapter -Physical) on L261 needs to be different for acceleratedNetworkingEnabledWindows.
I just haven't had a chance to figure out what it should be.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Actually, the (Get-NetAdapter -Physical) on L261 needs to be different for acceleratedNetworkingEnabledWindows.
I just haven't had a chance to figure out what it should be.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pradipd ok - we'll consider that for a separate PR

Copy link
Contributor

@PatrickLang PatrickLang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@acs-bot
Copy link

acs-bot commented Dec 17, 2019

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marosset, PatrickLang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [PatrickLang,marosset]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@acs-bot acs-bot merged commit eed798e into Azure:master Dec 17, 2019
@marosset marosset deleted the win-ext-net-in-cse branch December 17, 2019 21:17
@marosset marosset added this to In progress in backlog Dec 18, 2019
@marosset marosset moved this from In progress to Done in backlog Dec 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
backlog
  
Done
Development

Successfully merging this pull request may close these issues.

Move 'ext' network creation into CSE provisioning for Windows nodes
5 participants