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 6DAE2E795 for ; Sat, 12 Jan 2013 05:37:12 +0000 (UTC) Received: (qmail 36541 invoked by uid 500); 12 Jan 2013 05:37:11 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 36140 invoked by uid 500); 12 Jan 2013 05:37:09 -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 36098 invoked by uid 99); 12 Jan 2013 05:37:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2013 05:37:08 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of animesh.chaturvedi@citrix.com designates 66.165.176.89 as permitted sender) Received: from [66.165.176.89] (HELO SMTP.CITRIX.COM) (66.165.176.89) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Jan 2013 05:37:02 +0000 X-IronPort-AV: E=Sophos;i="4.84,456,1355097600"; d="scan'208";a="3542241" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Jan 2013 05:36:40 +0000 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.72]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Fri, 11 Jan 2013 21:36:39 -0800 From: Animesh Chaturvedi To: "cloudstack-dev@incubator.apache.org" Date: Fri, 11 Jan 2013 21:36:32 -0800 Subject: Re: [IP Clearance] Potential issues Thread-Topic: [IP Clearance] Potential issues Thread-Index: Ac3whssTaSjgINjgRequNhl3Hs6OMA== Message-ID: References: <7A92FF96DF135843B4B608FB576BFC3E012DA300EB62@SJCPMAILBOX01.citrite.net> <6876970739769119213@unknownmsgid> In-Reply-To: <6876970739769119213@unknownmsgid> 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 Yes I will include docs as well.=20 Thanks Animesh On Jan 11, 2013, at 7:03 PM, "Chip Childers" wr= ote: > On Jan 11, 2013, at 7:17 PM, Alex Huang wrote: >=20 >> Animesh, >>=20 >> Can you also work with Jessica on any potential issues on docs? She not= ed something in the original thread. >>=20 >> --Alex >=20 > +1 to that please. Docs are really no different from code in this respect= . >=20 >>> -----Original Message----- >>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com] >>> Sent: Friday, January 11, 2013 4:02 PM >>> To: cloudstack-dev@incubator.apache.org >>> Subject: [IP Clearance] Potential issues >>>=20 >>> Folks >>>=20 >>> I wanted to keep folks updated on where we are with IP clearance on the >>> different issues and starting this new thread >>>=20 >>> Here is the list of potential issues that has been identified. Please b= ring in any >>> other issue if you think it needs to go through IP clearance. I will st= art >>> individual threads on each one of them after the code has been posted t= o an >>> external public location. If there is quick consensus on the ones >>> recommended initially as 'No IP clearance needed' because they already >>> followed the process I will skip them. As the list is big I am looking = for >>> volunteers for help in posting the code and working through individual >>> threads >>>=20 >>> CLOUDSTACK-774 : >>> Code in ACS repo: No >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 5000 lines >>> Contributor : Frank >>> IP Clearance needed initial recommendation: Yes >>>=20 >>>=20 >>>=20 >>> CLOUDSTACK-306 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes in October >>> Contribution Size Approx: 1500 lines >>> Contributor : Sheng >>> IP Clearance needed initial recommendation: Yes >>>=20 >>> CLOUDSTACK-777/700 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: No >>> Community Discussion Done: Yes >>> Contribution Size Approx: 500 lines >>> Contributor : Kishan/Jayapal/Rajesh/Murali >>> IP Clearance needed initial recommendation: Yes >>>=20 >>> CLOUDSTACK-778/319 : >>> Code in ACS repo: No >>> Functional Spec Posted: No >>> Community Discussion Done: Yes >>> Contribution Size Approx: should be small >>> Contributor : Vijayendra >>> IP Clearance needed initial recommendation: This is a trivial issue so = may be >>> no >>>=20 >>>=20 >>> CLOUDSTACK-299 : >>> Code in ACS repo: UI code is there but backend is not >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 1400 lines >>> Contributor : Jayapal >>> IP Clearance needed initial recommendation: Yes >>>=20 >>> CLOUDSTACK-297 : >>> Code in ACS repo: No, but posted on review board >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 350 lines >>> Contributor : Hari >>> IP Clearance needed initial recommendation: >>>=20 >>> CLOUDSTACK-197 : >>> Code in ACS repo: Multiple patches posted on review board >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 3000 lines >>> Contributor : Likitha >>> IP Clearance needed initial recommendation: No, since incremental patch= es >>> were posted over a period >>>=20 >>>=20 >>> CLOUDSTACK-192 : >>> Code in ACS repo: No >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes, but no consensus reached >>> Contribution Size Approx: 1000 lines >>> Contributor : Sanjay >>> IP Clearance needed initial recommendation: Yes, if community agrees to >>> feature inclusion >>>=20 >>>=20 >>> CLOUDSTACK-304 / 784 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 600 >>> Contributor : Alena >>> IP Clearance needed initial recommendation: No, since commits were done >>> way back in October over a period of 1 week >>>=20 >>>=20 >>> CLOUDSTACK-265 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 450 >>> Contributor : Murali >>> IP Clearance needed initial recommendation: Yes >>>=20 >>> CLOUDSTACK-737 : >>> Code in ACS repo: No >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 2000 >>> Contributor : Anthony >>> IP Clearance needed initial recommendation: Yes >>>=20 >>> CLOUDSTACK-177 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 300 >>> Contributor : Brian >>> IP Clearance needed initial recommendation: No, multiple commits over >>> several days >>>=20 >>> CLOUDSTACK-662 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 500 >>> Contributor : Brian >>> IP Clearance needed initial recommendation: No, multiple commits over >>> several days >>>=20 >>>=20 >>> CLOUDSTACK-176 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: 200 >>> Contributor : Pranav >>> IP Clearance needed initial recommendation: No, multiple commits over >>> several days >>>=20 >>>=20 >>> CLOUDSTACK-312 : >>> Code in ACS repo: Yes >>> Functional Spec Posted: Yes >>> Community Discussion Done: Yes >>> Contribution Size Approx: >>> Contributor : Murali >>> IP Clearance needed initial recommendation: Potentially yes, multiple >>> commits in one day >>>=20 >>>=20 >>> CLOUDSTACK-873 : >>> Code in ACS repo: No >>> Functional Spec Posted: No >>> Community Discussion Done: No >>> Contribution Size Approx: Work not started >>> Contributor : Vijayendra/ Kelven >>> IP Clearance needed initial recommendation: No as work has not started = on it >>> yet. Preliminary investigation done, running into issues with vmware. >>>=20 >>>=20 >>> Thanks >>> Animesh >>=20