subject:"\[jira\] \[Commented\] \(CLOUDSTACK\-9184\) \[VMware\] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards"

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472888#comment-16472888
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388525919
 
 
   Trillian test result (tid-2667)
   Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 29153 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2634-t2667-vmware-65.zip
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Smoke tests completed. 63 look OK, 4 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_03_vpc_privategw_restart_vpc_cleanup | `Error` | 199.22 | 
test_privategw_acl.py
   test_04_extract_template | `Failure` | 138.61 | test_templates.py
   ContextSuite context=TestISOUsage>:setup | `Error` | 0.00 | test_usage.py
   test_06_download_detached_volume | `Failure` | 160.08 | test_volumes.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472466#comment-16472466
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388451236
 
 
   @blueorangutan test centos7 vmware-65
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472467#comment-16472467
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388451356
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-65) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472314#comment-16472314
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388429463
 
 
   Trillian test result (tid-2663)
   Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 16951 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2634-t2663-vmware-65.zip
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_public_ip_range.py
   Intermitten failure detected: /marvin/tests/smoke/test_reset_vm_on_reboot.py
   Intermitten failure detected: /marvin/tests/smoke/test_router_dhcphosts.py
   Intermitten failure detected: /marvin/tests/smoke/test_router_dns.py
   Intermitten failure detected: /marvin/tests/smoke/test_router_dnsservice.py
   Intermitten failure detected: 
/marvin/tests/smoke/test_routers_iptables_default_policy.py
   Intermitten failure detected: /marvin/tests/smoke/test_routers_network_ops.py
   Intermitten failure detected: /marvin/tests/smoke/test_routers.py
   Intermitten failure detected: /marvin/tests/smoke/test_scale_vm.py
   Intermitten failure detected: /marvin/tests/smoke/test_secondary_storage.py
   Intermitten failure detected: /marvin/tests/smoke/test_service_offerings.py
   Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
   Intermitten failure detected: /marvin/tests/smoke/test_ssvm.py
   Intermitten failure detected: /marvin/tests/smoke/test_templates.py
   Intermitten failure detected: /marvin/tests/smoke/test_usage.py
   Intermitten failure detected: /marvin/tests/smoke/test_vm_life_cycle.py
   Intermitten failure detected: /marvin/tests/smoke/test_vm_snapshots.py
   Intermitten failure detected: /marvin/tests/smoke/test_volumes.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_redundant.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_router_nics.py
   Intermitten failure detected: /marvin/tests/smoke/test_vpc_vpn.py
   Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py
   Smoke tests completed. 45 look OK, 22 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_03_vpc_privategw_restart_vpc_cleanup | `Error` | 189.64 | 
test_privategw_acl.py
   ContextSuite context=TestResetVmOnReboot>:setup | `Error` | 0.00 | 
test_reset_vm_on_reboot.py
   ContextSuite context=TestRouterDHCPHosts>:setup | `Error` | 0.00 | 
test_router_dhcphosts.py
   ContextSuite context=TestRouterDHCPOpts>:setup | `Error` | 0.00 | 
test_router_dhcphosts.py
   ContextSuite context=TestRouterDns>:setup | `Error` | 0.00 | 
test_router_dns.py
   ContextSuite context=TestChangeServiceOfferingForVmWithSnapshots>:setup | 
`Error` | 0.00 | test_vm_snapshots.py
   ContextSuite context=TestVmSnapshot>:setup | `Error` | 0.00 | 
test_vm_snapshots.py
   ContextSuite context=TestRouterDnsService>:setup | `Error` | 0.00 | 
test_router_dnsservice.py
   ContextSuite context=TestRouterIpTablesPolicies>:setup | `Error` | 0.00 | 
test_routers_iptables_default_policy.py
   ContextSuite context=TestVPCIpTablesPolicies>:setup | `Error` | 0.00 | 
test_routers_iptables_default_policy.py
   test_01_isolate_network_FW_PF_default_routes_egress_true | `Error` | 0.16 | 
test_routers_network_ops.py
   test_02_isolate_network_FW_PF_default_routes_egress_false | `Error` | 0.16 | 
test_routers_network_ops.py
   ContextSuite context=TestRedundantIsolateNetworks>:setup | `Error` | 1.33 | 
test_routers_network_ops.py
   ContextSuite context=TestRouterServices>:setup | `Error` | 0.00 | 
test_routers.py
   ContextSuite context=TestScaleVm>:setup | `Error` | 0.00 | test_scale_vm.py
   test_01_sys_vm_start | `Failure` | 0.10 | test_secondary_storage.py
   test_02_sys_template_ready | `Failure` | 0.09 | test_secondary_storage.py
   ContextSuite context=TestServiceOfferings>:setup | `Error` | 0.18 | 
test_service_offerings.py
   ContextSuite context=TestCreateVolume>:setup | `Error` | 0.00 | 
test_volumes.py
   ContextSuite context=TestVolumes>:setup | `Error` | 0.00 | test_volumes.py
   ContextSuite context=TestSnapshotRootDisk>:setup | `Error` | 0.00 | 
test_snapshots.py
   test_01_list_sec_storage_vm | `Failure` | 0.03 | test_ssvm.py
   test_02_list_cpvm_vm | `Failure` | 0.03 | test_ssvm.py
   test_03_ssvm_internals | `Failure` | 0.03 | test_ssvm.py
   test_04_cpvm_internals | `Failure` | 0.03 | test_ssvm.py
   test_05_stop_ssvm | `Failure` | 0.03 | test_ssvm.py
   test_06_stop_cpvm | `Failure` | 0.03 | test_ssvm.py
   test_07_reboot_ssvm | `Failure` | 0.03 | test_ssvm.py

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472263#comment-16472263
 ] 

ASF subversion and git services commented on CLOUDSTACK-9184:
-

Commit 1b3046e3767a5e2a989ae7a47d35289cec3f06bf in cloudstack's branch 
refs/heads/master from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1b3046e ]

CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth (#2634)

* CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth

This deprecates the vmware.ports.per.dvportgroup global setting.

The vSphere Auto Expand feature (introduced in vSphere 5.0) will take
care of dynamically increasing/decreasing the dvPorts when running out
of distributed ports . But in case of vSphere 4.1/4.0 (If used), as this
feature is not there, the new default value (=> 8) have an impact in the
existing deployments. Action item for vSphere 4.1/4.0: Admin should
modify the global configuration setting "vmware.ports.per.dvportgroup"
from 8 to any number based on their environment because the proposal
default value of 8 would be very less without auto expand feature in
general. The current default value of 256 may not need immediate
modification after deployment, but 8 would be very less which means
admin need to update immediately after upgrade.

Signed-off-by: Rohit Yadav 

> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472262#comment-16472262
 ] 

ASF subversion and git services commented on CLOUDSTACK-9184:
-

Commit 1b3046e3767a5e2a989ae7a47d35289cec3f06bf in cloudstack's branch 
refs/heads/master from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1b3046e ]

CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth (#2634)

* CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth

This deprecates the vmware.ports.per.dvportgroup global setting.

The vSphere Auto Expand feature (introduced in vSphere 5.0) will take
care of dynamically increasing/decreasing the dvPorts when running out
of distributed ports . But in case of vSphere 4.1/4.0 (If used), as this
feature is not there, the new default value (=> 8) have an impact in the
existing deployments. Action item for vSphere 4.1/4.0: Admin should
modify the global configuration setting "vmware.ports.per.dvportgroup"
from 8 to any number based on their environment because the proposal
default value of 8 would be very less without auto expand feature in
general. The current default value of 256 may not need immediate
modification after deployment, but 8 would be very less which means
admin need to update immediately after upgrade.

Signed-off-by: Rohit Yadav 

> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472247#comment-16472247
 ] 

ASF subversion and git services commented on CLOUDSTACK-9184:
-

Commit 1b3046e3767a5e2a989ae7a47d35289cec3f06bf in cloudstack's branch 
refs/heads/4.11 from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1b3046e ]

CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth (#2634)

* CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth

This deprecates the vmware.ports.per.dvportgroup global setting.

The vSphere Auto Expand feature (introduced in vSphere 5.0) will take
care of dynamically increasing/decreasing the dvPorts when running out
of distributed ports . But in case of vSphere 4.1/4.0 (If used), as this
feature is not there, the new default value (=> 8) have an impact in the
existing deployments. Action item for vSphere 4.1/4.0: Admin should
modify the global configuration setting "vmware.ports.per.dvportgroup"
from 8 to any number based on their environment because the proposal
default value of 8 would be very less without auto expand feature in
general. The current default value of 256 may not need immediate
modification after deployment, but 8 would be very less which means
admin need to update immediately after upgrade.

Signed-off-by: Rohit Yadav 

> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472248#comment-16472248
 ] 

ASF subversion and git services commented on CLOUDSTACK-9184:
-

Commit 1b3046e3767a5e2a989ae7a47d35289cec3f06bf in cloudstack's branch 
refs/heads/4.11 from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=1b3046e ]

CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth (#2634)

* CLOUDSTACK-9184: Fixes #2631 VMware dvs portgroup autogrowth

This deprecates the vmware.ports.per.dvportgroup global setting.

The vSphere Auto Expand feature (introduced in vSphere 5.0) will take
care of dynamically increasing/decreasing the dvPorts when running out
of distributed ports . But in case of vSphere 4.1/4.0 (If used), as this
feature is not there, the new default value (=> 8) have an impact in the
existing deployments. Action item for vSphere 4.1/4.0: Admin should
modify the global configuration setting "vmware.ports.per.dvportgroup"
from 8 to any number based on their environment because the proposal
default value of 8 would be very less without auto expand feature in
general. The current default value of 256 may not need immediate
modification after deployment, but 8 would be very less which means
admin need to update immediately after upgrade.

Signed-off-by: Rohit Yadav 

> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472246#comment-16472246
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd closed pull request #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/engine/schema/resources/META-INF/db/schema-41100to41110-cleanup.sql 
b/engine/schema/resources/META-INF/db/schema-41100to41110-cleanup.sql
index 704c71e659b..2c5855e1ce3 100644
--- a/engine/schema/resources/META-INF/db/schema-41100to41110-cleanup.sql
+++ b/engine/schema/resources/META-INF/db/schema-41100to41110-cleanup.sql
@@ -17,4 +17,6 @@
 
 --;
 -- Schema upgrade from 4.11.0.0 to 4.11.1.0
---;
\ No newline at end of file
+--;
+
+DELETE FROM `cloud`.`configuration` WHERE 
`name`='vmware.ports.per.dvportgroup';
diff --git 
a/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 
b/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
index 3cf0cd9..f586f393821 100644
--- 
a/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
+++ 
b/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
@@ -136,6 +136,8 @@
 private static final Logger s_logger = 
Logger.getLogger(VmwareManagerImpl.class);
 
 private static final long SECONDS_PER_MINUTE = 60;
+private static final int DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x = 256;
+private static final int DEFAULT_PORTS_PER_DV_PORT_GROUP = 8;
 
 private int _timeout;
 
@@ -194,7 +196,7 @@
 private StorageLayer _storage;
 private final String _privateNetworkVSwitchName = "vSwitch0";
 
-private int _portsPerDvPortGroup = 256;
+private int _portsPerDvPortGroup = DEFAULT_PORTS_PER_DV_PORT_GROUP;
 private boolean _fullCloneFlag;
 private boolean _instanceNameFlag;
 private String _serviceConsoleName;
@@ -279,8 +281,6 @@ public boolean configure(String name, Map 
params) throws Configu
 _instanceNameFlag = Boolean.parseBoolean(value);
 }
 
-_portsPerDvPortGroup = 
NumbersUtil.parseInt(_configDao.getValue(Config.VmwarePortsPerDVPortGroup.key()),
 _portsPerDvPortGroup);
-
 _serviceConsoleName = 
_configDao.getValue(Config.VmwareServiceConsole.key());
 if (_serviceConsoleName == null) {
 _serviceConsoleName = "Service Console";
@@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
+if (version != null && (version.equals("4.0") || 
version.equals("4.1")) && _portsPerDvPortGroup < 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x) {
+portsPerDvPortGroup = 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x;
+}
+}
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, null, 18,
-vsType, _portsPerDvPortGroup, null, false, 
BroadcastDomainType.Vlan, null, null);
+vsType, portsPerDvPortGroup, null, false, 
BroadcastDomainType.Vlan, null, null);
 }
 }
 
diff --git a/server/src/com/cloud/configuration/Config.java 
b/server/src/com/cloud/configuration/Config.java
index b2c44600a78..98bacf2b907 100644
--- a/server/src/com/cloud/configuration/Config.java
+++ b/server/src/com/cloud/configuration/Config.java
@@ -1139,14 +1139,6 @@
 "false",
 "Enable/Disable Nexus/Vmware dvSwitch in VMware environment",
 null),
-VmwarePortsPerDVPortGroup(
-"Network",
-ManagementServer.class,
-Integer.class,
-"vmware.ports.per.dvportgroup",
-"256",
-"Default number of ports per Vmware dvPortGroup in VMware 
environment",
-null),
 VmwareCreateFullClone(
 "Advanced",
 ManagementServer.class,
diff --git 
a/vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java 
b/vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java
index bab697aaafc..ecfa8ee2ca4 100644
---

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472244#comment-16472244
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388419620
 
 
   Manually tested, also verified on trillian env. Based on review and trillian 
tests results (including incoming/2nd run), merging this. 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471814#comment-16471814
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388346423
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-65) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471813#comment-16471813
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388346276
 
 
   @blueorangutan test centos7 vmware-65
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471792#comment-16471792
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388342619
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2048


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471760#comment-16471760
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388336034
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471759#comment-16471759
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388335948
 
 
   I found an issue with upgrade/backward compatibility, the new minor fix is 
that we don't force dvs portgroup number on existing switches, but only when 
creating new switch. Let's test this. /cc @PaulAngus 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471625#comment-16471625
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388291054
 
 
   Note: While I sent the PR, I'll give my LGTM as the changes are not authored 
by me.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471563#comment-16471563
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388282423
 
 
   Test LGTM. Are you lgtm on this @rafaelweingartner ?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471552#comment-16471552
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on a change in pull request #2634: CLOUDSTACK-9184: Fixes #2631 
VMware dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#discussion_r187535217
 
 

 ##
 File path: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 ##
 @@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
 
 Review comment:
   LGTM


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471240#comment-16471240
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388205878
 
 
   Trillian test result (tid-2653)
   Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 45122 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2634-t2653-vmware-65.zip
   Intermitten failure detected: /marvin/tests/smoke/test_deploy_vm_iso.py
   Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_02_cancel_host_maintenace_with_migration_jobs | `Error` | 2.32 | 
test_host_maintenance.py
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470645#comment-16470645
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


sureshanaparti commented on a change in pull request #2634: CLOUDSTACK-9184: 
Fixes #2631 VMware dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#discussion_r187382206
 
 

 ##
 File path: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 ##
 @@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
+if (version != null && (version.equals("4.0") || 
version.equals("4.1")) && _portsPerDvPortGroup < 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x) {
 
 Review comment:
   @rafaelweingartner Yes. For these versions, the default ports which is 256 
shouldn't change, for the backward compatibility. The below details can be 
documented in the upgrade details.
   
   `In case of vSphere 4.1/4.0 (If used), as this feature is not there, the new 
default value (=> 8) have an impact in the existing deployments. Action item 
for vSphere 4.1/4.0: Admin should modify the global configuration setting 
"vmware.ports.per.dvportgroup" from 8 to any number based on their environment 
because the proposal default value of 8 would be very less without auto expand 
feature in general. The current default value of 256 may not need immediate 
modification after deployment, but 8 would be very less which means admin need 
to update immediately after upgrade.`


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470635#comment-16470635
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


sureshanaparti commented on a change in pull request #2634: CLOUDSTACK-9184: 
Fixes #2631 VMware dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#discussion_r187382206
 
 

 ##
 File path: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 ##
 @@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
+if (version != null && (version.equals("4.0") || 
version.equals("4.1")) && _portsPerDvPortGroup < 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x) {
 
 Review comment:
   @rafaelweingartner Yes. For these versions, the default ports which is 256 
shouldn't change, for the backward compatibility. 
   
   `In case of vSphere 4.1/4.0 (If used), as this feature is not there, the new 
default value (=> 8) have an impact in the existing deployments. Action item 
for vSphere 4.1/4.0: Admin should modify the global configuration setting 
"vmware.ports.per.dvportgroup" from 8 to any number based on their environment 
because the proposal default value of 8 would be very less without auto expand 
feature in general. The current default value of 256 may not need immediate 
modification after deployment, but 8 would be very less which means admin need 
to update immediately after upgrade.`


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470618#comment-16470618
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


sureshanaparti commented on a change in pull request #2634: CLOUDSTACK-9184: 
Fixes #2631 VMware dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#discussion_r187379525
 
 

 ##
 File path: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 ##
 @@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
 
 Review comment:
   @rafaelweingartner No VMware ESXi/ESX hosts with these release versions. 
Take a look at the versions in the article 
https://kb.vmware.com/s/article/2143832.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470612#comment-16470612
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


sureshanaparti commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware 
dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388100897
 
 
   @rhtyd No comments. Thanks for taking this up!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470362#comment-16470362
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rafaelweingartner commented on a change in pull request #2634: CLOUDSTACK-9184: 
Fixes #2631 VMware dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#discussion_r187322162
 
 

 ##
 File path: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 ##
 @@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
 
 Review comment:
   Are the versions fixed? I mean, can't we have `4.2`, `4.3`, and so on.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470363#comment-16470363
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rafaelweingartner commented on a change in pull request #2634: CLOUDSTACK-9184: 
Fixes #2631 VMware dvs portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#discussion_r187320904
 
 

 ##
 File path: 
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 ##
 @@ -394,8 +394,16 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null, 
null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
+if (version != null && (version.equals("4.0") || 
version.equals("4.1")) && _portsPerDvPortGroup < 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x) {
 
 Review comment:
   do you need that second condition there `_portsPerDvPortGroup < 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x`?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470307#comment-16470307
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388034846
 
 
   @sureshanaparti I've concluded a standalone and upgrade test (upgrade from 
4.6) and conclude no regressions. Do you have any comments on the PR?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread Rohit Yadav (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470150#comment-16470150
 ] 

Rohit Yadav commented on CLOUDSTACK-9184:
-

Suresh - the reason for closing the old PR was that my requests for rebasing 
were ignored for months, the issue was recently reported as blocker so I opened 
a new PR rebasing your changes. If you need to make further improvements, you 
can push changes to the new PR, no point closing the new PR and opening the old 
PR when the work of rebasing is already done.


I'm in the meanwhile testing it against 4.11 including doing an upgrade related 
tests based on the reported blocker issue:

https://github.com/apache/cloudstack/issues/2631


- Rohit







> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470142#comment-16470142
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388003574
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-65) has been 
kicked to run smoke tests


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470141#comment-16470141
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-388003370
 
 
   @blueorangutan test centos7 vmware-65


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470140#comment-16470140
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #1253: CLOUDSTACK-9184: [VMware] 
vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 
onwards
URL: https://github.com/apache/cloudstack/pull/1253#issuecomment-388003293
 
 
   @sureshanaparti I've moved the changes to this new PR against 4.11: 
https://github.com/apache/cloudstack/pull/2634#issuecomment-387994777
   Perhaps you can share how you tested it, help with testing in general.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread Suresh Anaparti (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470123#comment-16470123
 ] 

Suresh Anaparti commented on CLOUDSTACK-9184:
-

Hi Rohit,

I’ll fix the PR# 1253 with the changes required if any. Can you please reopen 
that?  I don’t see any extra changes in the PR# 2634, other than rebasing.

Thanks,
Suresh

On 10/05/18, 1:48 PM, "Rohit Yadav (JIRA)"  wrote:


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohit Yadav closed CLOUDSTACK-9184.
---
Resolution: Fixed

> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
vCenter 5.0 onwards
> 
---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
setting the number of ports per dvportgroup of Distributed Virtual Switch (DVS) 
and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
dynamically from ESX 5.0 release. So, even if we set this global setting, auto 
expand will take effect and the value configured at cloudstack is not useful 
anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470105#comment-16470105
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


sureshanaparti commented on issue #1253: CLOUDSTACK-9184: [VMware] 
vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 
onwards
URL: https://github.com/apache/cloudstack/pull/1253#issuecomment-387996149
 
 
   @PaulAngus , @rhtyd  I'll continue work on the changes required if any, on 
this.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470095#comment-16470095
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-387994777
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2040


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470062#comment-16470062
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


blueorangutan commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-387987251
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470060#comment-16470060
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634#issuecomment-387987066
 
 
   @blueorangutan package


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470059#comment-16470059
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd opened a new pull request #2634: CLOUDSTACK-9184: Fixes #2631 VMware dvs 
portgroup autogrowth
URL: https://github.com/apache/cloudstack/pull/2634
 
 
   This deprecates the vmware.ports.per.dvportgroup global setting.
   
   The vSphere Auto Expand feature (introduced in vSphere 5.0) will take
   care of dynamically increasing/decreasing the dvPorts when running out
   of distributed ports . But in case of vSphere 4.1/4.0 (If used), as this
   feature is not there, the new default value (=> 8) have an impact in the
   existing deployments. Action item for vSphere 4.1/4.0: Admin should
   modify the global configuration setting "vmware.ports.per.dvportgroup"
   from 8 to any number based on their environment because the proposal
   default value of 8 would be very less without auto expand feature in
   general. The current default value of 256 may not need immediate
   modification after deployment, but 8 would be very less which means
   admin need to update immediately after upgrade.
   
   This continues and take-over from PR 
https://github.com/apache/cloudstack/pull/1253
   
   ## Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ## GitHub Issue/PRs
   
   
   
   
   
   
   ## Screenshots (if appropriate):
   
   ## How Has This Been Tested?
   
   
   
   
   
   ## Checklist:
   
   
   - [ ] I have read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md)
 document.
   - [ ] My code follows the code style of this project.
   - [ ] My change requires a change to the documentation.
   - [ ] I have updated the documentation accordingly.
   Testing
   - [ ] I have added tests to cover my changes.
   - [ ] All relevant new and existing integration tests have passed.
   - [ ] A full integration testsuite with all test that can run on my 
environment has passed.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470055#comment-16470055
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd closed pull request #1253: CLOUDSTACK-9184: [VMware] 
vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 
onwards
URL: https://github.com/apache/cloudstack/pull/1253
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 
b/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
index b0f87af648d..bb451ceb392 100644
--- 
a/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
+++ 
b/plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
@@ -134,6 +134,10 @@
 private static final long SECONDS_PER_MINUTE = 60;
 private static final int STARTUP_DELAY = 6; // 60 
seconds
 private static final long DEFAULT_HOST_SCAN_INTERVAL = 60; // 
every 10 minutes
+
+private static final int DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x = 256;
+private static final int DEFAULT_PORTS_PER_DV_PORT_GROUP = 8;
+
 private long _hostScanInterval = DEFAULT_HOST_SCAN_INTERVAL;
 private int _timeout;
 
@@ -180,7 +184,7 @@
 private StorageLayer _storage;
 private final String _privateNetworkVSwitchName = "vSwitch0";
 
-private int _portsPerDvPortGroup = 256;
+private int _portsPerDvPortGroup = DEFAULT_PORTS_PER_DV_PORT_GROUP;
 private boolean _fullCloneFlag;
 private boolean _instanceNameFlag;
 private String _serviceConsoleName;
@@ -267,8 +271,6 @@ public boolean configure(String name, Map 
params) throws Configu
 _instanceNameFlag = Boolean.parseBoolean(value);
 }
 
-_portsPerDvPortGroup = 
NumbersUtil.parseInt(_configDao.getValue(Config.VmwarePortsPerDVPortGroup.key()),
 _portsPerDvPortGroup);
-
 _serviceConsoleName = 
_configDao.getValue(Config.VmwareServiceConsole.key());
 if (_serviceConsoleName == null) {
 _serviceConsoleName = "Service Console";
@@ -387,8 +389,17 @@ private void prepareHost(HostMO hostMo, String 
privateTrafficLabel) throws Excep
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, 18, false, BroadcastDomainType.Vlan, null);
 }
 else {
+int portsPerDvPortGroup = _portsPerDvPortGroup;
+AboutInfo about = hostMo.getHostAboutInfo();
+if (about != null) {
+String version = about.getApiVersion();
+if (version != null && (version.equals("4.0") || 
version.equals("4.1")) && _portsPerDvPortGroup < 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x) {
+portsPerDvPortGroup = 
DEFAULT_PORTS_PER_DV_PORT_GROUP_VSPHERE4_x;
+}
+}
+
 HypervisorHostHelper.prepareNetwork(vSwitchName, "cloud.private", 
hostMo, vlanId, null, null, null, 18,
-vsType, _portsPerDvPortGroup, null, false, 
BroadcastDomainType.Vlan, null);
+vsType, portsPerDvPortGroup, null, false, 
BroadcastDomainType.Vlan, null);
 }
 }
 
diff --git a/server/src/com/cloud/configuration/Config.java 
b/server/src/com/cloud/configuration/Config.java
index 551c61ea2e4..e9ef4432f75 100644
--- a/server/src/com/cloud/configuration/Config.java
+++ b/server/src/com/cloud/configuration/Config.java
@@ -1135,14 +1135,6 @@
 "false",
 "Enable/Disable Nexus/Vmware dvSwitch in VMware environment",
 null),
-VmwarePortsPerDVPortGroup(
-"Network",
-ManagementServer.class,
-Integer.class,
-"vmware.ports.per.dvportgroup",
-"256",
-"Default number of ports per Vmware dvPortGroup in VMware 
environment",
-null),
 VmwareCreateFullClone(
 "Advanced",
 ManagementServer.class,
diff --git a/setup/db/db/schema-4930to41000-cleanup.sql 
b/setup/db/db/schema-4930to41000-cleanup.sql
index 986dcdfe7da..b9b853e34f2 100644
--- a/setup/db/db/schema-4930to41000-cleanup.sql
+++ b/setup/db/db/schema-4930to41000-cleanup.sql
@@ -21,4 +21,6 @@
 
 DELETE FROM `cloud`.`configuration` WHERE 
name='consoleproxy.loadscan.interval';
 
+DELETE FROM `cloud`.`configuration` WHERE 
`name`='vmware.ports.per.dvportgroup';
+
 DELETE FROM `cloud`.`host_details` where name = 'vmName' and  value in (select 
name from `cloud`.`vm_instance`  where state = 'Expunging' and

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-10 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470054#comment-16470054
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #1253: CLOUDSTACK-9184: [VMware] 
vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 
onwards
URL: https://github.com/apache/cloudstack/pull/1253#issuecomment-387985818
 
 
   Closing this, will send a new PR taking over this issue.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2018-05-08 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467213#comment-16467213
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


PaulAngus commented on issue #1253: CLOUDSTACK-9184: [VMware] 
vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 
onwards
URL: https://github.com/apache/cloudstack/pull/1253#issuecomment-387360970
 
 
   There is an issue with existing environments, which may be using 
dvsportgroups.  If portgroup has more than (say) 8 ports in use already then a 
error such as:
   `Cannot set number of ports to 10 because at least 11 out of 18 ports are 
still in use`
   will be thrown when creating a VM on said switch and the VM will fail to be 
deployed.
   Setting ALL dvsportgroups to use a sufficiently high number will be 
expensive in large environments.
   
   Code needs to set number of ports to slightly higher than the number of 
ports in use, on a per  portgroup basis.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>Priority: Major
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-12-17 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294380#comment-16294380
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


rhtyd commented on issue #1253: CLOUDSTACK-9184: [VMware] 
vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 
onwards
URL: https://github.com/apache/cloudstack/pull/1253#issuecomment-352289015
 
 
   @sureshanaparti ping, can you fix conflicts? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-03-13 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906913#comment-15906913
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@rhtyd @karuturi Could see vSphere 4.1 in the latest installation guide. 
Please note that this documentation needs to be updated at some point later.
> vSphere and vCenter, versions 4.1, 5.0, 5.1 or 5.5.
> VMware vCenter Standard Edition 4.1, 5.0, 5.1 or 5.5 must be installed 
and available to manage the vSphere hosts.
> CloudStack requires VMware vSphere 4.1, 5.0, 5.1 or 5.5. VMware vSphere 
4.0 is not supported.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-03-12 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906865#comment-15906865
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@rhtyd @karuturi Is this documented in any of the earlier release notes. 
Can we remove the config param "vmware.ports.per.dvportgroup" if vSphere 4.x is 
not supported?


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-03-12 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906779#comment-15906779
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@sureshanaparti Why don't we just remove Config for this setting and leave 
default to be 8? 
Your logic to handle v4.1 will take care of old installations.
As of May 2016 Vsphere 4.X is  not longer supported so we technically 
shouldn't even worry about it. 
@rhtyd @karuturi At some point we should remove vSphere 4.1 from a list of 
supported hypervisors.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-03-12 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906754#comment-15906754
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@nvazquez @serg38 Please review the code changes.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889578#comment-15889578
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
Packaging result: ✔centos6 ✔centos7 ✖debian. JID-546


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889544#comment-15889544
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@sureshanaparti sure
@blueorangutan package


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15889545#comment-15889545
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you 
posted as I make progress.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887965#comment-15887965
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@rhtyd @borisroman can you kick off vmware tests?


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887962#comment-15887962
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@sateesh-chodapuneedi These two test failures are due to the ssh failure to 
the router VM, are not related to this PR changes.

_test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failed_

> Failed to SSH into the Virtual Machine: SSH connection has Failed. Waited 
150s. Error is SSH Connection Failed
> === TestName: test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | 
Status : FAILED ===
> 
"/automation/virtenv/00-16-3e-17-43-25/396/test/integration/smoke/test_routers_network_ops.py",
 line 338, in test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true\n
result = check_router_command(virtual_machine, nat_rule.ipaddress, ssh_command, 
check_string, self)\n', '  File 
"/automation/virtenv/00-16-3e-17-43-25/396/test/integration/smoke/test_routers_network_ops.py",
 line 64, in check_router_command\ntest_case.fail("Failed to SSH into the 
Virtual Machine: %s" % e)\n', '  File 
"/usr/local/lib/python2.7/unittest/case.py", line 412, in fail\nraise 
self.failureException(msg)\n', 'AssertionError: Failed to SSH into the Virtual 
Machine: SSH connection has Failed. Waited 150s. Error is SSH Connection 
Failed\n']


_test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failed_

> Failed to SSH into the Virtual Machine: SSH connection has Failed. Waited 
150s. Error is SSH Connection Failed
> === TestName: test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | 
Status : FAILED ===
> 
> 
"/automation/virtenv/00-16-3e-17-43-25/396/test/integration/smoke/test_routers_network_ops.py",
 line 502, in test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false\\n
result = check_router_command(virtual_machine, nat_rule.ipaddress, ssh_command, 
check_string, self)\\n\', \'  File 
"/automation/virtenv/00-16-3e-17-43-25/396/test/integration/smoke/test_routers_network_ops.py",
 line 64, in check_router_command\\ntest_case.fail("Failed to SSH into the 
Virtual Machine: %s" % e)\\n\', \'  File 
"/usr/local/lib/python2.7/unittest/case.py", line 412, in fail\\nraise 
self.failureException(msg)\\n\', \'AssertionError: Failed to SSH into the 
Virtual Machine: SSH connection has Failed. Waited 150s. Error is SSH 
Connection Failed\\n\']






> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887940#comment-15887940
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
Please ignore the above BVT test results from @cloudmonger. These tests 
were executed on xenserver instead of VMware.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-26 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15885020#comment-15885020
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sateesh-chodapuneedi commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@sureshanaparti Can you please investigate the two failures listed in 
results from @cloudmonger?


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-26 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884967#comment-15884967
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 396
 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 Failed

 * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false 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_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


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879342#comment-15879342
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
@rhtyd  Can you please run trillian tests for this PR?


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2017-02-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879338#comment-15879338
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
Moved the schema changes to 4920-41000 upgrade path.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2016-11-30 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15709912#comment-15709912
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1253
  
Addressed all the changes suggested and rebased. With vSphere 4.0/4.1, when 
the ports per dvportgroup is set to less than 256 (current default), then it is 
set to the default 256, else it takes the actual config value.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2016-05-28 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305245#comment-15305245
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user bvbharatk commented on the pull request:

https://github.com/apache/cloudstack/pull/1253#issuecomment-98365
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 71
 Hypervisor xenserver
 NetworkType Advanced
 Passed=73
 Failed=0
 Skipped=3

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**

**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_vpc_vpn.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.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


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2016-05-02 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266442#comment-15266442
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user rhtyd commented on the pull request:

https://github.com/apache/cloudstack/pull/1253#issuecomment-216210337
  
@sureshanaparti please rebase against latest master, move the schema 
changes to 481-490 upgrade path

tag:vmware-pickup


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2016-04-07 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231416#comment-15231416
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user bvbharatk commented on the pull request:

https://github.com/apache/cloudstack/pull/1253#issuecomment-207147802
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 161
 Hypervisor xenserver
 NetworkType Advanced
 Passed=110
 Failed=18
 Skipped=4

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_vpc_router_nics.py

 * test_02_VPC_default_routes Failed

* test_vpc_redundant.py

 * test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL Failed

 * test_02_redundant_VPC_default_routes Failed

* test_privategw_acl.py

 * test_01_vpc_privategw_acl Failed

* test_scale_vm.py

 * ContextSuite context=TestScaleVm>:setup Failing since 2 runs

* test_router_dhcphosts.py

 * test_router_dhcphosts Failed

 * ContextSuite context=TestRouterDHCPHosts>:teardown Failed

* test_quota.py

 * test_01_quota Failed

 * test_02_quota Failed

 * test_03_quota Failed

 * test_04_quota Failed

 * test_05_quota Failed

 * test_06_quota Failed

 * test_07_quota Failed

* test_password_server.py

 * test_isolate_network_password_server Failed

* test_routers_network_ops.py

 * test_01_isolate_network_FW_PF_default_routes_egress_true Failed

 * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failed

 * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failed


**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_deploy_vgpu_enabled_vm
test_06_copy_template
test_06_copy_iso

**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_guest_vlan_range.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_non_contigiousvlan.py
test_deploy_vm_iso.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_ssvm.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


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2016-03-06 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182254#comment-15182254
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


Github user GabrielBrascher commented on the pull request:

https://github.com/apache/cloudstack/pull/1253#issuecomment-192951641
  
@sureshanaparti Although it might be a bit tricky, I believe that the ideal 
solution would be to check for the hypervisor version; if it is 4.1/4.0 then 
the default value of 8 is changed to 256 (or any recommended amount for the 
given version). This way does not rely on admin to manually configure it (the 
idea would be to consider the global configuration if the admin set it, would 
just change a default value).

I checked and maybe a method for check the hypervisor version and set the 
**_portsPerDvPortGroup** could be called by 
**com.cloud.hypervisor.vmware.manager.VmwareManagerImpl.addHostToPodCluster(VmwareContext,
 long, Long, Long, String)**. This method would search a host using the 
clusterId (**com.cloud.host.dao.HostDaoImpl.findByClusterId(Long)**); with the 
given HostVO it verifies the hypervisor version 
(**com.cloud.host.HostVO.getHypervisorVersion()**) to set the default value 
according this version.

Thanks.


> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2015-12-16 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061459#comment-15061459
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9184:


GitHub user sureshanaparti opened a pull request:

https://github.com/apache/cloudstack/pull/1253

CLOUDSTACK-9184: [VMware] vmware.ports.per.dvportgroup global setting is 
not useful from vCenter 5.0 onwards

Modify the default value of this setting, which is currently 256, by 
decreasing it to 8 because even a dvportgroup with autoexpand feature enabled 
there exists an initial number of ports as starting point, which can be again 
configured through this configuration setting. But keeping this value 256 
doesn't make sense when auto expand feature is available. Keeping the starting 
number of dvports per dvportgroup to reasonably minimum would ensure optimal 
distribution across dvportgroups in dvSwitch.

The vSphere Auto Expand feature (introduced in vSphere 5.0) will take care 
of dynamically increasing/decreasing the dvPorts when running out of 
distributed ports . But in case of vSphere 4.1/4.0 (If used), as this feature 
is not there, the new default value (=> 8) have an impact in the existing 
deployments. Action item for vSphere 4.1/4.0: Admin should modify the global 
configuration setting "vmware.ports.per.dvportgroup" from 8 to any number based 
on their environment because the proposal default value of 8 would be very less 
without auto expand feature in general. The current default value of 256 may 
not need immediate modification after deployment, but 8 would be very less 
which means admin need to update immediately after upgrade.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sureshanaparti/cloudstack CLOUDSTACK-9184

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1253.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 #1253


commit 4e0cd09226ed1819f51ad018ec0020358d5c3e85
Author: Suresh Kumar Anaparti 
Date:   2015-12-17T04:34:53Z

CLOUDSTACK-9184: [VMware] vmware.ports.per.dvportgroup global setting is 
not useful from vCenter 5.0 onwards

Fix: Modify the default value of this setting, which is currently 256, by 
decreasing it to 8 because even a dvportgroup with autoexpand feature enabled 
there exists an initial number of ports as starting point, which can be again 
configured through this configuration setting.




> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>Assignee: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards

2015-12-16 Thread Suresh Kumar Anaparti (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061426#comment-15061426
 ] 

Suresh Kumar Anaparti commented on CLOUDSTACK-9184:
---

>From VMware KB:

vSphere 5.0 has introduced a new advanced option for static port binding called 
Auto Expand. This port group property allows a port group to expand 
automatically by a small predefined margin whenever the port group is about to 
run out of ports.

With releases before the vSphere 5.0 version, users who choose static port 
binding in their deployment must
manually manage how many distributed ports are required per distributed port 
group. To reduce the
management effort involved with the static port-binding option, VMware 
introduced the Auto Expand feature
as part of the vSphere 5.0 release. This capability automatically increases the 
distributed port limits of the
distributed port group when it runs out of distributed ports. To enable this 
feature, users must employ the
vSphere API command or vSphere MOB, as described in VMware knowledge base 
article 1022312: 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US=displayKC=1022312.

In vSphere 5.1, when users choose static port binding, the Auto Expand feature 
is enabled by default. Users now
don’t have to worry about running out of distributed ports on distributed port 
groups or running a script on
distributed port groups to manually enable the Auto Expand feature.

Before vSphere 5.0 (vSphere 4.0,4.1,etc): No Auto Expand feature.
vSphere 5.0: Auto Expand is disabled by default.
vSphere 5.1 and 5.5: the Auto Expand feature is enabled by default.

> [VMware] vmware.ports.per.dvportgroup global setting is not useful from 
> vCenter 5.0 onwards
> ---
>
> Key: CLOUDSTACK-9184
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, VMware
>Affects Versions: 4.5.2
>Reporter: Suresh Kumar Anaparti
>
> CloudStack has a global config paramter vmware.ports.per.dvportgroup for 
> setting the number of ports per dvportgroup of Distributed Virtual Switch 
> (DVS) and this takes effect when the zone is created.
> Auto expand/shrink features adjusts the ports per dvportgroup value 
> dynamically from ESX 5.0 release. So, even if we set this global setting, 
> auto expand will take effect and the value configured at cloudstack is not 
> useful anymore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

61 matches

Mail list logo