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 <rohit.ya...@shapeblue.com>
Date:   Tue Sep 9 18:37:15 2014 +0200

    appliance: fix newer debian iso links and checksums for debian

    Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
    (cherry picked from commit ac5309b8b47ddb1e5588a2d5090f2bcce0e7c2a4)

    Conflicts:
        tools/appliance/definitions/systemvm64template/definition.rb
        tools/appliance/definitions/systemvmtemplate/definition.rb

diff --git a/tools/appliance/definitions/systemvm64template/definition.rb
b/tools/appliance/definitions/systemvm64template/definition.rb
index f9308a0..bd59025 100644
--- a/tools/appliance/definitions/systemvm64template/definition.rb
+++ b/tools/appliance/definitions/systemvm64template/definition.rb
@@ -3,9 +3,9 @@ Veewee::Definition.declare({
   :memory_size=> '256',
   :disk_size => '2500', :disk_format => 'VDI', :hostiocache => 'off',
   :os_type_id => 'Debian_64',
-  :iso_file => "debian-7.4.0-amd64-netinst.iso",
-  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.4.0/amd64/iso-cd/debian-7.4.0-amd64-netinst.iso
",
-  :iso_md5 => "e7e9433973f082a297793c3c5010b2c5",
+  :iso_file => "debian-7.5.0-amd64-netinst.iso",
+  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.5.0/amd64/iso-cd/debian-7.5.0-amd64-netinst.iso
",
+  :iso_md5 => "8fdb6715228ea90faba58cb84644d296",
   :iso_download_timeout => "1000",
   :boot_wait => "10", :boot_cmd_sequence => [
      '<Esc>',
diff --git a/tools/appliance/definitions/systemvmtemplate/definition.rb
b/tools/appliance/definitions/systemvmtemplate/definition.rb
index fcaab4d..9b57379 100644
--- a/tools/appliance/definitions/systemvmtemplate/definition.rb
+++ b/tools/appliance/definitions/systemvmtemplate/definition.rb
@@ -3,9 +3,9 @@ Veewee::Definition.declare({
   :memory_size=> '256',
   :disk_size => '2500', :disk_format => 'VDI', :hostiocache => 'off',
   :os_type_id => 'Debian',
-  :iso_file => "debian-7.4.0-i386-netinst.iso",
-  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.4.0/i386/iso-cd/debian-7.4.0-i386-netinst.iso
",
-  :iso_md5 => "7339b668a81b417ac023d73739dc6a03",
+  :iso_file => "debian-7.5.0-i386-netinst.iso",
+  :iso_src => "
http://cdimage.debian.org/mirror/cdimage/archive/7.5.0/i386/iso-cd/debian-7.5.0-i386-netinst.iso
",
+  :iso_md5 => "0e6eaacb5a5828473afe90f6df9c8f16",
   :iso_download_timeout => "1000",
   :boot_wait => "10", :boot_cmd_sequence => [
      '<Esc>',


2014-09-11 21:50 GMT+02:00 Sebastien Goasguen <run...@gmail.com>:

>
> On Sep 11, 2014, at 3:47 PM, Mike Tutkowski <mike.tutkow...@solidfire.com>
> 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, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> 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 getting this XAPI issue when
> >> trying to create a storage repository. Seems possibly related.
> >>
> >> On Thu, Sep 11, 2014 at 10:37 AM, Erik Weber <terbol...@gmail.com>
> wrote:
> >>
> >>> 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. 2014 15:45 skrev "Wei ZHOU" <ustcweiz...@gmail.com> følgende:
> >>>
> >>>> 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 <terbol...@gmail.com>:
> >>>>
> >>>>> On Thu, Sep 11, 2014 at 3:01 PM, Nux! <n...@li.nux.ro> 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 Template (KVM), but they are
> >>> still
> >>>>>> listed as systemvm-kvm-4.3 alongside the old ones.
> >>>>>> Other than that everything seems ok for now.
> >>>>>>
> >>>>>>
> >>>>> Is there an upgrade path from 4.3.0 systemvm template to 4.3.1? Log
> on
> >>>> to a
> >>>>> newly deployed one and check /etc/cloudstack-version
> >>>>>
> >>>>> --
> >>>>> Erik
> >>>>>
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the cloud
> >> <http://solidfire.com/solution/overview/?video=play>*™*
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > <http://solidfire.com/solution/overview/?video=play>*™*
>
>

Reply via email to