[
https://issues.apache.org/jira/browse/CLOUDSTACK-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907856#comment-15907856
]
ASF subversion and git services commented on CLOUDSTACK-9698:
-------------------------------------------------------------
Commit 09802e0f3c7a488545248e03431b9741076b1942 in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=09802e0 ]
Merge pull request #1861 from sateesh-chodapuneedi/pr-cloudstack-9698
CLOUDSTACK-9698 [VMware] Make hardcorded wait timeout for NIC adapter hotplug
as configurableJira
===
CLOUDSTACK-9698 [VMware] Make hardcoded wait timeout for NIC adapter hotplug as
configurable
Description
=========
Currently ACS waits for 15 seconds (hard coded) for hot-plugged NIC in VR
running on VMware to get detected by guest OS.
The time taken to detect hot plugged NIC in guest OS depends on type of VMware
NIC adapter like (E1000, VMXNET3, E1000e etc.)
and guest OS itself. In uncommon scenarios the NIC detection may take longer
time than 15 seconds,
in such cases NIC hotplug would be treated as failure which results in VPC tier
configuration failure.
Alternatively making the wait timeout for NIC adapter hotplug as configurable
will be helpful for admins in such scenarios. This is specific to VR running
over VMware hypervisor.
Also in future if VMware introduces new NIC adapter types which may take time
to get detected by guest OS, it is good to have flexibility of
configuring the wait timeout as fallback mechanism in such scenarios.
Fix
===
Introduce new configuration parameter (via ConfigKey)
"vmware.nic.hotplug.wait.timeout" which is "Wait timeout (milli seconds) for
hot plugged NIC of VM to be detected by guest OS." as fallback instead of hard
coded timeout, to ensure flexibility for admins given the listed scenarios
above.
Signed-off-by: Sateesh Chodapuneedi <sateesh.chodapune...@accelerite.com>
* pr/1861:
CLOUDSTACK-9698 Make the wait timeout for NIC adapter hotplug as configurable
Signed-off-by: Rajani Karuturi <rajani.karut...@accelerite.com>
> Make the wait timeout for NIC adapter hotplug as configurable
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-9698
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9698
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.9.0.1
> Environment: ACS 4.9 branch commit
> a0e36b73aebe43bfe6bec3ef8f53e8cb99ecbc32
> vSphere 5.5
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
> Fix For: 4.9.1.0
>
>
> Currently ACS waits for 15 seconds (*hard coded*) for hot-plugged NIC in VR
> to get detected by guest OS. The time taken to detect hot plugged NIC in
> guest OS depends on type of NIC adapter like (E1000, VMXNET3, E1000e etc.)
> and guest OS itself. In uncommon scenarios the NIC detection may take longer
> time than 15 seconds, in such cases NIC hotplug would be treated as failure
> which results in VPC tier configuration failure. Making the wait timeout for
> NIC adapter hotplug as configurable will be helpful for admins in such
> scenarios.
> Also in future if VMware introduces new NIC adapter types which may take time
> to get detected by guest OS, it is good to have flexibility of configuring
> the wait timeout.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
