Repository navigation
Add more control over network configs - #22
Merged
Merged
Conversation
… portgroup; allow configuration of other vswitches, networks, etc via userdata config
prwhitaker
force-pushed
the
config_control
branch
from
May 11, 2026 16:41
2a4a372 to
5186a06
Compare
cardoe
approved these changes
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Following the experience of using images created for newer versions of VCF, this PR introduces more control over the network setup that the esxi_netinit python code will generate.
It makes the following changes:
It also fixes a bug where the ESXi kickstart config was intended to reboot the host after executing the esxi_netinit code, but failed to do so (which leaves hosts in a state where when they are subsequently rebooted, they lose all network config)