Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3C3EFEDF8 for ; Thu, 17 Jan 2013 20:59:08 +0000 (UTC) Received: (qmail 55716 invoked by uid 500); 17 Jan 2013 20:59:07 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 55612 invoked by uid 500); 17 Jan 2013 20:59:07 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 55603 invoked by uid 99); 17 Jan 2013 20:59:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 20:59:07 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Alex.Huang@citrix.com designates 66.165.176.63 as permitted sender) Received: from [66.165.176.63] (HELO SMTP02.CITRIX.COM) (66.165.176.63) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 20:59:03 +0000 X-IronPort-AV: E=Sophos;i="4.84,486,1355097600"; d="scan'208";a="3935472" Received: from sjcpmailmx02.citrite.net ([10.216.14.75]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Jan 2013 20:58:42 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX02.citrite.net ([10.216.14.75]) with mapi; Thu, 17 Jan 2013 12:58:42 -0800 From: Alex Huang To: "cloudstack-dev@incubator.apache.org" Date: Thu, 17 Jan 2013 12:58:43 -0800 Subject: RE: [DISCUSS] IPv6 support draft functional spec(phase 1) Thread-Topic: [DISCUSS] IPv6 support draft functional spec(phase 1) Thread-Index: Ac307RI1ppxwsS4FQLWrGJfSopGENAAACyVw Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Sheng, Can you add in that SG does not support IPv6? Make sure everyone knows tha= t. --Alex > -----Original Message----- > From: Sheng Yang [mailto:sheng@yasker.org] > Sent: Thursday, January 17, 2013 11:58 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: [DISCUSS] IPv6 support draft functional spec(phase 1) >=20 > On Thu, Jan 17, 2013 at 10:38 AM, Sheng Yang wrote: > > On Thu, Jan 17, 2013 at 10:33 AM, Anthony Xu > wrote: > >> More comments, > >> > >> Can VM access VM by name on IPv6 network( router VM provide DNS > service ?)? > > > > Yes, dnsmasq would provide AAAA records. > > > >> Is password-reset service supported on IPv6 network? > > > > Should be in the future, but not phase 1, which only provide DNS and DH= CP. > > > >> Is meta-data and user-data service supported on IPv6 network? > > > > Not phase 1. > > > >> Is external network device (F5, SRX) supported on IPv6 network? > > > > Not in the plan. > > > >> What's the impact for Security enabled shared network? > > > > Not in the plan. Only support shared network without SG in the phase 1. > > > >> What's the impact for multiple IPs per NIC? > > > > I guess we may no longer need to have another nic for different public > > subnet, but need to be confirmed. >=20 > So I would update the systemvm first, adding the newer version of > dnsmasq and radvd. >=20 > Does anyone has specific suggestion on which version to be used? I can > get the dnsmasq from debian testing repo and it works for me. Radvd > can be get from debian stable repo, but I assume it maybe kind of old. >=20 > --Sheng > > > > --Sheng > >> > >> Anthony > >> > >>> -----Original Message----- > >>> From: Sheng Yang [mailto:sheng@yasker.org] > >>> Sent: Thursday, January 17, 2013 10:26 AM > >>> To: cloudstack-dev@incubator.apache.org > >>> Subject: Re: [DISCUSS] IPv6 support draft functional spec(phase 1) > >>> > >>> On Thu, Jan 17, 2013 at 10:20 AM, Anthony Xu > >>> wrote: > >>> > My misunderstanding, I thought that's the link-local ip in Xenserve= r > >>> or KVM:-) > >>> > > >>> > If a VM is on both IPv6 and IPv4 network, what's the link-local > >>> address? IPv4? IPv6? Both? > >>> > >>> For dual stack case, we still require IPv6 link-local address only. > >>> > >>> --Sheng > >>> > > >>> > > >>> > Anthony > >>> > > >>> >> -----Original Message----- > >>> >> From: Sheng Yang [mailto:sheng@yasker.org] > >>> >> Sent: Thursday, January 17, 2013 10:13 AM > >>> >> To: cloudstack-dev@incubator.apache.org > >>> >> Subject: Re: [DISCUSS] IPv6 support draft functional spec(phase 1) > >>> >> > >>> >> On Thu, Jan 17, 2013 at 9:49 AM, Anthony Xu > >>> >> wrote: > >>> >> > Thanks for the write-up, > >>> >> > > >>> >> > One comment, > >>> >> > Is there any reason not use link-local IPv4 address? > >>> >> > > >>> >> >>*User VM would have one link-local IPv6 address > >>> >> > >>> >> IPv6 required one auto configured link local address per nic(means > >>> >> likely one nic would have more than one IP address, and in the > >>> >> different subnet), and the link local address would be used to sen= d > >>> >> out DHCP request etc(http://tools.ietf.org/html/rfc3315). It's als= o > >>> >> the basic of Neighbor discovery mechanism in > >>> >> IPv6(http://tools.ietf.org/html/rfc4861). > >>> >> > >>> >> I think IPv4 link-local is less relevant in this case... > >>> >> > >>> >> --Sheng > >>> >> > > >>> >> >> -----Original Message----- > >>> >> >> From: Sheng Yang [mailto:sheng@yasker.org] > >>> >> >> Sent: Wednesday, January 16, 2013 7:11 PM > >>> >> >> To: cloudstack-dev@incubator.apache.org > >>> >> >> Subject: [DISCUSS] IPv6 support draft functional spec(phase 1) > >>> >> >> > >>> >> >> Hi, > >>> >> >> > >>> >> >> The first draft of IPv6 FS is available at > >>> >> >> > >>> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+support > >>> >> >> now. > >>> >> >> > >>> >> >> Basically based on our previous discussion, we would like to > >>> stick > >>> >> to > >>> >> >> dnsmasq, and assume shared network for advance zone in the > phase > >>> one, > >>> >> >> to make thing as simple as possible in phase 1. > >>> >> >> > >>> >> >> Comments/questions are welcome! > >>> >> >> > >>> >> >> --Sheng