Merge "Do not apply NoExecute taint to hosts"
This commit is contained in:
commit
fd512f798e
|
@ -1419,20 +1419,17 @@ class NFVIInfrastructureAPI(nfvi.api.v1.NFVIInfrastructureAPI):
|
||||||
raise
|
raise
|
||||||
|
|
||||||
if self._host_supports_kubernetes(host_personality):
|
if self._host_supports_kubernetes(host_personality):
|
||||||
if 'controller' in host_personality and \
|
if True:
|
||||||
'compute' in host_personality:
|
# For now, we do not want to apply the NoExecute taint.
|
||||||
# This is an AIO host (either simplex or duplex). For now,
|
# When the VIM detects that a service is failed on a host,
|
||||||
# we do not want to apply the NoExecute taint. When
|
# it goes through a disable/enable cycle. This would cause
|
||||||
# the host reboots (e.g. on a lock/unlock), the VIM will
|
# the NoExecute taint to be applied/removed which causes
|
||||||
# not initialize if it cannot register with rabbitmq
|
# most pods to be stopped/started. If the pods don't come
|
||||||
# (which is running in a pod). But the VIM must first
|
# back quickly enough the VIM will attempt another
|
||||||
# remove the NoExecute taint, before that pod will run.
|
# disable/enable, which can go on forever. For now,
|
||||||
# This is only necessary on AIO simplex hosts, but we have
|
# we will just avoid tainting hosts.
|
||||||
# no way to know whether the host is simplex or duplex
|
# TODO(bwensley): Rework when support for pure k8s hosts is
|
||||||
# in this plugin. Long term, this decision will be moved to
|
# added.
|
||||||
# the VIM, before invoking the plugin, once the plugins are
|
|
||||||
# refactored into separate enable/disable functions for
|
|
||||||
# nova, neutron, kubernetes, etc...
|
|
||||||
pass
|
pass
|
||||||
else:
|
else:
|
||||||
response['reason'] = 'failed to disable kubernetes services'
|
response['reason'] = 'failed to disable kubernetes services'
|
||||||
|
|
Loading…
Reference in New Issue