Bug 1125099 - [RFE][glance]: Proposal for using Launcher/ProcessLauncher for launching services
Summary: [RFE][glance]: Proposal for using Launcher/ProcessLauncher for launching serv...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/glan...
Whiteboard: upstream_milestone_none upstream_defi...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-31 04:07 UTC by RHOS Integration
Modified: 2015-03-19 17:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2015-03-19 17:09:19 UTC

Attachments (Terms of Use)

Description RHOS Integration 2014-07-31 04:07:03 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/use-common-service-framework.


Currently other openstack projects like nova, cinder, keystone etc. are using oslo-incubator service framework to launch the services. Similar to these projects glance should also use this service framework to launch the services.

As of now when SIGHUP signal is sent to glance-api parent process, it calls the callback handler and then throws OSError. The OSError is thrown because os.wait system call was interrupted due to SIGHUP callback handler. As a result of this parent process closes the server socket. All the child processes also gets terminated without completing existing api requests because the server socket is already closed and the glance service fails to restart.

Ideally when SIGHUP signal is received by the glance-api process, it should process all the pending requests and then restart the glance-api service.

If oslo-incubator's common service framework is used in glance then it will handle service restart on ‘SIGHUP’ signal properly.

Specification URL (additional information):


Note You need to log in before you can comment on or make changes to this bug.