What's new
Features for Private Network Support
The focus of this version is to provide a set of features and update existing commands to enable users to place virtual machines in private networks.
We provide a set of new commands to manage bridges, VLAN and VXLAN network devices on the KVM hosts.
list-bridge,register-bridge,unregister-bridgelist-vlan,register-vlan,unregister-vlanlist-vxlan,register-vxlan,unregister-vxlanlist-network-interfacevm-bridge-detach,vm-bridge-update
We also provide a mechanism to restrict some network devices used for node-wizard on the KVM host. From node-wizard, the KVM host admin can set which network devices/bridges can be used by virtual machines. By default, all the bridges are available to be used and none of network devices (physical and virtual) are available.
- Network devices:
list-allowed,add-allowed,delete-allowed - Bridges:
list-disallowed,add-disallowed,delete-disallowed
The list commands are also available from node-client.
Some customization is provided in VM creation for supporting private networks. Together with new networking features, this customization enables VMs to be in their own private networks.
- Bridge
- Gateway
- Name Server
Bridge for VM creation: The previous version has a hard-coded bridge name, br0External.
Now, users can change its name using set-host-env command or during node-wizard installation.
More Features
More customization in VM creation is provided for Ubuntu Server.
- log partition size
- Ubuntu repository to use
Some Kubernetes deployment places the ephemeral storage in /var/log partition. So, we need to change the log partition size. A private repository is a convenient feature for air-gapped environments.
Users can check the network bridges and network devices used by VM using vm-domain-info.
More OS support for node-client: Windows (amd64) and MacOS (amd64/arm64). Unlike Linux OS, only binary is provided. Auto-completion is not provided for these OSes.
Users can retrieve node-wizard log from node-client using system-log command.