Follow up fixes for graceful shutdown spec

Code Issues Proposed changes

folow up fixes for the comments in
- https://review.opendev.org/c/openstack/nova-specs/+/969299
Change-Id: I82b95e020a89ead1956830ea95e857f717e2405b
Signed-off-by: Ghanshyam <gmaan@ghanshyammann.com>

This commit is contained in:

Ghanshyam

2025年12月04日 16:46:55 +00:00

parent 4e95c63b60

commit 925e8c88f3

1 changed files with 4 additions and 4 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

8
specs/2026.1/approved/nova-services-graceful-shutdown-part1.rst

View File

@@ -37,7 +37,7 @@ time it will stop the communication needed for the in-progress operations. For

example, if live migration is in progress, the source and destination compute

communicate (sync and async way) multiple times with each other. Once the RPC

server on the compute service is stopped, it cannot communicate with the other

compute and fail the live migration. It will lead the system as well as the

compute and fails the live migration. It will lead the system as well as the

instance to be in an unwanted or unrecoverable state

Use Cases

@@ -117,7 +117,7 @@ Analysis per services and the required proposed RPC design change:

Currently, nova.service.py->stop() calls stop() and wait() on RPC server.

Once RPC server is stopped, it will stop listening to any new messages.

But it will not impact anything on the other scheduler worker, and they

But it will not impact anything on the other scheduler workers, and they

continue listening to the same queue and process the request. If any of

the scheduler worker is stopped, then the other workers will process the

request.

@@ -140,7 +140,7 @@ Analysis per services and the required proposed RPC design change:

The Nova conductor binary is a stateless service that can spawn multiple

worker threads. Each instance of the Nova conductor has its own RPC server,

but all the Nova conductor instances will listen to the same RPC topic

and queue ``conductor``. This allows the conductor instance to ack as a

and queue ``conductor``. This allows the conductor instance to act as a

distributed worker pool such that stopping an individual conductor instance

will not impact the RPC communication for the pool of conductor instances,

allowing other available workers to process the request. Each cell has its

@@ -452,7 +452,7 @@ None

Feature Liaison

---------------

gmaan

None

Work Items

----------

Follow up fixes for graceful shutdown spec

8 specs/2026.1/approved/nova-services-graceful-shutdown-part1.rst Unescape Escape View File

8
specs/2026.1/approved/nova-services-graceful-shutdown-part1.rst

View File