[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 <[email protected]>
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)

Reply via email to