Hi all,

+1 (binding)

Tested:
========
1. Advanced zone with XenServer
- Deployed VPCs, VMs and VPNs between them
- Crashed a XenServer, watched it recover
- Tested it again and all was fine. All I had to do was reset the VPN 
connection, but maybe it'd have done it automatically if I waited longer.

2. Advanced zone with KVM (on CentOS 7 that is, after some manual tweaks)
- Advanced zone with XenServer
- Deployed VPCs, VMs and VPNs between them
- Crashed a KVM hypervisor, watched it recover
- Tested it again and all was fine. VPN recovery was automatic.

3. Upgraded 4.4.4 -> 4.5.2 
It went fine.

About KVM on CentOS 7
At work we're actually running KVM on CentOS 7, on ACS 4.4.x. Although I know 
not many people do. I tried it on 4.5.2 and encountered the issues described in 
CLOUDSTACK-8443. I checked the documentation and it said we only support CentOS 
6.3 (I assume .3 should be .x but anyway) on ACS 4.5.x so I'll just ignore this 
for now.

I have updated the Jira issue with some findings and I will investigate this 
further, so we can fix it and at least start supporting CentOS 7 as a KVM 
hypervisor out-of-the-box in 4.6.

If we feel we want to fix KVM on CentOS 7 in 4.5.2 then we need another 
4.5.2RC, in which case I'm happy to help making it happen ;-)

Regards,
Remi



> On 20 Aug 2015, at 08:26, Rajani Karuturi <raj...@apache.org> wrote:
> 
> +1(binding)
> 
> tested fresh install on xenserver 6.5 advanced zone setup.
> 
> register template, create network, launch vm, view console etc. worked fine.
> 
> 
> ~Rajani
> 
> On Thu, Aug 20, 2015 at 12:04 AM, Milamber <milam...@apache.org> wrote:
> 
>> Hello,
>> 
>> +1 (binding)
>> 
>> * Building CloudStack ubuntu packages from Git 4.5.2 RC2 tag.
>> 
>> * Tests migration from 4.4.4 -> 4.5.2rc2 on Ubuntu 14.04.3 (1 mgr, 2
>> nodes, 1 nfs), basic install, NFS storage, KVM, SystemVM shapeblue, After
>> migration: some tests on HA (crash node), some tests with templates,
>> account management in webui, test localization french, and CS<->cloud-init
>> on debian.
>> 
>> * Tests fresh install on Ubuntu 14.04.3 (1 mgr, 2 nodes, 1 nfs), advanced
>> network install NFS storage, KVM, SystemVM shapeblue, some tests on HA
>> (crash node), some tests with templates, and CS<->cloud-init on debian.
>> 
>> * Some tests (register template, create network, register ssh key, create
>> instance, get IP) with Ansible + ansible-cloudstack module from @resmo
>> 
>> Thanks for the RM.
>> 
>> Milamber
>> 
>> 
>> Please note this bug message in the last migration step (when I rebooted
>> all systemvm/router).
>> 
>> root@cs-mgr1:~# cloudstack-sysvmadm -d 127.0.0.1 -u cloud -p cloudPass -a
>> /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such
>> file or directory
>> 
>> Stopping and starting 1 secondary storage vm(s)...
>> Done stopping and starting secondary storage vm(s)
>> 
>> Stopping and starting 1 console proxy vm(s)...
>> Done stopping and starting console proxy vm(s) .
>> 
>> Stopping and starting 1 running routing vm(s)...
>> Done restarting router(s).
>> 
>> 
>> 
>> 
>> On 19/08/2015 10:22, Rohit Yadav wrote:
>> 
>>> Hi All,
>>> 
>>> I've created a 4.5.2 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.5-RC20150819T1442
>>> Commit: 7385441807ba3fde3d45c226df6b1bdd2f36ae26
>>> Tag: 4.5.2-rc2
>>> 
>>> List of changes:
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.5-RC20150819T1442
>>> 
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.2/
>>> 
>>> PGP release keys (signed using 0EE3D884):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>> 
>>> The 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)
>>> 
>>> Regards.
>>> 
>>> 
>> 

Reply via email to