Yes, anyone doing hosting will view this as a critical requirement for self-service infrastructure. This is true for SPs like you mention but also a private cloud supporting multiple web sites.
-kevin > -----Original Message----- > From: Clayton Weise [mailto:cwe...@iswest.net] > Sent: Wednesday, November 21, 2012 6:41 PM > To: 'cloudstack-users@incubator.apache.org' > Subject: RE: Multiple IP's to one instance > > > I also argue that what they are asking for really is in conflict of the > > purpose of > a cloud environment. > > I think this depends on the scope of who the cloud owner is. If the owner is > a > single organization then yes, I would agree. However if the owner is a > service > provider, than I would disagree. I know there are larger things on the table > for > the ACS crew, so I'm not going to try and make a judgment call here as to how > they should prioritize because that's really more up to the community at large > and what kind of feedback they get from their paying clients (CloudPlatform) > as > well. And that's not something I think either of us have the data to make a > decision on. > > That being said, I don't know what kind of work is involved in adding a > feature > like this, and how much it would actually detract from the future development > of ACS. I know it's something that has come up in IRC on more than a few > occasions and it's not the first time we've seen it on the mailing list > either. I > would also encourage anybody involved in the community with the skills > required to work out a tech spec on this and put something more formal > together. I think part of the issue has been the fact (as we've seen) that > there > isn't a solid consensus on how to even accomplish this, let alone the specific > mechanics of how it will work. > > -----Original Message----- > From: Boylan, James [mailto:james.boy...@orbitz.com] > Sent: Wednesday, November 21, 2012 5:51 PM > To: 'cloudstack-users@incubator.apache.org' > Subject: Re: Multiple IP's to one instance > > 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- > us...@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.
