+0 only because of the issues in the release notes, a clean install and an upgrade from 4.3.1 went OK, but only because I know how to do it, it would not work if I followed the release notes. The Router Upgrade notification elements in the UI, introduced in 4.3 are also broken (this should possibly be a -1 as it could result in installs running with the wrong version of the VRs without realising)
Notes: 2x XenServer 6.2 in a single Cluster NFS Primary Storage x2 System VM Template from http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4.4-2014-09-30-xen.vhd.bz2 Clean install of 4.4.1 to single management server on CentOS 6.5 with MySQL installed locally Created new Zone, POD, Cluster, Sec Storage, Hosts, Pri Storage all via API Updated Various Global Settings via API Created Domains and Accounts via API Deployed VMs for user account as Root and configured network Egress rules via API Deployed VM as root via UI Live Migrated VMs between Hosts Offline Migrated (VM stopped) Root Volume between Pri Storage via UI - cloudstack service crashed! (Install is running inside VirtualBox and Management VM is also NFS Server so added more RAM and tried again) - repeated test after a manual clean up and it was successful Live Migrated (VM running) Root Volume between Pri Storage via UI Disabled / Re-enabled Host Adding / removing NICs and changing default etc via UI Deployed new VPC, with two tiers, added VM to each tier, setup ACLs etc via API Then I did an upgrade test of a 4.3.1 system using the latest system VM template from Jenkins (this system was originally built on 4.3.0 and upgraded to 4.3.1, before being upgraded to 4.4.1) New System VM template installed OK The steps in the release notes about downloading vhd-utils for XenServer are misleading. If you blindly follow the steps the simply end up with a 2nd copy 'vhd-utils.1' as this is an upgrade and you will already have vhd-utils on the management server, at least if upgrading from a recent release such as 4.3.x. If vhd-utils needs replacing we need to be specific about removing the old one. I don’t think it actually needs replacing, it's just in a different location to older installs, but the 4.3 upgrade guide still has this step in it. (I can't remember which release changed the location) The MySQL Statements for the manual upgrade of the template are also incorrect as they do not include the DB name so fail e.g. select id,name from vm_template where name = 'systemvm-xenserver-4.4'; should be select id,name from cloud.vm_template where name = 'systemvm-xenserver-4.4'; The same with the following commands update vm_template set type='SYSTEM' where id='<ID FROM COMMAND #1>'; update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='ConsoleProxy' and hypervisor_type = 'xenserver'; update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='SecondaryStorageVm' and hypervisor_type = 'xenserver'; update configuration set value = 'systemvm-xenserver-4.4' where name = 'router.template.xen'; should be update cloud.vm_template set type='SYSTEM' where id='<ID FROM COMMAND #1>'; update cloud.vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='ConsoleProxy' and hypervisor_type = 'xenserver'; update cloud.vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='SecondaryStorageVm' and hypervisor_type = 'xenserver'; update cloud.configuration set value = 'systemvm-xenserver-4.4' where name = 'router.template.xen'; However I did not need to do this as the cloud.vm_instance table and cloud.configuration table had automatically been updated to the correct values, so are these steps actually necessary? 4.3 introduced the ability to manage the restart of VRs via the UI, but after upgrading to 4.4.1 the UI lists all VRs as NOT requiring upgrade, even though they have not been upgraded yet and are clearly shown as still be at version 4.3 I could fix the release notes issues, but there may be good reasons why they are how they are that I am not aware of, so just wanted to highlight them for now. I have only tested the XenServer upgrade steps and only from 4.3 so there may be similar errors in other sections. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -----Original Message----- From: Pierre-Luc Dion [mailto:pd...@cloudops.com] Sent: 30 September 2014 03:31 To: dev@cloudstack.apache.org Subject: Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 1 in branch 4.4-RC20140924T2100 +1 basic deployment, did tests upgrade from 4.3.0 and 4.2.1 to 4.4.1 , it went smoothly in both cases. I've tests using XenServer 6.2.0 with system vm from : http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/131/ Please let me know what should be the URLs for system vm that will goes in the RN if this vote pass. *Pierre-Luc DION* Architecte de Solution Cloud | Cloud Solutions Architect t 855.652.5683 *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Mon, Sep 29, 2014 at 5:22 PM, Ian Duffy <i...@ianduffy.ie> wrote: > Tested using XenServer 6.2.1. > > Brought up an environment within VirtualBox with basic networking and > booted a PE enabled template. > > Instance came up without issue, security groups worked, password > resets worked. > > +1 for basic functionality working. > > On 29 September 2014 15:49, Leo Simons <lsim...@schubergphilis.com> wrote: > > > * NOTICE is missing copyright statement (see other e-mail) > > * CHANGES.md does not list changes from 4.4.0 to 4.4.1 > > (list _is_ at > > > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en > /latest/fixed_issues.html > > ) > > * INSTALL.md states to get source code from git (see other e-mail) > > * checksums&sig ok > > * build & run from scratch based on README works > > * local automated tests inside devcloud-like virtual box pass > > (from tag) > > * jenkins-controlled automated tests inside SBP test environment pass > > (from 4.4 branch with identical code aside from version # change) > > > > +1 from me (non-binding :-D) > > > > > > cheers, > > > > > > Leo > > > > On Sep 29, 2014, at 12:01 AM, Daan Hoogland > > <daan.hoogl...@gmail.com> > > wrote: > > > Hi All, > > > > > > I've created a 4.4.1 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.4-RC20140924T2100 > > > Commit: 620ad650bdda23cabdf4c9dc480072c02c59a2d1 > > > > > > List of changes: > > > > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en > /latest/ > > > > > > Source release (checksums and signatures are available at the same > > > location): > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.4.1/ > > > > > > PGP release keys (signed using 4096R/AA4736F3): > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > > > > > Vote will be open for 72 hours. > > > > > > 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) > > > > > > -- > > > Daan > > > > > Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/> This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
