Having different IPs per server

Got Ubuntu 16.04 and i am wondering about this:

Got a new server to setup with Cloudmin Pro and want to have 3 virtual machines (one Windows, probably with KVM, two linux'es perhaps with lxc but without lxd). My server has 4 different public IP's i could use. When i read about lxc and cloudmin, i would normally use internal IP's. Can i use public IP's as well and how would i setup them? Also, if i am using kvm and lxc, will Cloudmin take care of installing everything it needs or would i need to do this beforehand? This server hosts several virtual hosts at the moment, which i move to a different one, in order to be able to setup this one with Cloudmin Pro. Any best practice for that?

Thanks and best

Status: 
Active

Comments

Howdy -- yeah it should be no problem to use public IP's, and I believe that's what most folks use (though to be fair most of my experience is with KVM and Xen).

Are you seeing something somewhere that's suggesting internal IP's?

The Cloudmin installer will install a number of basic packages during the installation process, though the Cloudmin documentation may have you install a handful of packages for the particular Virtual Machine type you're looking to use.

The Cloudmin documentation explains which packages you need, as well as how to go about configuring bridging, and adding IP addresses.

These links should help you get started:

https://www.virtualmin.com/documentation/cloudmin/virtualization/lxc

https://www.virtualmin.com/documentation/cloudmin/virtualization/kvm

https://www.virtualmin.com/documentation/cloudmin/vm/create-kvm

If i am using different public IP's? The last time i locked me out by trying to bridge interfaces ;-)

What am i trying to say is: If i have more virtual machines than public ip's i usually need bridging, correct But if i have 4 public IPs and one of them for the host system, would i need for three vm's network bridging, given i can access all systems while using my public ip's? And how would i need to setup my eth0 interface for this?

You don't need one bridge per VM. Typically, the host system has an eth0 interface (with no IP) which is connected to a br0 bridge that has an IP. VMs are also connected to the bridge, and have their own IPs - typically public. However, it's perfectly OK to have a VM with a private IP (like 192.168.1.2), but you would need to create a br0:1 virtual interface on the host with an IP in the same private range for it to work.