[
https://issues.apache.org/jira/browse/CLOUDSTACK-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Animesh Chaturvedi updated CLOUDSTACK-1766:
-------------------------------------------
These blockers and critical issues are resolved but not verified. Reporters of
these issues please verify the fixes and help close these issues
> VmWare DVS vmware.ports.per.dvportgroup setting not used
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-1766
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1766
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, VMware
> Affects Versions: 4.2.0
> Environment: 4.2 Master
> Reporter: ilya musayev
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Labels: CLOUDSTACK, DVS, VMWARE
> Fix For: 4.2.0
>
>
> 1) vmware.ports.per.dvportgroup setting is not read or used. In my case, i
> set it to 512, while it fails back to 256 - no matter what i tried.
> * The 512 value stays set in CloudStack, however in vmware dvs under
> portgroup number of ports, it does not change and uses default 256.
> I made a test and set a static variable of numPorts = 512 in
> vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java and
> it took the static entry without issues.
> Please double check this part.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
