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