Hi all,
The XenServer 6.2 are done. Based on the tests I have execute against 2
different hypervisors, with a single host and a clustered host, my vote for the
4.6.0 RC2 is..
==> +1 (binding)
Test report below.
Cheers,
Wilder
:: Environment 1 ::
* Hardware required: TRUE
* Management Server + MySQL on CentOS 7.1
* Two XenServer 6.2 hosts
:: Tests Suites Executed ::
nosetests --with-marvin
--marvin-config=/data/shared/marvin/mct-zone1-xen1-ISOLATED.cfg -s -a
tags=advanced,required_hardware=true component/test_vpc_redundant.py
component/test_routers_iptables_default_policy.py
component/test_routers_network_ops.py component/test_vpc_router_nics.py
component/test_password_server.py component/test_router_dhcphosts.py
smoke/test_loadbalance.py smoke/test_ssvm.py smoke/test_network.py
:: Environment 2 ::
* Hardware required: FALSE
* Management Server + MySQL on CentOS 7.1
* Two XenServer 6.2 hosts
:: Tests Suites Executed ::
nosetests --with-marvin
--marvin-config=/data/shared/marvin/mct-zone1-xen1-ISOLATED.cfg -s -a
tags=advanced,required_hardware=false smoke/test_routers.py
smoke/test_reset_vm_on_reboot.py smoke/test_vm_life_cycle.py
component/test_vpc_routers.py smoke/test_service_offerings.py
component/test_vpc_offerings.py smoke/test_network_acl.py
smoke/test_privategw_acl.py smoke/test_network.py
:: Summary ::
* Tests executes: 71
* Successfull tests: 61
* Skipped tests: 10(*)
* Failed tests: 0
(*) Due to host credentials. It will works if we have if the DC has only 1
host. All those tests were executed successfully on KVM, when I had 1 host
only. See previous email.
:: Test results for Environment 1 ::
Create a redundant VPC with two networks with two VMs in each network ... SKIP:
Marvin configuration has no host credentials to
chec
k router services
Create a redundant VPC with two networks with two VMs in each network and check
default routes ... SKIP: Marvin configuration has no host credentials to
check router services
Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName:
test_02_routervm_iptables_policies | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policies on VPC router ... === TestName:
test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName:
test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics after
destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default
routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName:
test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... ===
TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName:
test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName:
test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName:
test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test SSVM Internals ... SKIP: Marvin configuration has no host
credentials to check router services
Test CPVM Internals ... SKIP: Marvin configuration has no host
credentials to check router services
Test stop SSVM ... SKIP: Marvin configuration has no host
credentials to check router services
Test stop CPVM ... SKIP: Marvin configuration has no host
credentials to check router services
Test reboot SSVM ... SKIP: Marvin configuration has no host
credentials to check router services
Test reboot CPVM ... SKIP: Marvin configuration has no host
credentials to check router services
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS ===
ok
Test destroy CPVM ... SKIP: Marvin configuration has no host
credentials to check router services
Test for port forwarding on source NAT ... === TestName:
test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName:
test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : SUCCESS
===
ok
Test for Router rules for network rules on acquired public IP ... === TestName:
test_network_rules_acquired_public_ip_1_static_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName:
test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName:
test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status : SUCCESS
===
ok
----------------------------------------------------------------------
Ran 29 tests in 8203.218s
OK (SKIP=9)
(END)
:: Test results for Environment 2 ::
Test router internal advanced zone ... SKIP: Marvin configuration has no host
credentials to check router services
Test restart network ... === TestName: test_03_restart_network_cleanup | Status
: SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status :
SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status :
SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS
===
ok
Test reset virtual machine on reboot ... === TestName:
test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter |
Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS
===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple
| Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS
===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status :
SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status :
SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status :
SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status :
SUCCESS ===
ok
Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS ===
ok
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm |
Status : SUCCESS ===
ok
Test start/stop of router after addition of one guest network ... === TestName:
test_01_start_stop_router_after_addition_of_one_guest_network | Status :
SUCCESS ===
ok
Test reboot of router after addition of one guest network ... === TestName:
test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to change service offering of router after addition of one guest network
... === TestName:
test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status
: SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName:
test_05_destroy_router_after_addition_of_one_guest_network | Status : SUCCESS
===
ok
Test to stop and start router after creation of VPC ... === TestName:
test_01_stop_start_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName:
test_02_reboot_router_after_creating_vpc | Status : SUCCESS ===
ok
Tests to change service offering of the Router after ... === TestName:
test_04_change_service_offerring_vpc | Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName:
test_05_destroy_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to create service offering ... === TestName:
test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName:
test_02_edit_service_offering | Status : SUCCESS ===
ok
Test to delete service offering ... === TestName:
test_03_delete_service_offering | Status : SUCCESS ===
ok
Test create VPC offering ... === TestName: test_01_create_vpc_offering | Status
: SUCCESS ===
ok
Test VPC offering without load balancing service ... === TestName:
test_03_vpc_off_without_lb | Status : SUCCESS ===
ok
Test VPC offering without static NAT service ... === TestName:
test_04_vpc_off_without_static_nat | Status : SUCCESS ===
ok
Test VPC offering without port forwarding service ... === TestName:
test_05_vpc_off_without_pf | Status : SUCCESS ===
ok
Test VPC offering with invalid services ... === TestName:
test_06_vpc_off_invalid_services | Status : SUCCESS ===
ok
Test update VPC offering ... === TestName: test_07_update_vpc_off | Status :
SUCCESS ===
ok
Test list VPC offering ... === TestName: test_08_list_vpc_off | Status :
SUCCESS ===
ok
test_09_create_redundant_vpc_offering
(integration.component.test_vpc_offerings.TestVPCOffering) ... === TestName:
test_09_create_redundant_vpc_offering | Status : SUCCESS ===
ok
test_privategw_acl (integration.smoke.test_privategw_acl.TestPrivateGwACL) ...
=== TestName: test_privategw_acl | Status : SUCCESS ===
ok
Test for delete account ... === TestName: test_delete_account | Status :
SUCCESS ===
ok
Test for Associate/Disassociate public IP address for admin account ... ===
TestName: test_public_ip_admin_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for user account ... ===
TestName: test_public_ip_user_account | Status : SUCCESS ===
ok
Test for release public IP address ... === TestName: test_releaseIP | Status :
SUCCESS ===
ok
----------------------------------------------------------------------
Ran 42 tests in 5350.271s
OK (SKIP=1)
(END)
On 11 Nov 2015, at 13:39, Wilder Rodrigues
<[email protected]<mailto:[email protected]>> wrote:
Hi Nux,
Concerning your second comment:
2 - after upgrading the packages to 4.6.0, the mgmt server complains the 4.5
systemvm is missing - wtf?
We explained how the upgrade is done in the issue ==>
https://issues.apache.org/jira/browse/CLOUDSTACK-9046
The current way ACS does the upgrade requires one to follow all the path. So,
going from 4.4.x to 4.6.x requires an upgrade to 4.5.x first. In order to avoid
that, you have to register a SystemVM template 4.5.x before as well. That’s how
I did that and how I have tested. All in the issue above. So, the second point
doesn’t really block the RC.
Now, about your first point, since you already mentioned how to get it working,
I wouldn’t say that’s a blocker, right?
Given the current state of the upgrade path, or how it is implemented, perhaps
the issue you created should be marked either “won’t fix” or be changed into an
improvement.
Cheers,
Wilder
On 11 Nov 2015, at 13:11, Nux!
<[email protected]<mailto:[email protected]><mailto:[email protected]>> wrote:
-1
I'm testing upgrade from 4.4.1 (what we run in production) to 4.6.0 and have
hit 2 issues.
1 - minor packaging issue, upgrading to 4.6.0 makes cloudstack-awsapi-4.4.1
complain about missing deps; rpm -e --nodeps cloudstack-awsapi gets rid of the
problem, perhaps there's a better way to obsolete this package
2 - after upgrading the packages to 4.6.0, the mgmt server complains the 4.5
systemvm is missing - wtf?
opened https://issues.apache.org/jira/browse/CLOUDSTACK-9056 for this with more
info
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro<http://www.nux.ro/><http://www.nux.ro<http://www.nux.ro/>>
----- Original Message -----
From: "Remi Bergsma"
<[email protected]<mailto:[email protected]>>
To: [email protected]<mailto:[email protected]>
Sent: Tuesday, 10 November, 2015 15:03:03
Subject: [VOTE] Apache CloudStack 4.6.0 (round 2)
Hi all,
I've created a 4.6.0 release candidate, 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=4.6.0-RC20151110T1545
Commit: e31ade03c66368c64f0cd66cb7b0b754cddfb79d
Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.6.0/
PGP release keys (signed using A47DDC4F):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS
Vote will be open for at least 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)
