38cca9d905
Change If1e03c9343b8cc9c34bd51c2b4d25acdb21131ff made the os-services REST API only able to perform PUT actions on nova-compute services, since those are the only ones with host mappings in the API database. Attempting to enable or disable a nova-scheduler service, for example, will fail with a 404 error now. The enable_new_services config option is used to auto-disable newly registered services to test them out before bringing them into the pool of services for scheduling. This was really only intended, and only makes sense for, nova-compute services. Disabling scheduler, conductor, or API services does nothing functionally, and requires the operator to later enable those services just to make the GET /os-services output make sense. This change makes the enable_new_services config option only have an effect on auto-disabling new nova-compute services. All other services are ignored and will not be auto-disabled. The config option help text is updated to make this clear. Change-Id: Ie9cb44d3f87ba85420e2909170f4d207ec4bf717 Closes-Bug: #1697960
10 lines
437 B
YAML
10 lines
437 B
YAML
---
|
|
other:
|
|
- |
|
|
The ``[DEFAULT]/enable_new_services`` configuration option will now only be
|
|
used to auto-disable new nova-compute services. Other services like
|
|
nova-conductor, nova-scheduler and nova-osapi_compute will not be
|
|
auto-disabled since disabling them does nothing functionally, and starting
|
|
in Pike the ``PUT /os-services/enable`` REST API will not be able to find
|
|
non-compute services to enable them.
|