Hello all

+1 (binding) from my side considering the following tests:

*Test environment configurations:*
- Apache CloudStack: Management server + DB (Ubuntu 18.04)
- Hosts: KVM (Ubuntu 18.04)
- Shared storage: Ceph/RBD
- Local storage: KVM file system
- Secondary Storage: NFS
*Network:*
- Advanced network with Security Group
- Basic network with Security Group
*Main tests:*
- Build 4.13.0.0 from source
- Update cloudstack-management.service on the management node
- Update cloudstack-management.service running on KVM hosts
- CPVM & SSVM health check
- Test user VM lifecycle (deploy, stop/start, migrate, restart, destroy,
expunge)
- Test VM volume "offline" migration (Ceph <> Ceph, Ceph <> local, local <>
local)
- Put a host in maintenance and "recover" it back to Up/Enabled
- VM live migration shared storage (Ceph/RBD)
- VM live migration local storage (filesystem KVM)
- Deploy VMs via UI in advanced networks with SG and IPv6 CIDR #3571
- SG rules correctly deployed and migrated along with VM (live migrate VM
and check that SG is removed at the old host and added at the newer one)

*Issues considered as a blocker:* None

*Raised flags:*
- Libvirt exception when trying to migrate VM on local storage: I will
investigate deeper; however, I did not classify this issue as a blocker due
to the fact that I could not reproduce on another test environemt (also
live migrating VM allocated on KVM + Ubuntu 18.04 local storage).
Exception: "Copy operation failed in
'StorageSystemDataMotionStrategy.copyAsync': org.libvirt.LibvirtException:
End of file while reading data: Input/output error"
- Schema SQL upgrade path has a few "INSERT INTO" without the "IGNORE"
(INSERT IGNORE INTO `cloud`.<TABLE>). Would cause an issue when reverting
from an updated environment, but not an issue for most of the users and it
is definitely not a blocker
- A few glitches on UI, nothing that would cause big issues for the end user

Regards,
Gabriel.

Em sáb, 31 de ago de 2019 às 08:00, Gabriel Beims Bräscher <
gabrasc...@gmail.com> escreveu:

> Hi Paul,
>
> I am testing the RC, final checks on the way. I will be updating my
> feedback here soon.
>
> Thanks!
>
> Em sáb, 31 de ago de 2019 às 07:57, Paul Angus <paul.an...@shapeblue.com>
> escreveu:
>
>> We're looking good to for a release, but I'm just holding off to hear
>> from Gabriel who raised a blocker last time around.
>>
>> @gabrasc...@gmail.com <gabrasc...@gmail.com>  are you testing this RC
>> (should we wait for you)?
>>
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> @shapeblue
>>
>>
>>
>> ------------------------------
>> *From:* Ismaili, Liridon (SWISS TXT) <liridon.isma...@swisstxt.ch>
>> *Sent:* Friday, August 30, 2019 3:54:45 PM
>> *To:* dev@cloudstack.apache.org <dev@cloudstack.apache.org>;
>> us...@cloudstack.apache.org <us...@cloudstack.apache.org>
>> *Subject:* Re: [VOTE] Apache CloudStack 4.13.0.0 RC2
>>
>> Hi Guys,
>>
>> +1 from our side
>>
>> Following upgrade was done:
>> from 4.11.3 to 4.13 RC2
>> - VMWare 6.5
>> - Advanced network setup
>>
>> Post upgrade steps:
>> - redeployed systemVMs
>> - redeployed vRouters
>>
>> Tests done:
>> - create / started / stopped / destroyed VMs which were created before
>> and after the upgrade
>> - create / restart / cleanup / redundant vRouters
>> - upload / delete templates and multi disk templates
>> - create / delete projects / accounts / users
>>
>> Regards
>> Liridon
>>
>> -----Original Message-----
>> From: Paul Angus <paul.an...@shapeblue.com<mailto:
>> paul%20angus%20%3cpaul.an...@shapeblue.com%3e>>
>> Reply-To: us...@cloudstack.apache.org<mailto:us...@cloudstack.apache.org>
>> To: dev@cloudstack.apache.org <dev@cloudstack.apache.org<mailto:%
>> 22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
>> us...@cloudstack.apache.org <us...@cloudstack.apache.org<mailto:%
>> 22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
>> Subject: [VOTE] Apache CloudStack 4.13.0.0 RC2
>> Date: Wed, 28 Aug 2019 22:02:32 +0000
>>
>>
>> Hi All,
>>
>>
>> We had an excellently low number of bugs in RC1, so here's RC2 with just
>> 3 fixes...
>>
>>
>> I've created a 4.13.0.0 release (RC2), with the following artefacts up
>> for testing and a vote:
>>
>>
>> Git Branch and Commit SH:
>>
>> <
>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535
>> >
>>
>>
>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535
>>
>>
>> Commit: 7c7efe76013675b476d8aa14c36a353cd5d429fc
>>
>>
>> Source release (checksums and signatures are available at the same
>> location):
>>
>> <https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/>
>>
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/
>>
>>
>>
>> PGP release keys (signed using 51EE0BC8):
>>
>> <https://dist.apache.org/repos/dist/release/cloudstack/KEYS>
>>
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>>
>>
>> The vote will be open until 31st August.
>>
>>
>> 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)
>>
>>
>> Additional information:
>>
>>
>> For users' convenience, I've built packages from
>> 7c7efe76013675b476d8aa14c36a353cd5d429fc and published RC1 repository here:
>>
>> <http://packages.shapeblue.com/testing/41300rc2/>
>>
>> http://packages.shapeblue.com/testing/41300rc2/
>>
>>
>>
>> The systemvm templates are unchanged from 4.11.3/4.12.0:
>>
>> <http://download.cloudstack.org/systemvm/4.11/>
>>
>> http://download.cloudstack.org/systemvm/4.11/
>>
>>
>>
>> Fixes in RC2
>>
>>
>> #3566   server: fix NPE for the case where volume is not attached to a VM
>>
>> #3567   fix xenserver 7.1.0 os mapping typo
>>
>> #3571   Unable to deploy VMs via UI in advanced networks with SG and IPv6
>> cidr
>>
>>
>>
>>
>>
>> <mailto:paul.an...@shapeblue.com <paul.an...@shapeblue.com>>
>>
>> paul.an...@shapeblue.com
>>
>>
>>
>> <http://www.shapeblue.com>
>>
>> www.shapeblue.com
>>
>>
>> Amadeus House, Floral Street, London  WC2E 9DPUK
>>
>> @shapeblue
>>
>>
>>
>>
>>
>>

Reply via email to