You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Chip Childers <ch...@sungard.com> on 2012/10/09 15:36:29 UTC
[ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Hi all,
Lots of things are happening right now around 4.0.0, so we're still
not ready to VOTE.
Here's a summary of the outstanding issues (as I see them):
* AWASPI was integrated to quickly, and some things were missed. The
thread Wido started on it's appropriateness needs to come to
consensus. If it does stay, it needs the DEB packaging to be
completed and tested (CLOUDSTACK-294). Wido is willing to do the
packaging after consensus is reached.
* CLOUDSTACK-301 is a blocker as well - That one looks like there is
missing code? Devdeep Singh is the assigned community member.
* CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
with the test team to get it resolved / closed?
* CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
make a recommendation as to the severity and timing of a fix? It's
currently unassigned.
* The release notes need to be pulled in from
https://reviews.apache.org/r/7498/ I'll take responsibility for doing
that today.
* We didn't pull the internationalization resources into 4.0 (they
were committed to master last night by David). I'd suggest we hold of
on putting them in the 4.0 branch, but that we use master to build the
project's documentation site.
That's all I have on my list right now. Shout if there are any other
issues, and PLEASE get involved in reaching conclusions to the issues
noted above.
-chip
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Sudha Ponnaganti <su...@citrix.com>.
Testing with non OSS build on VMWare + EC2 is done on RHEL
Ubuntu build is done - testing is in progress
-----Original Message-----
From: Sudha Ponnaganti [mailto:sudha.ponnaganti@citrix.com]
Sent: Tuesday, October 09, 2012 10:38 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Validation of EC2 with oss build is done.
Testing EC2 APIs with non oss build + VMware now
-----Original Message-----
From: Sudha Ponnaganti
Sent: Tuesday, October 09, 2012 9:41 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Edison has provided build. After a few issues, QA has finished sanity validation of EC2 API on Ubuntu on empty zones. Able to execute commands successfully. Also validated the same again on RHEL. Works fine.
Now progressing with validation on zones ( should be done in another 30min) and Edison also requested to validate non OSS build with VMWare and EC2. Will do that tonight.
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Tuesday, October 09, 2012 8:33 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Sudha,
Can you update folks officially with where your testing is?
-chip
On Tue, Oct 9, 2012 at 4:54 PM, Sudha Ponnaganti <su...@citrix.com> wrote:
> Yes Chip. Will update forum shortly
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 1:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
> On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
>> From this list, it looks like we have two blockers left.
>>
>> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
>
> I see that Edison has committed the DEB files, and the build is working properly on jenkins.cs.o.
>
> QA team - have you started testing the AWSAPI code on Ubuntu?
>
>> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
>>
>> Will
>>
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Tuesday, October 09, 2012 6:36 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>>
>>> Hi all,
>>>
>>> Lots of things are happening right now around 4.0.0, so we're still
>>> not ready to VOTE.
>>>
>>> Here's a summary of the outstanding issues (as I see them):
>>>
>>> * AWASPI was integrated to quickly, and some things were missed.
>>> The thread Wido started on it's appropriateness needs to come to
>>> consensus. If it does stay, it needs the DEB packaging to be
>>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>>> packaging after consensus is reached.
>>>
>>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>>> missing code? Devdeep Singh is the assigned community member.
>>>
>>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you
>>> work with the test team to get it resolved / closed?
>>>
>>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug
>>> and make a recommendation as to the severity and timing of a fix?
>>> It's currently unassigned.
>>>
>>> * The release notes need to be pulled in from
>>> https://reviews.apache.org/r/7498/ I'll take responsibility for
>>> doing that today.
>>>
>>> * We didn't pull the internationalization resources into 4.0 (they
>>> were committed to master last night by David). I'd suggest we hold
>>> of on putting them in the 4.0 branch, but that we use master to
>>> build the project's documentation site.
>>>
>>> That's all I have on my list right now. Shout if there are any
>>> other issues, and PLEASE get involved in reaching conclusions to the issues noted above.
>>>
>>> -chip
>>
>
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Sudha Ponnaganti <su...@citrix.com>.
Validation of EC2 with oss build is done.
Testing EC2 APIs with non oss build + VMware now
-----Original Message-----
From: Sudha Ponnaganti
Sent: Tuesday, October 09, 2012 9:41 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Edison has provided build. After a few issues, QA has finished sanity validation of EC2 API on Ubuntu on empty zones. Able to execute commands successfully. Also validated the same again on RHEL. Works fine.
Now progressing with validation on zones ( should be done in another 30min) and Edison also requested to validate non OSS build with VMWare and EC2. Will do that tonight.
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Tuesday, October 09, 2012 8:33 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Sudha,
Can you update folks officially with where your testing is?
-chip
On Tue, Oct 9, 2012 at 4:54 PM, Sudha Ponnaganti <su...@citrix.com> wrote:
> Yes Chip. Will update forum shortly
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 1:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
> On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
>> From this list, it looks like we have two blockers left.
>>
>> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
>
> I see that Edison has committed the DEB files, and the build is working properly on jenkins.cs.o.
>
> QA team - have you started testing the AWSAPI code on Ubuntu?
>
>> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
>>
>> Will
>>
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Tuesday, October 09, 2012 6:36 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>>
>>> Hi all,
>>>
>>> Lots of things are happening right now around 4.0.0, so we're still
>>> not ready to VOTE.
>>>
>>> Here's a summary of the outstanding issues (as I see them):
>>>
>>> * AWASPI was integrated to quickly, and some things were missed.
>>> The thread Wido started on it's appropriateness needs to come to
>>> consensus. If it does stay, it needs the DEB packaging to be
>>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>>> packaging after consensus is reached.
>>>
>>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>>> missing code? Devdeep Singh is the assigned community member.
>>>
>>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you
>>> work with the test team to get it resolved / closed?
>>>
>>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug
>>> and make a recommendation as to the severity and timing of a fix?
>>> It's currently unassigned.
>>>
>>> * The release notes need to be pulled in from
>>> https://reviews.apache.org/r/7498/ I'll take responsibility for
>>> doing that today.
>>>
>>> * We didn't pull the internationalization resources into 4.0 (they
>>> were committed to master last night by David). I'd suggest we hold
>>> of on putting them in the 4.0 branch, but that we use master to
>>> build the project's documentation site.
>>>
>>> That's all I have on my list right now. Shout if there are any
>>> other issues, and PLEASE get involved in reaching conclusions to the issues noted above.
>>>
>>> -chip
>>
>
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Sudha Ponnaganti <su...@citrix.com>.
Edison has provided build. After a few issues, QA has finished sanity validation of EC2 API on Ubuntu on empty zones. Able to execute commands successfully. Also validated the same again on RHEL. Works fine.
Now progressing with validation on zones ( should be done in another 30min) and Edison also requested to validate non OSS build with VMWare and EC2. Will do that tonight.
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Tuesday, October 09, 2012 8:33 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Sudha,
Can you update folks officially with where your testing is?
-chip
On Tue, Oct 9, 2012 at 4:54 PM, Sudha Ponnaganti <su...@citrix.com> wrote:
> Yes Chip. Will update forum shortly
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 1:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
> On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
>> From this list, it looks like we have two blockers left.
>>
>> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
>
> I see that Edison has committed the DEB files, and the build is working properly on jenkins.cs.o.
>
> QA team - have you started testing the AWSAPI code on Ubuntu?
>
>> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
>>
>> Will
>>
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Tuesday, October 09, 2012 6:36 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>>
>>> Hi all,
>>>
>>> Lots of things are happening right now around 4.0.0, so we're still
>>> not ready to VOTE.
>>>
>>> Here's a summary of the outstanding issues (as I see them):
>>>
>>> * AWASPI was integrated to quickly, and some things were missed.
>>> The thread Wido started on it's appropriateness needs to come to
>>> consensus. If it does stay, it needs the DEB packaging to be
>>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>>> packaging after consensus is reached.
>>>
>>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>>> missing code? Devdeep Singh is the assigned community member.
>>>
>>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you
>>> work with the test team to get it resolved / closed?
>>>
>>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug
>>> and make a recommendation as to the severity and timing of a fix?
>>> It's currently unassigned.
>>>
>>> * The release notes need to be pulled in from
>>> https://reviews.apache.org/r/7498/ I'll take responsibility for
>>> doing that today.
>>>
>>> * We didn't pull the internationalization resources into 4.0 (they
>>> were committed to master last night by David). I'd suggest we hold
>>> of on putting them in the 4.0 branch, but that we use master to
>>> build the project's documentation site.
>>>
>>> That's all I have on my list right now. Shout if there are any
>>> other issues, and PLEASE get involved in reaching conclusions to the issues noted above.
>>>
>>> -chip
>>
>
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Chip Childers <ch...@sungard.com>.
Sudha,
Can you update folks officially with where your testing is?
-chip
On Tue, Oct 9, 2012 at 4:54 PM, Sudha Ponnaganti
<su...@citrix.com> wrote:
> Yes Chip. Will update forum shortly
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 1:53 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
> On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
>> From this list, it looks like we have two blockers left.
>>
>> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
>
> I see that Edison has committed the DEB files, and the build is working properly on jenkins.cs.o.
>
> QA team - have you started testing the AWSAPI code on Ubuntu?
>
>> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
>>
>> Will
>>
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Tuesday, October 09, 2012 6:36 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>>
>>> Hi all,
>>>
>>> Lots of things are happening right now around 4.0.0, so we're still
>>> not ready to VOTE.
>>>
>>> Here's a summary of the outstanding issues (as I see them):
>>>
>>> * AWASPI was integrated to quickly, and some things were missed. The
>>> thread Wido started on it's appropriateness needs to come to
>>> consensus. If it does stay, it needs the DEB packaging to be
>>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>>> packaging after consensus is reached.
>>>
>>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>>> missing code? Devdeep Singh is the assigned community member.
>>>
>>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
>>> with the test team to get it resolved / closed?
>>>
>>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
>>> make a recommendation as to the severity and timing of a fix? It's
>>> currently unassigned.
>>>
>>> * The release notes need to be pulled in from
>>> https://reviews.apache.org/r/7498/ I'll take responsibility for
>>> doing that today.
>>>
>>> * We didn't pull the internationalization resources into 4.0 (they
>>> were committed to master last night by David). I'd suggest we hold
>>> of on putting them in the 4.0 branch, but that we use master to build
>>> the project's documentation site.
>>>
>>> That's all I have on my list right now. Shout if there are any other
>>> issues, and PLEASE get involved in reaching conclusions to the issues noted above.
>>>
>>> -chip
>>
>
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Sudha Ponnaganti <su...@citrix.com>.
Yes Chip. Will update forum shortly
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Tuesday, October 09, 2012 1:53 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
> From this list, it looks like we have two blockers left.
>
> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
I see that Edison has committed the DEB files, and the build is working properly on jenkins.cs.o.
QA team - have you started testing the AWSAPI code on Ubuntu?
> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
>
> Will
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Tuesday, October 09, 2012 6:36 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>
>> Hi all,
>>
>> Lots of things are happening right now around 4.0.0, so we're still
>> not ready to VOTE.
>>
>> Here's a summary of the outstanding issues (as I see them):
>>
>> * AWASPI was integrated to quickly, and some things were missed. The
>> thread Wido started on it's appropriateness needs to come to
>> consensus. If it does stay, it needs the DEB packaging to be
>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>> packaging after consensus is reached.
>>
>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>> missing code? Devdeep Singh is the assigned community member.
>>
>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
>> with the test team to get it resolved / closed?
>>
>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
>> make a recommendation as to the severity and timing of a fix? It's
>> currently unassigned.
>>
>> * The release notes need to be pulled in from
>> https://reviews.apache.org/r/7498/ I'll take responsibility for
>> doing that today.
>>
>> * We didn't pull the internationalization resources into 4.0 (they
>> were committed to master last night by David). I'd suggest we hold
>> of on putting them in the 4.0 branch, but that we use master to build
>> the project's documentation site.
>>
>> That's all I have on my list right now. Shout if there are any other
>> issues, and PLEASE get involved in reaching conclusions to the issues noted above.
>>
>> -chip
>
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
> From this list, it looks like we have two blockers left.
>
> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
I see that Edison has committed the DEB files, and the build is
working properly on jenkins.cs.o.
QA team - have you started testing the AWSAPI code on Ubuntu?
> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
>
> Will
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Tuesday, October 09, 2012 6:36 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>
>> Hi all,
>>
>> Lots of things are happening right now around 4.0.0, so we're still not ready
>> to VOTE.
>>
>> Here's a summary of the outstanding issues (as I see them):
>>
>> * AWASPI was integrated to quickly, and some things were missed. The
>> thread Wido started on it's appropriateness needs to come to consensus. If
>> it does stay, it needs the DEB packaging to be completed and tested
>> (CLOUDSTACK-294). Wido is willing to do the packaging after consensus is
>> reached.
>>
>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is missing
>> code? Devdeep Singh is the assigned community member.
>>
>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
>> with the test team to get it resolved / closed?
>>
>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
>> make a recommendation as to the severity and timing of a fix? It's
>> currently unassigned.
>>
>> * The release notes need to be pulled in from
>> https://reviews.apache.org/r/7498/ I'll take responsibility for doing that
>> today.
>>
>> * We didn't pull the internationalization resources into 4.0 (they were
>> committed to master last night by David). I'd suggest we hold of on putting
>> them in the 4.0 branch, but that we use master to build the project's
>> documentation site.
>>
>> That's all I have on my list right now. Shout if there are any other issues,
>> and PLEASE get involved in reaching conclusions to the issues noted above.
>>
>> -chip
>
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Vijayendra Bhamidipati <vi...@citrix.com>.
-----Original Message-----
From: Will Chan [mailto:will.chan@citrix.com]
Sent: Tuesday, October 09, 2012 12:35 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 12:30 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
>
> What's required to pull the feature out? Do we want to note it in the
> release notes and leave the code as-is?
>
>> I think we just release note this and leave the code as-is. The only time the bug surfaces is if are actually using vSwitch.
>> Will
I agree - we should relnote this and leave the code as-is. It will not interfere with existing non-dvs vmware (local vswitch) networking code paths, which have been tested.
Regards,
Vijay
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Oct 9, 2012 at 3:38 PM, Chip Childers <ch...@sungard.com> wrote:
> On Tue, Oct 9, 2012 at 3:34 PM, Will Chan <wi...@citrix.com> wrote:
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Tuesday, October 09, 2012 12:30 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>>
>>>
>>> What's required to pull the feature out? Do we want to note it in the
>>> release notes and leave the code as-is?
>>>
>>
>> I think we just release note this and leave the code as-is. The only time the bug surfaces is if are actually using vSwitch.
>>
>> Will
>>
>
> OK, I'll take a quick crack at adding it to the release notes (or more
> specifically, to be sure that CLOUDSTACK-301 is in the known issues
> list).
References to a working Nexus 1KV function have been removed from the
docs (everywhere I could find a reference to Nexus), with the
exception of a release note about 301.
Thanks.
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Oct 9, 2012 at 3:34 PM, Will Chan <wi...@citrix.com> wrote:
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Tuesday, October 09, 2012 12:30 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>
>>
>> What's required to pull the feature out? Do we want to note it in the
>> release notes and leave the code as-is?
>>
>
> I think we just release note this and leave the code as-is. The only time the bug surfaces is if are actually using vSwitch.
>
> Will
>
OK, I'll take a quick crack at adding it to the release notes (or more
specifically, to be sure that CLOUDSTACK-301 is in the known issues
list).
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Will Chan <wi...@citrix.com>.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 12:30 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
>
> What's required to pull the feature out? Do we want to note it in the
> release notes and leave the code as-is?
>
I think we just release note this and leave the code as-is. The only time the bug surfaces is if are actually using vSwitch.
Will
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Sudha Ponnaganti <su...@citrix.com>.
VMware in general has been tested with regression features. Only Nexus vSwitch is what has been broken. Code can be left in the same state and fix it for next release.
If Sateesh checks in code, require a day at least to do sanity validation. It would be ok to release note it for now as we do not have that kind of time now.
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Tuesday, October 09, 2012 12:30 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
> From this list, it looks like we have two blockers left.
>
> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
Great, that's fantastic news.
> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
I would agree. I think we need to pull this feature out. There isn't an existing CloudStack release that has it (only CloudPlatform has it as a commercial product).
What's required to pull the feature out? Do we want to note it in the release notes and leave the code as-is?
>
> Will
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Tuesday, October 09, 2012 6:36 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>
>> Hi all,
>>
>> Lots of things are happening right now around 4.0.0, so we're still
>> not ready to VOTE.
>>
>> Here's a summary of the outstanding issues (as I see them):
>>
>> * AWASPI was integrated to quickly, and some things were missed. The
>> thread Wido started on it's appropriateness needs to come to
>> consensus. If it does stay, it needs the DEB packaging to be
>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>> packaging after consensus is reached.
>>
>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>> missing code? Devdeep Singh is the assigned community member.
>>
>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
>> with the test team to get it resolved / closed?
>>
>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
>> make a recommendation as to the severity and timing of a fix? It's
>> currently unassigned.
>>
>> * The release notes need to be pulled in from
>> https://reviews.apache.org/r/7498/ I'll take responsibility for
>> doing that today.
>>
>> * We didn't pull the internationalization resources into 4.0 (they
>> were committed to master last night by David). I'd suggest we hold
>> of on putting them in the 4.0 branch, but that we use master to build
>> the project's documentation site.
>>
>> That's all I have on my list right now. Shout if there are any other
>> issues, and PLEASE get involved in reaching conclusions to the issues noted above.
>>
>> -chip
>
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Oct 9, 2012 at 3:18 PM, Will Chan <wi...@citrix.com> wrote:
> From this list, it looks like we have two blockers left.
>
> 1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
Great, that's fantastic news.
> 2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
I would agree. I think we need to pull this feature out. There isn't
an existing CloudStack release that has it (only CloudPlatform has it
as a commercial product).
What's required to pull the feature out? Do we want to note it in the
release notes and leave the code as-is?
>
> Will
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Tuesday, October 09, 2012 6:36 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>>
>> Hi all,
>>
>> Lots of things are happening right now around 4.0.0, so we're still not ready
>> to VOTE.
>>
>> Here's a summary of the outstanding issues (as I see them):
>>
>> * AWASPI was integrated to quickly, and some things were missed. The
>> thread Wido started on it's appropriateness needs to come to consensus. If
>> it does stay, it needs the DEB packaging to be completed and tested
>> (CLOUDSTACK-294). Wido is willing to do the packaging after consensus is
>> reached.
>>
>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is missing
>> code? Devdeep Singh is the assigned community member.
>>
>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
>> with the test team to get it resolved / closed?
>>
>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
>> make a recommendation as to the severity and timing of a fix? It's
>> currently unassigned.
>>
>> * The release notes need to be pulled in from
>> https://reviews.apache.org/r/7498/ I'll take responsibility for doing that
>> today.
>>
>> * We didn't pull the internationalization resources into 4.0 (they were
>> committed to master last night by David). I'd suggest we hold of on putting
>> them in the 4.0 branch, but that we use master to build the project's
>> documentation site.
>>
>> That's all I have on my list right now. Shout if there are any other issues,
>> and PLEASE get involved in reaching conclusions to the issues noted above.
>>
>> -chip
>
RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Will Chan <wi...@citrix.com>.
>From this list, it looks like we have two blockers left.
1. Adding deb package for AWSAPI. Edison said he'll look into this and QA for this should be pretty simple.
2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatform recently GAed in our 3.0.5 release (Burbank). It look like with the recent changes to the plugin framework, the porting of the feature was not done well. The time to fix this and to QA it properly could be in the order of days or perhaps a week. I would hate to delay the release of CloudStack anymore due to this one feature. What does the community think? Do you think we should drop this and release 4.0? I believe we have a couple of other features that are in similar situations (i.e. Netscalar autoscaling, but I could be wrong).
Will
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 6:36 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>
> Hi all,
>
> Lots of things are happening right now around 4.0.0, so we're still not ready
> to VOTE.
>
> Here's a summary of the outstanding issues (as I see them):
>
> * AWASPI was integrated to quickly, and some things were missed. The
> thread Wido started on it's appropriateness needs to come to consensus. If
> it does stay, it needs the DEB packaging to be completed and tested
> (CLOUDSTACK-294). Wido is willing to do the packaging after consensus is
> reached.
>
> * CLOUDSTACK-301 is a blocker as well - That one looks like there is missing
> code? Devdeep Singh is the assigned community member.
>
> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
> with the test team to get it resolved / closed?
>
> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
> make a recommendation as to the severity and timing of a fix? It's
> currently unassigned.
>
> * The release notes need to be pulled in from
> https://reviews.apache.org/r/7498/ I'll take responsibility for doing that
> today.
>
> * We didn't pull the internationalization resources into 4.0 (they were
> committed to master last night by David). I'd suggest we hold of on putting
> them in the 4.0 branch, but that we use master to build the project's
> documentation site.
>
> That's all I have on my list right now. Shout if there are any other issues,
> and PLEASE get involved in reaching conclusions to the issues noted above.
>
> -chip
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Noah Slater <ns...@tumbolia.org>.
Chip, I've introduced another blocker for the release. See my thread
"Incubator status page". Thanks!
On Tue, Oct 9, 2012 at 8:00 PM, Chip Childers <ch...@sungard.com>wrote:
> On Tue, Oct 9, 2012 at 2:57 PM, Noah Slater <ns...@tumbolia.org> wrote:
> > If these are all tagged up in JIRA, I can create and share a filter for
> us.
> > (And again for the next release, and so on.)
>
> Thanks Noah! I think we're good right now, as we're not dealing with
> too many bugs in the system overall (the benefit of starting fresh).
> I'm able to find the outstanding issues easily enough.
>
> +1 to establishing a shared filter for future releases. It will help
> immensely the next time around.
>
> -chip
>
> > On Tue, Oct 9, 2012 at 2:36 PM, Chip Childers <chip.childers@sungard.com
> >wrote:
> >
> >> Hi all,
> >>
> >> Lots of things are happening right now around 4.0.0, so we're still
> >> not ready to VOTE.
> >>
> >> Here's a summary of the outstanding issues (as I see them):
> >>
> >> * AWASPI was integrated to quickly, and some things were missed. The
> >> thread Wido started on it's appropriateness needs to come to
> >> consensus. If it does stay, it needs the DEB packaging to be
> >> completed and tested (CLOUDSTACK-294). Wido is willing to do the
> >> packaging after consensus is reached.
> >>
> >> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
> >> missing code? Devdeep Singh is the assigned community member.
> >>
> >> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
> >> with the test team to get it resolved / closed?
> >>
> >> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
> >> make a recommendation as to the severity and timing of a fix? It's
> >> currently unassigned.
> >>
> >> * The release notes need to be pulled in from
> >> https://reviews.apache.org/r/7498/ I'll take responsibility for doing
> >> that today.
> >>
> >> * We didn't pull the internationalization resources into 4.0 (they
> >> were committed to master last night by David). I'd suggest we hold of
> >> on putting them in the 4.0 branch, but that we use master to build the
> >> project's documentation site.
> >>
> >> That's all I have on my list right now. Shout if there are any other
> >> issues, and PLEASE get involved in reaching conclusions to the issues
> >> noted above.
> >>
> >> -chip
> >>
> >
> >
> >
> > --
> > NS
>
--
NS
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Oct 9, 2012 at 2:57 PM, Noah Slater <ns...@tumbolia.org> wrote:
> If these are all tagged up in JIRA, I can create and share a filter for us.
> (And again for the next release, and so on.)
Thanks Noah! I think we're good right now, as we're not dealing with
too many bugs in the system overall (the benefit of starting fresh).
I'm able to find the outstanding issues easily enough.
+1 to establishing a shared filter for future releases. It will help
immensely the next time around.
-chip
> On Tue, Oct 9, 2012 at 2:36 PM, Chip Childers <ch...@sungard.com>wrote:
>
>> Hi all,
>>
>> Lots of things are happening right now around 4.0.0, so we're still
>> not ready to VOTE.
>>
>> Here's a summary of the outstanding issues (as I see them):
>>
>> * AWASPI was integrated to quickly, and some things were missed. The
>> thread Wido started on it's appropriateness needs to come to
>> consensus. If it does stay, it needs the DEB packaging to be
>> completed and tested (CLOUDSTACK-294). Wido is willing to do the
>> packaging after consensus is reached.
>>
>> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
>> missing code? Devdeep Singh is the assigned community member.
>>
>> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
>> with the test team to get it resolved / closed?
>>
>> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
>> make a recommendation as to the severity and timing of a fix? It's
>> currently unassigned.
>>
>> * The release notes need to be pulled in from
>> https://reviews.apache.org/r/7498/ I'll take responsibility for doing
>> that today.
>>
>> * We didn't pull the internationalization resources into 4.0 (they
>> were committed to master last night by David). I'd suggest we hold of
>> on putting them in the 4.0 branch, but that we use master to build the
>> project's documentation site.
>>
>> That's all I have on my list right now. Shout if there are any other
>> issues, and PLEASE get involved in reaching conclusions to the issues
>> noted above.
>>
>> -chip
>>
>
>
>
> --
> NS
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Noah Slater <ns...@tumbolia.org>.
If these are all tagged up in JIRA, I can create and share a filter for us.
(And again for the next release, and so on.)
On Tue, Oct 9, 2012 at 2:36 PM, Chip Childers <ch...@sungard.com>wrote:
> Hi all,
>
> Lots of things are happening right now around 4.0.0, so we're still
> not ready to VOTE.
>
> Here's a summary of the outstanding issues (as I see them):
>
> * AWASPI was integrated to quickly, and some things were missed. The
> thread Wido started on it's appropriateness needs to come to
> consensus. If it does stay, it needs the DEB packaging to be
> completed and tested (CLOUDSTACK-294). Wido is willing to do the
> packaging after consensus is reached.
>
> * CLOUDSTACK-301 is a blocker as well - That one looks like there is
> missing code? Devdeep Singh is the assigned community member.
>
> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
> with the test team to get it resolved / closed?
>
> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
> make a recommendation as to the severity and timing of a fix? It's
> currently unassigned.
>
> * The release notes need to be pulled in from
> https://reviews.apache.org/r/7498/ I'll take responsibility for doing
> that today.
>
> * We didn't pull the internationalization resources into 4.0 (they
> were committed to master last night by David). I'd suggest we hold of
> on putting them in the 4.0 branch, but that we use master to build the
> project's documentation site.
>
> That's all I have on my list right now. Shout if there are any other
> issues, and PLEASE get involved in reaching conclusions to the issues
> noted above.
>
> -chip
>
--
NS
Re: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Posted by Rohit Yadav <ro...@citrix.com>.
On 09-Oct-2012, at 7:06 PM, Chip Childers <ch...@sungard.com> wrote:
> Hi all,
>
> Lots of things are happening right now around 4.0.0, so we're still
> not ready to VOTE.
>
> Here's a summary of the outstanding issues (as I see them):
>
> * AWASPI was integrated to quickly, and some things were missed. The
> thread Wido started on it's appropriateness needs to come to
> consensus. If it does stay, it needs the DEB packaging to be
> completed and tested (CLOUDSTACK-294). Wido is willing to do the
> packaging after consensus is reached.
I think we should get started for awsapi debian pkg, it does not make any sense now to discuss to throw away something; we're in a code-freeze now :)
So let's postpone that discussion post 4.0.
> * CLOUDSTACK-156 is a blocker that was reopened. Rohit, can you work
> with the test team to get it resolved / closed?
Done.
>
> * CLOUDSTACK-298 is set as Critical. Can someone triage that bug and
> make a recommendation as to the severity and timing of a fix? It's
> currently unassigned.
Triaged to 4.1, a transition state issue like 118.
Regards.
>
> * The release notes need to be pulled in from
> https://reviews.apache.org/r/7498/ I'll take responsibility for doing
> that today.
>
> * We didn't pull the internationalization resources into 4.0 (they
> were committed to master last night by David). I'd suggest we hold of
> on putting them in the 4.0 branch, but that we use master to build the
> project's documentation site.
>
> That's all I have on my list right now. Shout if there are any other
> issues, and PLEASE get involved in reaching conclusions to the issues
> noted above.
>
> -chip