cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9184) [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter 5.0 onwards
Date Mon, 13 Mar 2017 02:15:04 GMT

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

Mime
View raw message