cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-9698) Make the wait timeout for NIC adapter hotplug as configurable
Date Fri, 23 Dec 2016 13:03:58 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sateesh Chodapuneedi updated CLOUDSTACK-9698:
---------------------------------------------
    Description: 
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.

  was:Making the wait time for NIC adapter hotplug as configurable will be helpful for admins
so that ACS does not wait for for NIC adapter to be detected by guest OS, which ensures more
flexibility to customers. In future if VMware introduces new NIC adapter types which may take
time (like VMXNET3 in this case, which takes few more seconds than other NIC adapter types
like E1000) to get detected by guest OS, this fix will ensure flexibility of configuring the
wait time.


> 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.4#6332)

Mime
View raw message