Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45596D636 for ; Wed, 21 Nov 2012 20:07:58 +0000 (UTC) Received: (qmail 70901 invoked by uid 500); 21 Nov 2012 20:07:57 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 70875 invoked by uid 500); 21 Nov 2012 20:07:57 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 70866 invoked by uid 99); 21 Nov 2012 20:07:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2012 20:07:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Jonathan.Bastin@peerpointinternet.co.uk designates 212.58.128.87 as permitted sender) Received: from [212.58.128.87] (HELO mail1.peerpointinternet.co.uk) (212.58.128.87) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2012 20:07:51 +0000 Received: from 7S2V3Q1 (78.86.176.61) by PPIEXCH1.peerpointinternet.co.uk (212.58.128.87) with Microsoft SMTP Server id 14.1.218.12; Wed, 21 Nov 2012 20:10:21 +0000 From: Jonathan Bastin To: References: <67EF18FDCA335F489B366120481AB6C5F69D73F611@BANPMAILBOX01.citrite.net> <007a01cdc808$deeba090$9cc2e1b0$@tls.net> <005801cdc81b$e5e75e30$b1b61a90$@peerpointinternet.co.uk> <006001cdc81f$40e78af0$c2b6a0d0$@peerpointinternet.co.uk> <99EF7882C313584A9F88BBA2D5BB6FD93C17942B@EGEXCMB02.oww.root.lcl> <006201cdc820$2f498b30$8ddca190$@peerpointinternet.co.uk> <6E004C34C1C59E45A35B4338808BC315013 0132F7028@SJCPMAILBOX01.citrite.net> <99EF7882C313584A9F88BBA2D5BB6FD93C17943B@EGEXCMB02.oww.root.lcl> <6E004C34C1C59E45A35B4338808BC3150130132F7035@SJCPMAILBOX01.citrite.net> In-Reply-To: <6E004C34C1C59E45A35B4338808BC3150130132F7035@SJCPMAILBOX01.citrite.net> Subject: RE: Multiple IP's to one instance Date: Wed, 21 Nov 2012 20:07:35 +0000 Message-ID: <006601cdc823$d9332270$8b996750$@peerpointinternet.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJzqmBs2MmwR1ihu0jzKG58kS4qYwEEq1CmAl4r2RoB1FMFhAF+d9MKAh8hGO8CKU20qwIYW1JTArnrhUICpDN+bwHiFJYJAQ5VE8kCX6LsYwGcd3gtAsr4khICyM6J9AMvw6ipASoEzeqVjn2/YA== Content-Language: en-gb X-Virus-Checked: Checked by ClamAV on apache.org Personally for immediate requirements multiple IP's per nic would surfice but also multiple nics to different networks as well could be a request. -----Original Message----- From: Hari Kannan [mailto:hari.kannan@citrix.com] Sent: 21 November 2012 20:05 To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance It is an interesting topic - as I see it, there seem to be some hypervisors/OS limitations (on virtual environments) that, while allowing multiple nics per VM, limit the number - so, by extending in 2 dimensions (multiple nics per vm and multiple ips per nics), you can extend the number of IPs per VM - for that reason, I can see the benefit. Another reason, could be that AWS supports both, so stay compatible and competitive, we may need to consider it. Plus, there may be technical challenges in implementin= g multiple nics in a Basic network zone (this I'm not sure, esp if it is even possible to have multiple IPs per nic on basic zone).. -----Original Message----- From: Boylan, James [mailto:JAMES.BOYLAN@orbitz.com] Sent: Wednesday, November 21, 2012 11:46 AM To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance Single NIC. I can definitely seeing situations where you would want to have multiple interfaces for managing the traffic within a VM. But I don't reall= y see the real benefit in a cloud environment for having a number of IPs assigned to one NIC. (Cloud environment not just a virtual environment.) -- James -----Original Message----- From: Hari Kannan [mailto:hari.kannan@citrix.com] Sent: Wednesday, November 21, 2012 1:42 PM To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance @James: Are you saying there is no benefit in having a single VM having multiple IPs or a single NIC having multiple IPs? -----Original Message----- From: Jonathan Bastin [mailto:jonathan.bastin@peerpointinternet.co.uk] Sent: Wednesday, November 21, 2012 11:41 AM To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance But if customer requests it then you need to provide it. May people use IP locking than port locking for SSL certs. -----Original Message----- From: Boylan, James [mailto:JAMES.BOYLAN@orbitz.com] Sent: 21 November 2012 19:37 To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance I don't actually see the benefit of this. It really goes against the whole point of a Cloud environment. You shouldn't find yourself in a situation where you need multiple IPs per interface. -- James -----Original Message----- From: Jonathan Bastin [mailto:jonathan.bastin@peerpointinternet.co.uk] Sent: Wednesday, November 21, 2012 1:35 PM To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance I said to fill my request it would need to work on advanced with the guest network as this is where the pool sits. I also request this on a shared and an isolated network. -----Original Message----- From: Anthony Xu [mailto:Xuefei.Xu@citrix.com] Sent: 21 November 2012 19:29 To: cloudstack-users@incubator.apache.org Subject: RE: Multiple IP's to one instance Where is FS for this feature? Will this feature be added to basic zone? If that's the case, Security group needs to be changed, otherwise the second I= P will not work because of anti-spoofing. Anthony > -----Original Message----- > From: Jonathan Bastin [mailto:jonathan.bastin@peerpointinternet.co.uk] > Sent: Wednesday, November 21, 2012 11:11 AM > To: cloudstack-users@incubator.apache.org > Subject: RE: Multiple IP's to one instance > > I suggested that a few emails back and ultimately that is the quickest > way and a dev did post back to say they were working on it for release > 4.1 if it makes it. > > -----Original Message----- > From: Clayton Weise [mailto:cweise@iswest.net] > Sent: 21 November 2012 18:23 > To: cloudstack-users > Subject: RE: Multiple IP's to one instance > > Given that limitation, couldn't CloudStack just take whatever steps > necessary to make sure that the IP address doesn't get assigned to > anything else and let the user manually add that second address? It > just seems easier > > -----Original Message----- > From: Facundo Guerrero [mailto:fguerrero@ipaddress.com.ar] > Sent: Wednesday, November 21, 2012 9:50 AM > To: cloudstack-users > Subject: Re: Multiple IP's to one instance > > KVM has a limit of 8 nic's per VM. and there is no limit for multimes > ip's on the same nic. > > *Facundo Guerrero* > *System Administrator* > *IPaddress integradores de soluciones* > Tel: (54 11) 6009-5800 int 117 > GPG ID: 0x14F4C737 > fguerrero@ipaddress.com.ar > *www.ipaddress.com.ar* > > > > > 2012/11/21 Chip Childers > > > On Wed, Nov 21, 2012 at 12:34 PM, Anthony Xu > wrote: > > > CS manages User VM IP through DHCP service, I'm not sure DHCP can > > deliver two IPs for one MAC/NIC. > > > I agree that multiple NICs is easier than multiple IPs on same NIC. > > > > Since they are virtual hardware anyway, it's logical to just create > > new interfaces instead of dealing with the difficulties of multiple > > IPs per NIC. > > > > > Anthony > > > > > > > > > > > >> -----Original Message----- > > >> From: Matthew Hartmann [mailto:mhartmann@tls.net] > > >> Sent: Wednesday, November 21, 2012 8:54 AM > > >> To: cloudstack-users@incubator.apache.org > > >> Subject: RE: Multiple IP's to one instance > > >> > > >> What would be really neat is if you could have multiple NICs per > VM > > >> without having to have multiple virtual networks. For example, if > > >> I'm hosting a shared web server and need to host multiple SSL > > >> websites, I'm going to need not just multiple public IPs but > > >> multiple NICs as well on the VM. IMO, I believe this would be > > >> easier than trying to manage multiple IPs on one VIF. > > >> > > >> Matthew Hartmann > > >> Systems Administrator | V: 812.378.4100 x 850 | E: > > >> mhartmann@tls.net > > >> > > >> TLS.NET, Inc. > > >> http://www.tls.net > > >> > > >> -----Original Message----- > > >> From: Jonathan Bastin > > >> [mailto:Jonathan.Bastin@peerpointinternet.co.uk] > > >> Sent: Monday, November 19, 2012 1:35 PM > > >> To: cloudstack-users@incubator.apache.org > > >> Subject: Re: Multiple IP's to one instance > > >> > > >> It should be what ever the user wishes to allocate per single nic > > >> > > >> Regards, > > >> > > >> > > >> Jonathan Bastin > > >> 07739668262 > > >> > > >> ----- Reply message ----- > > >> From: "Anthony Xu" > > >> To: "cloudstack-users@incubator.apache.org" > > >> > > >> Subject: Multiple IP's to one instance > > >> Date: Mon, Nov 19, 2012 18:21 > > >> > > >> > > >> > > >> 'multiple IP's per NIC on guest VM' > > >> > > >> Does that mean there is one NIC in guest VM, and there are more > > >> than one IPs on this guest NIC? > > >> > > >> Can you elaborate more how you are going to implement it? > > >> > > >> > > >> Anthony > > >> > > >> > -----Original Message----- > > >> > From: Jayapal Reddy Uradi > > >> > [mailto:jayapalreddy.uradi@citrix.com] > > >> > Sent: Monday, November 19, 2012 3:50 AM > > >> > To: cloudstack-users@incubator.apache.org > > >> > Subject: RE: Multiple IP's to one instance > > >> > > > >> > I will work on this feature 'multiple IP's per NIC on guest VM'. > > >> Hope > > >> > fully it will come in 4.1 release. > > >> > > > >> > Thanks, > > >> > Jayapal > > >> > > > >> > > On 16/11/12 4:20 PM, "Geoff Higginbottom" > > >> > > wrote: > > >> > > > > >> > > >This gets my vote > > >> > > > > > >> > > >Regards > > >> > > > > > >> > > >Geoff > > >> > > > > > >> > > > > > >> > > >-----Original Message----- > > >> > > >From: Jonathan Bastin > > >> > [mailto:jonathan.bastin@peerpointinternet.co.uk] > > >> > > >Sent: 16 November 2012 10:00 > > >> > > >To: cloudstack-users@incubator.apache.org > > >> > > >Subject: RE: Multiple IP's to one instance > > >> > > > > > >> > > >Everybody wanting this please vote for it and see if we can > > >> > > >get > > >> this > > >> > to > > >> > > >happen. > > >> > > > > > >> > > >-----Original Message----- > > >> > > >From: Facundo Guerrero [mailto:fguerrero@ipaddress.com.ar] > > >> > > >Sent: 16 November 2012 03:25 > > >> > > >To: cloudstack-users > > >> > > >Subject: Re: Multiple IP's to one instance > > >> > > > > > >> > > >I not use the dhcp server to assign the ip into the vm. i > only > > >> made > > >> > nat > > >> > > >1:1 to other ip's in the network, then i add the new ip into > > >> > > >the > > >> vm > > >> > as > > >> > > >eth0:1, eth0:2. > > >> > > > > > >> > > >Jira link > > > >> > > >https://issues.apache.org/jira/browse/CLOUDSTACK-24 > > >> > > > > > >> > > >I'll send you the modifications that i made to the script. > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > >2012/11/15 Clayton Weise > > >> > > > > > >> > > >> Also, what is your bug ID for this feature request so we > can > > >> vote > > >> > on it. > > >> > > >> > > >> > > >> -----Original Message----- > > >> > > >> From: Facundo Guerrero [mailto:fguerrero@ipaddress.com.ar] > > >> > > >> Sent: Thursday, November 15, 2012 5:00 PM > > >> > > >> To: cloudstack-users@incubator.apache.org > > >> > > >> Subject: Re: Multiple IP's to one instance > > >> > > >> > > >> > > >> Jonathan > > >> > > >> > > >> > > >> Thats is not possible yet, i open a feature request asking > > >> > > >> for > > >> > this. > > >> > > >> I made some hacks on the virtual router to add more that > > >> > > >> open IP > > >> > on > > >> > > >> the same > > >> > > >VM. > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> 2012/11/15 Jonathan Bastin > > >> > > > >> > > >> > > >> > > >> > I have made a guest network (cloudstack implementation > > >> advanced > > >> > > >> > networking) with live IP's that is a shared network. > > >> > > >> > What I > > >> want > > >> > to > > >> > > >> > know > > >> > > >> is > > >> > > >> > how to I assign more than one IP to an instance without > > >> > > >> > using > > >> an > > >> > > >> > isolated network with a router. I literally want to > assign > > >> > > >> > say > > >> 5 > > >> > > >> > IP's to one instance. > > >> > > >> > > > >> > > >> ---------------------------------------------------------- > > >> > > >> - > - > > >> > > >> ---- > > >> -- > > >> > --- > > >> > > >> - > > >> > > >> ---------------------------------------------------- > > >> > > >> > This email (including any attachments) is intended only > > >> > > >> > for > > >> the > > >> > > >> > recipient(s) named above. It may contain confidential or > > >> > privileged > > >> > > >> > information and should not be read, copied or otherwise > > >> > > >> > used > > >> by > > >> > any > > >> > > >> > other person. If you are not the named recipient please > > >> contact > > >> > the > > >> > > >> > sender and delete the email from your system. The > author's > > >> > > >> > incumbent expressions, views and thoughts are their own > > >> > > >> > and > > >> not > > >> > > >> > necessarily representative of those of the Peer Point > > >> > > >> > Internet > > >> > Ltd > > >> > > >> > or associated > > >> > > >companies. > > >> > > >> > > > >> > > >> > > >> > > > > > >> > > >------------------------------------------------------------ > > >> > > >- > - > > >> > > >---- > > >> -- > > >> > --- > > >> > > >--- > > >> > > >------------------------------------------------ This email > > >> > (including > > >> > > >any attachments) is intended only for the recipient(s) named > above. > > >> > It > > >> > > >may contain confidential or privileged information and > > >> > > >should not > > >> be > > >> > > >read, copied or otherwise used by any other person. If you > are > > >> > > >not > > >> > the > > >> > > >named recipient please contact the sender and delete the > email > > >> from > > >> > > >your system. The author's incumbent expressions, views and > > >> thoughts > > >> > are > > >> > > >their own and not necessarily representative of those of the > > >> > > >Peer > > >> > Point > > >> > > >Internet Ltd or associated companies. > > >> > > > > > >> > > >ShapeBlue provides a range of strategic and technical > > >> > > >consulting > > >> and > > >> > > >implementation services to help IT Service Providers and > > >> Enterprises > > >> > to > > >> > > >build a true IaaS compute cloud. ShapeBlue=B9s expertise, > > >> > > >combined > > >> > with > > >> > > >CloudStack technology, allows IT Service Providers and > > >> > > >Enterprises > > >> > to > > >> > > >deliver true, utility based, IaaS to the customer or end-user. > > >> > > > > > >> > > >________________________________ > > >> > > > > > >> > > >This email and any attachments to it may be confidential and > > >> > > >are intended solely for the use of the individual to whom it > > >> > > >is > > >> > addressed. > > >> > > >Any views or opinions expressed are solely those of the > author > > >> > > >and > > >> > do > > >> > > >not necessarily represent those of Shape Blue Ltd. If you > > >> > > >are not > > >> > the > > >> > > >intended recipient of this email, you must neither take any > > >> > > >action based upon its contents, nor copy or show it to anyone. > > >> > > >Please > > >> > contact > > >> > > >the sender if you believe you have received this email in > error. > > >> > Shape > > >> > > >Blue Ltd is a company incorporated in England & Wales. > > >> > > > > > >> > > > > >> > > >> ----------------------------------------------------------------- > > >> - > - > > >> ---- > > >> ----- > > >> ---------------------------------------------- This email > > >> (including any > > >> attachments) is intended only for the recipient(s) named above. > > >> It may contain confidential or privileged information and should > > >> not be read, copied or otherwise used by any other person. If you > > >> are not the named recipient please contact the sender and delete > > >> the email from your system. > > >> The author's incumbent expressions, views and thoughts are their > > >> own and not necessarily representative of those of the Peer Point > > >> Internet Ltd or associated companies. > > > > > > > > > > ---------------------------------------------------------------------- > - > --------------------------------------------------- This email > (including any attachments) is intended only for the recipient(s) > named above. It may contain confidential or privileged information and > should not be read, copied or otherwise used by any other person. If > you are not the named recipient please contact the sender and delete > the email from your system. The author's incumbent expressions, views > and thoughts are their own and not necessarily representative of those > of the Peer Point Internet Ltd or associated companies. ---------------------------------------------------------------------------= - ---------------------------------------------- This email (including any attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not the named recipient please contact the sender and delete the email from your system. The author's incumbent expressions, views and thoughts are their own and no= t necessarily representative of those of the Peer Point Internet Ltd or associated companies. ---------------------------------------------------------------------------= - ---------------------------------------------- This email (including any attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not the named recipient please contact the sender and delete the email from your system. The author's incumbent expressions, views and thoughts are their own and no= t necessarily representative of those of the Peer Point Internet Ltd or associated companies. ---------------------------------------------------------------------------= ----------------------------------------------- This email (including any a= ttachments) is intended only for the recipient(s) named above. It may conta= in confidential or privileged information and should not be read, copied or= otherwise used by any other person. If you are not the named recipient ple= ase contact the sender and delete the email from your system. The author's = incumbent expressions, views and thoughts are their own and not necessarily= representative of those of the Peer Point Internet Ltd or associated compa= nies.