You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Animesh Chaturvedi <an...@citrix.com> on 2013/09/21 05:36:11 UTC
[VOTE] Release Apache CloudStack 4.2.0 (sixth round)
I've created a 4.2.0 release, with the following artifacts up for a vote:
Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
Commit: 69c459342c568e2400d57ee88572b301603d8686
List of changes:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
PGP release keys (signed using 94BE0D7C):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS
Testing instructions are here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
Vote will be open for 72 hours (Monday 9/23 PST EOD).
For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Hugo Trippaers <hu...@trippaers.nl>.
+1 (binding)
Based on previous testing of the 5th round RC and a manual comparison of the differences.
Cheers,
Hugo
On Sep 23, 2013, at 2:24 PM, Marcus Sorensen <sh...@gmail.com> wrote:
> +0 (binding), created 4.1.1 zone with vms and a vpc, upgraded to 4.2
> via RPMs. Restarted vpc. Then wiped database and redeployed zone, vms
> to test 4.2 basic functionality. All on CentOS 6.4
>
> The reason for the +0 is that I found a regression when going beyond
> the basic testing and trying things like maintenance mode, I'm not
> sure if it's related to the new storage framework or not, but it
> definitely didn't exist in the previous release. I'm including the bug
> below. Basically the agent fails to connect to the management server
> on restart because we are trying to register the same pool multiple
> times. We should just check for the pool, match the uuid/properties,
> and say 'success' if it already exists. There is a hokey workaround,
> which is why I'm not going to block, if you stop libvirtd after taking
> the host out of maintenance and wait for the agent to reconnect, then
> you can start libvirtd again and everything will jumpstart into
> action. That can be done in order to complete a successful upgrade,
> and upon deploying a fresh zone I don't think anyone will notice until
> they go to use maintenance mode.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-4725
>
> Should be easy to fix, but I'm not going to look at it right this
> second. Maybe Edison can take a peek in the meantime.
>
> Looks like nobody has voted yet, I'm not sure if that means nobody has
> tested over the weekend or if they're being more thorough. If we do
> find that nobody has tested, and decide to fix this, I'd request we
> pull in 39f7ddbb8f7eedb050da2991cdc1fb72a9e97f5f from 4.2-forward as
> well.
>
> On Fri, Sep 20, 2013 at 9:36 PM, Animesh Chaturvedi
> <an...@citrix.com> wrote:
>>
>>
>>
>>
>> I've created a 4.2.0 release, with the following artifacts up for a vote:
>>
>> Git Branch and Commit SH:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
>> Commit: 69c459342c568e2400d57ee88572b301603d8686
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>>
>> PGP release keys (signed using 94BE0D7C):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Testing instructions are here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>>
>> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>>
>> For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>>
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Marcus Sorensen <sh...@gmail.com>.
Further testing shows that this only seems to affect an upgraded
agent. I can reproduce if I install agent 4.1.1, then upgrade to 4.2,
but not if I start fresh with agent 4.2. If I had to guess, the
upgrade maybe makes the local storage pool re-register(maybe it
creates a new host in the table or something like that, haven't
looked), where it looks like a duplicate.
On Mon, Sep 23, 2013 at 12:36 AM, Marcus Sorensen <sh...@gmail.com> wrote:
> I think this does have to do with the new default storage plugin. I
> think it only affects local storage, as the agent attempts to register
> it's local storage pool uuid as a pool with the mgmt server, who says
> 'sorry, this pool already exists in the database'.
>
> On Mon, Sep 23, 2013 at 12:24 AM, Marcus Sorensen <sh...@gmail.com> wrote:
>> +0 (binding), created 4.1.1 zone with vms and a vpc, upgraded to 4.2
>> via RPMs. Restarted vpc. Then wiped database and redeployed zone, vms
>> to test 4.2 basic functionality. All on CentOS 6.4
>>
>> The reason for the +0 is that I found a regression when going beyond
>> the basic testing and trying things like maintenance mode, I'm not
>> sure if it's related to the new storage framework or not, but it
>> definitely didn't exist in the previous release. I'm including the bug
>> below. Basically the agent fails to connect to the management server
>> on restart because we are trying to register the same pool multiple
>> times. We should just check for the pool, match the uuid/properties,
>> and say 'success' if it already exists. There is a hokey workaround,
>> which is why I'm not going to block, if you stop libvirtd after taking
>> the host out of maintenance and wait for the agent to reconnect, then
>> you can start libvirtd again and everything will jumpstart into
>> action. That can be done in order to complete a successful upgrade,
>> and upon deploying a fresh zone I don't think anyone will notice until
>> they go to use maintenance mode.
>>
>> https://issues.apache.org/jira/browse/CLOUDSTACK-4725
>>
>> Should be easy to fix, but I'm not going to look at it right this
>> second. Maybe Edison can take a peek in the meantime.
>>
>> Looks like nobody has voted yet, I'm not sure if that means nobody has
>> tested over the weekend or if they're being more thorough. If we do
>> find that nobody has tested, and decide to fix this, I'd request we
>> pull in 39f7ddbb8f7eedb050da2991cdc1fb72a9e97f5f from 4.2-forward as
>> well.
>>
>> On Fri, Sep 20, 2013 at 9:36 PM, Animesh Chaturvedi
>> <an...@citrix.com> wrote:
>>>
>>>
>>>
>>>
>>> I've created a 4.2.0 release, with the following artifacts up for a vote:
>>>
>>> Git Branch and Commit SH:
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
>>> Commit: 69c459342c568e2400d57ee88572b301603d8686
>>>
>>> List of changes:
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
>>>
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>>>
>>> PGP release keys (signed using 94BE0D7C):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>
>>> Testing instructions are here:
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>>>
>>> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>>>
>>> For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
>>>
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>>
>>>
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Marcus Sorensen <sh...@gmail.com>.
I think this does have to do with the new default storage plugin. I
think it only affects local storage, as the agent attempts to register
it's local storage pool uuid as a pool with the mgmt server, who says
'sorry, this pool already exists in the database'.
On Mon, Sep 23, 2013 at 12:24 AM, Marcus Sorensen <sh...@gmail.com> wrote:
> +0 (binding), created 4.1.1 zone with vms and a vpc, upgraded to 4.2
> via RPMs. Restarted vpc. Then wiped database and redeployed zone, vms
> to test 4.2 basic functionality. All on CentOS 6.4
>
> The reason for the +0 is that I found a regression when going beyond
> the basic testing and trying things like maintenance mode, I'm not
> sure if it's related to the new storage framework or not, but it
> definitely didn't exist in the previous release. I'm including the bug
> below. Basically the agent fails to connect to the management server
> on restart because we are trying to register the same pool multiple
> times. We should just check for the pool, match the uuid/properties,
> and say 'success' if it already exists. There is a hokey workaround,
> which is why I'm not going to block, if you stop libvirtd after taking
> the host out of maintenance and wait for the agent to reconnect, then
> you can start libvirtd again and everything will jumpstart into
> action. That can be done in order to complete a successful upgrade,
> and upon deploying a fresh zone I don't think anyone will notice until
> they go to use maintenance mode.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-4725
>
> Should be easy to fix, but I'm not going to look at it right this
> second. Maybe Edison can take a peek in the meantime.
>
> Looks like nobody has voted yet, I'm not sure if that means nobody has
> tested over the weekend or if they're being more thorough. If we do
> find that nobody has tested, and decide to fix this, I'd request we
> pull in 39f7ddbb8f7eedb050da2991cdc1fb72a9e97f5f from 4.2-forward as
> well.
>
> On Fri, Sep 20, 2013 at 9:36 PM, Animesh Chaturvedi
> <an...@citrix.com> wrote:
>>
>>
>>
>>
>> I've created a 4.2.0 release, with the following artifacts up for a vote:
>>
>> Git Branch and Commit SH:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
>> Commit: 69c459342c568e2400d57ee88572b301603d8686
>>
>> List of changes:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>>
>> PGP release keys (signed using 94BE0D7C):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Testing instructions are here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>>
>> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>>
>> For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>>
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Amogh Vasekar <am...@citrix.com>.
+1
Based on testing described in release procedure.
Thanks,
Amogh
On 9/22/13 11:24 PM, "Marcus Sorensen" <sh...@gmail.com> wrote:
>+0 (binding), created 4.1.1 zone with vms and a vpc, upgraded to 4.2
>via RPMs. Restarted vpc. Then wiped database and redeployed zone, vms
>to test 4.2 basic functionality. All on CentOS 6.4
>
>The reason for the +0 is that I found a regression when going beyond
>the basic testing and trying things like maintenance mode, I'm not
>sure if it's related to the new storage framework or not, but it
>definitely didn't exist in the previous release. I'm including the bug
>below. Basically the agent fails to connect to the management server
>on restart because we are trying to register the same pool multiple
>times. We should just check for the pool, match the uuid/properties,
>and say 'success' if it already exists. There is a hokey workaround,
>which is why I'm not going to block, if you stop libvirtd after taking
>the host out of maintenance and wait for the agent to reconnect, then
>you can start libvirtd again and everything will jumpstart into
>action. That can be done in order to complete a successful upgrade,
>and upon deploying a fresh zone I don't think anyone will notice until
>they go to use maintenance mode.
>
>https://issues.apache.org/jira/browse/CLOUDSTACK-4725
>
>Should be easy to fix, but I'm not going to look at it right this
>second. Maybe Edison can take a peek in the meantime.
>
>Looks like nobody has voted yet, I'm not sure if that means nobody has
>tested over the weekend or if they're being more thorough. If we do
>find that nobody has tested, and decide to fix this, I'd request we
>pull in 39f7ddbb8f7eedb050da2991cdc1fb72a9e97f5f from 4.2-forward as
>well.
>
>On Fri, Sep 20, 2013 at 9:36 PM, Animesh Chaturvedi
><an...@citrix.com> wrote:
>>
>>
>>
>>
>> I've created a 4.2.0 release, with the following artifacts up for a
>>vote:
>>
>> Git Branch and Commit SH:
>>
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>>s/heads/4.2
>> Commit: 69c459342c568e2400d57ee88572b301603d8686
>>
>> List of changes:
>>
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C
>>HANGES;hb=4.2
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>>
>> PGP release keys (signed using 94BE0D7C):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> Testing instructions are here:
>>
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proce
>>dure
>>
>> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>>
>> For sanity in tallying the vote, can PMC members please be sure to
>>indicate "(binding)" with their vote?
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>>
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Marcus Sorensen <sh...@gmail.com>.
+0 (binding), created 4.1.1 zone with vms and a vpc, upgraded to 4.2
via RPMs. Restarted vpc. Then wiped database and redeployed zone, vms
to test 4.2 basic functionality. All on CentOS 6.4
The reason for the +0 is that I found a regression when going beyond
the basic testing and trying things like maintenance mode, I'm not
sure if it's related to the new storage framework or not, but it
definitely didn't exist in the previous release. I'm including the bug
below. Basically the agent fails to connect to the management server
on restart because we are trying to register the same pool multiple
times. We should just check for the pool, match the uuid/properties,
and say 'success' if it already exists. There is a hokey workaround,
which is why I'm not going to block, if you stop libvirtd after taking
the host out of maintenance and wait for the agent to reconnect, then
you can start libvirtd again and everything will jumpstart into
action. That can be done in order to complete a successful upgrade,
and upon deploying a fresh zone I don't think anyone will notice until
they go to use maintenance mode.
https://issues.apache.org/jira/browse/CLOUDSTACK-4725
Should be easy to fix, but I'm not going to look at it right this
second. Maybe Edison can take a peek in the meantime.
Looks like nobody has voted yet, I'm not sure if that means nobody has
tested over the weekend or if they're being more thorough. If we do
find that nobody has tested, and decide to fix this, I'd request we
pull in 39f7ddbb8f7eedb050da2991cdc1fb72a9e97f5f from 4.2-forward as
well.
On Fri, Sep 20, 2013 at 9:36 PM, Animesh Chaturvedi
<an...@citrix.com> wrote:
>
>
>
>
> I've created a 4.2.0 release, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> Commit: 69c459342c568e2400d57ee88572b301603d8686
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>
> PGP release keys (signed using 94BE0D7C):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>
> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>
> For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Chip Childers <ch...@sungard.com>.
On Sat, Sep 21, 2013 at 03:36:11AM +0000, Animesh Chaturvedi wrote:
>
> I've created a 4.2.0 release, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> Commit: 69c459342c568e2400d57ee88572b301603d8686
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>
> PGP release keys (signed using 94BE0D7C):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>
> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>
> For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
+1 (binding)
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Milamber <mi...@apache.org>.
+1
Two tests (same env: CentOS 6.4 + KVM + NFS primary storage):
* Fresh install test
* Upgrade from 4.1.1 (fresh install with simple VMs/VirtualRouter) to
4.2.0 with success (after some fails because the Release Notes were
incomplete)
Tests of all languages UI with success (login + each main menus). Please
note: for several languages, the new behaviors like Affinity Groups and
Region are untranslated. Perhaps, a call to translate before the start
of release process (or just after commit the behavior) should be done
just before?.
Redundant Virtual Router : ok
HA+KVM success (test with remove ethernet cable)
Thanks for the RC manager!
Milamber
Le 21/09/2013 04:36, Animesh Chaturvedi a ecrit :
>
>
>
> I've created a 4.2.0 release, with the following artifacts up for a vote:
>
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> Commit: 69c459342c568e2400d57ee88572b301603d8686
>
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>
> PGP release keys (signed using 94BE0D7C):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
>
> Vote will be open for 72 hours (Monday 9/23 PST EOD).
>
> For sanity in tallying the vote, can PMC members please be sure to indicate "(binding)" with their vote?
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
>
RE: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: Tuesday, September 24, 2013 1:47 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
>
> Someone please check this, as I'm not familiar with the doc layout,
> especially trying to decipher it in xml.
>
> commit to 4.2 branch: da56b6212bbcf9e363ba1add180516584a3d695b
[Animesh>] Marcus a minor xml closing tag was missed, I fixed and kicked off a new build.
>
> On Mon, Sep 23, 2013 at 4:35 PM, Marcus Sorensen <sh...@gmail.com>
> wrote:
> > I think I'll wait until the vote passes, just to be sure that it won't
> > need to be backed out.
> >
> > On Mon, Sep 23, 2013 at 3:47 PM, Animesh Chaturvedi
> > <an...@citrix.com> wrote:
> >>
> >>
> >>> -----Original Message-----
> >>> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> >>> Sent: Monday, September 23, 2013 2:44 PM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
> >>>
> >>> I can change my vote to +1 if we include instructions similar to the
> >>> following in the upgrade notes:
> >>>
> >>> If using local storage on KVM, the local storage path needs to be
> >>> changed in order to pass new validation. Remove any trailing slashes
> >>> in the path column of the storage_pool table before starting agents.
> >>> e.g.:
> >>>
> >>> mysql -e 'update cloud.storage_pool set
> path="/var/lib/libvirt/images"
> >>> where path="/var/lib/libvirt/images/"';
> >>>
> >>> If using a custom path, insert your path in place of
> >>> "/var/lib/libvirt/images/". If your custom path did not contain a
> >>> trailing "/", there's no need to do this procedure.
> >>
> >>
> >> [Animesh>] Marcus do you want to go ahead and update the Release
> Notes in 4.2 branch in file docs/en-US/Release_Notes.xml. I just
> finished making few other changes that were discussed.
> >>
> >>>
> >>> On Mon, Sep 23, 2013 at 3:00 PM, Chiradeep Vittal
> >>> <Ch...@citrix.com> wrote:
> >>> > +1 (binding)
> >>> >
> >>> > On 9/20/13 8:36 PM, "Animesh Chaturvedi"
> >>> > <an...@citrix.com>
> >>> > wrote:
> >>> >
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >>I've created a 4.2.0 release, with the following artifacts up for
> >>> >>a
> >>> vote:
> >>> >>
> >>> >>Git Branch and Commit SH:
> >>> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlo
> >>> >>g;h=
> >>> >>refs
> >>> >>/heads/4.2
> >>> >>Commit: 69c459342c568e2400d57ee88572b301603d8686
> >>> >>
> >>> >>List of changes:
> >>> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_pl
> >>> >>ain;
> >>> >>f=CH
> >>> >>ANGES;hb=4.2
> >>> >>
> >>> >>Source release (checksums and signatures are available at the same
> >>> >>location):
> >>> >>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> >>> >>
> >>> >>PGP release keys (signed using 94BE0D7C):
> >>> >>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>> >>
> >>> >>Testing instructions are here:
> >>> >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+tes
> >>> >>t+pr
> >>> >>oced
> >>> >>ure
> >>> >>
> >>> >>Vote will be open for 72 hours (Monday 9/23 PST EOD).
> >>> >>
> >>> >>For sanity in tallying the vote, can PMC members please be sure to
> >>> >>indicate "(binding)" with their vote?
> >>> >>
> >>> >>[ ] +1 approve
> >>> >>[ ] +0 no opinion
> >>> >>[ ] -1 disapprove (and reason why)
> >>> >>
> >>> >>
> >>> >
RE: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: Tuesday, September 24, 2013 1:47 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
>
> Someone please check this, as I'm not familiar with the doc layout,
> especially trying to decipher it in xml.
>
> commit to 4.2 branch: da56b6212bbcf9e363ba1add180516584a3d695b
>
[Animesh>] I kicked off a new Release Note build on Jenkins, looking at the diff it should be fine
> On Mon, Sep 23, 2013 at 4:35 PM, Marcus Sorensen <sh...@gmail.com>
> wrote:
> > I think I'll wait until the vote passes, just to be sure that it won't
> > need to be backed out.
> >
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Marcus Sorensen <sh...@gmail.com>.
Someone please check this, as I'm not familiar with the doc layout,
especially trying to decipher it in xml.
commit to 4.2 branch: da56b6212bbcf9e363ba1add180516584a3d695b
On Mon, Sep 23, 2013 at 4:35 PM, Marcus Sorensen <sh...@gmail.com> wrote:
> I think I'll wait until the vote passes, just to be sure that it won't
> need to be backed out.
>
> On Mon, Sep 23, 2013 at 3:47 PM, Animesh Chaturvedi
> <an...@citrix.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>>> Sent: Monday, September 23, 2013 2:44 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
>>>
>>> I can change my vote to +1 if we include instructions similar to the
>>> following in the upgrade notes:
>>>
>>> If using local storage on KVM, the local storage path needs to be
>>> changed in order to pass new validation. Remove any trailing slashes in
>>> the path column of the storage_pool table before starting agents.
>>> e.g.:
>>>
>>> mysql -e 'update cloud.storage_pool set path="/var/lib/libvirt/images"
>>> where path="/var/lib/libvirt/images/"';
>>>
>>> If using a custom path, insert your path in place of
>>> "/var/lib/libvirt/images/". If your custom path did not contain a
>>> trailing "/", there's no need to do this procedure.
>>
>>
>> [Animesh>] Marcus do you want to go ahead and update the Release Notes in 4.2 branch in file docs/en-US/Release_Notes.xml. I just finished making few other changes that were discussed.
>>
>>>
>>> On Mon, Sep 23, 2013 at 3:00 PM, Chiradeep Vittal
>>> <Ch...@citrix.com> wrote:
>>> > +1 (binding)
>>> >
>>> > On 9/20/13 8:36 PM, "Animesh Chaturvedi"
>>> > <an...@citrix.com>
>>> > wrote:
>>> >
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>I've created a 4.2.0 release, with the following artifacts up for a
>>> vote:
>>> >>
>>> >>Git Branch and Commit SH:
>>> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
>>> >>refs
>>> >>/heads/4.2
>>> >>Commit: 69c459342c568e2400d57ee88572b301603d8686
>>> >>
>>> >>List of changes:
>>> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
>>> >>f=CH
>>> >>ANGES;hb=4.2
>>> >>
>>> >>Source release (checksums and signatures are available at the same
>>> >>location):
>>> >>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>>> >>
>>> >>PGP release keys (signed using 94BE0D7C):
>>> >>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>> >>
>>> >>Testing instructions are here:
>>> >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
>>> >>oced
>>> >>ure
>>> >>
>>> >>Vote will be open for 72 hours (Monday 9/23 PST EOD).
>>> >>
>>> >>For sanity in tallying the vote, can PMC members please be sure to
>>> >>indicate "(binding)" with their vote?
>>> >>
>>> >>[ ] +1 approve
>>> >>[ ] +0 no opinion
>>> >>[ ] -1 disapprove (and reason why)
>>> >>
>>> >>
>>> >
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Marcus Sorensen <sh...@gmail.com>.
I think I'll wait until the vote passes, just to be sure that it won't
need to be backed out.
On Mon, Sep 23, 2013 at 3:47 PM, Animesh Chaturvedi
<an...@citrix.com> wrote:
>
>
>> -----Original Message-----
>> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
>> Sent: Monday, September 23, 2013 2:44 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
>>
>> I can change my vote to +1 if we include instructions similar to the
>> following in the upgrade notes:
>>
>> If using local storage on KVM, the local storage path needs to be
>> changed in order to pass new validation. Remove any trailing slashes in
>> the path column of the storage_pool table before starting agents.
>> e.g.:
>>
>> mysql -e 'update cloud.storage_pool set path="/var/lib/libvirt/images"
>> where path="/var/lib/libvirt/images/"';
>>
>> If using a custom path, insert your path in place of
>> "/var/lib/libvirt/images/". If your custom path did not contain a
>> trailing "/", there's no need to do this procedure.
>
>
> [Animesh>] Marcus do you want to go ahead and update the Release Notes in 4.2 branch in file docs/en-US/Release_Notes.xml. I just finished making few other changes that were discussed.
>
>>
>> On Mon, Sep 23, 2013 at 3:00 PM, Chiradeep Vittal
>> <Ch...@citrix.com> wrote:
>> > +1 (binding)
>> >
>> > On 9/20/13 8:36 PM, "Animesh Chaturvedi"
>> > <an...@citrix.com>
>> > wrote:
>> >
>> >>
>> >>
>> >>
>> >>
>> >>I've created a 4.2.0 release, with the following artifacts up for a
>> vote:
>> >>
>> >>Git Branch and Commit SH:
>> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
>> >>refs
>> >>/heads/4.2
>> >>Commit: 69c459342c568e2400d57ee88572b301603d8686
>> >>
>> >>List of changes:
>> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
>> >>f=CH
>> >>ANGES;hb=4.2
>> >>
>> >>Source release (checksums and signatures are available at the same
>> >>location):
>> >>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>> >>
>> >>PGP release keys (signed using 94BE0D7C):
>> >>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> >>
>> >>Testing instructions are here:
>> >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
>> >>oced
>> >>ure
>> >>
>> >>Vote will be open for 72 hours (Monday 9/23 PST EOD).
>> >>
>> >>For sanity in tallying the vote, can PMC members please be sure to
>> >>indicate "(binding)" with their vote?
>> >>
>> >>[ ] +1 approve
>> >>[ ] +0 no opinion
>> >>[ ] -1 disapprove (and reason why)
>> >>
>> >>
>> >
RE: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Animesh Chaturvedi <an...@citrix.com>.
> -----Original Message-----
> From: Marcus Sorensen [mailto:shadowsor@gmail.com]
> Sent: Monday, September 23, 2013 2:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
>
> I can change my vote to +1 if we include instructions similar to the
> following in the upgrade notes:
>
> If using local storage on KVM, the local storage path needs to be
> changed in order to pass new validation. Remove any trailing slashes in
> the path column of the storage_pool table before starting agents.
> e.g.:
>
> mysql -e 'update cloud.storage_pool set path="/var/lib/libvirt/images"
> where path="/var/lib/libvirt/images/"';
>
> If using a custom path, insert your path in place of
> "/var/lib/libvirt/images/". If your custom path did not contain a
> trailing "/", there's no need to do this procedure.
[Animesh>] Marcus do you want to go ahead and update the Release Notes in 4.2 branch in file docs/en-US/Release_Notes.xml. I just finished making few other changes that were discussed.
>
> On Mon, Sep 23, 2013 at 3:00 PM, Chiradeep Vittal
> <Ch...@citrix.com> wrote:
> > +1 (binding)
> >
> > On 9/20/13 8:36 PM, "Animesh Chaturvedi"
> > <an...@citrix.com>
> > wrote:
> >
> >>
> >>
> >>
> >>
> >>I've created a 4.2.0 release, with the following artifacts up for a
> vote:
> >>
> >>Git Branch and Commit SH:
> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
> >>refs
> >>/heads/4.2
> >>Commit: 69c459342c568e2400d57ee88572b301603d8686
> >>
> >>List of changes:
> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
> >>f=CH
> >>ANGES;hb=4.2
> >>
> >>Source release (checksums and signatures are available at the same
> >>location):
> >>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> >>
> >>PGP release keys (signed using 94BE0D7C):
> >>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>
> >>Testing instructions are here:
> >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
> >>oced
> >>ure
> >>
> >>Vote will be open for 72 hours (Monday 9/23 PST EOD).
> >>
> >>For sanity in tallying the vote, can PMC members please be sure to
> >>indicate "(binding)" with their vote?
> >>
> >>[ ] +1 approve
> >>[ ] +0 no opinion
> >>[ ] -1 disapprove (and reason why)
> >>
> >>
> >
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Marcus Sorensen <sh...@gmail.com>.
I can change my vote to +1 if we include instructions similar to the
following in the upgrade notes:
If using local storage on KVM, the local storage path needs to be
changed in order to pass new validation. Remove any trailing slashes
in the path column of the storage_pool table before starting agents.
e.g.:
mysql -e 'update cloud.storage_pool set path="/var/lib/libvirt/images"
where path="/var/lib/libvirt/images/"';
If using a custom path, insert your path in place of
"/var/lib/libvirt/images/". If your custom path did not contain a
trailing "/", there's no need to do this procedure.
On Mon, Sep 23, 2013 at 3:00 PM, Chiradeep Vittal
<Ch...@citrix.com> wrote:
> +1 (binding)
>
> On 9/20/13 8:36 PM, "Animesh Chaturvedi" <an...@citrix.com>
> wrote:
>
>>
>>
>>
>>
>>I've created a 4.2.0 release, with the following artifacts up for a vote:
>>
>>Git Branch and Commit SH:
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs
>>/heads/4.2
>>Commit: 69c459342c568e2400d57ee88572b301603d8686
>>
>>List of changes:
>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CH
>>ANGES;hb=4.2
>>
>>Source release (checksums and signatures are available at the same
>>location):
>>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>>
>>PGP release keys (signed using 94BE0D7C):
>>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>>Testing instructions are here:
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proced
>>ure
>>
>>Vote will be open for 72 hours (Monday 9/23 PST EOD).
>>
>>For sanity in tallying the vote, can PMC members please be sure to
>>indicate "(binding)" with their vote?
>>
>>[ ] +1 approve
>>[ ] +0 no opinion
>>[ ] -1 disapprove (and reason why)
>>
>>
>
Re: [VOTE] Release Apache CloudStack 4.2.0 (sixth round)
Posted by Chiradeep Vittal <Ch...@citrix.com>.
+1 (binding)
On 9/20/13 8:36 PM, "Animesh Chaturvedi" <an...@citrix.com>
wrote:
>
>
>
>
>I've created a 4.2.0 release, with the following artifacts up for a vote:
>
>Git Branch and Commit SH:
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs
>/heads/4.2
>Commit: 69c459342c568e2400d57ee88572b301603d8686
>
>List of changes:
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CH
>ANGES;hb=4.2
>
>Source release (checksums and signatures are available at the same
>location):
>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
>
>PGP release keys (signed using 94BE0D7C):
>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>Testing instructions are here:
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proced
>ure
>
>Vote will be open for 72 hours (Monday 9/23 PST EOD).
>
>For sanity in tallying the vote, can PMC members please be sure to
>indicate "(binding)" with their vote?
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>