I also argue that what they are asking for really is in conflict of the purpose of a cloud environment. If you are merely after a virtualized environment you can use vsphere, kvm with virt-manager or xenserver. Multiple IPs per nic do nothing to improve the performance or the functionality of a cloud environment.
Going down the road of adding features like that would be taking valuable development time away from tasks and features that actually benefit a cloud architecture. While I do understand their issue, there are other ways of implementing what they are listing as reasons that is cloud architecture friendly. (using NAT and isolated private networks for one) -- James ----- Original Message ----- From: David Nalley [mailto:da...@gnsa.us] Sent: Wednesday, November 21, 2012 06:12 PM To: cloudstack-users@incubator.apache.org <cloudstack-users@incubator.apache.org> Subject: Re: Multiple IP's to one instance > - it is expected that there is a 'primary ip' assigned by DHCP and the > additional ips are assigned manually by the VM owner. However additional > ips are requested through CS API/UI. I am conflicted on this - I know the limitations with adding additional interfaces. I'd almost argue for requiring number of interfaces/IPs to be set at machine instantiation and still handing out addresses to all interfaces via DHCP, but not all OSes will handle that cleanly.
