[GitHub] cloudstack issue #1900: CLOUDSTACK-8862: Introduced new state attaching for ...
Github user cloudmonger commented on the issue: https://github.com/apache/cloudstack/pull/1900 ### ACS CI BVT Run **Sumarry:** Build Number 358 Hypervisor xenserver NetworkType Advanced Passed=105 Failed=0 Skipped=7 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** **Skipped tests:** test_01_test_vm_volume_snapshot test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_11_ss_nfs_version_on_ssvm test_nested_virtualization_vmware test_3d_gpu_support test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_loadbalance.py test_routers.py test_reset_vm_on_reboot.py test_deploy_vms_with_varied_deploymentplanners.py test_network.py test_router_dns.py test_non_contigiousvlan.py test_login.py test_deploy_vm_iso.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_routers_network_ops.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1886: CLOUDSTACK-9728: Fixed traffic sentinel HTTP 414 err...
Github user cloudmonger commented on the issue: https://github.com/apache/cloudstack/pull/1886 ### ACS CI BVT Run **Sumarry:** Build Number 357 Hypervisor xenserver NetworkType Advanced Passed=103 Failed=2 Skipped=7 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** * test_routers_network_ops.py * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failing since 2 runs * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failing since 3 runs **Skipped tests:** test_01_test_vm_volume_snapshot test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_11_ss_nfs_version_on_ssvm test_nested_virtualization_vmware test_3d_gpu_support test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_loadbalance.py test_routers.py test_reset_vm_on_reboot.py test_deploy_vms_with_varied_deploymentplanners.py test_network.py test_router_dns.py test_non_contigiousvlan.py test_login.py test_deploy_vm_iso.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: No removed date for templates after account cleanup
Hi Dmytro, That is intentional, which was introduced as part of CLOUDSTACK-5997. Please refer to CLOUDSTACK-5997 (https://issues.apache.org/jira/browse/CLOUDSTACK-5997) for more details. -Suresh On 19/02/17, 2:29 AM, "Dmytro Shevchenko" wrote: Hi all, Is this a bug when you removing account, all templates marked as Inactive, but 'removed' column = NULL in vm_template table? CS version: 4.8.0.1 -- Best regards Dmytro Shevchenko DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Accelerite, a Persistent Systems business. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent Systems business does not accept any liability for virus infected mails.
No removed date for templates after account cleanup
Hi all, Is this a bug when you removing account, all templates marked as Inactive, but 'removed' column = NULL in vm_template table? CS version: 4.8.0.1 -- Best regards Dmytro Shevchenko
Re: Attaching more than 14 data volumes to an instance
Thanks for bringing this up. The max data volumes limit of a VM should be based on the hypervisor capabilities, instead of the hardcoded value. I created the PR# 1953 (https://github.com/apache/cloudstack/pull/1953). Please check. Even though the underlying hypervisor supports more limit, it is being restricted in CloudStack using the limits set in cloud.hypervisor_capabilities table. Only max number of Guest VMs per host (max_guests_limit, which was introduced initially) can be updated using the API updateHypervisorCapabilities. The other limits (max_data_volumes_limit, max_hosts_per_cluster), that were introduced later, are not part of updateHypervisorCapabilities API. This API has to be improved to include these limits as well. I’m working on this, will raise a PR. I checked the limits set for VMware hypervisor and observed some discrepancies. These can be either updated from the updateHypervisorCapabilities API (max_data_volumes_limit, max_hosts_per_cluster after improvements) or schema update during upgradation. Which one would be better? For schema update, I have to raise a PR. mysql> SELECT hypervisor_version, max_guests_limit, max_data_volumes_limit, max_hosts_per_cluster FROM cloud.hypervisor_capabilities where hypervisor_type = 'VMware'; ++--++---+ | hypervisor_version | max_guests_limit | max_data_volumes_limit | max_hosts_per_cluster | ++--++---+ | 4.0| 128 | 13 | 32 | | 4.1| 128 | 13 | 32 | | 5.0| 128 | 13 | 32 | | 5.1| 128 | 13 | 32 | | 5.5| 128 | 13 | 32 | | 6.0| 128 | 13 | 32 | | default| 128 | 13 | 32 | ++--++---+ 7 rows in set (0.00 sec) Actual VMware maximum limits => max_guests_limit: 128(3.5), 320(4.0, 4.1), 512(5.0, 5.1, 5.5), 1024(6.0) max_data_volumes_limit: 60 - SCSI + 4 - IDE (3.5, 4.0, till 6.0) max_hosts_per_cluster:32 (3.5, 4.0, till 5.5); 64(6.0) -Suresh On 16/02/17, 11:06 AM, "Koushik Das" wrote: The hardcoded value of 15 needs to be fixed, it can be replaced with getMaxDataVolumesSupported() just above it. Please file a bug and if possible raise a PR as well. -Koushik On 15/02/17, 11:21 PM, "Voloshanenko Igor" wrote: On VM we try to emulate real hardware ))) So any device honor specification In this case PCI :) To be honest we can increase limits by adding multifunctional devices or migrate to virtio-iscsi-blk But as for me - 14 disks more than enough now About 3 for cdrom. I will check . I think CDROM emulated as IDE device, not via virtio-blk For 0 - root volume , interesting , in this case we can easily add 1 more DATA disk :) ср, 15 февр. 2017 г. в 19:24, Rafael Weingärtner < rafaelweingart...@gmail.com>: > I thought that on a VM we would not be bound by PCI limitations. > Interesting explanations, thanks. > > > On Wed, Feb 15, 2017 at 12:19 PM, Voloshanenko Igor < > igor.voloshane...@gmail.com> wrote: > > > I think explanation very easy. > > PCI itself can handle up to 32 devices. > > > > If you run lspci inside empty (fresh created) VM - you will see, that 8 > > slots already occupied > > [root@test-virtio-blk ~]# lspci > > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev > > 02) > > 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton > II] > > 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton > > II] > > 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB > [Natoma/Triton > > II] (rev 01) > > 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) > > 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 > > 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device > > 00:04.0 SCSI storage controller: Red Hat, Inc Virtio block device > > > > [root@test-virtio-blk ~]# lspci | wc -l > > 8 > > > > So, 7 system devices + 1 ROOT disk > > > > in current implementation, we used virtio-blk
[GitHub] cloudstack pull request #1953: CLOUDSTACK-9794: Unable to attach more than 1...
GitHub user sureshanaparti opened a pull request: https://github.com/apache/cloudstack/pull/1953 CLOUDSTACK-9794: Unable to attach more than 14 devices to a VM Updated hardcoded value with max data volumes limit from hypervisor capabilities. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9794 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1953.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1953 commit cdf50c1e0f69297beb335f852ae82663bbc87fb4 Author: Suresh Kumar Anaparti Date: 2017-02-18T20:22:30Z CLOUDSTACK-9794: Unable to attach more than 14 devices to a VM Updated hardcoded value with max data volumes limit from hypervisor capabilities. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1885: CLOUDSTACK-9724: Fixed missing additional public ip ...
Github user cloudmonger commented on the issue: https://github.com/apache/cloudstack/pull/1885 ### ACS CI BVT Run **Sumarry:** Build Number 356 Hypervisor xenserver NetworkType Advanced Passed=101 Failed=2 Skipped=7 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** * test_router_dns.py * test_router_dns_guestipquery Failing since 2 runs * test_routers_network_ops.py * ContextSuite context=TestRedundantIsolateNetworks>:setup Failed **Skipped tests:** test_01_test_vm_volume_snapshot test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_11_ss_nfs_version_on_ssvm test_nested_virtualization_vmware test_3d_gpu_support test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_loadbalance.py test_routers.py test_reset_vm_on_reboot.py test_deploy_vms_with_varied_deploymentplanners.py test_network.py test_non_contigiousvlan.py test_login.py test_deploy_vm_iso.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1866: Advanced isolated network egress destination cidr su...
Github user cloudmonger commented on the issue: https://github.com/apache/cloudstack/pull/1866 ### ACS CI BVT Run **Sumarry:** Build Number 355 Hypervisor xenserver NetworkType Advanced Passed=78 Failed=17 Skipped=7 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** * test_vm_snapshots.py * test_change_service_offering_for_vm_with_snapshots Failed * test_01_create_vm_snapshots Failed * test_02_revert_vm_snapshots Failed * test_03_delete_vm_snapshots Failed * test_service_offerings.py * test_04_change_offering_small Failed * test_loadbalance.py * test_01_create_lb_rule_src_nat Failed * test_02_create_lb_rule_non_nat Failed * test_assign_and_removal_lb Failed * test_router_dns.py * test_router_dns_guestipquery Failed * test_non_contigiousvlan.py * test_extendPhysicalNetworkVlan Failing since 2 runs * test_volumes.py * test_01_create_volume Failed * test_02_attach_volume Failed * test_vm_life_cycle.py * test_10_attachAndDetach_iso Failed * test_routers_network_ops.py * test_01_isolate_network_FW_PF_default_routes_egress_true Failed * test_02_isolate_network_FW_PF_default_routes_egress_false Failed * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failed * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failing since 2 runs **Skipped tests:** test_01_test_vm_volume_snapshot test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_11_ss_nfs_version_on_ssvm test_nested_virtualization_vmware test_3d_gpu_support test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_routers_iptables_default_policy.py test_routers.py test_reset_vm_on_reboot.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_deploy_vm_iso.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_disk_offerings.py --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1829: CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1829 LGTM, code and (regression) tests. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
