This repository was archived by the owner on Apr 3, 2025. It is now read-only.
Support ZStack EIP and PortForwarding , Custom Init Scripts and DefaultL3Network #3
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.
Add four options: PublicNetwork(UUID), NetworkMode (Flat, EIP, PortForwarding), Custom Init Scripts Download Urls.
Automatically create an EIP or two PortForwarding rules and attach it/them to created VM, (only) when specified "NetworkMode" is not ZStack FlatNetwork (use EIP or PortForwarding).
The created EIP or PF rules will be deleted when VM is destroyed.
The VIP that created and referenced by EIP or PF rules will be "public address" (rke.cattle.io/external-ip), and the IPv4 address of first NIC of VM will be "private address" (rke.cattle.io/internal-ip)
Use L3NetworkUUID of first Nic as DefaultL3NetworkUUID
Fix go-zstack SDK bug (DefaultL3NetworkUUID should be defaultL3NetworkUUID in JSON region)
Execute Custom Init Scripts before and after "autoFdisk"