+1 (binding)
Tested RHEL 6.3 MS with XS 6.2 (fresh install). Followed test procedure
(s/4.3.0/4.3.1) to verify bits and hash.
--
Chiradeep
> On Sep 11, 2014, at 1:02 PM, "Sebastien Goasguen" wrote:
>
>
>> On Sep 11, 2014, at 3:56 PM, Wei ZHOU wrote:
>>
>> Sorry I just notice Rohit made a s
Upgraded one of my test environments, no issues found so far +1 binding.
On 9/11/14, 4:07 PM, Mike Tutkowski wrote:
Based on my regression testing, I am +1.
On Thu, Sep 11, 2014 at 1:50 PM, Sebastien Goasguen
wrote:
On Sep 11, 2014, at 3:47 PM, Mike Tutkowski
wrote:
OK, I looked into this
On 12-Sep-2014, at 6:43 am, Erik Weber wrote:
> Do we have an official upgrade path for those who want to upgrade?
Upgrade path exists between 4.3.0 and 4.3.1, and in 4.4 branch from 4.3.1 to
4.4.1.
To upgrade systemvms, you can add an new template or register/seed the template.
https://cwiki
Do we have an official upgrade path for those who want to upgrade?
Erik
12. sep. 2014 01:15 skrev "Rohit Yadav"
følgende:
> HI,
>
> On 11-Sep-2014, at 9:56 pm, Wei ZHOU wrote:
> > Sorry I just notice Rohit made a systemvm template change (commit
> > 3a0f1550289a8a2a50b0f786821cec2e5c914e62) on
HI,
On 11-Sep-2014, at 9:56 pm, Wei ZHOU wrote:
> Sorry I just notice Rohit made a systemvm template change (commit
> 3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
> The systemvm template will be built based on debian 7.5.0 instead of 7.4.0
The quoted commit and changes to use 7.5
Based on my regression testing, I am +1.
On Thu, Sep 11, 2014 at 1:50 PM, Sebastien Goasguen
wrote:
>
> On Sep 11, 2014, at 3:47 PM, Mike Tutkowski
> wrote:
>
> > OK, I looked into this more.
> >
> > It turns out the regression test that was failing is only valid in 4.4
> and
> > beyond, so it
On Sep 11, 2014, at 3:56 PM, Wei ZHOU wrote:
> Sorry I just notice Rohit made a systemvm template change (commit
> 3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
> The systemvm template will be built based on debian 7.5.0 instead of 7.4.0
>
Wei, can you test and vote ? that would
On Sep 11, 2014, at 3:47 PM, Mike Tutkowski
wrote:
> OK, I looked into this more.
>
> It turns out the regression test that was failing is only valid in 4.4 and
> beyond, so it is not a valid test for 4.3.
>
so can you vote ? we need your binding vote :)
> On Thu, Sep 11, 2014 at 11:14 AM,
Sorry I just notice Rohit made a systemvm template change (commit
3a0f1550289a8a2a50b0f786821cec2e5c914e62) on 9th, September.
The systemvm template will be built based on debian 7.5.0 instead of 7.4.0
==
commit 3a0f1550289a8a2a50b0f786821cec2e5c914e62
Author: Rohit Yadav
Date: Tue S
OK, I looked into this more.
It turns out the regression test that was failing is only valid in 4.4 and
beyond, so it is not a valid test for 4.3.
On Thu, Sep 11, 2014 at 11:14 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> I have an integration test failing when trying to create a
I have an integration test failing when trying to create a (XenServer)
storage repository.
Let me look into it for an hour or so and then I can respond back as to if
it's a code issue.
I'm thinking now it's a problem with XAPI. At first the code wasn't
compiling due to XAPI changes and now I'm ge
Except heartbleed fix.
I was merely checking if it's even poosible to do an automated upgrade.
The way i know the upgrade process we add some sql magic to check for new
systemvm templates. If that's not made for 4.3.1 it won't do much good to
add it as systemvm-hypervisor-version.
Erik
11. sep.
> Sent: Thursday, 11 September, 2014 2:44:57 PM
> Subject: Re: [VOTE] Release Apache CloudStack 4.3.1 round #4
>
> As far as I know, there is no systemvm change during upgrade from 4.3.0 to
> 4.3.1
>
> 2014-09-11 15:22 GMT+02:00 Erik Weber :
>
> > On Thu, Sep 11,
As far as I know, there is no systemvm change during upgrade from 4.3.0 to
4.3.1
2014-09-11 15:22 GMT+02:00 Erik Weber :
> On Thu, Sep 11, 2014 at 3:01 PM, Nux! wrote:
>
> > Hello,
> >
> > I've upgraded and it looks ok for now.
> > I have used these system VMs
> > http://jenkins.buildacloud.org/
On Thu, Sep 11, 2014 at 3:01 PM, Nux! wrote:
> Hello,
>
> I've upgraded and it looks ok for now.
> I have used these system VMs
> http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm/ and
> added them as systemvm-kvm-4.3 in the Templates.
> I expected them to replace SystemVM Templ
On Thu, Sep 11, 2014 at 3:15 PM, Rohit Yadav
wrote:
>
> On 11-Sep-2014, at 2:06 pm, Erik Weber wrote:
> > The spec requires openjdk 1.6 to build, but you can easily have both 1.6
> > and 1.7 installed and have it built with 1.7 if that is your default
> java,
> > am I correct?
> >
> > I'm not sa
On 11-Sep-2014, at 2:06 pm, Erik Weber wrote:
> The spec requires openjdk 1.6 to build, but you can easily have both 1.6
> and 1.7 installed and have it built with 1.7 if that is your default java,
> am I correct?
>
> I'm not saying this should warrant the vote to fail, just want to mention
> it.
2:16:44 PM
> Subject: Re: [VOTE] Release Apache CloudStack 4.3.1 round #4
>
>
> On 11-Sep-2014, at 11:10 am, Nux! wrote:
> > I'm going to try upgrading an existing 4.3.0 env, do we also need to
> > upgrade the SystemVMs?
>
> Ideally, yes
I'll revert my initial message.
Making sure the RPMs are built with openjdk 1.6 does indeed work, so this
is a build issue.
This is however something that could bite someone though.
The spec requires openjdk 1.6 to build, but you can easily have both 1.6
and 1.7 installed and have it built with
On 11-Sep-2014, at 11:10 am, Nux! wrote:
> I'm going to try upgrading an existing 4.3.0 env, do we also need to upgrade
> the SystemVMs?
Ideally, yes
Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +41 779015219 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
Find
On Thu, Sep 11, 2014 at 10:54 AM, Rohit Yadav
wrote:
> Hi Erik,
>
> On 11-Sep-2014, at 10:11 am, Erik Weber wrote:
> > I don't know if packaging issues is relevant or not, but rpms require
> > openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.
> >
> > [root@cloud-lab-node3 c
I'm going to try upgrading an existing 4.3.0 env, do we also need to upgrade
the SystemVMs?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "sebgoa"
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 10 September, 2014 4:31:09 PM
>
Hi Erik,
On 11-Sep-2014, at 10:11 am, Erik Weber wrote:
> I don't know if packaging issues is relevant or not, but rpms require
> openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.
>
> [root@cloud-lab-node3 cloudstack]# cat agent/cloudstack-agent.err
>
> log4j:WARN No appende
On Wed, Sep 10, 2014 at 5:31 PM, sebgoa wrote:
> Hi All,
>
> I've created a 4.3.1 release, with the following artifacts up for a vote:
>
>
I don't know if packaging issues is relevant or not, but rpms require
openjdk 1.6 rather than 1.7, which makes the kvm agent unable to start.
[root@cloud-la
+1 installed on KVM, tested with basic zone, vm lifecycles and other things as
recommended in the release test procedure but with KVM only.
New deb/rpm repo built out of this voting candidate (4.3.1-voting-04) can be
found and used from here:
http://packages.bhaisaab.org/cloudstack/main/
On 10-
+1 for me based on the fact that the Debian packages build fine and the
changelog says 4.3.1
I currently don't have a 4.3 dev environment available, so I wasn't able
to test the functionality.
Wido
On 09/10/2014 05:31 PM, sebgoa wrote:
> Hi All,
>
> I've created a 4.3.1 release, with the follow
26 matches
Mail list logo
