From 6ad1ce4df50866862abba5aeabde53ef5ac37150 Mon Sep 17 00:00:00 2001 From: Jarrod Johnson Date: Thu, 11 Jul 2019 11:41:42 -0400 Subject: [PATCH] Back off concurrent retrieval. Some BMCs are incapable of handling concurrent requests. This is a blow particularly to high latency management given Redfish's tendency to require a lot of resource fetches, but we don't have a particularly discoverable strategy for knowing in advance whether an implementation is up for some optimization. --- .../confluent/plugins/hardwaremanagement/redfish.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/confluent_server/confluent/plugins/hardwaremanagement/redfish.py b/confluent_server/confluent/plugins/hardwaremanagement/redfish.py index 6c4189cd..e4d3d6d3 100644 --- a/confluent_server/confluent/plugins/hardwaremanagement/redfish.py +++ b/confluent_server/confluent/plugins/hardwaremanagement/redfish.py @@ -152,7 +152,9 @@ def sanitize_invdata(indata): class IpmiCommandWrapper(ipmicommand.Command): def __init__(self, node, cfm, **kwargs): - kwargs['pool'] = eventlet.greenpool.GreenPool(4) + #kwargs['pool'] = eventlet.greenpool.GreenPool(4) + #Some BMCs at the time of this writing crumble under the weight + #of 4 concurrent requests. For now give up on this optimization. self.cfm = cfm self.node = node self._inhealth = False