You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by David Nalley <da...@gnsa.us> on 2013/01/24 18:20:01 UTC
IP Clearance
Hi folks:
Abhi posted these a bit earlier today - want to surface them to the
list, please review and bubble any concerns up to the list.
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-documenation-for-various-features.xml
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-egress-firewall-rules.xml
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-enahnced-baremetal-provisioning.xml
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-network-services-in-shared-networks.xml
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone.xml
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-reset-ssh-key.xml
http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-srx-f5-inline-mode.xml
Based on my reading of the ICLA, most of these should only require a
signed ICLA by the author, as they have the authority from Citrix to
submit this code under their ICLA. If there are concerns here, please
raise them.
Finally - I plan on requesting that an officer/member pick these up
shortly and push them forward in the process if there is no negative
reaction.
--David
RE: IP Clearance
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Friday, January 25, 2013 7:28 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Animesh Chaturvedi; David Nalley
> Subject: Re: IP Clearance
>
> On Fri, Jan 25, 2013 at 8:24 AM, Abhinandan Prateek
> <Ab...@citrix.com> wrote:
> > David/Animesh,
> >
> > If we have javelin merge before ip-clearance then almost none of the
> > feature patches submitted can be merged without git conflicts.
> > In that case developers will have to submit new patches or make
> > modifications to the patches they provided as part of the ip clearance
> > process.
> > Are we giving this a thought ? Can minor changes be made to the
> > patches as they have been signed etc ? Can we plan to expedite the
> > clearance process so that the patches make it to the master before javelin
> merge ?
>
> Well, I've certainly raised the concern several times.
>
> I'm not sure what to do. We have a couple of issues:
>
> 1 - Our release schedule closes down the release to new features and
> improvements on the 31st.
> 2 - There isn't such a thing as "expediting" IP clearance. If we assume that
> ICLA's are contractually enough (which IMO they are), then we need to get a
> member / officer to sponsor it within the IPMC as fast as possible. That being
> said, the vote at the IPMC will be at least 3 days.
> 3 - The javelin merge is still in progress.
>
> -chip
[Animesh>] ICLA's and the Xml files are taken care of. David do we have a sponsor to take the process forward?
>
> > -abhi
> >
> > On 25/01/13 12:01 PM, "Abhinandan Prateek"
> > <Ab...@citrix.com>
> > wrote:
> >
> >>Made the required changes to ip clearance documentation. Please, take
> >>the process forward.
> >>
> >>-abhi
> >>
> >>On 24/01/13 11:58 PM, "Animesh Chaturvedi"
> >><an...@citrix.com>
> >>wrote:
> >>
> >>>
> >>>> -----Original Message-----
> >>>> From: David Nalley [mailto:david@gnsa.us]
> >>>> Sent: Thursday, January 24, 2013 9:23 AM
> >>>> To: cloudstack-dev@incubator.apache.org
> >>>> Subject: Re: IP Clearance
> >>>>
> >>>> On Thu, Jan 24, 2013 at 12:20 PM, David Nalley <da...@gnsa.us> wrote:
> >>>> > Hi folks:
> >>>> >
> >>>> > Abhi posted these a bit earlier today - want to surface them to
> >>>> > the list, please review and bubble any concerns up to the list.
> >>>> >
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> > rance/cloudstack-documenation-for-various-features.xml
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> > rance/cloudstack-egress-firewall-rules.xml
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> > rance/cloudstack-enahnced-baremetal-provisioning.xml
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> > rance/cloudstack-network-services-in-shared-networks.xml
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> >
> >>>>rance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zo
> >>>>ne
> >>>> > .xml
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> > rance/cloudstack-reset-ssh-key.xml
> >>>> >
> >>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-cl
> >>>>ea
> >>>> > rance/cloudstack-srx-f5-inline-mode.xml
> >>>> >
> >>>> > Based on my reading of the ICLA, most of these should only
> >>>> > require a signed ICLA by the author, as they have the authority
> >>>> > from Citrix to submit this code under their ICLA. If there are
> >>>> > concerns here, please raise them.
> >>>> >
> >>>> > Finally - I plan on requesting that an officer/member pick these
> >>>> > up shortly and push them forward in the process if there is no
> >>>> > negative reaction.
> >>>> >
> >>>> > --David
> >>>>
> >>>> Quick followup from Chip in IRC:
> >>>>
> >>>> Abhi: You listed yourself as the ASF officer/member shepherding
> >>>>these through - though to my knowledge you aren't a member or
> >>>>officer, I assume the easiest way to get that dealt with is to have
> >>>>the officer/member amend these when we find one.
> >>>>
> >>>[Animesh>] Asked Abhi to clear the ASF member name which he
> >>>inadvertently put in as himself.
> >>>
> >>>> Also, can we get the official archive linke (mail-archive.a.o
> >>>>rather than the markmail link on these?)
> >>>[Animesh>] Ok that was my bad, I provided 3 updated files to Abhi with
> >>>mail.archive.a.o links. He has commit rights and will update the
> >>>files
> >>>
> >>>>
> >>>> --David
> >>
> >
> >
Re: IP Clearance
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Jan 25, 2013 at 8:24 AM, Abhinandan Prateek
<Ab...@citrix.com> wrote:
> David/Animesh,
>
> If we have javelin merge before ip-clearance then almost none of the
> feature patches submitted can be merged without git conflicts.
> In that case developers will have to submit new patches or make
> modifications to the patches they provided as part of the ip clearance
> process.
> Are we giving this a thought ? Can minor changes be made to the patches as
> they have been signed etc ? Can we plan to expedite the clearance process
> so that the patches make it to the master before javelin merge ?
Well, I've certainly raised the concern several times.
I'm not sure what to do. We have a couple of issues:
1 - Our release schedule closes down the release to new features and
improvements on the 31st.
2 - There isn't such a thing as "expediting" IP clearance. If we
assume that ICLA's are contractually enough (which IMO they are), then
we need to get a member / officer to sponsor it within the IPMC as
fast as possible. That being said, the vote at the IPMC will be at
least 3 days.
3 - The javelin merge is still in progress.
-chip
> -abhi
>
> On 25/01/13 12:01 PM, "Abhinandan Prateek" <Ab...@citrix.com>
> wrote:
>
>>Made the required changes to ip clearance documentation. Please, take the
>>process forward.
>>
>>-abhi
>>
>>On 24/01/13 11:58 PM, "Animesh Chaturvedi" <an...@citrix.com>
>>wrote:
>>
>>>
>>>> -----Original Message-----
>>>> From: David Nalley [mailto:david@gnsa.us]
>>>> Sent: Thursday, January 24, 2013 9:23 AM
>>>> To: cloudstack-dev@incubator.apache.org
>>>> Subject: Re: IP Clearance
>>>>
>>>> On Thu, Jan 24, 2013 at 12:20 PM, David Nalley <da...@gnsa.us> wrote:
>>>> > Hi folks:
>>>> >
>>>> > Abhi posted these a bit earlier today - want to surface them to the
>>>> > list, please review and bubble any concerns up to the list.
>>>> >
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> > rance/cloudstack-documenation-for-various-features.xml
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> > rance/cloudstack-egress-firewall-rules.xml
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> > rance/cloudstack-enahnced-baremetal-provisioning.xml
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> > rance/cloudstack-network-services-in-shared-networks.xml
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> >
>>>>rance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone
>>>> > .xml
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> > rance/cloudstack-reset-ssh-key.xml
>>>> >
>>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>>> > rance/cloudstack-srx-f5-inline-mode.xml
>>>> >
>>>> > Based on my reading of the ICLA, most of these should only require a
>>>> > signed ICLA by the author, as they have the authority from Citrix to
>>>> > submit this code under their ICLA. If there are concerns here, please
>>>> > raise them.
>>>> >
>>>> > Finally - I plan on requesting that an officer/member pick these up
>>>> > shortly and push them forward in the process if there is no negative
>>>> > reaction.
>>>> >
>>>> > --David
>>>>
>>>> Quick followup from Chip in IRC:
>>>>
>>>> Abhi: You listed yourself as the ASF officer/member shepherding these
>>>> through - though to my knowledge you aren't a member or officer, I
>>>>assume
>>>> the easiest way to get that dealt with is to have the officer/member
>>>>amend
>>>> these when we find one.
>>>>
>>>[Animesh>] Asked Abhi to clear the ASF member name which he inadvertently
>>>put in as himself.
>>>
>>>> Also, can we get the official archive linke (mail-archive.a.o rather
>>>>than the
>>>> markmail link on these?)
>>>[Animesh>] Ok that was my bad, I provided 3 updated files to Abhi with
>>>mail.archive.a.o links. He has commit rights and will update the files
>>>
>>>>
>>>> --David
>>
>
>
Re: IP Clearance
Posted by Abhinandan Prateek <Ab...@citrix.com>.
David/Animesh,
If we have javelin merge before ip-clearance then almost none of the
feature patches submitted can be merged without git conflicts.
In that case developers will have to submit new patches or make
modifications to the patches they provided as part of the ip clearance
process.
Are we giving this a thought ? Can minor changes be made to the patches as
they have been signed etc ? Can we plan to expedite the clearance process
so that the patches make it to the master before javelin merge ?
-abhi
On 25/01/13 12:01 PM, "Abhinandan Prateek" <Ab...@citrix.com>
wrote:
>Made the required changes to ip clearance documentation. Please, take the
>process forward.
>
>-abhi
>
>On 24/01/13 11:58 PM, "Animesh Chaturvedi" <an...@citrix.com>
>wrote:
>
>>
>>> -----Original Message-----
>>> From: David Nalley [mailto:david@gnsa.us]
>>> Sent: Thursday, January 24, 2013 9:23 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: IP Clearance
>>>
>>> On Thu, Jan 24, 2013 at 12:20 PM, David Nalley <da...@gnsa.us> wrote:
>>> > Hi folks:
>>> >
>>> > Abhi posted these a bit earlier today - want to surface them to the
>>> > list, please review and bubble any concerns up to the list.
>>> >
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> > rance/cloudstack-documenation-for-various-features.xml
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> > rance/cloudstack-egress-firewall-rules.xml
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> > rance/cloudstack-enahnced-baremetal-provisioning.xml
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> > rance/cloudstack-network-services-in-shared-networks.xml
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> >
>>>rance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone
>>> > .xml
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> > rance/cloudstack-reset-ssh-key.xml
>>> >
>>>http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>>> > rance/cloudstack-srx-f5-inline-mode.xml
>>> >
>>> > Based on my reading of the ICLA, most of these should only require a
>>> > signed ICLA by the author, as they have the authority from Citrix to
>>> > submit this code under their ICLA. If there are concerns here, please
>>> > raise them.
>>> >
>>> > Finally - I plan on requesting that an officer/member pick these up
>>> > shortly and push them forward in the process if there is no negative
>>> > reaction.
>>> >
>>> > --David
>>>
>>> Quick followup from Chip in IRC:
>>>
>>> Abhi: You listed yourself as the ASF officer/member shepherding these
>>> through - though to my knowledge you aren't a member or officer, I
>>>assume
>>> the easiest way to get that dealt with is to have the officer/member
>>>amend
>>> these when we find one.
>>>
>>[Animesh>] Asked Abhi to clear the ASF member name which he inadvertently
>>put in as himself.
>>
>>> Also, can we get the official archive linke (mail-archive.a.o rather
>>>than the
>>> markmail link on these?)
>>[Animesh>] Ok that was my bad, I provided 3 updated files to Abhi with
>>mail.archive.a.o links. He has commit rights and will update the files
>>
>>>
>>> --David
>
Re: IP Clearance
Posted by Abhinandan Prateek <Ab...@citrix.com>.
Made the required changes to ip clearance documentation. Please, take the
process forward.
-abhi
On 24/01/13 11:58 PM, "Animesh Chaturvedi" <an...@citrix.com>
wrote:
>
>> -----Original Message-----
>> From: David Nalley [mailto:david@gnsa.us]
>> Sent: Thursday, January 24, 2013 9:23 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: IP Clearance
>>
>> On Thu, Jan 24, 2013 at 12:20 PM, David Nalley <da...@gnsa.us> wrote:
>> > Hi folks:
>> >
>> > Abhi posted these a bit earlier today - want to surface them to the
>> > list, please review and bubble any concerns up to the list.
>> >
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-documenation-for-various-features.xml
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-egress-firewall-rules.xml
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-enahnced-baremetal-provisioning.xml
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-network-services-in-shared-networks.xml
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone
>> > .xml
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-reset-ssh-key.xml
>> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
>> > rance/cloudstack-srx-f5-inline-mode.xml
>> >
>> > Based on my reading of the ICLA, most of these should only require a
>> > signed ICLA by the author, as they have the authority from Citrix to
>> > submit this code under their ICLA. If there are concerns here, please
>> > raise them.
>> >
>> > Finally - I plan on requesting that an officer/member pick these up
>> > shortly and push them forward in the process if there is no negative
>> > reaction.
>> >
>> > --David
>>
>> Quick followup from Chip in IRC:
>>
>> Abhi: You listed yourself as the ASF officer/member shepherding these
>> through - though to my knowledge you aren't a member or officer, I
>>assume
>> the easiest way to get that dealt with is to have the officer/member
>>amend
>> these when we find one.
>>
>[Animesh>] Asked Abhi to clear the ASF member name which he inadvertently
>put in as himself.
>
>> Also, can we get the official archive linke (mail-archive.a.o rather
>>than the
>> markmail link on these?)
>[Animesh>] Ok that was my bad, I provided 3 updated files to Abhi with
>mail.archive.a.o links. He has commit rights and will update the files
>
>>
>> --David
RE: IP Clearance
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Thursday, January 24, 2013 9:23 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: IP Clearance
>
> On Thu, Jan 24, 2013 at 12:20 PM, David Nalley <da...@gnsa.us> wrote:
> > Hi folks:
> >
> > Abhi posted these a bit earlier today - want to surface them to the
> > list, please review and bubble any concerns up to the list.
> >
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-documenation-for-various-features.xml
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-egress-firewall-rules.xml
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-enahnced-baremetal-provisioning.xml
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-network-services-in-shared-networks.xml
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone
> > .xml
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-reset-ssh-key.xml
> > http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clea
> > rance/cloudstack-srx-f5-inline-mode.xml
> >
> > Based on my reading of the ICLA, most of these should only require a
> > signed ICLA by the author, as they have the authority from Citrix to
> > submit this code under their ICLA. If there are concerns here, please
> > raise them.
> >
> > Finally - I plan on requesting that an officer/member pick these up
> > shortly and push them forward in the process if there is no negative
> > reaction.
> >
> > --David
>
> Quick followup from Chip in IRC:
>
> Abhi: You listed yourself as the ASF officer/member shepherding these
> through - though to my knowledge you aren't a member or officer, I assume
> the easiest way to get that dealt with is to have the officer/member amend
> these when we find one.
>
[Animesh>] Asked Abhi to clear the ASF member name which he inadvertently put in as himself.
> Also, can we get the official archive linke (mail-archive.a.o rather than the
> markmail link on these?)
[Animesh>] Ok that was my bad, I provided 3 updated files to Abhi with mail.archive.a.o links. He has commit rights and will update the files
>
> --David
Re: IP Clearance
Posted by David Nalley <da...@gnsa.us>.
On Thu, Jan 24, 2013 at 12:20 PM, David Nalley <da...@gnsa.us> wrote:
> Hi folks:
>
> Abhi posted these a bit earlier today - want to surface them to the
> list, please review and bubble any concerns up to the list.
>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-documenation-for-various-features.xml
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-egress-firewall-rules.xml
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-enahnced-baremetal-provisioning.xml
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-network-services-in-shared-networks.xml
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-optional-public-ip-assignment-for-EIP-with-basic-zone.xml
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-reset-ssh-key.xml
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/cloudstack-srx-f5-inline-mode.xml
>
> Based on my reading of the ICLA, most of these should only require a
> signed ICLA by the author, as they have the authority from Citrix to
> submit this code under their ICLA. If there are concerns here, please
> raise them.
>
> Finally - I plan on requesting that an officer/member pick these up
> shortly and push them forward in the process if there is no negative
> reaction.
>
> --David
Quick followup from Chip in IRC:
Abhi: You listed yourself as the ASF officer/member shepherding these
through - though to my knowledge you aren't a member or officer, I
assume the easiest way to get that dealt with is to have the
officer/member amend these when we find one.
Also, can we get the official archive linke (mail-archive.a.o rather
than the markmail link on these?)
--David