yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #78699
[Bug 1831195] [NEW] disable one compute service will prevent scheduler to choose the hypervisor the compute service manange
Public bug reported:
Description
===========
When one nova compute service manage multi hypervisors, disable the nova-compute service will prevent nova scheduler from choosing all the hypervisor it manages because the code in compute_filter.py :
service = host_state.service
if service['disabled']:
LOG.debug("%(host_state)s is disabled, reason: %(reason)s",
{'host_state': host_state,
'reason': service.get('disabled_reason')})
return False
and i think this is not reasonable.
One solution is to make each compute service manage only one
hypervisor, but this result more compute services.
Steps to reproduce
==================
Expected result
===============
operator can disable individual hypervisor
Actual result
=============
Disable one nova compute prevent nova scheduer choosing all the hypervisors it manages
Environment
===========
Logs & Configs
==============
** Affects: nova
Importance: Undecided
Status: New
** Tags: hypervisor nova-compute scheduler
** Tags added: hypervisor
** Tags added: nova-compute scheduler
** Description changed:
- When one nova compute service manage multi hypervisors, disable the
- nova-compute service will prevent nova scheduler from choosing all the
- hypervisor it manages because the code in compute_filter.py :
+ Description
+ ===========
+ When one nova compute service manage multi hypervisors, disable the nova-compute service
+ will prevent nova scheduler from choosing all the hypervisor it manages because the code
+ in compute_filter.py :
- service = host_state.service
- if service['disabled']:
- LOG.debug("%(host_state)s is disabled, reason: %(reason)s",
- {'host_state': host_state,
- 'reason': service.get('disabled_reason')})
- return False
+ service = host_state.service
+ if service['disabled']:
+ LOG.debug("%(host_state)s is disabled, reason: %(reason)s",
+ {'host_state': host_state,
+ 'reason': service.get('disabled_reason')})
+ return False
- and i think this is not reasonable.
+ and i think this is not reasonable.
- One solution is to make each compute service manage only one hypervisor,
- but this result more compute services.
+ One solution is to make each compute service manage only one hypervisor, but this result
+ more compute services.
+
+
+ Steps to reproduce
+ ==================
+
+ Expected result
+ ===============
+ operator can disable individual hypervisor
+
+ Actual result
+ =============
+ Disable one nova compute prevent nova scheduer choosing all the hypervisors it manages
+
+ Environment
+ ===========
+
+ Logs & Configs
+ ==============
** Description changed:
- Description
- ===========
- When one nova compute service manage multi hypervisors, disable the nova-compute service
- will prevent nova scheduler from choosing all the hypervisor it manages because the code
- in compute_filter.py :
+ Description
+ ===========
+ When one nova compute service manage multi hypervisors, disable the nova-compute service will prevent nova scheduler from choosing all the hypervisor it manages because the code in compute_filter.py :
- service = host_state.service
- if service['disabled']:
+ service = host_state.service
+ if service['disabled']:
LOG.debug("%(host_state)s is disabled, reason: %(reason)s",
{'host_state': host_state,
'reason': service.get('disabled_reason')})
- return False
+ return False
- and i think this is not reasonable.
+ and i think this is not reasonable.
- One solution is to make each compute service manage only one hypervisor, but this result
- more compute services.
-
+ One solution is to make each compute service manage only one
+ hypervisor, but this result more compute services.
- Steps to reproduce
- ==================
-
- Expected result
- ===============
- operator can disable individual hypervisor
+ Steps to reproduce
+ ==================
- Actual result
- =============
- Disable one nova compute prevent nova scheduer choosing all the hypervisors it manages
-
- Environment
- ===========
-
- Logs & Configs
- ==============
+ Expected result
+ ===============
+ operator can disable individual hypervisor
+
+ Actual result
+ =============
+ Disable one nova compute prevent nova scheduer choosing all the hypervisors it manages
+
+ Environment
+ ===========
+
+ Logs & Configs
+ ==============
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1831195
Title:
disable one compute service will prevent scheduler to choose the
hypervisor the compute service manange
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
When one nova compute service manage multi hypervisors, disable the nova-compute service will prevent nova scheduler from choosing all the hypervisor it manages because the code in compute_filter.py :
service = host_state.service
if service['disabled']:
LOG.debug("%(host_state)s is disabled, reason: %(reason)s",
{'host_state': host_state,
'reason': service.get('disabled_reason')})
return False
and i think this is not reasonable.
One solution is to make each compute service manage only one
hypervisor, but this result more compute services.
Steps to reproduce
==================
Expected result
===============
operator can disable individual hypervisor
Actual result
=============
Disable one nova compute prevent nova scheduer choosing all the hypervisors it manages
Environment
===========
Logs & Configs
==============
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1831195/+subscriptions
Follow ups